Read about our update schedules here.

Introduction

A Salesforce solution that is Easy delivers value fast. A solution well-architected to be Easy is intentional, automated, and engaging.

Intentional solutions deliver business value immediately and over time.
Automated solutions enable the business to get work done faster and at scale.
Engaging solutions delight users and drive adoption.

Creating architectures that are Easy can pose complex challenges for an architect. Given the flexibility of the Salesforce Platform and variety of automation tools available, implementation details may vary widely between individual Salesforce orgs. Easy architectures may require more intelligent (and difficult) trade-off analyses and conversations with your stakeholders. A solution design could be resilient and reliable to a programmer, but not simple for an org administrator to own or maintain. Such a solution wouldn’t be well-architected to be Easy.

To arrive at an Easy solution, you must understand business priorities deeply and accurately. You must understand your users, including their preferences, their needs, and the day-to-day realities of their work. You must also understand the skills (and skill gaps) in your delivery and maintenance teams. You will need to iterate through different tooling options and design patterns to arrive at a solution that is intentional in getting value to the business while being manageable for delivery and maintenance teams, automates work faster and at scale, and truly engages users.

The following sections provide more in-depth guidance for core considerations of an Easy solution architecture.

Easy Overview