Know Implementation Roles
Learning Objectives
After completing this unit, you’ll be able to:
- List the different roles for implementation success.
- Describe the three implementation models.
Meet the Team
Sending a rocket into space requires a team with all the right expertise. It’s no different for a solid implementation. You need the right people in position for a successful solution launch.
Let’s take a look at a typical implementation team.
Role
|
Role Owner
|
What They Do
|
|
---|---|---|---|
Customer
|
Partner
|
||
Business Executive Sponsor
|
✓
|
|
|
IT Executive Sponsor
|
✓
|
|
|
Client Subject Matter Experts (SMEs)
|
✓
|
|
|
Engagement Manager
|
|
✓
|
|
Project Manager
|
✓
|
✓
|
|
Solution Consultant
|
|
✓
|
|
Salesforce Admin
|
✓
|
|
|
Change Management Expert
|
✓
|
✓
|
|
Keep in mind, for smaller SMB projects, the team may consist of just one or two people playing multiple roles. The scope and complexity of the project determines which roles are fulfilled by the partner and which roles are fulfilled by you. The roles defined above are just a place to start.
And of course, at any point in time, your Salesforce account executive and our Customer Success Group (CSG) teams are here to support you.
Who Pilots the Ship?
The last thing to consider when selecting the right partner for blastoff is which implementation model fits you the best. There are three options to choose from:
- The partner does all of the implementation.
- The partner and you co-pilot the implementation.
- You do all of the implementation, with a partner’s guidance.
Let’s look at the pros and cons of each model.
The Partner Does All of the Implementation
In this model, you outsource most, if not all, of the project work to the partner.
Pros
|
Cons
|
Risks
|
---|---|---|
|
Higher out-of-pocket implementation cost
|
|
The potential risk: Do you have the resources to manage the solution after the implementation, or are you prepared to engage the partner to manage the solution going forward?
The Partner and You Co-Pilot the Implementation
In this model, you and the partner split the deliverables for joint development.
Pros
|
Cons
|
Risks
|
---|---|---|
|
|
If your team doesn’t understand the Salesforce platform, they may re-create the existing processes
|
The potential risk: You might experience project delays and increased cost if your team doesn’t understand what the Salesforce platform can do.
You Do All of the Implementation with a Partner’s Guidance
In this model, the partner takes on an advisory role. You own all the deliverables with a partner as your guide.
Pros
|
Cons
|
Risks
|
---|---|---|
|
Project may take longer to complete if there aren’t enough knowledgeable resources to do the work
|
|
The potential risk: If your in-house resources lack experience with and knowledge of business transformation and the Salesforce platform, you could end up with a set of requirements that simply re-create the same pain points, just on a different platform.
It’s critical to the success of the implementation to make sure your model is clear. Provide details in the proposal about who is doing what and who owns each deliverable. It’s just as important to outline what you’re not going to do. Leaving things undefined creates more uncertainty, and no one wants that to happen.
No matter which model you choose, you now know the importance of selecting the right partner, at the right time.