Put a Best-Before Date on Stories

Definition

Time-constrained work is a blind spot in flexible backlogs: an item can sit as "low priority" for months, then suddenly become an emergency in the last week before its real deadline — not because the deadline moved, but because it was never captured. The fix is procedural: require an explicit "best before" date when a stakeholder proposes a story, tag those stories visibly and separately from the rest of the backlog, and schedule them early enough to avoid a last-minute scramble — while guarding against "rotten fruit" stories whose proposed deadline is already almost here.

In the Book

Chapter 2's example is a regulatory-reporting request raised six months ahead of a compliance deadline, repeatedly bumped by "more important" work until the financial controller panicked a week out and the team dropped everything to firefight — followed weeks later by a second, unrelated stakeholder causing the identical pattern. Reviewing six months of planned-versus-actual work, the team found this was systemic, not a one-off: both sides blamed the other (the business saw an unproductive, uncaring team; the team saw stakeholders randomly reshuffling priorities), when the actual failure was that nobody had surfaced the timing constraint early enough to plan around it. The fix — require and visibly flag a best-before date at proposal time, using a separate lane, differently shaped or colored cards, or a shared deadline calendar — let the team absorb deadline-driven work at a sustainable pace instead of in a scramble, while a minimum lead-time rule (a best-before date must be at least a month out) stopped stakeholders from gaming the system with already-urgent "rotten fruit" requests.

Why It Matters

Genuine emergencies are rare; most "urgent" work is actually a known deadline that stayed invisible until it became one. Making the deadline a required, visible field at intake — not a data point extracted only once someone is already panicking — converts a recurring trust-eroding firefight into ordinary scheduling, and preserves the team's ability to actually respond fast when a real emergency does arrive. The same discipline (surface the deadline at intake, not at the crisis) applies to any queue absorbing requests from multiple stakeholders with different, uncommunicated time horizons — support tickets, procurement, compliance work, editorial calendars.