What is a next action?
A next action is the next concrete step that moves a relationship forward. These are not next actions: "Acme website," "Proposal," "Waiting." These are:- Follow up with Sarah about the proposal on Thursday.
- Send James the progress update promised today.
- Ask Maya to approve homepage version 3.
Why one primary action works
A client may have dozens of open tasks. But from a relationship perspective, one thing usually deserves your attention first.If development can't continue until the client approves the design, you may have twenty implementation tickets, yet the relationship's real next action is "get approval." Everything else is secondary until that's resolved. Choosing one makes prioritization much easier.Sort your day into four groups
1. Overdue. Something should already have happened: an update you promised yesterday, a proposal follow-up due Monday, a client question still unanswered. These come first.2. Today. Actions scheduled for now: send the weekly update, follow up on a proposal, request approval, schedule a call.3. Waiting. The client has the ball: feedback, assets, approval, confirmation. Every waiting item still needs a date when you will look at it again.4. Upcoming. Things that don't need attention yet. This lets you see pressure building before it becomes overdue.Don't sort by deal stage alone
Pipeline stages like Lead, Qualified, Proposal and Won are useful, but they don't tell you what to do this morning. Two prospects can both be in "Proposal sent." One received it yesterday. The other received it nine days ago and hasn't replied. Same stage, completely different action.A next-action view captures that difference.Use reasons, not just reminders
Compare two reminders.Follow up with Northwind.
Follow up with Northwind: no reply six days after the proposal.The second one gives you the context, and makes the message easier to write:
Hi Maya, just checking back on the proposal we sent last week. Happy to walk through the scope together if that would be easier. Does anything need clarifying before you decide on next steps?
Before and after
VagueExecutable
AcmeAsk Acme to approve homepage v3 by Thursday
ProposalFollow up on Northwind proposal if no reply by Wednesday
Waiting on clientCheck for Brightline assets on Monday; if missing, send reminder
UpdateSend James the progress update promised on today's call
Check inAsk Priya how the launch went, due two weeks after go-live
A sample morning
Here's how a ten-minute morning can look with a list like this:- Overdue (1): you promised Acme a revised scope yesterday. Send it now.
- Today (3): follow up on the Northwind proposal, request approval from Brightline, schedule a call with a new lead.
- Waiting (4): Vertex assets are two days late. Send a short nudge. The other three aren't due for a check yet.
Set the next action after every interaction
The easiest way to maintain the system is to make this part of closing the loop:- After a meeting: what happens next?
- After sending a proposal: when will I follow up if they don't reply?
- After requesting approval: when will I check again?
- After receiving a client request: when will I respond?
What if nothing is required?
That's fine. Not every client needs an active task all the time. What matters is that "nothing needed" is a decision, not an accident.There is a big difference between "no next action because everything is fine" and "no next action because we forgot to create one." A good system makes that difference visible.Common mistakes
- Writing several next actions per client. Pick the one that unblocks the most.
- Using nouns instead of verbs. "Contract" is a topic, "Send contract to Alex" is an action.
- Leaving waiting items without a date. They quietly turn into forgotten items.
- Updating only when something goes wrong. Update after every conversation, while you remember it.