Empowering Product and Engineering Leaders to Achieve the Best Business Results
21 May, 2021
How do you set up a team to deliver the best results? I am a firm believer in a product-led organization. We are no longer living in a world where product teams should be measured on the number of features they ship. They need to be measured on creating high quality customer experiences that deliver concrete value. In this world, the product manager is responsible for aligning teams cross-functionally around goals, defining success, gathering the best ideas and prioritizing work for the team. Whether the team delivers 1 feature or 100 features, it all comes down to whether those features deliver results for the business.
For example, I once worked at an online education company where we had an issue effectively monetizing our courses. We had a freemium model, and needed to find more impactful ways to entice students to convert from the free to the paid track. There were any number of ways to achieve this outcome, and the product team had to do lots of experiments to discover the right features to build. Our challenge in leadership was making the team accountable for achieving the monetization outcome, and not a specific set of features.
One of the most important foundations you can provide a product team is proper context. What results is the company trying to achieve as a business in what timeframe? How are the specific results a team is driving important to those overall company results? I make sure the context is clear before we start talking about features and deadlines. Any team is going to make thousands of decisions -- big and small -- throughout the course of development. Context helps the team make the right decisions.
How do you know if the context you have provided is robust and complete? Ultimately of course it comes down to whether the team achieves the results, but there are many signals you can pick up along the way. Ask the team to present their chosen strategy for achieving the result to make sure it aligns with the context. Check in periodically on progress to find out what they are learning, and how they might want to change their approach to reflect those learnings. At every step, you should be seeing some progress that is leading to the desired outcome.
How much oversight should you provide? There is no right answer, and it depends on how much you trust that the team is on the right track. If the team really understands the context and is making good decisions, I would encourage you to give them as much latitude as possible. If you see problems with their decision making, I would lean in more often until you feel they are back on track. Repeated questionable decisions by a group of well meaning employees are almost always due to lack of appropriate context. Make it your job to ensure the team is well prepared by filling in the context gaps.
- Proper context is critical for a team to achieve the right results. Make sure you are arming your leaders with the business goals, and how their work leads to those goals.
- Ensure you understand the strategy the team has chosen to achieve results, and check in on their progress. If they aren’t consistently making good decisions, see if there is a problem with the context you’ve given them. If they are making good decisions, give them more autonomy.
- One of the best measures of progress is learning. Is the team learning more with each step about how to achieve the result? Encourage them to adapt their plans to incorporate that learning.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
This was not a high point in my career. It's a story of single metric bias, how I let one measure become a 'source of truth', failed to manage up and ended up yelling at one of the most respected engineers in my team.
Chief Technology and Product Officer at Hive Learning
Supporting principles on why being data led (not driven) helps with the story telling.
Head of Engineering at Xero
When you grow fast, its normal to focus on Value delivery aka "Feature Releases". Too many releases too soon will inevitably lead to piling tech debts and before you know, inefficiencies creep in, performances goes down, and ultimately any new release takes too long. Sounds familiar? Then read on..
VP - Engineering at ITILITE Technologies
Teams have tremendous impact on the products on they build. T.E.A.M definition - Together Everybody Achieves More is true. A collaborative and empowered team builds great product versus the good ones.
Senior Software Engineering Manager at Anaplan
A high performance team refers to “ a group of goal-focused individuals with specialized expertise and complementary skills who collaborate, innovate and produce consistently superior results.”
Senior Software Engineering Manager at Anaplan