To Top
Tips For Gathering Requirements For Salesforce Projects

GATHERING REQUIREMENTS FOR SALESFORCE PROJECTS

Publish date:

GATHERING REQUIREMENTS FOR SALESFORCE PROJECTS

“You must always examine what’s working, evolve your ideas, and change the way you do things.”  ― Quote by Marc Benioff, Behind the Cloud: The Untold Story of How Salesforce.com Went from Idea to Billion-Dollar Company-and Revolutionized an Industry

As we all know the first step in any Salesforce deployment / execution is conversations between the Business Analysts, Salesforce Admins, Architects, and Consultants from the Salesforce partner company and the client team. This lays the foundation of the project to begin in the smoothest of manners and no surprises springing during the process. Otherwise, the team can be thrown off gear and the integrity of the org can be in doubt. As easy as gathering the requirements of the client company sounds simple, doing it well is a different thing all together. We have compiled some helpful tips for the Salesforce personnel when they open dialogues with a client. Let's read on.

1. Question and strengthen the company requirements. Posing vital questions to the client is a good way to test their assumptions as well as firm up their end business goals. The more you ask or cross check, the better for you. This to and fro will help the client team to think, reflect and articulate in a better manner. Articulation and clarity of thought / vision is what you should be looking for. If they aren't able to, well they need to further gain clarity.

2. Be clear on the time & other important aspects that will entail on the requirements or changes requested by the client team. it's always good to be upfront and transparent then to "grin and bear" it. Even if you don't have answers to their requirements immediately, get back to them preferably with alternatives. By respecting your clients and having open conversations as adults, they will understand the Salesforce journey better and be helpful to you and themselves.

3. Beware of doubting Thomas questions. During your conversations if words like "sometimes", "maybe", "occasionally" surface from their end, it's time to be alert. These exceptions can impact the process automation or development projects and lead to escalation of problems. Resolving these exceptions is vital for many reasons including save energy, finances and time.  Resolving these exceptions ambiguity will lead to refined processes.

4. The client should put together a project team that includes decision makers from all concerned departments. This way all discussions are holistic, and everyone is onboard with decisions taken. Noone is neglected or suffers.

Always keep in mind that Salesforce administrators or in any other role, you don't have to always be a "yes" person and please the clients all the time. Using the word "no' or suggesting alternatives will be your way of doing the client and your company a big favour. As in life, learn to say "no" professionally and come out a winner

About the Author

author
Mohit Sharma

Mohit is Practice Lead, 4x Certified Salesforce Consultant, Salesforce trainer, blogger, writer, and full-time husband. With over 8 years of experience implementing Salesforce, and an obsession for innovation, ready to tackle any new project that comes his way.

Leave a Comment

FEEDBACK