Product Operating Model

J

Jordan Reyes

@jordan-reyes

·

Design product operating models for effective team coordination

26 copies0 forks
Define a product operating model for {{organization}}.

Org size: {{size}}
Product complexity: {{complexity}}
Current challenges: {{challenges}}

**Operating Model Components:**

**1. Governance Structure**

*Decision Rights*
- Product strategy decisions
- Roadmap decisions
- Feature decisions
- Technical decisions

*Forums*
- Leadership reviews
- Product council
- Technical reviews
- Sprint ceremonies

**2. Planning Cadence**

| Cycle | Purpose | Participants | Output |
| Annual | Strategy | Leadership | Vision, themes |
| Quarterly | Roadmap | PM, Eng, Design | OKRs, roadmap |
| Sprint | Execution | Pod | Sprint goals |

**3. Communication Rhythms**

*Upward*
- Executive reporting
- Board updates

*Lateral*
- Cross-team syncs
- Dependency management

*Downward*
- Team updates
- Decision cascades

**4. Role Clarity**

*Product Management*
- PM levels and expectations
- Scope by level

*Product Leadership*
- Strategic vs operational
- Span of control

**5. Metrics Framework**
- North star metric
- Team-level metrics
- Individual metrics

**6. Continuous Improvement**
- Retrospective cadence
- Process evolution
- Operating model reviews

Details

Category

Productivity

Use Cases

Org designProcess definitionScaling teams

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing