The Customer is Always Right: Tips for Working Big on a Small Budget
24 October, 2018
My team was working on a big, high priority project for a customer who had paid in advance. There were multiple parties involved, including an integration partner responsible for installation and management of the software on customer site and the actual customer. I was originally given the project requirements from our integration partners. When I started analyzing the scope of the project, I realized that the project was slowly growing from a small project to a very large due to unclear requirements from customer and integration partner. It reached the point that it was clear that we would not be able to complete the project as assigned because the volume of work was too substantial. It simply did not seem feasible given the budget under which we were working. We directly contacted the customer and learned that there were absolutely no additional resources or money that can be allocated to the project.
I organized a workshop with the customer. At the start of the workshop, I reiterated that we needed to focus on the problems and the things they were trying to achieve. I let the customer drive the agenda in terms of what they wanted to do, without telling them that we didn't have a large enough budget. Soon enough, it was quite clear that what the customer was looking for and what we were already planning to do were actually well aligned. By the end of the meeting, I was able to draw a clear roadmap with a timeline so everybody had a clear understanding of what work they were doing and when they had to have it completed. I agreed to follow-up with them every two weeks just to make sure we were staying on-task.
The project was successful. We were even able to make money off of it. If I had to do it again, I would make sure that we speak to the customer ourselves instead of going through a third party, as that led to confusion. Also, as soon as there is a commitment from the customer, I would organize a workshop or a meeting to physically understand the requirement and get a clear outcome early in the process. Also, don't let sales get paid without understanding cost involved.
Murali Bala, Director, Software Engineering at Capital One, shares his experience of building a guest relationship management tool by embracing the customer-first mindset and working backward.
Director, Software Engineering at Capital One
Benjamin Ritchie, CPO at Cognism, demonstrates the importance of making implicit decisions and actions readily obvious when debating company-wide topics.
CPO at Cognism
Marc LeBrun, VP of Engineering at Flow Kana and a co-creator of the Apple Mac, recalls how one of his early prototypes failed to meet the original intent but how that failure turned into an unanticipated opportunity.
VP Engineering at Flow Kana
Alessandro Pintaudi, Product Management Director at Payfit, talks about how teams need to focus more time on building the right things and how to keep doing it with scale.
Product Management Director at PayFit
Maria Petrova, Principal Product Manager at Zalando describes how she built an organizational design from product and stack in a way that tech and product effectively function in a collaborative environment.
Principal Product Manager at Zalando
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.