How often have you been asked on transformational projects that who would be doing what? Especially when you have multiple types of Salesforce Architects. Various titles, you name it, like Chief Architect, Lead Architect, Platform Architect, Enterprise Architect, and the list goes on.
In this post, I aim to share my experience and point of view on the difference between the roles & responsibilities of Solution & Technical Architects concerning Salesforce implementation.
Instead of just writing a few bullets, I would explain it as a story, just like I did here.
Once upon a time in the bustling city of Alpharetta, a growing company named “Shivasoft” decided it was time to implement Salesforce as their new CRM system. They hired two well-known Salesforce gurus, Sarah, the Solution Architect, and Tony, the Technical Architect. They were ready to conquer the world of Shivasoft, one Salesforce configuration at a time.
However, upon their arrival, they realized that not only did the company have no idea what their roles and responsibilities were, but Sarah and Tony were also unsure how to divide their tasks. It was like a scene from a sitcom, as the company’s employees and the Salesforce gurus stumbled their way through the project, hoping to make sense of their roles.
As the project progressed, Sarah and Tony tried to take turns doing various tasks. One day, Sarah would be mapping out process flows, while Tony would be discussing page layouts, dynamic forms or quick actions. The next day, Tony would be elbow-deep in Apex code, while Sarah would attempt to make sense of security settings. The office turned into a playground of trial and error, much to the amusement of the employees.
Realizing that they needed to get a grip on their roles, Sarah and Tony organized a meeting to determine their responsibilities. After several hours of intense discussion and a whiteboard full of scribbles, they finally identified the 10 key differences between a Solution Architect and a Technical Architect.
- Solution Architects focus on understanding business requirements, while Technical Architects dive deep into technical details and system architecture.
- Solution Architects design the functional aspects of the system, ensuring that it meets the company’s goals and objectives, whereas Technical Architects concentrate on the system’s performance, security, and integration.
- Solution Architects create user stories, process flows, and wireframes to illustrate the proposed solution, while Technical Architects develop technical specifications, data models, and integration designs.
- Solution Architects align the project with industry best practices and Salesforce guidelines, while Technical Architects ensure that the solution follows technical best practices and the latest technologies.
- Solution Architects are responsible for stakeholder management and communication, whereas Technical Architects primarily interact with developers and other technical team members.
- Solution Architects oversee end-to-end solution delivery, ensuring it is scalable and maintainable, while Technical Architects focus on the system’s stability and reliability.
- Solution Architects evaluate and select Salesforce applications and third-party tools to meet business requirements, while Technical Architects assess the technical feasibility of these tools and their integration with the existing system.
- Solution Architects collaborate with business analysts and product owners to define functional requirements, while Technical Architects work with developers to translate these requirements into technical tasks.
- Solution Architects leads or guides user acceptance testing (UAT) and ensure that the solution meets end-user’s expectations, while Technical Architects are responsible for system testing, performance testing, and ensuring code quality.
- Solution Architects focus on change management and user adoption, while Technical Architects handle release management and deployment processes.
- Bonus – The solution Architect would review the solution built by the team to make sure they followed best practices of out of box capabilities, point & click-based approaches, and configurable capabilities like flows, reports, etc. however Technical Architect would review best practices, design patterns, and frameworks, etc. are followed correctly for Apex, LWC, Triggers.
With this newfound understanding, Sarah and Tony embraced their respective roles and worked together seamlessly, like two sides of the same coin. The Salesforce project, once a chaotic mess, turned into a well-coordinated symphony, making Shivasoft’s CRM system the talk of Alpharetta.
The story of Sarah and Tony teaches us the importance of understanding the differences between roles and responsibilities in any project. It shows that with clear communication, collaboration, and a bit of humor, any challenge can be overcome, and success can be achieved.
Feel free to share your point of view & feedback on this post. Also, don’t forget to check this article from Salesforce Ben to learn about other Architect’s roles & responsibilities.