# Prepare an industry analyst briefing

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

## Situation and outcome
Mornavik is a fictional developer-platform company of about 220 people. Its product, Peldravon, runs workflows and AI agents durably: runs survive crashes and deploys. An industry analyst firm, Ardmell Research, is writing its landscape of workflow orchestration platforms and invited Mornavik to brief it (R001). Ardmell sent a ten-question questionnaire (R002). You are the Peldravon product manager. The analyst relations lead (the AR lead) owns the relationship and sends everything to Ardmell; you prepare the deck and the written answers (R003).

Your outcome is a briefing pack ready for the clearance review: a deck, written answers to all ten questions, an evidence table and a clearance note. The pack goes to the AR lead on Monday 19 October at 12:00, the Head of Communications and legal counsel review it on Tuesday 20 October at 10:00, and the AR lead sends it to Ardmell at 17:00. The briefing itself is on Thursday 22 October. Every answer must be true and also inside what Mornavik may say outside; where it is not yours to decide, put the decision to the reviewer with proposed wording. A pack that holds a topic back with an honest holding line, or that recommends rescheduling the briefing until a wording is cleared, is a valid result. Your pack does not clear anything, send anything to Ardmell, contact customers or partners, or commit dates.

The period is 2026-01-15 through 2026-10-16 inclusive; the snapshot is Friday 16 October, morning. Work with 65 records (Ardmell's emails and questionnaire, disclosure and reference policy, the cleared roadmap, internal roadmap notes, owner-confirmed figures, incident and security records, CRM rows, benchmarks, pricing and leadership messages) and an AI first draft of the deck and answers that Mornavik's AR-prep agent prepared on Thursday evening. The draft is a draft, not an authority, and it has not been cleared. All figures are synthetic, so answer from the records supplied: outside knowledge of real companies 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 deck and the written answers. Choose and reconcile the sources, tag each answer cleared, needs clearance or defer, propose wording for every reviewer decision and write the clearance note. You may recommend what to say; you may not clear material, send anything to Ardmell, name a customer or partner without permission, or commit dates beyond the cleared roadmap.

## About the team
A developer-platform team preparing a written briefing pack for an industry analyst, to be cleared by communications and legal before the analyst relations lead sends it.

An AR-prep agent drafts decks and questionnaire answers from the wiki, the internal roadmap, battlecards, the CRM, the status page, the website and dashboards; sales engineering runs an AI benchmark harness; reps tag CRM opportunities; a person checks every figure against its owner before it goes to clearance.

The PM owns the deck, the answers and the proposed wording; finance, the data team and SRE own the figures; customer marketing owns reference permissions; the Head of Communications with legal counsel clears everything external; the analyst relations lead owns the relationship and sends the pack.

## Work to complete
1. Read the questionnaire (R002), the AR lead's brief (R003) and sources/coverage-and-access.md. Then read planning/briefing-pack-outline.md for the house deck outline and the three disclosure tags.
2. Audit the AI first draft against the original records. Keep, correct or reject each row and say why. Tell apart a figure its owner confirmed, a claim someone made, an internal plan and something cleared for outside use, and keep evidence that points the other way visible.
3. Count the quantities your answers state, for example customers, customers who moved from Ravnelrun, reference customers who may take an analyst call and accounts hit by the incident. Count organisations rather than rows, count a repeat, a copy or a relay once, and state the definition each count uses. How Ardmell will score is not known.
4. Write the answers to Q01 to Q10 and the deck. Tag every answer cleared, needs clearance or defer. Your tag is a proposal: cleared means the answer uses only material already cleared for outside use, and the whole pack still waits for the reviewer. Put anything you cannot say on the defer list with an honest holding line and a follow-up route.
5. Where an answer or a wording is the reviewer's call, say so, give your proposed wording and name an owner. Name follow-on work without starting it.
6. Apply the correction note (U001) from your download, as you would any other source. Carry each justified revision through every file and keep the earlier reading visible. The corrections log is your own account of how you worked.
7. Hand off clearly: what changed from the draft, what the reviewer must decide, who owns each open item, and what is not cleared.

## 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-clearance-precheck-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).
- briefing-deck.md: the deck, one slide for each level-2 heading, at most 10 slides and at most 600 words. If the correction note (U001) gives a smaller slide limit, the smaller limit applies to your revised file.
- answers.md: Q01 to Q10, each tagged cleared, needs clearance or defer, then a defer list with a holding line for each deferred topic. At most 1,200 words.
- evidence.csv: it already has one row for each record, R001–R065, with the record ID and the organisation ID filled in. Fill in the empty columns on every row: the question the record bears on most (deck, Q01 to Q10, defer or context), how you use it, and a one-sentence reason. For how you use it, supports, contrary, confirmed figure, unconfirmed figure, needs clearance, defer, claim, context or not used are suggested and your own words are accepted. Do not add, delete or retype record or organisation IDs. If the correction note (U001) changes a record, revise its row in place, put U001 in the evidence_version column, and keep the earlier reading visible in your reason or the clearance note.
- clearance-note.md: at most 500 words in all, so keep the corrections log short: one line for each draft row you changed or rejected, with the records checked and the before and after. Spend most of the words on the reviewer decisions. The note holds: the corrections log, then the reviewer decisions with your proposed wording and an owner for each, then what is not cleared.

Keep every file within these limits: the reviewer reads all of it. Words in prose and in table cells count toward a limit; headings, table borders and other markdown symbols do not, and the README and evidence.csv are not counted.

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 figures
- Weighs uncertainty and risk
- Checks and fixes the AI draft
- Hands off clearly
- Explains the reasoning
- Says only what is cleared

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.
