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
"If given a choice in my career and my personal life, I will choose process over ambiguity every single time."
Amy ThibodeauOpening Keynote: Process and Ambiguity
October 23, 2019
"When projects are late or delayed it’s often due to organizational and cultural issues rather than conduct of the project team."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Sounding authentically like you, while professional, is more engaging than robotic business writing."
Bruce GillespieLearning from journalism: Balancing impactful communication with compassionate storytelling
March 13, 2025
"Our Jira integration will be two-way so you can link design activities to epics, user stories, or tasks."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"Cutting down on the analysis time was huge for us, speeding up speed to insight significantly."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Safety is your number one concern, privacy is your number two, and usability is number three."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019
"Proactive measurement before release combined with post-release evaluation is the ideal approach."
Jack MoffettUX Metrics That Matter and The Future of our Design at Scale Conference: A Community Conversation
September 22, 2022
"If I stop doing it, it stops, and I'm the human in the loop, or the monkey in the middle."
Christian CrumlishThe Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
August 14, 2025
"Hiring team members with lived experience was key for authentic engagement and facilitating workshops."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
