Lead Effectively While Preserving Team Autonomy with Growth Boards
Summary
The best companies build their most innovative products when they give teams problems to solve, rather than features to build, and allow them to learn, test, and iterate rapidly. Everywhere we see the value in less design up front, speaking directly with users, and leaders getting out of the way. However, how can self-organizing teams be sure that collectively we're headed in the same direction? How can leaders with limited resources ensure our teams are aligned without disempowering them? Enter Growth Boards, a lean governance tool to help you find that happy medium between chaos and command and control.
Key Insights
-
•
Growth boards are a lean governance tool that align autonomous product teams with leadership by focusing on real business metrics and outcomes rather than output or status updates.
-
•
Enterprises are shifting from project-focused teams with detailed requirements to empowered, cross-disciplinary product teams responsible for problem-solving and business outcomes.
-
•
Lean governance aims to find a balance between chaos (lack of direction) and command and control (rigid planning), enabling faster decisions while preserving team autonomy.
-
•
Cross-functional leadership boards including business, IT, finance, legal, and design improve decision-making by sharing diverse perspectives, especially exposing product teams to financial metrics.
-
•
Product designers are fully integrated in product teams and leadership boards, underscoring the importance of user-centered design in enterprise product strategies.
-
•
Growth board meetings happen quarterly and cover vision, customer problems, experiments, team health, blockers, and specific asks, ensuring transparency and alignment.
-
•
Growth boards enable early detection of teams that should pivot, spin down, or receive more resources, improving allocation of funding and strategic focus.
-
•
Initial implementation of growth boards can be time-consuming and feel burdensome, but over time they become more fluid and support continuous product strategy refinement.
-
•
Follow-up and transparent feedback after growth board meetings are essential to avoid teams feeling ignored and to maintain momentum and alignment.
-
•
Before implementing growth boards, companies should establish clear objectives and measurable key results (OKRs) and ensure teams have meaningful metrics to track progress.
Notable Quotes
"Everyone is looking for ways to build better products and go faster, breaking down silos between business and IT."
"Leaders getting out of the way and letting teams make decisions with the immediate knowledge they have is key to agile at scale."
"Growth boards are not physical boards; the board refers to people like a board of directors guiding product investment decisions."
"Lean governance tries to find that happy medium where we make decisions quickly, keep teams aligned, and let them solve problems on their own."
"Many product teams have never come face to face with their revenue numbers before, so cross-functional exposure is eye-opening."
"Growth boards are really aimed around being very honest about the health of your product, not just painting a rosy status update."
"The conversation is about how much is this team costing the organization and whether that cost will be worth it in the future."
"Growth boards helped us identify teams that hit their runway early and needed to pivot or spin down, reallocating resources strategically."
"It took a long time for teams to prepare their first growth board presentations because many weren’t used to roadmapping or metrics."
"Growth boards demonstrate you can have agile development at enterprise scale without rigid processes or devolving into chaos."
Or choose a question:
More Videos
"Thank you to all our sponsors; this entire conference would not be possible without you."
Bria AlexanderOpening Remarks
September 29, 2021
"The pressures in large organizations make it hard for teams to see the value of empathy and cross-team connection."
Matt StoneScaling Empathy, A Case Study in Change Management
June 11, 2021
"We get these 75-page PRDs created by enthusiastic people, not PMs, and they’re unreadable. We call that fake holder input."
Paul FordNew work, new words: A glossary for AI
June 9, 2026
"Program managers are just expense of routers—what they missed was the how, that secret sauce of EQ."
Indra KlavinsA Design Ops Girl in a Dev Ops World
October 23, 2019
"Emergence means that something new arises through simple interactions; we design interactions so systems find their own desirable solutions."
Meghan Hellstern Joanne DongThe Next 100 Years of Civic Design: How Might We Better Rise to Meet the Challenges of Today and Tomorrow?
December 10, 2021
"Remote research is not a silver bullet."
Sarah RinkRemote User Research: Dos and Don'ts from the Virtual Field
June 11, 2020
"The cognitive load saved by not having to manage security software on mobile phones is a huge accessibility win."
Sam ProulxMobile Accessibility and You
June 9, 2022
"Levels can mean really different things at different companies, so ask a lot of questions about expectations for each level."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"Communicate as much as possible and in different formats, because different formats resonate differently with people."
Michelle ChinThe DesignOps Starter Kit
September 29, 2021
