The setting

Ledgerly makes bookkeeping software for freelancers and small shops, about 30,000 paying users. You are the product manager for the mobile app, working with two engineers, Priya and Tomas, and a designer, Rae.

Every mission on this path happens at the same company, so context carries over the way it does in a real job: the data you cleaned in mission two is the data the finance lead questions in mission four.

The missions

1. problem briefstarter

Frame the receipt-capture problem for Ledgerly's roadmap

Ledgerly's churn survey keeps surfacing the same complaint: dealing with expenses is the worst part of the month. Leadership assumes the fix is a faster manual entry form, but nobody has written down what users actually struggle with. Your VP wants a problem brief before any design work starts.

You deliver: A one-page problem brief that defines the core user problem, sizes it with evidence, and challenges the manual-form assumption.

Scored on: Problem statement, Grounded in evidence, Challenges the assumption, Scope sized.

Working from: interview_notes.md, churn_reasons.csv.

2. PRDstarter

Write the PRD for Ledgerly receipt capture v1

The problem is validated and leadership has agreed the real job is capturing receipts in the moment. Now your VP wants a PRD before the team commits to a two-week build. Vague scope here means a blown timeline later.

You deliver: A PRD for receipt capture v1 with goals, non-goals, user stories, and success metrics.

Scored on: Clear scope and non-goals, Measurable success goal, Respects constraints, User stories.

Working from: problem_brief_summary.md, constraints.md.

3. prioritizationcore

Rank Ledgerly's Q3 backlog without chasing the loudest request

Engineering has 12 weeks of capacity for Q3 and the backlog is bigger than that. Leadership is leaning toward building dark mode first because it is the most upvoted request, and you suspect that is the wrong call.

You deliver: A prioritized Q3 plan with a consistent scoring method and a selected set that fits 12 engineering weeks.

Scored on: Consistent framework, Weighs paying signal, Fits capacity, Tied to goals.

Working from: feature_requests.csv, q3_goals.md.

4. launch plancore

Plan the Ledgerly receipt capture launch

The build is done and your VP wants a launch plan before anything reaches customers. A sloppy launch of a churn-sensitive feature could make the very problem worse.

You deliver: A launch plan with staged rollout, risks and mitigations, go/no-go criteria, and rollback.

Scored on: Staged rollout, Catches the gaps, Risks and mitigations, Go/no-go and rollback.

Working from: release_state.md, launch_checklist.md.

5. metric reviewstretch

Run the four-week metric review after receipt capture launch

It is four weeks since receipt capture went to 100 percent. Leadership wants to know if it worked and whether anything broke along the way. The numbers look messy at a glance and it would be easy to draw the wrong conclusion.

You deliver: A metric review memo with a launch verdict, the regression story, and a recommendation.

Scored on: Reads the trend correctly, Links to release, Adoption reported, Clear recommendation.

Working from: post_launch_metrics.csv, release_log.md.

How the scoring works

Each deliverable is graded against the rubric written for that mission. Separately, every mission on every path is graded on how you used AI, against the same four criteria:

  • Understood the task. The learner framed the goal for the assistant clearly instead of pasting the brief and hoping.
  • Grounded in the material. The learner directed the assistant into the provided files and based the work on them, not on invented facts.
  • Verified the output. The learner checked claims, numbers, or coverage against the source material before submitting.
  • Iterated with judgment. The learner refined weak parts of the draft with specific follow-ups rather than accepting the first answer.

Both scores, with the work behind them, go on your proof profile. That is what makes a claim like "I can use AI for product management" something an employer can check.