The comparison table§
| System | Answers the question | What is left to the person |
|---|---|---|
| GTD David Allen | "Where do I put my inbox?" | Sorted lists and contexts; what to do today is still your call |
| Eisenhower matrix | "What is important and what is urgent?" | Four quadrants of tasks; a plan for the day does not follow from them |
| OKR | "Where are we going this quarter?" | Goals and metrics; does not work with a daily list |
| "Three most important tasks" Ivy Lee, MIT, 1-3-5 | "What matters most today?" | Three tasks you picked yourself, by intuition; tomorrow the choice is yours again |
| CALM Vasily Chernogorov | "What makes today a closed day?" | A ready Day Focus: three tasks by the 2+1 rule; zero overdue by morning |
CALM vs GTD§
What GTD does. Getting Things Done solves the inbox problem: everything that lands in your head is captured, sorted into projects and contexts, and reviewed on a regular cycle. It is the best known answer to "how do I stop holding it all in my head".
Where GTD goes quiet. Once the list is sorted, GTD says: choose by context, time and energy — which hands the choice straight back to the person. In the morning, in front of a well-sorted list of forty tasks, you are alone with the decision again.
How it fits with CALM. Very well: keep the portfolio by GTD and close the days by CALM. Marking along the four axes is the same processing of inputs, only with a fixed set of answers — and from those answers the algorithm assembles the day without calling on intuition.
CALM vs the Eisenhower matrix§
What the matrix does. It spreads tasks across two axes — importance and urgency — and shows that "urgent" and "important" are different things. A powerful instrument of awareness.
Where the matrix goes quiet. A plan for the day does not follow from the quadrants. The "important, not urgent" quadrant may hold fifteen tasks, and the matrix does not say how many of them to take today. Urgency also moves: by evening half of the "not urgent" has become urgent, and the system does not know it.
How CALM differs. The Level axis asks not "is this important" but what happens if you do not do it — a question with a verifiable answer. And the CALM day matrix is built on Level × Change not for awareness but for selecting three specific tasks.
CALM vs OKR§
What OKR does. It holds quarterly objectives and measurable key results and aligns a team around a shared direction. It works on a horizon of months.
Where OKR goes quiet. Between "the goal of the quarter" and "what do I do on Thursday" lies a gap. OKR does not descend to the daily task list, and does not claim to.
How it fits with CALM. No conflict: set goals by OKR, close days by CALM. The Change axis is the bridge — Grow marks the tasks that move you forward, and the 2+1 rule guarantees them a place in every day. That is exactly how a quarterly objective avoids dying under operations.
CALM vs the "three most important tasks" approach§
What the approach does. The Ivy Lee Method, MIT (Most Important Tasks), the 1-3-5 rule — all of them say the same thing: choose a few main tasks for the day and do them first. Simple advice, and it works.
Where the approach goes quiet. How exactly to choose those three: by eye, from scratch every morning. On a bad day the choice is made by anxiety — the loudest tasks get picked, not the most important ones. And nothing protects a place for the tasks that build tomorrow.
How CALM differs. This is the closest family of methods — the same number three, different mechanics. In CALM the three tasks are produced by an algorithm from the marking: the 2+1 rule reserves a place for a Grow task, the reading order of the matrix is deterministic, and the safeguards know what to do on overload and with stuck tasks.
The main difference§
CALM does not argue with GTD and does not replace OKR. It takes on the level where those systems go quiet: the specific day. Keep the portfolio by GTD, set goals by OKR — and close days by CALM.
The same list gives the same day to anyone.
Task selection in CALM is a function of the marking, not of anyone's opinion. Methods written for humans require interpretation; CALM is formalised to the point where a machine can execute it — which you can try in any language model right now.
Take the method as a whole — the four axes, the day algorithm, the safeguards and the week.