ai-real-deadlines-vs-felt-urgencylisted

# Real Deadlines vs Felt Urgency **The problem this solves:** almost everything feels urgent, almost nothing is, and the few things that genuinely have a closing window rarely feel like anything at all. Plans then get built around the loud items and the quiet closing one is missed — usually noticed weeks later, when the cheap version of it is no longer available. An assistant makes this worse by default. Asked *what should we do first*, it produces a confident ordering, and confident ordering reads as analysis. The ordering is usually driven by whatever was mentioned most recently and most emphatically. ## When to Use - a plan is being sequenced and something is "the priority" - someone says *we should do this today* — and the reason is not yet stated - a task feels urgent and you cannot name what closes if it slips - you are about to work late, cut scope, or skip verification to "make it" - an agent is about to recommend an order of work Do **not** load this when the deadline is already known, external, and written down. Then the question is sequencing, not urgency, and this skill only adds a step. ## The single question For every item: > **What becomes more expensive, or impossible, if this slips — and by how much?** Three honest answers: - **a rising cost** — name it and name the rate. *Renaming is free now and costs the accumulated history later.* That is a real window. - **a hard boundary** — an external date somebody else set. Real, and the rarest. - **nothing