Salesforce Diaries

How Implementing Salesforce has Evolved Little bit about me I started my Salesforce career in 2009, working as a Graduate for Deloitte on a large Salesforce Customer Portal implementation for a media client in London. Having worked through multiple roles from developer through to Program Architect I have had a chance to see the growth and evolution of the Salesforce platform. In 2018 I obtained the elusive Salesforce Certified Technical Architect qualification, the topmost credential in the Salesforce ecosystem and am now the Head of Architecture for a global Salesforce Silver Consulting Partner, VRP Consulting, helping our enterprise clients innovate on the platform. In this article I will be talking about how the platform has evolved and how some of its newest features are transforming the way Salesforce is implemented. How things began Back in 2009, the declarative options were more limited and required the use of APEX code to deliver any form of cus

The Role of the Technical Architect In your standard Salesforce project, there are multiple roles involved: Business Analyst, Quality Assurance, Project Managers, Developers and the infamous Technical Architects. The success and cohesion of the team and steer of the project is heavily based on the quality of the Technical Architect involved. The architect plays a critical role throughout the lifecycle of the project from Presales through to Delivery & Handover, and it with their expertise that the project evolves. The TA must provide strong support for all members of the project team, and is the heartbeat of the project team as the delivery carries on. “The binding glue of a Project” The role of the Technical Architect is to have a deep understanding of the Salesforce platform, alongside supporting technologies, but also have a strong understanding of what the client is intending to do. I like to think of the Architect as “the binding glue of the project”, suppor