Skip to content

Request or topic? The one-page guide

One page for your team channel or the wall by the planning board: what a request has to say before anyone sizes it, and what to send back when it does not.

Play the two-minute game

Request or topic?

Before you size it, schedule it or say yes, look for three things.

  • The need

    What should change, or what problem exists.

    If it is missing, ask:"What should be different afterwards?"

  • The impact

    Who is affected, and what happens if nothing changes.

    If it is missing, ask:"Who does this affect, and what happens if we leave it?"

  • Why now

    The deadline, event or pressure behind it.

    If it is missing, ask:"What makes this matter now?"

Decidable = the need, plus the impact or why now.

A deadline and a senior name are not a need. If nobody can say what should be different afterwards, it is a topic, however urgent it sounds. Send one question back, not a meeting.

CEO, by direct message
Dashboard. Customers keep asking. Before the conference would be great.

Send it back. There is pressure and there is a date, so it feels urgent and real — but nobody knows what the dashboard should show. A date on an unknown is how the worst commitments get made.

Finance, by email
The quarterly revenue report takes 40 minutes to run and it blocks the close. Can it run in under five?

Decidable as it stands. No deadline, and it does not need one: the need and who it hurts are both stated. Short is not the same as vague.

Eight more like these, two minutes:
deliverysheet.com/spot-the-request

The rule on the sheet is the one this product holds at its front door, and the one the free request check applies to a message you paste. Why a deadline alone does not make a request is argued in a topic is not a request.