Why change management is the key to Salesforce architecture

Online meetup of the Salesforce Architect Community Group Utrecht with Kid Jansen presenting on possible ways to approach Salesforce architecture that leverage change management to make the requirements better fit the features, capabilities and limitations of Salesforce.

Chapters:
1:56 - Problem Statement
6:13 - System of Systems Thinking
13:12 - Architecture Methodology Domains - TOGAF ADM
16:23 - Architectural Domains
21:40 - Architecture Layers
27:18 - Top-down approach to architecture
32:35 - The problems with a top-down approach to architecture
37:26 - Potential issues with the implementation when forcing the traditional architecture approach
40:47 - Why the bottom-up approach to architecture isn’t architecture
44:00 - Why Change Management is the key to a better approach to Salesforce architecture
1:05:58 - Potential challenges with business
1:15:10 - Q&A

------------------------------------------------------------------------------------------------------
Problem Statement

The traditional top-down approach to architecture does not fit well with Salesforce.

This is mostly because of the cloud, multi-tenant and XaaS characteristics of Salesforce:

- Because of the PaaS aspect the technology architecture is a given, providing constraints to higher domains of architecture

- The SaaS aspect means you get a lot of functionality out of the box, which to some extent can be configured and extended. These capabilities and features should be leveraged, not conflicted with

This means a traditional business-to-technology and top-down approach to architecture is likely to result in conflicts, often manifesting itself as an implementation that mostly satisfies functional requirements, but with a poor technical implementation quality that's not compliant with architectural principles and non-functional requirements.