Category: Salesforce

This question was recently discussed in an online forum recently. To answer it, let’s look a little closer at what it means to be a Salesforce professional.

As the recent series on Salesforce roles explored, titles are given to people doing a certain type of work.… Read the rest

The last two roles are pretty straight forward, so we’ll combine them into a single email.

These days, the Administrator (Admin) is more than someone that configures users, resets their password, and adds some fields. In some cases, they are a one person army.… Read the rest

Most of the roles described so far lean towards the technical side. Most of them require good communication skills, but as a Business Analyst (BA), those skills are core.

BAs are like the glue of the project. They keep everything connected, and know a little bit of everything.… Read the rest

The single person responsible for the development of Salesforce projects is the Development Lead (DL).

In this context, development doesn’t just mean apex classes and triggers. It includes Visualforce pages, Lightning Web Components, flows, managed packages, connected apps, and even configuration.… Read the rest

There are too many Salesforce clouds to be a master of all of them. When someone specializes in a single cloud or platform, and knows it in incredible detail, they are called a Subject Matter Expert (SME).

SMEs are important to have in a project when a very granular level of detail is needed.… Read the rest

On smaller Salesforce projects, the Lead Consultant (LC) is usually the same person as the Solution Architect (SA). On larger projects though, it makes sense to divide this role into two.

When both roles are involved, the SA focuses on researching solutions, doing proof of concepts, and supporting the LC, and the LC is the single person responsible for the overall solution.… Read the rest

Whenever data is involved in a Salesforce project, you’ll typically find a Data Architect (DA).

DAs are masters of data. They analyze it, process it, protect it, and make recommendations based on data requirements.

Additional responsibilities include

• Defining the high-level data approach around governance and deduplication processes
• Leading the strategy to define and align with architecture around data approach re: migration vs integration.

If you’re technical and talking to clients just isn’t your thing, consider the Technical Architect (TA) position.

TAs are responsible for the technical elements of the Salesforce platform. This requires strong technical knowledge, understanding concepts such as event-driven and data-driven architecture, and platform events.… Read the rest

If the Program Architect represents the football coach, then the Solution Architect (SA) represents the quarterback.

The SA is often found in the field, beside the other players, and calling the shots. They decide and are responsible for the solution, from a functional perspective.… Read the rest

One step down, from the Enterprise Architect, in terms of visibility, is the Program Architect (PA).

The main responsibility of the PA is the strategy of the entire program within Salesforce. A program is usually composed of one or more projects.… Read the rest

In the Salesforce ecosystem, the Enterprise Architect (EA) has the widest technical view. They see the complete end-to-end architecture, and are not limited to just the CRM.

This means they understand and are responsible for

• The purpose and high-level features of each system connected to Salesforce
• The types of integrations between systems
• Choosing tools and app used across systems

They are very technical, are able to discuss approaches with fellow architects, and ensure fellow architects are aligned.… Read the rest

In the realm of Salesforce, there are plenty of hats you can wear.

The responsibilities for some of these hats (or roles) are straightforward. Other roles have multiple names and meanings, and other-others overlap multiple roles (also considered to be a *really* big hat!).… Read the rest