Turn old deliverables into interactive site artifacts — step 2 of 3

Build-brief checkpoint. You just saw a finished brief for the weekly status update. Now write that brief yourself from the story below.

The scenario. Every Monday someone pastes last week's update into a long weekly status email. The people who actually read it are the people who have to act on it this week. What they really need to decide is which two items need a push. The raw material already exists: last week's update, the tracker export, and owner notes. A small site could show a timeline, owners, risks, and open decisions — and let a reader filter items by owner and status. Two catches: numbers lag a day, and customer names can't appear on a shared page. You'd call it done when a reader can name the two push items in under ten minutes. It could live at /internal/weekly-status or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the incident postmortem. Now write that brief yourself from the story below.

The scenario. Someone drops an incident postmortem on the on-call team picking this week's follow-ups. What they really need to decide is which two follow-ups ship this week. The raw material already exists: the postmortem, the timeline, and the ticket export. An incident follow-up site could show a timeline, services, actions, and owners — and let the team filter actions by service and owner. One catch: customer identifiers stay redacted. You'd call it done when the team can name the two follow-ups in under ten minutes. It could live at /internal/incident-followups or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the campaign brief. Now write that brief yourself from the story below.

The scenario. Someone forwards this week's campaign brief and asks the campaign team locking this week's ship list to make the call. What they really need to decide is which two assets slip. The raw material already exists: the brief, the asset list, and channel owners. A campaign ship-list site could show channels, assets, dates, and blockers — and let a lead filter assets by channel and status. Two catches: legal review is pending on one claim, and dates move. You'd call it done when a lead can name the two slipping assets in under ten minutes. It could live at /internal/campaign-ship-list or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the brand-review deck. Now write that brief yourself from the story below.

The scenario. Someone drops a brand-review deck on the reviewers signing off this week's assets. What they really need to decide is which two pieces get redone. The raw material already exists: the deck, the design kit, and the export folder. A kit review site could show assets, kit rules, notes, and decisions — and let a reviewer filter assets by type and kit fit. One catch: licensed photography can't leave the folder. You'd call it done when a reviewer can name the two redo pieces in under ten minutes. It could live at /internal/kit-review or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the weekly queue report. Now write that brief yourself from the story below.

The scenario. Every Monday someone pastes ticket counts into a long weekly queue report. The people who actually read it are support leads planning staffing. What they really need to decide is which queue gets the extra agent. The raw material already exists: the ticket export, last week's report, and the on-call notes. A queue staffing decision site could show queue volumes, wait times, and week-over-week — and let a lead filter by queue. Two catches: ticket data lags a day, and customer names can't appear on a shared page. You'd call it done when a lead can pick the extra-agent queue in under five minutes. It could live at /internal/support-staffing or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the claims spreadsheet. Now write that brief yourself from the story below.

The scenario. Someone dumps the claims spreadsheet on the editors clearing copy before it ships. What they really need to decide is which claims stay. The raw material already exists: the spreadsheet, the source docs, and last week's struck list. A claim-check site could show claims, sources, status, and struck lines — and let an editor filter claims by status and product. One catch: unpublished numbers can't appear on a shared page. You'd call it done when an editor can name the claims that stay in under ten minutes. It could live at /internal/claim-check or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the research readout. Now write that brief yourself from the story below.

The scenario. Someone sends a research readout to the person who has to pick a finding to act on. What they really need to decide is which finding to act on. The raw material already exists: the readout, the cleaned export, and the method note. A findings decision site could show cuts, receipts, caveats, and open questions — and let a reader filter findings by segment and confidence. Two catches: the source file is one week stale, and raw PII can't appear on a shared page. You'd call it done when a reader can name the finding to act on in under ten minutes. It could live at /internal/findings-decision or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the Q3 roadmap presentation. Now write that brief yourself from the story below.

The scenario. Someone walks directors deciding Q3 scope through a Q3 roadmap presentation. What they really need to decide is which two initiatives need scope cuts. The raw material already exists: roadmap slides, launch dates, owner notes, and the risk register. A Q3 roadmap decision site could show a timeline, initiatives, risks, constraints, and a decision log — and let a director filter initiatives by team and delivery confidence. Three catches: staffing gaps, launch dependencies, and a compliance review. You'd call it done when a director can compare initiatives and name the two scope cuts in under ten minutes. It could live at /internal/q3-roadmap-decision or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the interview debrief packet. Now write that brief yourself from the story below.

The scenario. Someone dumps interview notes into an interview debrief packet for the hiring panel deciding who advances. What they really need to decide is which candidate advances. The raw material already exists: debrief notes, the score sheet, and the job brief. A panel decision site could show candidates, receipts, open questions, and a decision log — and let the panel filter notes by candidate and competency. One catch: candidate names stay on a restricted page. You'd call it done when the panel can name who advances in under ten minutes. It could live at /internal/panel-decision or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the SOP packet. Now write that brief yourself from the story below.

The scenario. Someone hands the on-call lead running tonight's process an SOP packet. What they really need to decide is which handoff is blocked. The raw material already exists: the SOP, last night's notes, and the approval list. A handoff decision site could show steps, owners, gates, and exceptions — and let a lead filter steps by owner and approval status. One catch: customer names stay off the shared page. You'd call it done when a lead can name the blocked handoff in under five minutes. It could live at /internal/handoff-board or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.

Build-brief checkpoint. You just saw a finished brief for the privilege review memo. Now write that brief yourself from the story below.

The scenario. Someone drops a privilege review memo on the partners deciding what can leave the firm. What they really need to decide is which passages stay privileged. The raw material already exists: the memo, the source contract, and the cite list. A privilege decision site could show clauses, citations, privilege calls, and open questions — and let a partner filter clauses by matter and privilege status. Two catches: work product stays internal, and client names can't appear on a shared page. You'd call it done when a partner can name the passages that stay privileged in under ten minutes. It could live at /internal/privilege-review or this brief.

Your job. Pull each value out of that story and fill in the brief dictionary. This is judgment work, not copy work: the story doesn't label which sentence is the audience, the decision, or the acceptance criteria — you decide.

Write the values in your own words. Close counts: capitalization, spacing, and small wording differences won't fail you, and if your version is close you can mark yourself correct. If you get stuck, skip or show example & continue.