Following the Customer’s Lead
21 June, 2021
One of the challenges of being in a start-up’s project team is actually to make sure that you are user-centered and that you are actually developing a product for the user that brings value. There are only a finite number of ways to do this. Usually, into my own magic potion, I put a lot of product intuition, which is not very tangible.
You also have direction from the company giving some overarching shape to your strategy. You’ve got your users, the way that they’re using the app and any feedback that they happen to be providing. What is the best way to put it all together?
I started looking into the support tickets so that I would be able to see any conversations happening with the customers. I wanted to see any problems or feedback being brought up repeatedly so that I would be able to investigate them more closely. What are the underlying issues that the user is struggling with?
After doing this for some time, I realized that we could kind of put all of the problems into buckets; a single conversation could potentially fit into several. The buckets included bugs, feature requests, feedback, or simply confusion about some part of the service that we were providing.
Every bucket could then be attached with an action item. For instance, with a bug, you could instantly create a bug report addressing it, which can then be estimated and added to your team’s sprint. For a feature request, you can do the same. I try to actually understand what the real need of the user was. Feedback can sometimes enter the developer’s domain, but it can also be directed to marketing, design, or other departments, as well.
We go through these queries weekly and tag them with these four different types of labels. They are then prioritized according to urgency. I don’t know a lot of PMs who are doing this in this sort of fashion.
- Every conversation becomes an important way to transform the product. Take in every piece of input from your users and feed it back into the service that you provide for them.
- This is a great way of getting other departments involved. They will be able to see what’s happening and add their insight.
- This way of working really does make your customers feel as though you listen to them.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Vadim Antonov, Engineering Manager at Meta, details his process of implementing an organized execution system for his cross-functional team.
Engineering Manager at Facebook
James Engelbert, Head of Product at BT, shares how he helped his team approach learning differently.
Head of Product at BT
Albert Lie, former Founding Engineer and Tech Lead at Xendit, didn’t know what it takes to become an early engineering hire and not a lot of people around him experienced this unknown and arcane path. He had to learn it the hard way from the pitfalls he encountered along the way and he has been creating numerous frameworks to measure his growth and keep burgeoning in this role since then. He codifies and expresses the systems he put in place surrounding the balance of customer inquiry to product building and growing the engineering team.
Former Tech Lead at Xendit
Matt Anger, Senior Staff Engineer at DoorDash, shares some of the benefits of having one-on-one meetings and tips on how both parties should run them.
Senior Staff Engineer at DoorDash
Deepesh Makkar, Sr Director of Engineering at SunPower Corporation, details the processes he formalized to stay in touch with large, remote teams that are located internationally.
Sr Director of Engineering at SunPower Corporation
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.