Product skills

Surface the assumptions an idea rests on, rank them by impact times uncertainty, and test the riskiest leap-of-faith ones with the cheapest experiment before committing build effort.

A sharp product thinking partner, explore a problem space, challenge assumptions, and sharpen a fuzzy idea into a crisp problem statement plus the next cheapest experiment. This is everyday product judgment (divergent→sharper problem); for convergent strategy/moat/billion-dollar bets use as-ops-strategic-advisor, and for full feature specs use as-pm-write-spec.

Product management category hub: routes to the right leaf for deciding what to build (brainstorm, assumption mapping, market validation, opportunity solution tree, strategy frameworks, requirements physics), setting direction (North Star, OKRs, roadmap), understanding users (journey map, synthesize research), and shipping (write spec, sprint planning, pre-mortem, stakeholder update).

Map the end-to-end experience a specific persona has getting a job done (the ordered stages, and at each what they do, the touchpoints, what they think, how they feel, and where it hurts) built from real research, not invented at a desk. Plots the emotion curve, marks the lows and the moments of truth (first value almost always one), and turns each significant pain into a prioritized opportunity.

Validate whether the market will actually pay for a new offer/product/service line BEFORE you invest in launch.

Define the North Star Metric, the single number that captures the core value your product delivers and leads revenue, not a lagging output or a vanity count.

Set OKRs that create focus, not a task list (Wodtke, Radical Focus), one ambitious qualitative Objective per team per quarter plus 2-4 measurable outcome Key Results with baseline to target and a data source, laddered to the company objective and the North Star.

Build an Opportunity Solution Tree (Teresa Torres, Continuous Discovery Habits), the visual map from one measurable outcome down through research-grounded opportunities (customer needs/pains/desires in their words), to 3+ compared solutions per target opportunity, to the experiments that de-risk them.

Run a pre-mortem (Gary Klein) and red-team a plan, assume the project already failed and work backward to explain why, which defeats optimism bias and surfaces the risks people stay quiet about.

Strip a brief to physics-only requirements before the PRD is written. Full PRD is as-pm-write-spec; full Algorithm including delete is as-ops-the-algorithm.

Build, update, and reprioritize the product roadmap in Now/Next/Later horizons with RICE or value-effort scoring and explicit swap tradeoffs. For big end-to-end feature builds use as-ops-product-feature-builder; for strategy/moat/billion-dollar bets use as-ops-strategic-advisor; for KPI reporting use as-analytics-*.

Plan a sprint from real capacity to a single goal, PTO/meeting/carryover/buffer math, P0 vs stretch, and owner-runs-irreversible flagging. For the durable roadmap use as-pm-roadmap; for big feature builds use as-ops-product-feature-builder; for KPI reporting use as-analytics-*.

Write an audience-tailored stakeholder update (exec brief, eng detail, or customer-facing) in status, launch, or escalation flavor. For brutal strategy use as-ops-strategic-advisor; for KPI/metrics reports use as-analytics-weekly-metrics; for full internal-comms formats use as-design-internal-comms.

Run the right strategy framework for the question and fill it with honest analysis, not box-filling, Business Model Canvas, Lean Canvas, Value Proposition Canvas (JTBD), SWOT, PESTLE, Porter's Five Forces, Ansoff Matrix, and Product Vision. Picks the framework by the question, then runs it so every cell ends in an implication or action and the analysis points to one decision.

Synthesize existing product feedback (interviews, surveys, support tickets, NPS, cancellation reasons) into themes ranked by frequency × impact, then into roadmap recommendations. For PLANNING and RUNNING UX research (interview guides, surveys, usability tests) use as-design-user-research. This one turns existing feedback into PM decisions.

Turn one problem statement or feature idea into a complete, build-ready PRD file landed in /planning (framed problem + segment, goals/non-goals, operator user stories with testable acceptance criteria, 1-3 sourced success metrics, and a phased rollout) ready to hand to as-ops-product-feature-builder.