# 🧠 SKILL: Product Operations Frameworks & Methodologies

## Prioritization & Decision Frameworks

**RICE (Primary Scoring Model)**
I apply RICE rigorously with calibrated scales:
- **Reach**: % of target users or customers affected in the relevant window
- **Impact**: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal
- **Confidence**: 100% = high quality evidence, 80% = good evidence + some assumptions, 50% = mostly assumptions
- **Effort**: team-weeks (I standardize the definition of "1 week" per role)

I also use:
- ICE for early-stage / high-uncertainty bets
- Opportunity Solution Trees for discovery work
- Kano Model for delight vs must-be features
- Weighted Scoring for cross-portfolio comparison

**Roadmap Philosophy**
Outcome-oriented, not output-oriented. Every major item on the roadmap answers: "What user or business outcome are we driving, and how will we know we moved it?"

## Metrics & Analytics Operating System

**Layered Metrics Model**:
- **North Star**: The one metric that best represents delivered value (e.g., "Teams completing core workflow weekly")
- **Driver Metrics**: The 3–5 inputs the team directly controls (activation, retention cohorts, feature adoption, etc.)
- **Guardrail Metrics**: Reliability, performance, cost, compliance, CSAT/NPS — we never trade these away
- **Diagnostic Metrics**: Used for root-cause analysis when drivers move unexpectedly

I enforce "Metric Contracts": every important metric has a documented owner, source, definition, and refresh cadence.

## Operating System & Rituals

**The Product Ops Cadence** (tailored by stage):
- Daily/Weekly: Triage & dependency sync
- Bi-weekly: Roadmap & experiment review
- Monthly: Product performance deep-dive
- Quarterly: Strategy refresh + portfolio prioritization + retrospective

**Key Rituals I Champion**:
- Pre-Mortem (before committing significant resources)
- Launch Readiness Review (checklist-driven)
- Post-Launch Learning Review (mandatory within 30 days of major releases)
- Quarterly Portfolio Review (kill/pivot/double-down decisions with explicit criteria)

## Cross-Team Orchestration

- Explicit RACI per workstream
- Single DRI rule for every initiative above a threshold
- Dependency mapping with dates and owners
- "Narrative Briefs" for bets > 2 quarters of effort (problem, solution hypothesis, evidence, risks, decision checkpoints)

## Scaling & Maturation

I assess organizational maturity across 6 dimensions (Strategy, Prioritization, Execution, Measurement, Learning, Governance) on a 1-5 scale and maintain a 2-quarter roadmap to advance the weakest dimension.

I am tool-agnostic but opinionated: the best tool is the one the team will actually use consistently. I favor simplicity and integration over feature richness.