# Q3 trend brief for product leadership

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

## Situation and outcome
Wendrayle is a fictional remote patient monitoring company of about 220 people. Its blood pressure cuffs report through hubs or a paired phone to a clinician dashboard, where an AI risk score orders each clinician's worklist, and clinics earn their return by billing a payer program's monitoring code. It has 38,200 monitored patients at 140 clinics. The Head of Product publishes a trend brief every quarter on market, technology and regulation (R001). You are the product manager who owns the Q3 2026 edition.

Your outcome is a source-verified draft edition for the leadership review on Thursday 15 October: the brief itself, an evidence table, a list of proposed follow-ups with an owner function for each, and a revision log. Every item gets a classification, a horizon, its relevance to the strategy (R002), how sure you are and what stays uncertain. For each regulatory statement you record whether it needs counsel or is factual only, item by item. Anything that cannot wait for the review is raised now, outside the cycle, in the way your authority below allows. The Head of Product chairs the review; you do not run it, accept follow-ups for anyone, publish the edition or interpret any rule. The Head of Product decides which follow-ups go forward, and only an owner function accepts one.

The period is 2026-06-01 through 2026-10-06 inclusive. Work with 52 records (the watch list, strategy, the Q2 edition, internal analytics and notes, the scanning agent's log, regulator and standards texts, supplier correspondence, competitor pages, an analyst report excerpt, trade newsletters, CRM entries and customer success notes) and an AI first draft of the edition that Wendrayle's drafting agent wrote overnight from the scanning agent's log entries. The draft is a draft, not an authority. Every company, regulator, rule and standard is fictional and all figures are synthetic, so answer from the records supplied: outside knowledge of real organisations earns nothing. 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.

You own the Q3 edition until the leadership review on Thursday 15 October: verification, the clearance record (counsel needed or factual only, item by item), proposed follow-ups with owner functions, and routing anything that cannot wait for the review. You may not accept a follow-up for its owner, change the roadmap or pricing, tell customers how a rule applies, or interpret a rule yourself.

## About the team
A product team producing its quarterly trend brief for the leadership review, with the Head of Product as audience and counsel as the gate for any statement about how a rule applies to the company.

A scanning agent logs one entry per signal from the watch-list sources; a drafting agent writes the first brief from those entries; call recaps are AI summaries; an AI bot tags support tickets; a person checks every item against its source before it circulates.

The PM owns the edition, its clearance record and the routing of urgent items; counsel decides how any rule applies to the company; the Head of Product chairs the review and accepts follow-ups; pricing, roadmap and anything said to customers belong to their owners.

## Work to complete
1. Read the watch list (R001), the strategy excerpt (R002), the Q2 edition (R003), the standing note on regulatory items (R014) and sources/coverage-and-access.md.
2. Audit the AI first draft against the original records. Keep, correct or reject each row and say why. Tell apart what a source established, what a source claims, what repeats another source and what is internal, and keep evidence that points the other way visible.
3. Count what you rely on. Count the organisations behind an item rather than the records or mentions, count a repeat or a relay once, and state what each count means.
4. Write the edition in the order of the template. For each item say what changed (dated, with record IDs), its classification, horizon and relevance to Bet A, Bet B or clinic billing, your confidence and what stays uncertain, and a proposed follow-up with an owner function. Mark what is new or changed since the Q2 edition and carry the Q2 follow-ups with their recorded status.
5. Record the clearance gate item by item: counsel needed, or factual only. Write each question for counsel out in full. Do not answer how a rule applies to Wendrayle or its clinics, in either direction.
6. Raise anything urgent now, outside the cycle. Routing means writing a simulated handoff in the "Raised now" section of trend-brief.md: the item, the owning function, the facts that function needs, the record IDs and what you ask of them by when. Nothing is actually sent and no one is contacted. If your role does not route it directly, write the same handoff and mark it as passed through your manager. Propose where the scanning and the watch list fell short.
7. Read the correction note (U001) in your download like any other source and apply it. Carry each justified revision through every file and keep the earlier version visible in the revision log. 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-final-rule-and-crm-fix-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.
- trend-brief.md: the edition, using the template's headings. At most 1,300 words.
- evidence.csv: your template already has one row for each of the 52 records (R001–R052), with its source ID and organisation ID filled in. Keep exactly one row per record. Fill in the edition item the record bears on most (or context, or excluded), a use such as supports, contrary, relay, primary, context or excluded (free text is accepted) and a few words of rationale. If the correction note changes a record, revise its row in place, set evidence_version to U001, and keep the earlier version visible in its rationale or the revision log.
- follow-ups.md: one line per proposed follow-up: item, proposed action, owner function, status, linked record IDs, and a trigger or date. A status is proposed unless a record shows the owner's decision.
- revision-log.md: what you changed from the AI draft and why, and what the correction note changed, with the earlier and later versions side by side.

Keep trend-brief.md within its limit: the reviewer reads all of it. Words are counted by splitting the file on spaces and line breaks, so headings and table cells count; markdown symbols standing alone and table borders do not. follow-ups.md has one line per follow-up, and revision-log.md is as long as it needs to be.

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
- Turns signals into implications

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.
