Building Salesforce Well-Architected
In case you missed the preview we shared at TDX, Salesforce Well-Architected shows architects what healthy solutions look like and where to spend time. We’re working with experts across Salesforce and throughout the ecosystem to create prescriptive guidance, tools, and resources to make the work of building well-architected solutions clearer.
Along with building Salesforce Well-Architected, we’ve been putting it to use as we design and deliver our own infrastructure.
In this post, I want to take a look at what you can expect in the first release of Salesforce Well-Architected, and what you will see on our blog in the weeks to come.
Let’s start with what (and when) we’re releasing Well-Architected.
Our v1 release
We will release the first version (v1) of Salesforce Well-Architected on architect.salesforce.com in July, near the end of the month.
We’ll publish a fundamental framework for designing and roadmapping solutions that are Trusted, Easy & Adaptable. We’re organizing the framework along two dimensions: capabilities (what a healthy system should be and do) and behaviors (how a healthy system should act).
You can see a high-level outline here:
In our framework documentation, we’ll walk through prescriptive guidance and best practices, discuss patterns and anti-patterns, and provide ways to measure an org’s architectural maturity.
We will also release some self-guided assessments to help you evaluate solutions and understand where you could focus effort and maximize impact. Along with these assessments, we’ll be publishing resources and tools to help you with specific kinds of work, like templates for common types of roadmaps or for calculating the business impact & cost effectiveness of automations.
What’s coming in the weeks ahead?
Behind the scenes, we’ve been putting Salesforce Well-Architected to work. We’ve been designing, prioritizing and implementing a core technology infrastructure for ourselves. Some of what we’re learning has gone back into deepening our v1 tools and documentation.
Other parts of what we’ve learned and where we’ve gotten feedback from other architects led us to write two blog series: Lessons Learned from Salesforce Well-Architected and Slack for Architects. We’ll publish posts from these series in the weeks leading up to our July v1 launch — and continuing in the weeks after our launch.
Here’s a look at some of the posts in our Lessons Learned from Salesforce Well-Architected series:
- Streamline and Optimize Processes for Automation
- Identify Business Value as an Architect
- Simplify Your Data Model
- Applying well-architected to architect.salesforce.com
- The How & Why of Architecture Review Boards
- Using Pace Layered Architecture
- How to Drive Buy-In with Roadmaps
And what you’ll see in our Slack for Architects series:
- Using Slack as a Control Plane
- Using Slack for Async Collaboration and Work
- Using Slack to Drive Onboarding, Feedback and Awareness
- Applying well-architected to Slack
As we release posts in these series, we’ll update links in this overview. In the meantime, you can stay up-to-date with every post by following us here on Medium (if you haven’t already).
We’re looking forward to sharing our v1 release in July — and to publishing more about what we’ve learned along the way.
