Here at OpFocus, we reinforce industry best practices during every project. These best practices ensure that we provide a level of excellence to our clients that few other companies are able to. After sitting down with a few of our practice leads, I’ve compiled a list of best practices that are crucial to the success of our team. Watch for yourself to discover these insights!
– Act as a trusted advisor to the client.
– Communicate honestly and frequently.
– Listen to and learn from the client’, never delay or surprise the client
– Be positive and bring creative solutions to the table
– The client will appreciate your honesty
– It will build a sense of you being a part of the team
– If you haven’t built up that report with the client it’s only a matter of time until they find another consultant
– Building that trusted long term relationship is the only way to secure
– Be open and transparent with the client
– If you don’t know the answer, say so
– The client will appreciate the honesty
– Try to keep your teams lean and narrow
– If you bring in too large of a team it can cause the project to move very slowly
– Take the time to identify the key project resources that will be making decisions
– Get all the involved stakeholders involved in the project
– If the project includes many different departments, involve them all so everyone is on the same page and there are fewer surprises down the line
– If we can’t get all the departments involved in the process in some way, the project is doomed to fail
– There are very few silos of the platform in Salesforce
– Most changes will impact other areas of the platform
– Get buy-in from the key departments that might reasonably be impacted by that solution
– Get council from these departments early in the process, the eventual rollout will be a lot more successful
– Sometimes a client will say “I trust that you will build a solution that works, I don’t need to test it”
– Testing is a great way to confirm that the way you expected the system to work is the way it really should work
– We like to consider we considered everything but there is nothing like working with the system in a test environment
– Stakeholders should definitely be involved in the testing of the platform
– First and foremost, follow CPQ best practices
– CPQ allows you to do creative things but understanding when to use each solution is very valuable.
– Do what the tool is designed to do and work within its guardrails
– Understanding the needs and challenges of this business will lead you to a better solution for everyone.
– If you don’t follow CPQ best practices and you find yourself down the path of configurations, you may find the consequences of not following these best practices.
– This can be challenging to wind it back and try to stay on track with the project
– Clearly set expectations
– In the world of CPQ, it’s something new to a lot of people and they don’t know what they don’t know
– It’s oftentimes the first time they are seeing this type of project
– If you clearly layout expectations at the beginning, there will not be any surprises down the line.
– Be sure to include the correct stakeholder in the project from the very beginning
– We want to make sure we have representation from everyone that will be touching the system
– It is best to include them from the very beginning so we can understand all of their requirements
– This also makes every department feel like they have a stake in the project
Sign up for weekly OpFocus blog updates!