inspired-product

# Empowered Product Teams Framework

Framework for building products customers love through empowered teams that own continuous discovery and delivery. The best product companies don't ship features -- they solve problems, and they give teams the autonomy and accountability to figure out how.

## Core Principle

**Empowered product teams** = cross-functional groups given problems to solve (not features to build) who own discovery and delivery end-to-end.

Most product failures come not from bad engineering or design but from building things nobody wants. Feature teams receive roadmaps and execute; empowered teams receive objectives and discover solutions. The difference between a feature factory and an innovation engine is whether teams are missionaries (driven by vision and empathy) or mercenaries (driven by a handed-down backlog).

## Scoring

**Goal: 10/10.** Rate product team structures, discovery practices, or delivery processes 0-10 against the principles below. Always state the current score and the specific improvements needed to reach 10/10.

## Framework

### 1. Product Discovery vs Delivery

**Core concept:** Product work runs on two parallel tracks: discovery determines what to build by addressing risks before engineering investment; delivery builds production-quality software. Most organizations skip discovery entirely, jumping from idea to backlog to sprint.

**Why it works:** Discovery is cheap and fast; delivery is expensive and slow. Validating ideas before committing engineering avoids the most common failure mode: building something nobody wants.

**Key insights:**
- Discovery answers four risks: value (will customers use it?), usability (can they figure it out?), feasibility (can we build it?), viability (does it work for the business?)
- Discovery output is validated ideas backed by evidence, not PRDs or specifications
- Run 10-20 discovery iterations per feature that reaches delivery -- most ideas won't work, so fail fast and cheap
- Discovery is not a phase; it runs continuously alongside delivery, with engineers participating

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| New feature | Validate all four risks before committing | Prototype-test onboarding flow with 5 users before building |
| Roadmap prioritization | Prioritize strongest discovery evidence | Ship the feature with 4/5 successful user tests, not the CEO's request |
| Sprint planning | Feed backlog from validated discovery output | Only discovery-tested items enter the sprint |

**Ethical boundary:** Never cherry-pick discovery evidence to justify a predetermined conclusion -- discovery is honest inquiry, not confirmation theater.

See: [references/discovery-techniques.md](references/discovery-techniques.md) for the four risks framework, prototyping techniques, and user testing.

### 2. Empowered Product Teams

**Core concept:** A small, durable, cross-functional group (product manager, product designer, engineers) given a problem to solve, owning discovery and delivery, accountable for outcomes rather than output.

**Why it works:** Teams that own problems end-to-end develop the domain expertise, customer empathy, and creative solutions no top-down roadmap can match -- missionaries who believe in what they build because they discovered it.

**Key insights:**
- The PM is not a project manager or backlog administrator -- they own value and viability and need deep knowledge of customers, data, business, and industry
- The product designer owns the user experience holistically, not just visual design
- Engineers are the best source of innovation because they know what is technically possible
- Keep teams durable (stable membership) and highly collaborative
- Accountability means outcomes (adoption, retention, revenue), not output (stories shipped)

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Team structure | Organize around outcomes, not components | "New user activation" team owns the whole first-week experience |
| Hiring | Hire PMs for competence, not credentials | Evaluate customer knowledge, data fluency, business acumen |
| Performance | Measure results, not velocity | Track activation-rate improvement, not stories per sprint |

**Ethical boundary:** Never claim to empower teams while overriding their discovery findings with executive mandates -- if leadership dictates the solution, the team is not empowered.

See: [references/empowered-teams.md](references/empowered-teams.md) for roles, missionary vs mercenary dynamics, coaching, and accountability.

### 3. Product Discovery Techniques

**Core concept:** Systematically test ideas against the four risks using opportunity assessment, customer interviews, prototyping, and user testing -- producing evidence quickly and cheaply.

**Why it works:** Ideas are assumptions; without rapid testing, teams build for months on untested assumptions and discover failure only after launch. Discovery techniques compress learning cycles from months to days.

**Key insights:**
- Prototypes are the primary tool: high-fidelity for usability, live-data for feasibility, Wizard of Oz for value
- Test with real target users, not colleagues; qualitative testing (5 users) reveals problems, quantitative validates at scale
- Interview for behavior (what they did), not opinion (what they say they want)
- Data reveals patterns but not causes -- pair it with qualitative discovery
- Feasibility spikes let engineers explore technical risk without full implementation

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| Early idea | Opportunity assessment before design work | Who is it for, what problem, how will we measure success? |
| Usability | High-fidelity prototype with 5 target users | Clickable Figma prototype testing task completion |
| Value | Fake door or Wizard of Oz test | Button for unbuilt feature, measure cl