Do, Delay, Discuss: The One Rule That Clears an Overloaded Day
Solo builders rarely fail from lack of ideas. They fail from a day that pretends twelve things are equally important.
Do / Delay / Discuss is a forcing function. It is not a productivity aesthetic. It is a way to stop negotiating with yourself in the middle of the afternoon.
The three buckets
Do
Work that needs your hands, your name, or your authority today. If someone else can do it to 80% quality, it does not belong here.
Delay
Real work on a wrong day. Delay is not avoidance if you name the return date. "Someday" is avoidance. "Thursday after the client call" is a plan.
Discuss
Anything that is stuck because it is social: a decision between people, a conflict, a scope fight, a price conversation. If you keep "thinking about it," it probably needs a conversation, not another private draft.
A twenty-minute end-of-day version
Solo operators often need this at 4:40 p.m., not only in the morning.
- List everything still open (brain dump, two minutes).
- Mark each item D, L, or S (Do / deLay / diScuss).
- Keep only three Dos for tomorrow morning.
- Put Delays on the calendar with a time.
- Send one Discuss message before you shut the laptop (schedule the call, do not solve the whole thing in text).
The lies each DISC type tells
- D: "Everything is a Do." No. Speed without selection is thrash.
- I: "Discuss means another brainstorm." No. Discuss means a decision with a person, time-boxed.
- S: "Delay means I am disappointing someone." No. Unnamed overload is what disappoints them later.
- C: "I need a better system before I sort." No. Sorting is the system for today.
When to break the rule
Crises collapse the model. If production is down, you do not workshop the taxonomy. For every other day, three buckets beat a color-coded matrix you will not maintain.
If your week feels like a pile, try one clean Do / Delay / Discuss pass tonight. Then let tomorrow's Morning Brief argue with your list. The tension between the two is useful data, not a failure.