# Propose a priority order for the next quarter

Pellowin · Product-management work sample
All company, retailer, maker, partner and incident information is original synthetic material.

## Situation and outcome
Pellowin is a fictional UK and Ireland wholesale marketplace where about 16,000 independent retailers buy from about 2,100 makers. Its Retailer Ordering squad plans Q1 2027 (4 January to 2 April, 13 weeks). Twelve candidate items have scorecards and votes, and a planning agent has drafted an order that nobody has checked. The planning review is on 15 October 2026.

Your outcome is a **proposed Q1 2027 priority order** for that review: the twelve items in order with a cut line at the capacity the squad really has, a rationale for each item and for each departure from the scores or votes, the dependencies kept, and a review record that shows each stakeholder's position, the contested items, and who decides them and by when. A justified "this placement needs a decision first" is a valid result. Running the votes or the review, the Head of Product's ruling and publication, sprint and release planning, building a roadmap, negotiating other teams' dates and detailed estimation are not part of this work.

The evidence period is 2026-08-10 through 2026-10-09 inclusive. Examine 70 source records from planning documents, scorecards, dependency notes, capacity notes, importance and feasibility votes, a positions thread, CRM requests, support tickets, an incident review and finance note, analytics summaries and research. The scorecards, votes and thread are supplied as records, not run by you. 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 proposed Q1 priority order for the 15 October planning review: the order with a cut line at capacity, a rationale for each item and for each departure from scores or votes, the dependencies respected, and a review record of each stakeholder's position with who decides contested items and by when. Approval, publication, other teams' plans and the Q1 goals belong to others.

## About the team
A wholesale-marketplace product squad proposing its Q1 2027 priority order for the planning review.

A planning agent compiles candidates, fills in missing scorecard factors, tallies votes and drafts the order; a notes assistant summarises threads and call notes. People own the scorecard factors, the capacity and the agreement.

The Head of Product decides anything the stakeholders do not agree on and publishes the order; presenters own their scorecard factors; other teams and partners own their own dates.

## Work to complete
1. Read planning/candidate-items.md and sources/coverage-and-access.md before making claims about customers, capacity or dates. The charter, goals and calendar are the first three records.
2. Audit the AI draft against the original records. For each of the twelve items decide whether it sits above or below the cut line, in what order, and 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 tally is not customer evidence until it traces to accounts. Say whether a number counts requests, accounts, votes or estimates.
4. Check the scores and votes before you rely on them: who owns each scorecard factor, which ballot is the latest, and whether an item has been scored on what its presenter actually entered.
5. Keep contrary evidence visible. Treat severity separately from reach, and do not discount a serious event because few retailers saw it. Treat a claim nobody has tested as a claim.
6. Work out the capacity the squad really has from the records, and draw the cut line there. Keep every dependency intact. When an item depends on another of the squad's own items (C01 to C12), it goes above the line only if that item does too, and your order or your stated build sequence shows which comes first. When it depends on work another team or partner owns, you do not place that work: show it as a dated dependency, ask for it as a request, and plan around the date that team or partner owns.
7. Read the correction note (updates/U001-crm-and-payments-v1.md) with the other sources and apply it. Carry each repair through the order, the evidence table, the review record and the revision log, and keep the original wording of a source that the correction disputes.
8. Keep it a proposal. You recommend a place for all twelve items; mark as provisional any placement that is disputed or needs a decision first. The Head of Product approves the order. Record each stakeholder's position or "no response", the contested items with each side's reasons, and who decides what is not agreed and by when. Recommending a placement is your job; settling a dispute is not. Asks of other teams are requests, not commitments.

## 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-payments-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.
- priority-order.md: the proposed order, about 1,400 words at most. State that it is a proposal for the 15 October review, give each item's place, goal, weeks, running total and rationale, mark the cut line, explain each departure from the scores and votes, the dependencies and dates, and the counts, contrary evidence, confidence and limits.
- evidence.csv: the template already has one row for each record, R001–R070, with its record ID and account ID filled in. Fill in the item column (C01 to C12, or context for a record outside the items) and the basis column (supports, contrary, score, vote, dependency, capacity, position or context are suggested; your own word is fine) on every row. A record that bears on more than one item gets an extra row for each; never remove a record's row or retype its IDs. Keep the original account 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.
- review-record.md: each stakeholder's position or "no response", the contested items, who decides and by when, about 600 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
- Weighs evidence and risk
- Catches and fixes AI mistakes
- Shows agreement and decisions
- Explains the order
- Orders against capacity

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.
