{"id":"pm-one-pager-four-lines","audience":"product-managers","category":"writing-feedback","track":"writing","technique":"constraints","title":"Squeeze a feature idea into a four-line one-pager","free":false,"task":"Your director reads one-pagers in the 5 minutes before portfolio review, and she wants them as 4 lines labeled Problem:, Who:, Proposal: and Success metric:, in that order, each one sentence, plain text. The Who line must name the specific customer segment from your notes, and the success metric must be the one the team agreed on, not the first idea.","materialLabel":"Your brainstorm notes (attached to your prompt automatically)","material":"Brainstorm - \"Repeat last week\" for Shiftly (Nov 12)\n\nProblem we keep hearing: warehouse shift leads rebuild next week's schedule by hand every Sunday, about 2 hours each, even though 80% of it is the same as last week.\n\nWho: mostly warehouse shift leads at sites with 30-80 hourly workers. Retail store managers mentioned it once, but their schedules change a lot more week to week.\n\nIdea: a \"Repeat last week\" button that copies the whole schedule, then flags anyone with approved time off or a new availability conflict so the lead can fix just those.\n\nAlso floated (parked): auto-scheduling with AI, a mobile widget.\n\nMetrics brainstorm:\n- First idea: page views of the scheduling page.\n- Kai: page views will go up even if nobody uses the button, bad metric.\n- Agreed metric (Kai + me): % of active warehouse sites that use \"Repeat last week\" at least 2 weeks in a row within 30 days of launch. Target 40%.\n\nEngineering guess: 3 weeks. Design: Mo has a sketch.\nDirector's note on last one-pager: \"too long, I stopped reading.\"","rules":[{"type":"maxSentences","max":4},{"type":"plainText"}],"mistakes":[{"title":"Saying 'write a one-pager'","why":"The AI writes a full page with headings like Background, Goals, Risks and Timeline.","fix":"Be exact: \"4 lines labeled Problem:, Who:, Proposal:, Success metric:, one sentence each.\"","checks":["maxSentences","r0"]},{"title":"Letting it format","why":"AI defaults to bold labels and headings, which your director's template doesn't use.","fix":"Add: \"Plain text, no bold or headings.\"","checks":["plainText"]},{"title":"Vague 'who'","why":"The AI writes 'managers' or 'our users' because it smooths over the segment.","fix":"Add: \"Who: warehouse shift leads, the segment from my notes.\"","checks":["r1"]},{"title":"Using the first metric","why":"Page views come first in the notes, so the AI picks them.","fix":"Add: \"Use the agreed metric, not page views. Skip parked ideas.\"","checks":["r2"]}],"promptHints":[{"label":"Shows the labels","patterns":["problem:","who:","proposal:","success metric:?"]},{"label":"Limits each line","patterns":["one sentence","single sentence","\\b(4|four)\\b.{0,15}(line|sentence)"]},{"label":"Names the segment","patterns":["warehouse","shift lead","segment"]},{"label":"Picks the agreed metric","patterns":["agreed","not page views","40%","2 weeks in a row"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"A one-pager for a busy director is a format problem. Give the AI the exact labels, one sentence each, the real segment and the agreed metric.","rubricLabels":["Has exactly 4 lines labeled Problem:, Who:, Proposal: and Success metric:, in that order, with no other sections","The Who line names warehouse shift leads (sites with 30-80 hourly workers is a bonus), not a generic 'managers' or retail","The Success metric line uses the agreed metric (share of warehouse sites using Repeat last week 2+ weeks in a row within 30 days, target 40%), not page views, and nothing parked (AI auto-scheduling, widget) appears"]}