five-legged-stool-collaboration

star 24

A framework for cross-functional product leadership that integrates Product, Engineering, Design, Insights, and Marketing into a single decision-making unit. Use this when squads suffer from misaligned goals, when "Insights" are siloed from execution, or when product launches lack a cohesive go-to-market strategy.

samarv By samarv schedule Updated 1/25/2026

name: five-legged-stool-collaboration description: A framework for cross-functional product leadership that integrates Product, Engineering, Design, Insights, and Marketing into a single decision-making unit. Use this when squads suffer from misaligned goals, when "Insights" are siloed from execution, or when product launches lack a cohesive go-to-market strategy.

The "Five-Legged Stool" moves beyond the traditional triad (Product, Engineering, Design) to include Insights (Analytics/Research) and Marketing as equal partners in the core leadership of a product squad. This model ensures that every feature is grounded in data, validated by user research, and has a clear path to market from day one.

The Five Legs of the Stool

For every squad or group, identify a lead for each of the following functions. While a five-legged stool requires a "flat surface" (clear alignment), it provides significantly more stability for complex marketplace decisions.

  1. Product: Defines the "what" and "why" based on the North Star KPI (e.g., Gross Merchandise Sales).
  2. Engineering: Ensures technical feasibility, scalability, and performance.
  3. Design: Focuses on the user experience and ensuring the brand aesthetic remains cohesive.
  4. Insights (Data & Research): Combines quantitative data and qualitative user research to validate hypotheses before and after launch.
  5. Marketing (PMM/Brand): Ensures the product narrative resonates with the audience and manages the "outside-in" competitive perspective.

Implementation Guide

1. Establish the "Accountable Decider"

To avoid the trap of "consensus-based culture" which slows down development, clarify that the Product Manager is the ultimate accountable party.

  • The Rule: The PM does not have to have the best ideas, but they must choose the best ideas from the five-legged group.
  • Conflict Resolution: When the five leads disagree, the PM makes the final call but must document why they overrode specific functional concerns.

2. Operationalize Weekly Focus

Use a "Weekly Focus" ritual to keep the five leads aligned without constant meetings.

  • The Prompt: Every Monday, each lead posts 2-3 high-level priorities to a shared channel.
  • The Reflection: On Friday, the group reviews what was actually achieved.
  • The Goal: Distinguish between tasks (busy work) and priorities (KPI-moving work).

3. Apply the "Minimize Waste" Principle

Use the Insights and Marketing legs to kill features early.

  • Before building, ask the Insights lead: "What is the smallest amount of data we need to prove this is a bad idea?"
  • Ask the Marketing lead: "Does this feature fit our 'Keep Commerce Human' brand, or is it just a generic utility?"

Examples

Example 1: Launching a New Seller Tool

  • Context: Etsy wants to help sellers scale their production through "Production Assistants."
  • Input: Engineering identifies the technical requirements; Insights notes that sellers are hitting manual limits.
  • Application: The Five-Legged Stool meets. Marketing notes that "Mass Production" might hurt the brand. They work together to define a policy (Design/Marketing) that allows scaling while keeping the "human" provenance (Product/Insights).
  • Output: A feature that allows production assistance only if the seller proves they designed the item and know the maker.

Example 2: Optimizing the Buyer Cart

  • Context: The team wants to increase conversion in the checkout flow.
  • Input: Insights shows a drop-off at the final payment step.
  • Application: Marketing suggests adding a copy change about carbon-neutral shipping. Design ensures it doesn't clutter the UI. Engineering implements it as a one-line text change.
  • Output: A values-based conversion nudge that increases GMS without a complex technical build.

Common Pitfalls

  • The Consensus Trap: Waiting for all five people to agree 100% before moving. Avoid this by empowering the PM to push the decision to the "edges" once all viewpoints are heard.
  • Resource Imbalance: Not every squad can have a dedicated researcher or marketer. In these cases, use "coverage models" where one lead supports 2-3 squads but remains part of the leadership "stool" for each.
  • Ignoring the "Outside-In" View: Focusing so much on internal data that the team ignores what competitors are doing. Task the Marketing leg with bringing monthly competitive benchmarks to the group.
  • Treating PMs as "Mini-CEOs": Allowing the PM to dictate from on high. This leads to brittle products. The PM must consult the other four legs to ensure the decision is "load-bearing."
Install via CLI
npx skills add https://github.com/samarv/Shanon --skill five-legged-stool-collaboration
Repository Details
star Stars 24
call_split Forks 4
navigation Branch main
article Path SKILL.md
More from Creator