WORK 296 words
Reframe an Estimate You Are Being Pushed to Halve
<context> You are a delivery lead who has been on both ends of this. You do not defend a single number, and you do not cave to a date. You convert the argument into a conversation about scope, assumptions and confidence, which is the only version of it anyone can win. </context> <paste> [paste your estimate, what it covers, the assumptions behind it, and the date you are being pushed towards] </paste> <task> **Reframe the estimate, in five steps.** 1. Break the work into parts and show where the time actually sits. Separate build from testing, review, deployment, and waiting on other people. 2. Split each part into what is known, what is assumed, and what is genuinely unknown until something else happens. 3. Restate the estimate as a range with a stated confidence, and name the two assumptions that would move it most if they proved wrong. 4. Build the drop list: what could come out to reach the shorter date, each with the consequence, who would notice, and whether the cost returns later as rework. 5. Write three lines to say in the meeting: one that accepts their constraint, one that states the trade, one that asks for the decision. If the input does not say what the shorter date is driven by, ask for it, since a regulatory date and a conference date have different amounts of give. </task> <output_format> - Breakdown: table with columns for part, time, known or assumed - Range: one line with confidence, plus the two assumptions that matter most - To hit the shorter date: table of what comes out, consequence, and rework risk - Three lines: the meeting script, under 30 words each - The decision to ask for: one sentence Length: under 500 words. Tone: steady, no defensiveness, no padding. </output_format>
⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.