# 30-day product-management foundations

## Outcome

By day 30, produce and present one end-to-end product decision case containing:

- product and business model;
- target user and evidence-backed problem;
- opportunity and solution choices;
- product flow with failure states;
- metric tree and instrumentation plan;
- guesstimate or market-size model;
- experiment or validation plan;
- prioritized roadmap;
- launch and risk plan;
- one-page executive decision memo.

Use one product throughout the month. Prefer a product you can observe and recruit users for. If using a real company, clearly label public facts and assumptions.

## Minimum cadence

- 60–90 minutes on weekdays.
- One 2–3 hour weekend build block.
- One mock or artifact review each week.
- Ten minutes of retrieval practice at the start of every session.

## Week 1 — Understand products as systems

### Goals

- Distinguish outputs from outcomes.
- Map users, customers, payers, suppliers, partners, and regulators.
- Explain the product’s value exchange and business model.
- Decompose one outcome into a metric tree.
- Make a transparent estimate using units and ranges.

### Day 1: PM role and product context

Study the difference between product, project, program, marketing, design, engineering, and service ownership. Write:

- the product boundary;
- the company mission and current business objective;
- what the PM can influence;
- five decisions a PM owns or shapes;
- five decisions owned by partners.

**Artifact:** product context one-pager.

### Day 2: Actors and value exchange

Map every actor, what they contribute, what value they receive, and where incentives conflict. Include non-users affected by the product.

**Artifact:** actor and value-flow map.

### Day 3: Business model and economics

Write the revenue model, payer, pricing unit, variable costs, gross-margin drivers, acquisition motion, retention mechanism, and major operational constraint.

**Artifact:** business-model snapshot with at least three uncertain assumptions.

### Day 4: Outcomes and metric trees

Choose a user outcome and business outcome. Define:

- primary outcome;
- leading inputs;
- one activation metric;
- retention definition;
- monetization link;
- quality, safety, and fairness guardrails.

Every metric must state population, action, time window, and aggregation.

**Artifact:** metric tree and metric dictionary.

### Day 5: First guesstimate

Estimate a decision-relevant quantity such as monthly transactions, storage, support workload, or addressable revenue. Use:

1. clarification;
2. equation tree;
3. assumptions and units;
4. low/base/high cases;
5. sensitivity;
6. a second triangulation method;
7. the decision the estimate informs.

**Artifact:** one-page estimate.

### Day 6: Product teardown

Walk through acquisition, first use, core value, repeat use, payment, support, and exit. Record moments of friction, delight, uncertainty, and exclusion.

**Artifact:** current-state journey and annotated teardown.

### Day 7: Review

Present the system map in ten minutes. Ask the reviewer:

- Which actor or incentive did I miss?
- Which metric could be gamed?
- Which assumption drives my estimate?
- Where did I confuse a feature with an outcome?

Revise once.

### Week 1 exit criteria

- The product boundary and business model are coherent.
- Metric definitions include numerator/denominator or exact event semantics.
- Estimate arithmetic and units are correct.
- Reviewer can restate the product’s core value after the presentation.

## Week 2 — Discover and design

### Goals

- Learn from past behavior rather than stated preference.
- Separate observation, finding, insight, opportunity, and solution.
- Prioritize one segment and one job.
- Design multiple solutions before converging.
- Include accessibility, recovery, privacy, and operational reality.

### Day 8: Research plan

State the decision, knowledge gaps, participant criteria, method, sample rationale, discussion guide, consent, and synthesis plan.

**Artifact:** research plan.

### Days 9–10: Three story-based interviews

Ask about a recent real instance. Probe trigger, context, sequence, alternatives, pain, workarounds, consequences, and language. Avoid pitching a solution.

**Artifact:** interview snapshots separating verbatim evidence from interpretation.

### Day 11: Synthesis

Build an experience map. Cluster observations, write findings, derive opportunities, and record contradictions and outliers.

**Artifact:** evidence table and opportunity map.

### Day 12: Segment and prioritize

Segment only where needs, behavior, economics, or constraints differ. Compare segments using problem severity, frequency, reach, strategic fit, access, risk, and willingness or ability to change.

**Artifact:** segment decision memo.

### Day 13: Diverge on solutions

Generate at least ten directions across workflow, information, incentives, automation, human service, policy, and “remove the step.” Select three meaningfully different concepts.

**Artifact:** solution portfolio and assumption map.

### Day 14: Converge and design the flow

Choose one solution. Design entry, first action, happy path, empty/loading/error/offline states, recovery, permissions, notifications, help, accessibility, abuse prevention, and exit.

**Artifact:** low-fidelity flow and MVP boundary.

### Week 2 exit criteria

- Every prioritized opportunity is traceable to user evidence.
- The selected segment is a decision, not “everyone.”
- At least three solution directions were compared.
- MVP removes nonessential scope without removing the value proposition.
- Flow includes recovery and at least one relevant inclusive-design constraint.

## Week 3 — Measure, experiment, and diagnose

### Goals

- Create reliable event definitions and funnels.
- Interpret cohorts and retention.
- Design a useful experiment or alternative causal method.
- Diagnose an unexpected metric change systematically.
- Separate containment from permanent prevention.

### Day 15: Instrumentation

Create a tracking plan with event name, trigger, actor, properties, source, expected volume, privacy classification, and quality check.

### Day 16: Funnel and cohort analysis

Define the critical journey and cohort start. Explain which conversion and retention cuts would reveal meaningful differences.

### Day 17: Experiment design

Write the hypothesis, eligibility, assignment unit, treatment, primary metric, guardrails, minimum detectable effect, duration drivers, novelty/interference risks, decision rule, and follow-up.

If randomization is impossible or unethical, choose a better design and explain its limitations.

### Day 18: RCA setup

Use a synthetic incident: the primary outcome drops 12% week over week. First validate metric definition and instrumentation, then establish onset, magnitude, duration, and affected segments.

### Day 19: RCA decomposition

Build:

- metric/funnel tree;
- timeline of releases, experiments, campaigns, policy, vendor, and market events;
- segment cuts;
- hypothesis table with likelihood, impact, evidence, and cheapest discriminating test.

### Day 20: RCA actions

Write containment, rollback criteria, owner communication, permanent corrective actions, detection improvements, and a blameless postmortem outline.

### Day 21: Timed practice and review

Run one 35-minute metrics case and one 35-minute RCA case. Score both. Repeat the lower-scoring answer after feedback.

### Week 3 exit criteria

- Metric definitions are queryable rather than aspirational.
- Experiment decision rule was set before observing results.
- RCA begins with data integrity and change-point analysis.
- Hypotheses are prioritized by evidence and test value.
- Corrective actions address a class of failures, not only the proximate symptom.

## Week 4 — Choose, deliver, launch, and influence

### Goals

- Connect diagnosis, strategic choices, roadmap, and goals.
- Prioritize with judgment rather than a score alone.
- Define execution and launch readiness.
- Communicate a decision clearly.
- Build the first behavioral story bank.

### Day 22: Strategic diagnosis

Write the challenge, customer/market insight, company advantage or constraint, and the consequence of doing nothing.

### Day 23: Strategic choices

Decide where to play, how to win, required capabilities, and what not to do. State what evidence would invalidate the strategy.

### Day 24: Prioritization

Compare at least eight opportunities. Use an explicit model, then document overrides for dependencies, strategy, risk, regulation, learning, or sequencing.

### Day 25: Outcome roadmap

Create now/next/later horizons with outcome, target segment, problem, evidence, metric, candidate bets, dependencies, and review trigger. Avoid promised feature/date precision beyond available confidence.

### Day 26: Requirements and delivery

Write a lightweight brief: problem, user, outcome, non-goals, constraints, scenarios, acceptance boundaries, metrics, telemetry, rollout, operations, open questions, and decision owners.

### Day 27: Go-to-market and lifecycle

Define positioning, audience, channel, migration, education, sales/support enablement, launch tier, rollout, rollback, success review, and sunset/data-export obligations.

### Day 28: Decision writing

Compress the case into a one-page memo: decision, context, options, evidence, trade-offs, risks, owner, next step, and review date.

### Day 29: Behavioral foundation

Create eight story outlines: ownership, conflict, failure, influence, ambiguity, difficult prioritization, customer advocacy, and ethical escalation. Use real experiences; never invent one. Separate personal actions from team actions.

### Day 30: Capstone defense

Present for 20 minutes and take 20 minutes of adversarial questions. Submit the revised case with a short retrospective:

- what changed because of evidence;
- where uncertainty remains;
- which decision was hardest;
- what you would test next;
- which PM domain is now the weakest link.

## Final exit criteria

- Case has a clear, falsifiable decision.
- Evidence, inference, and hypothetical assumptions are visibly separate.
- Recommendation connects user value, business value, feasibility, and risk.
- Math and metrics survive review.
- Product flow handles failure and inclusion.
- Roadmap reflects strategic choices rather than a feature list.
- Reviewer scores the case at least 70/100 with no critical dimension below 2/4.