Plan of how to best use Salesforce across your business factoring in these considerations:
- Organizational
- Business
- Technical
- Support
Outlines when a single-Org or multiple-Orgs should be used, and sets up standards to for change-management :
- The procedure when a business unit wants a new Salesforce solution
- An approach for consolidating or splitting existing Orgs
- Processes to keep consistency across orgs

Benefits	Challenges
Cross-business unit collaboration Shared solutions for common business processes Ability to share data where appropriate Unified reporting	Org complexity could become a barrier to progress - Slow down Innovation Time to market and innovation could be impacted when multiple teams roll out new functionality concurrently Greater potential of hitting org limits

Pros	Cons
Shared data Shared configuration & coding effort Standardized processes Cross-business collaboration Clear cost to the Enterprise Single login Single support model Centralized integration	Reduced delivery velocity Increased solution complexity: Particularly security, business rules, automation Heavier governance overhead Potential to hit technical limits Unclear cost to the business unit Change Management overhead Some loss of autonomy

Benefits	Challenges
Org-wide settings are easier to govern and manage & Reduced risk of exceeding org limits Simplified complexity, reduces testing burdens Improved time to market and freedom to innovate (autonomy) - Agility Security	Less reuse of configuration and code Inferior collaboration across business units Duplicated administration functions required

Pros	Cons
High autonomy Fast implementation speed Less business complexity Clear cost to the business unit Distinct leadership Distributed data Personalized and flexible	No consolidated view and reporting Duplication of efforts Org consolidation is complex Effort to share data Effort to reuse configuration & code Reduced cross-business collaboration Potential multiple logins Complex, possibly increased cost to the enterprise

Cultural
- Collaboration
- Level of autonomy
Business
- Level of shared processes and data
- Flexibility or ability to change
- Business Unit & customer segmentation
Technical
- Security Requirements
- Salesforce Limits
- Application Architecture
Support
- Salesforce Governance
- End-user Training
- Deployment

Challenges	Best Practices
Focus on technology: Many businesses want to define an org strategy and often start with the technology. However, the correct approach is to start with the business requirements. Culture: Many customers have different cultures within different business units and this causes significant political issues that you need to consider. Lack of Analysis: Before making any strategic decision, gather a detailed analysis of the business and cultural considerations that need to be carried out.	Focus on High Value Business Processes: Most business units have many different business processes, but when considering an org strategy, focus only on the most significant ones. Develop a Roadmap: Changing the current org architecture takes time. Minimize the business risks by using a step-by-step approach. Create a Governance Framework: To be successful in any Salesforce project, you’ll need a lightweight governance framework in place.

Challenges

Best Practices

Focus on technology:
Many businesses want to define an org strategy and often start with the technology. However, the correct approach is to start with the business requirements.
Culture:
Many customers have different cultures within different business units and this causes significant political issues that you need to consider.
Lack of Analysis:
Before making any strategic decision, gather a detailed analysis of the business and cultural considerations that need to be carried out.

Focus on High Value Business Processes:
Most business units have many different business processes, but when considering an org strategy, focus only on the most significant ones.
Develop a Roadmap: Changing the current org architecture takes time. Minimize the business risks by using a step-by-step approach.
Create a Governance Framework:
To be successful in any Salesforce project, you’ll need a lightweight governance framework in place.

UI:
- VisualForce pages
- Canvas
Application Logic:
- Apex Web Services
- Outbound Messaging
- Streaming API
- Platform Events
Data Layer:
- APIs(REST, SOAP, Bulk )
- Salesforce-to-Salesforce
- Salesforce Connect