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
"The biggest problem was to solve the engagement problem first with the sponsor, then the team, then external stakeholders."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Performance management is really about the employee experience; avoid surprises by coaching continuously on both what and how folks are doing."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"Human connection is a basic need that doesn’t get paused just because someone works remotely."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"Designers contribute experimental patterns back to the design system early, making their work visible even before full validation."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"You need to find your own mattress—a grounding purpose or phrase—that you can rely on when progress feels hopeless."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"We decided not to chase shiny objects because we wanted to stay true to our mission."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Provoking and reframing perspective helps teams get unstuck by thinking in new and surprising ways."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"Regulations are design problems, not just technical ones, influencing how we create products and experiences."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Imagine your current design ops team is like a coin and every time you flip it, it comes up heads, but coins have two sides."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
What strategies motivate cross-functional teams to input their research findings into a centralized repository?
How can lifelong learning be incorporated as a core principle of design education and beyond?
How can AI help automate the population of a UX research repository from unstructured data sources?