# Plan a launch and report what is ready

Ottermile · Product-management work sample
All company, customer and data in this exercise are original synthetic material.

## Situation and outcome
Ottermile is a fictional running app sold by subscription in the US, UK, Canada, Australia and Germany. Its Family plan lets up to 6 members share goals and, with Pacenorl, share a live location while a member runs. It ships in app 6.4, and general availability is planned for Tuesday 27 October (R001). You took over as the Family plan's product manager on 9 October. The launch sponsor, GM Consumer, asks for the launch plan and a readiness status for the plan review on Monday 19 October: what is ready, what blocks, who owns each item and what she has to decide (R002). She approves the plan; the ship call stays with the VP Engineering.

Your outcome is a proposed launch plan and an evidence-backed readiness status for the sponsor. Each checklist item has one owner, a criterion, the evidence of completion, a blocking flag, a due date and a status taken from evidence: done, in progress or blocked. Use done only when a record shows it; use blocked only when a named dependency stops the item; use in progress for everything else, including an item with no evidence yet or one nobody has started, and say that in the criterion or evidence column. The plan also lists the decisions only the sponsor or the release decision owner can take. A plan that says plainly what is not ready for approval is a valid result. The plan does not approve itself, waive a criterion, make the ship call, run campaigns, cancel media, sign off operations or give legal opinions.

The period is 2026-08-10 through 2026-10-16 inclusive; the snapshot is Friday 16 October. Work with 58 records (planning documents, tracker exports, beta extracts, readiness trackers and team messages) and an AI first draft of the plan. The draft is a draft, not an authority. Use the supplied record IDs and source context; do not contact the fictional teams or seek private data or live queries.

## Your role
You are joining the team as Product Manager.

Own the plan, the checklist and the readiness status, and propose the stage, markets and date to the sponsor with what each option assumes. Item owners own their items; legal, privacy and Trust & Safety own their sign-offs; the sponsor approves the plan and any waiver; the release decision owner makes the ship call.

## About the team
A consumer subscription team preparing a launch plan and readiness status for the launch sponsor's review.

A launch agent drafts the plan and readiness checklist from the tracker, the release calendar and the launch channel; a person checks every status against its evidence before the sponsor sees it.

Item owners own their items; legal, privacy and Trust & Safety own their sign-offs; the sponsor approves the plan and any waiver; the release decision owner makes the ship call.

## Work to complete
1. Frame the question: what the sponsor must decide on 19 October and what you propose. Read sources/coverage-and-access.md before you make any claim about what the records cover.
2. Read the launch process (R005) and the beta exit criteria (R003). Build the readiness checklist for the stage and markets you propose, with one owner, a criterion, the evidence of completion, a blocking flag and a due date for every item.
3. Take each status from the records, not from what someone says is done or from a digest that repeats it. Count markets from the per-market rows, and say which markets a status covers.
4. Audit the AI first draft against the original records. Keep, correct or reject each row and say why. Keep evidence that points the other way visible, and tell apart a measured figure, a person's claim and a gap.
5. Treat severity separately from frequency. Name the owner who can confirm or act on each item without deciding for them.
6. Put the work in dependency order against the release calendar and the marketing calendar, with a date for each step.
7. Apply the correction note (U001) in your download like the other sources. Carry each justified change through every file, and keep the original reading of any record it changes visible next to the revised one. The revision log is your own account of how you worked.
8. Hand off clearly: status, blocking items, the decisions for the sponsor and the release decision owner, and owner questions. Say that it is a proposal.

## Time
You have 90 minutes of work time. The clock starts when you press Start.

After that comes a 10-minute break, then a written interview: up to eight typed questions about your own files, for about 15 minutes. If you submit early, your break starts straight away.

## Mid-task correction
There is no mid-task correction in this take-home. Everything you need is in the files you download at Start, including the correction note **updates/U001-release-and-correction-v1.md**. Read it with the other sources, apply it where it changes your work, and cite it as U001.

## Tools and help
Use any tools and help you like: AI tools and agents, search, your own notes, friends or colleagues. You don't need a paid tool, an API key or an account.

Nothing you do in your own tools is watched. Only your files and your interview answers are reviewed. When you submit, you can say which tools or help you used. That is optional, and leaving it empty is never held against you.

## Submission
Hand in one ZIP with these files at its top level. Start from the copies in the templates folder.
- README.md: list every file you hand in and say how you used the correction note (U001).
- launch-plan.md: at most two pages equivalent (about 1,100 words). The proposed stage, markets and date with what each option assumes, the readiness status, the blocking items and sequence, the decisions for the sponsor and the release decision owner, and the limits.
- checklist.csv: required header item,function,owner,criterion,evidence_required,blocking,due,status,markets,source_ids. One row per checklist item with one owner, and at most 30 rows; a row may cover several markets when the owner, criterion and status are the same in each. Status is done, in progress or blocked. (An item with no evidence yet, or not started, is in progress; do not call it blocked unless something specific stops it.) Due is a calendar date: when a date depends on someone else, give the date by which you need their answer.
- evidence.csv: already has one row for every record, R001–R058, with the record ID and market ID filled in. Do not retype them or add or remove rows. For each row, fill in checklist_item (the checklist item the record bears on most; name your own items), status and a rationale of one sentence. A status such as done, in progress, blocked, context, contrary or excluded is suggested and free text is accepted. If the correction note changes a record, revise its row in place, set evidence_version to U001, and keep the earlier reading visible in its rationale or the revision log.
- revision-log.md: at most about 600 words. Material changes, verification checks and remaining gaps. No private prompts or unrelated files.
- questions.md: at most 10 open questions, each with one suggested owner and the decision that depends on it.

Keep every file within these limits: the reviewer reads all of it.

Words are counted in the prose of each document you write; headings, tables, the evidence file and the README do not count.

Use plain text files only: .md, .txt, .csv or .json. Put your work in the files themselves; a link to a document somewhere else does not count. Your ZIP can be up to 5 MB, or 20 MB unzipped, with at most 39 files of up to 2 MB each. Programs, macros, password-protected ZIPs and ZIPs inside your ZIP are not accepted.

Upload your ZIP on your take-home page and wait for **Received and checked**. It normally appears within a few seconds of the upload finishing. If it has not appeared after a minute, upload the ZIP again; if it still does not appear, use **Help and support**. You can replace your ZIP until you submit. Submitting is final and starts your break.

If time runs out before you submit, the last ZIP marked **Received and checked** is handed in for you. If none was received, the team is told that you need support.

If something goes wrong, use **Help and support** on your take-home page. A technical problem is never counted against you. Writing to us does not pause the clock.

## What happens next
The written interview covers these parts of the job:
- Checks status against evidence
- Weighs risk and gaps
- Checks and repairs the AI draft
- Hands off to the right owners
- Explains their choices
- Builds a plan owners can run

An AI then drafts a review from your files and your answers. Each point quotes what it rests on. A person at the company reads the review and makes any decision. No one is hired, rejected or ranked automatically.
