# Build a proposed product roadmap for approval

Fenmore Systems · Product-management work sample
All company, customer, partner and regulator information is original synthetic material.

## Situation and outcome
Fenmore Systems is a fictional B2B software company. Its product, Fenmore Inspect, lets multi-site operators run safety inspections on a mobile app, chase corrective actions and satisfy auditors. The VP Product reviews the 2027 roadmap for approval on 21 October 2026.

Your outcome is a **proposed 2027 roadmap** for that review: items placed in Now (Q1 2027), Next (Q2 2027) and Later (H2 2027 and beyond), a rationale for every item and every exclusion, a capacity and dependency check, and the decisions the VP must make. A justified "this placement needs a decision first" is a valid result. Approving or publishing the roadmap, reviewing and republishing it later, a customer-facing roadmap, release content, writing requirements and negotiating other teams' roadmaps are not part of this work.

The evidence period is 2026-07-13 through 2026-10-09 inclusive. Examine 62 source records from planning, sales, customer success, support, research, usage analytics, other teams' and partners' roadmaps, capacity sheets and a roadmap workshop. Alongside them you have the 2027 goals, the ten candidate items and an AI-drafted roadmap that nobody has checked. The AI draft is 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.

Prepare the whole 2027 internal roadmap proposal for the VP Product's approval review on 21 October: horizons, a rationale for every item and exclusion, the dependency and capacity check, and the decisions the VP must make. Approval, customer dates, other teams' roadmaps and the hiring freeze belong to others.

## About the team
A B2B inspection-software team proposing its 2027 roadmap for the VP Product's approval review.

A planning agent drafts the roadmap from the input pack, an estimate assistant sizes tickets from their text and a meeting assistant summarises workshops; people confirm estimates, dates and commitments.

The VP Product approves the roadmap; squad leads confirm estimates; other teams and partners own their own dates; sales and customer success own customer conversations.

## Work to complete
1. Read planning/2027-goals.md, planning/candidate-items.md and sources/coverage-and-access.md before making claims about customers, capacity or dates.
2. Audit the AI draft against the original records. For each of the ten items, decide whether it is Now, Next, Later or left out, and say why. Change only what the evidence warrants. A row that still stands is kept, with its reason.
3. Count records and accounts separately. A repeated, copied or relayed record is not a new account, and an internal or partner figure is not customer evidence until it traces to a customer statement or data. Say whether a number counts requests, losses, accounts or internal inputs.
4. Keep contrary evidence visible. Treat severity separately from frequency, and do not discount a serious event because it was seen once.
5. Check that the plan fits. Work out what each squad can take on in each quarter from the capacity records, and say which estimates you rely on and why. Check each dependency against its owner's date, and plan around dated events.
6. Apply the correction note (U001) in your download like the other sources. Carry each repair through the roadmap, the capacity and dependency check, the evidence table and the revision log, and keep the original wording of a source that the note disputes.
7. Keep it a roadmap, not a ranked backlog: tie each item to a goal, and say what is left out and what would bring it back.
8. Hand off for the review. List the decisions that belong to the VP or to other owners without taking them yourself, with who owns each answer. Nothing you write reads as approved, and nothing promises a date to a customer or to another team.

## 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-crm-and-platform-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).
- roadmap.md: the proposed 2027 roadmap, about 1,500 words at most. State that it is a proposal for the 21 October review, give each item's horizon, goal and rationale, say what is left out, list the decisions for the VP, and explain counts, contrary evidence, confidence and limits.
- evidence.csv: already has one row for every record, R001–R062, with the record ID and account ID filled in. Do not retype them or remove rows. For each row, fill in item (I1 to I10, or context for a record outside the items), basis (for example supports, contrary, dependency, capacity, deadline or context) and, in one sentence, a rationale. If a record bears on more than one item, copy its row and change the item. 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.
- feasibility-check.md: per-squad capacity and placed work for Q1 and Q2, and each dependency's owner, date and status, about 700 words at most.
- revision-log.md: material changes to the AI draft, 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 draft
- Prepares the approval decision
- Explains their choices
- Sequences against capacity and dates

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.
