Module 12 — Expert Kavanah · Lesson 12.1
A Day in Expert Kavanah
The morning loop, the working middle, and the two-minute close
~10 min
What you'll learn
- Run a morning loop that decides the day in fifteen minutes
- Keep the board reflecting reality without it becoming admin
- Close the day in two minutes
- Identify which part of the routine is failing when the day goes wrong
A product is only as good as the routine someone builds around it. This is the routine — not aspirational, just what the surfaces are actually shaped for. It takes about twenty minutes of the day in total, and almost all of the value is in the first fifteen.
The morning loop: fifteen minutes
Read the digest. If you scheduled My Daily Digest, it is already in your inbox and it has told you what is due, what is overdue, and what changed. You have started before opening the app.
Open the dashboard and read the right rail. Briefing, agent alerts, notifications, activity. This is where a parked approval, a broken integration or a mention surfaces, and it is a two-minute scan.
Clear the approval queue. Anything the agent parked overnight. Doing this first means the work it was waiting on can proceed while you do everything else.
Open My Work and pick the day. Two or three things that are actually today, moved into a working status so the board says what is true.
That is the loop. Fifteen minutes, and the rest of the day has a shape.
The working middle
Three habits, none of them ceremony.
Capture immediately with c. A thought about work becomes a task in two keystrokes. Do not batch this; batching is how things get lost between the thought and the sitting down.
Delegate the tedious parts to the agent as they arise. Summarize this thread. Draft that reply. Find the slot. Break this brief into tasks. Each of those is a minute you did not spend, and the aggregate over a week is the actual return on the product.
Put decisions on the work, not in chat. If a conversation determines something about a task, the determination goes in the task's comments. This is the single habit that most changes whether a workspace explains itself in three months.
The close: two minutes
Close what is done.
For anything you expected to finish and did not, either change the date or say why in a comment. Not both, not neither. This is the step that keeps due dates meaning commitment rather than becoming decoration.
Log your time roughly, if you track it.
That is it. Two minutes, and the effect is that tomorrow's digest is about reality and your calibration data is real.
When the day goes wrong
The failure is almost always locatable in one of the three phases.
If the day had no shape, the morning loop did not happen. Usually because the digest is not scheduled, so there was nothing to start from.
If work got lost, capture failed. Something was agreed and never written down — which is what task capture and triage exist for, and which is worth turning on if this is a pattern.
If the board disagrees with reality, the close did not happen. This is the most common, because it is the phase with no immediate cost — the price is paid tomorrow, by someone reading a board that lies.
Diagnosing which phase failed is more useful than resolving to try harder, because each has a different fix.
Run the loop tomorrow
- 1
Schedule the daily digest tonight
Or ask the agent to. Without it, the morning loop has no starting point and usually does not happen.
- 2
Start tomorrow on the dashboard rail
Briefing, agent alerts, notifications, activity. Two minutes, and it is where problems surface first.
- 3
Clear the approval queue before anything else
It unblocks work the agent is waiting to do while you get on with the rest of the day.
- 4
Close what is done; re-date or comment on what slipped. This is the step with no immediate cost and the largest delayed one.
What to watch
- Morning-loop consistency
- How many working days start with the digest and the dashboard rail.
- Healthy signal: Most of them. This is the habit the rest of the routine hangs off.
- Board-reality agreement
- How often what people are actually working on matches what the board says.
- Healthy signal: Daily. Divergence makes every downstream number — capacity, cycle time, the digest — a description of a fiction.
- Approval queue age at end of day
- Whether anything is still parked when you finish.
- Healthy signal: Empty. A queue that survives the day teaches people the agent does not work.
Key takeaways
- ·Morning loop: digest, dashboard rail, approval queue, pick the day. Fifteen minutes.
- ·Capture with c immediately — batching is how things get lost between thought and desk.
- ·Decisions about work go in the task's comments, not in chat.
- ·The two-minute close is what keeps due dates meaning commitment.
- ·When a day goes wrong, locate which phase failed rather than resolving to try harder.
Next: the loop that runs at week and month scale.