A company is held together by structure. My day was held together by mood
In a company nobody starts the morning asking what we're doing today. The structure of the work answers it: roles, priorities, deadlines, agreements. People arrive on Monday knowing where they're going.
For years my own day began with exactly that question — answered by instinct, by mood, by whatever looked most urgent at seven in the morning. Volume was never the problem: an owner-operator always has more than fits a day, and that's normal, not an emergency. I had no rule for choosing. A manager builds systems for a hundred people and rarely has one for themselves. Their own work gets assigned by a voice in their head.
At best there's a tracker. But a tracker is a warehouse, not a system: everything lands in it, and sorting is manual and starts over every morning. You open it expecting a plan and find a dump — today's work mixed in with things you filed six months ago and haven't touched since. The list grows faster than you can sort it — and at some point you stop opening it at all.
The 159-percent plan I signed off on for myself
That week I read my plan for the first time as a manager, not its author. 46 tasks. By my own estimates, 159 percent of the hours I had. 17 closed. 29 moved into next week, on top of what was already there.
No manager in their right mind signs a plan like that for their team. I signed it for myself. An overloaded plan is not a plan. It's next week's overdue work with a tidy interface.
The irony: that 159 percent was counted in a currency I later threw out. And the second number is no better — 17 of 46 is 37 percent of my own plan. Neither is a measurement; both are symptoms of planning in a unit I don't control.
That conclusion cost CALM a whole section: the hour is the wrong currency. It assumes the day is yours to spend, and for an owner-operator half of it goes to things that didn't exist when the day started. So I dropped time estimates: in CALM a task is described not in hours but in four coordinates — Change · Area · Level · Mode.
It wasn't me. It was the level
I changed tools happily enough — one tracker, then another, eventually Todoist. Two weeks of discipline, and the list would swell again. For a long time I assumed the problem was me. It turned out to be the level.
Over twenty years of management I've tried practically every known way of running tasks. GTD, the Eisenhower matrix, OKR, and the "three most important tasks" rule — each does its own job well. But they work at the level of the portfolio, the priority, the quarter. Life happens at the level of the day. Between "here are your priorities" and "here's what you do today, starting at nine" sits a gap — one each of them, to its credit, leaves to you.
What I saw when I finally measured my own portfolio
Twenty years measuring other people's work; my own, not once. I marked the whole thing up against a single set of rules. Here is the picture:
- 390 live tasks.
- 74 of those weren't tasks at all — they were projects disguised as tasks. "The website," "hiring," "reporting": you can't do them, you can only live in them.
- 316 real tasks.
- 63 carried the top priority — one line in five.
- Of those 63, eight actually moved something forward.
A priority is what you choose at the expense of everything else. When one line in five carries it, nothing has been chosen: that isn't a priority, it's noise.
But the number that matters is eight. The other 55 were holding what already existed. That isn't junk — without it the business stops. Yet a day of almost pure defense is paid for out of the future, and the bill comes later. I was very busy. What I was busy with was defense.
That number is why CALM makes one rule mandatory, not advisable: the place for tomorrow is never left to "if there's time at the end." It's reserved before the day starts.
Until the rules are written down, there is no method
The system came together over years — from practice, not from a book; the first sketches date back to 2025. I'm not the only one running it: for about six months these rules — first spoken, then written down — have held my team's days as well as mine.
As long as they live in your head, they're only a habit — and a habit has two fatal defects.
It can't be checked. Until a rule is written down, you can't say whether you kept it yesterday or quietly got around it — memory adjusts to the result.
It can't be handed over — not to a team, not to another person, not to a machine.
Until the rules are written down, you don't have a method — you have yourself on a good day.
So I sat down and wrote them out in full. That's how a habit became a method: CALM — Change · Area · Level · Mode. I wrote it, and I test it on myself first. A method begins where the rules are precise enough that the same list gives the same day to anyone — to you, to me, to a machine. The text is open: a closed rule can't be checked. I run a daily self-test.
Doing three tasks is easy. Doing the right three is hard
Anyone can close three tasks a day with no method at all. The difficulty is selection: the gap between three random tasks and the right three is the gap between a busy year and a year that produced something.
On a good day instinct chooses. On a bad day anxiety does: you take whatever shouts loudest, not whatever costs the most to skip. An owner-operator has far more bad days than good ones.
The right three aren't chosen by willpower at seven in the morning. They come out of the marking: CALM defines what puts a task into the Focus, and the assistant applies that rule every day. An algorithm chooses, not anxiety — and an algorithm never has a bad day.
What the method does to a day
Four questions per task — Change · Area · Level · Mode:
- Change — does it move you forward or hold you in place: Grow or Stay.
- Area — work or life: Work or Life.
- Level — how important it is that this task gets done: Key, Important, Regular.
- Mode — what mode the task is in: you're doing it yourself (Do), you've delegated it and are waiting for delivery (Delegated), or you're waiting on someone else's answer (Waiting).
The day is then assembled by the 2+1 rule. Two tasks hold your today. One builds your tomorrow. Success of the day = the Focus is closed. The planning currency is places, not hours: six a day — three in the Day Focus, three in the Bonus, which is extra and never a debt. Delegated and Waiting sit apart and take up no places. Everything else gets an honest "not today." Zero overdue by morning. The method turns an endless to-do list into a series of closed days. Full mechanics: heyjimmy.ai/en/calm.
The method is only half the answer
Road-testing the rules made something else clear: the method alone isn't enough. Rules you have to remember and apply by hand won't survive the first hard week — on a hard day you do what catches your eye first, not what's right. You need a tool that holds the rules for you — assembling the Focus in the morning, closing the day in the evening.
That's what I'm building now, where methodology meets AI. The model does what people find hardest: it asks the four questions every day and refuses to accept that "today is a special case."
That's what this blog is about. I'm not selling productivity: I built the method for myself and I'm still its first user. Expect numbers from my own portfolio and write-ups of what got cut from the method and why. If a rule doesn't survive my week, I'll say so as plainly as I just admitted to 46 tasks at 159 percent.
How to try it
Three ways in — take any of them:
- On paper, today. Take your list, ask each task the four questions, assemble three by the 2+1 rule, and close the day in the evening. Starting takes one day and needs no migration; keep the tool you already use.
- The method in full — heyjimmy.ai/en/calm: the marking, the 2+1 rule, the full mechanics of the day.
- Jimmy, the AI assistant — in early access, free with an invite code. It runs on top of Todoist, lives in Telegram, and brings you a ready-made Day Focus every morning: t.me/Hey_JimmyAI_bot. Want these rules running for your team, not just for you? Write to me and we'll figure it out.
I promise nothing in advance. I'll only say how my day differs from the old one: in the evening I know whether it's closed. I never used to. I was just tired.
4 questions · 3 tasks · 1 closed day.
Vasily Chernogorov — author of the CALM method (Change · Area · Level · Mode).