Protecting team boundaries on Salesforce projects.
by Jon Cline
I remember working on a project for about three months and just before our weekly demo on a Thursday, we were alerted that the prior stakeholder and VP had moved on and a new client team has been assembled to work with us. These things happen of course though once the demo was done the new VP called me directly and stated pending their final review, any undesired work would need to be marked as non-billable in order to continue the project.
Would you be tempted to give in to this request and how would you push back in a way that keeps this new stakeholder engaged?
Do you have the fact pattern and artifacts to build a case and politely push back toward justifying the prior investment?
Is your team ready to handle curveball requests from stakeholders and protect your team’s commitments?
Related Articles
Related
When Projects Go Awry: Lessons from Digital Transformation Failures
Summary: Digital transformation projects can fail for many reasons. When one project fails, it can cause a domino effect, impacting operations, stakeholder trust, finances, and company culture. Common reasons for project failure include unclear vision, poor...
No Salesforce interview yet? Here’s some help.
Summary: Job hunting can be tough, and this offers strategies to improve your chances of landing an interview. First, evaluate the business as a customer through their website, social media, and review sites, noting areas for improvement. Next, engage key staff via...
Showcase Your Maturity in Your Salesforce Interview: Go Beyond Technical Skills
Employers value emotional maturity in Salesforce professionals alongside technical skills. During interviews, highlight your ability to build strong relationships, navigate conflicts, and consider diverse perspectives. Showcase how you've supported team cohesion, gone...