# Write the opportunity brief for medication refills

Dapplewick · Product-management work sample
All company, household, pet, partner and data in this exercise are original synthetic material.

## Situation and outcome
Dapplewick is a fictional consumer pet-care app for iOS and Android in the US and Canada. The free app keeps pet profiles, vet records and reminders. Dapplewick Plus adds several pets, a shared household of up to four logins and vet chat. You are the product manager for the Care area. The VP Growth has asked for in-app pharmacy ordering on the Q1 roadmap (R001). The Head of Product has asked you for an opportunity brief on medication refills for the monthly product review on 14 October, under the intake rules (R002). A research agent drafted a first brief overnight. Nobody has checked it.

Your outcome is an opportunity brief marked proposed, for that review. It frames the problem and who has it, says what the evidence can and cannot support, sets a goal and a success measure with a baseline, lists risks and key assumptions, and recommends a next step against the intake rules. A well-argued "hold for validation" or "do not pursue" is a valid result, and so is an honest evidence gap. The brief does not decide, approve discovery, commit a solution, a partner or a roadmap slot, run validation research, build the business case or write requirements.

The evidence period is 2026-07-01 through 2026-10-02 inclusive. Work with 56 records (strategy and rules, dashboards and analyses, support tickets, feedback, community posts, interviews, surveys, partner and market material, and engineering notes) alongside the AI first brief. The AI brief is a draft, not an authority. Use the supplied record IDs and source context; do not contact the fictional teams, partners or households, or seek private data or live queries.

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

You own the opportunity brief and its recommended next step, marked proposed, for the Head of Product's review on 14 October. You may bound the problem, set the success measure and route risks. You may not approve discovery, commit a solution, a partner or a roadmap slot, or change the intake rules.

## About the team
A consumer pet-care app's Care team preparing an opportunity brief on medication refills for the monthly product review.

A triage bot tags support tickets, a review-mining agent clusters feedback, interview summaries are AI-generated, and a research agent drafted the first brief overnight; people own evidence approval, the brief and the decision.

The Head of Product decides at the monthly product review; engineering, the vet advisor and the data analyst own their own questions; partners and the roadmap are not the PM's to commit.

## Work to complete
1. Read sources/coverage-and-access.md, then frame the question: what problem, for whom, and what the brief is asked to decide.
2. Audit the AI first brief against the original records. Keep, correct or reject each section and say why. Count households, not records or tickets, and keep evidence that points the other way visible.
3. State the problem without naming a solution: who has it, the job they are doing, the pain, their current workarounds, and what is out of scope. Say what else could explain the pain.
4. Set a goal and a success measure with a baseline you can trust, name risks to value, usability, feasibility and viability, and list the key assumptions.
5. Recommend one next step against the intake rules, with what it rests on. If you recommend holding for validation, list each question with the evidence needed, an owner and a trigger for revisiting.
6. Read the correction note (updates/U001-feasibility-and-data-check-in-v1.md) with the other sources and apply it. Carry each justified revision through every file and keep the earlier version visible. Write down any serious risk with its owner and the action you want taken now, in open-questions.md, whatever the brief recommends. The revision log is your own account of how you worked.

## 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-feasibility-and-data-check-in-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 the correction note (U001) changed your work, or that it did not.
- opportunity-brief.md: about 1,000 words at most. Mark it proposed. Cover the problem, who has it, the job and pain, current workarounds, the evidence and its limits, why now, what is out of scope, feasibility notes, strategic fit and alternatives (noted, not decided), the goal and success measure with a baseline, risks, key assumptions and the recommended next step.
- evidence.csv: the template already has one row for each record, R001–R056, with its record ID and household ID filled in. Fill in the claim column with your own claim (write none for a record that bears on no claim) and the stance column with what the record does for it (supports, contradicts, context, coverage limit or excluded are suggested; your own word is fine) on every row. A record that bears on more than one claim gets an extra row for each; never remove a record's row or retype its IDs. Keep the original household visible when a correction moves a record. Add a rationale, an observation_group and an evidence_version where they help. Cite the correction note as U001.
- open-questions.md: one line per question, with the evidence needed, an owner and a trigger for revisiting. Include risks that need an owner now.
- revision-log.md: material changes, verification checks and remaining gaps. No private prompts or unrelated files.

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 sources and counts
- Judges what the evidence supports
- Checks and repairs the AI draft
- Hands off to the right owners
- Explains their choices
- Frames the problem, not a solution

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.
