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
"Design ops’ job is like jazz rules—it provides a framework so creativity can flow without worrying about inventing structure mid-process."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"A really strong book has to be designed as a journey with a consistent voice guiding the reader."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"The difference between director and principal often lies in whether you’re inspired more by leading people or focused on outputs and craft."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"We are really good at finding problems, but the opportunity solution tree helps pick the best ones to focus on."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"User recordings are your most valuable asset but have become riskier due to biometric privacy laws."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Matching is very much an art, not a science; there are no hard and fast rules for what counts as a good match."
Joshua NobleCasual Inference
October 6, 2023
"Findings are observations with a short shelf life, whereas insights get deep into the why and the consequences."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"We are obligated to treat each other with kindness and respect; this is a safe and inclusive space."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"I’ve nearly bought products in my sleep because I memorized the key presses from consistent checkout flows."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
