# Revise a product strategy for leadership review

Tolvane · Product-management work sample
All company, customer, partner and incident information is original synthetic material.

## Situation and outcome
Tolvane is a fictional B2B software company. Its product, Tolvane Dispatch, schedules and dispatches technicians for field-service operators such as HVAC, plumbing and lift-maintenance companies. Strategy v1 was approved on 12 March 2026. Leadership reviews the H2 revision on 9 October 2026.

Your outcome is a **revised strategy draft** ready for that review, with a change log, an evidence table and an open-issues list, **or a justified evidence-gap record** for any decision the evidence cannot yet settle. You recommend; leadership approves. Nothing you write is approved, and the leadership decision is not yours to make. If you end with an evidence-gap record, you still hand in the same five files listed under Submission, with the gap and what to verify written into them. Alignment meetings, the leadership decision, publication, the team briefing, the roadmap, quarterly goals, a north-star metric and pricing are not part of this work.

The evidence period is 2026-07-06 through 2026-09-25 inclusive. Examine 52 source records from research, win/loss interviews, sales, customer success, analytics, the AI dispatch pilot and partners. Alongside them you have the current strategy, the H2 objectives and a request from leadership, and an AI-revised draft of the strategy that nobody has checked. The AI draft and the current strategy are not evidence authority. Work with the supplied source IDs and context; do not contact fictional organisations or seek private data.

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

Revise the whole H2 strategy draft for the leadership review: decide which of D1-D7 change, keep the rest with reasons, and list the conflicts leadership must decide. You own the draft recommendation. Security, mobile and pilot owners validate their domains; approval, roadmap, pricing and partner terms are not yours.

## About the team
A B2B field-service software team revising its approved product strategy for a leadership review.

A strategy agent may draft revisions and AI may summarise notes; a person checks claims, counts and uncertainty against the sources.

Leadership approves the strategy; people own alignment, roadmap, pricing, partner terms and any customer commitment.

## Work to complete
1. Read strategy/current-strategy.md, strategy/h2-objectives.md and sources/coverage-and-access.md before making claims about customers, segments or the market.
2. Audit the AI draft against the original records. For each of D1 to D7, decide whether to keep it, change it or mark it not ready for decision, and say why. Change only what the evidence warrants. A decision that still stands is kept, with its reason.
3. Count records and organisations separately. A relayed, copied or repeated record is not a new organisation, and a partner's or seller's figure is not customer evidence until it traces to a customer statement or data. Do not turn the customer total into a rate.
4. Keep contrary evidence visible. Treat severity separately from frequency, and do not discount a serious event because it was seen once.
5. Apply the correction note (U001) in your download like the other sources. Carry each repair through the strategy, the change log, the evidence table and the open issues, and keep the original wording of a source that the note disputes.
6. Keep it a strategy: a few critical problems, each with a bet and its risk, and with positioning, product definition and delivery following from them. Say what Tolvane will not do. It is not a roadmap or a feature list.
7. Hand off for the review. List the conflicts leadership must decide (you may recommend an option, but do not present any conflict as settled; approval stays with leadership), the questions owners must answer, and a proposed owner and review triggers for the strategy. Nothing you write reads as approved.

## 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-organisation-and-rfp-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).
- strategy.md: the revised H2 strategy draft, about 1,500 words at most. State that it is a draft for the 9 October review, give the decision you take on each of D1 to D7, and explain counts, contrary evidence, confidence and limits.
- evidence.csv: already has one row for every record, S001–S052, with the record ID and organisation ID filled in. Do not retype them or remove rows. For each row, fill in decision (D1 to D7, or none for a record outside the strategy), stance (for example supports, contrary or context) and, in one sentence, a rationale. If a record bears on more than one decision, copy its row and change the decision. Columns such as observation_group are there for you to use or ignore. If the correction note changes a record, revise its row in place, set evidence_version to U001 and keep the earlier reading visible in the rationale. If it gives a record a different organisation, leave the original org_id as it is (that is the one to keep visible) and write the corrected organisation in the rationale.
- revision-log.md: material changes to the AI draft, verification checks and remaining gaps. No private prompts or unrelated files.
- open-issues.md: conflicts for leadership, questions with suggested owners, and a proposed strategy owner with review triggers.

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 draft
- Prepares the leadership decision
- Explains their choices
- Keeps the strategy focused

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.
