Field note · the owner's desk
Have you ever found your team stuck for days, waiting on your yes?
They sent the request and moved on. You meant to look that night. That night became Thursday.
Who this is for
- You still approve what matters: proposals, change orders, rates, hires, spend.
- Requests reach you by email, between twenty others.
- Your team won't chase the owner, so they wait.
When we'd tell you not to bother
If approvals already run through a system with reminders, you're set. If only one or two people need your sign-off, you'll remember them.
The chain
What we see in the chain
- Request sent
- Lands in your inbox
- Buried
- Team waits
- Client waits
- You find it
A finished proposal sits in drafts. A project manager needs a go on a change order. A recruiter needs a rate approved.
Each lands among other mail. Nobody wants to nudge the owner, so the work sits, and the client waits too.
In construction, it's the change order. In a marketing agency, it's the creative sign-off. In an accounting practice, it's partner review.
The fix
The fix we'd build: a decision list
One list of everyone waiting on your yes, oldest first. It's part of a Business Blind Spot Monitor, which works like an executive assistant on steroids.
What that changes
- Every request for your decision lands in one place.
- Each line shows who's waiting, what they need and for how long.
- You clear it in one sitting instead of scattered moments.
- Your people stop waiting, and stop wondering whether to chase.
Worth
What it's worth, by your own count
Count the people who waited on you last week, and the days each one waited.
Those are working days your team spent parked. Picture the same work moving on day one.
Thursday · 8:00 a.m.
Waiting on you: 4 items, oldest first
- Proposal for a dental groupin drafts, 6 days
- Change order 14, warehouse jobasked 4 days ago
- Rate for two forklift driversasked 3 days ago
- Spring campaign budgetasked yesterday
Method
How it runs, every step
+ Show the method
What it works from
Email and calendar requests addressed to you that ask for a decision. Phrases like "need your go" or "waiting on you". Drafts you started and never sent.
The steps
- Spots each request for your decision, and who sent it.
- Checks whether you've already answered, in that thread or another.
- Puts open requests on one list, oldest first.
- Delivers the list when you choose, daily or twice a week.
- Drops an item once you've answered.
Who signs off
Every decision stays yours. The list only shows what's waiting.
What it never does
It never approves for you or answers your team. It never tells anyone you've seen their request.
What we'd need from you
Nothing to start. Later, read-only access to your mailbox and drafts, once you decide. The names whose requests come first.
Neighbouring jobs
- Parked decisions that have come due.
- A morning list of the five things that need you.
- Conversations that went quiet with a question still open.
You become the owner who is never the hold-up.
Nobody waits days for your yes, and the work keeps moving.
Yours will be shaped by your own week. That's what a first conversation sorts out.
Next step
Rather talk it over?
A first conversation with one of our co-founders costs nothing. It runs about an hour, and we need no access.
Someone reads every note, and replies within a working day, usually.