Calm planning
Calm planning is planning that stays lightweight, continuous, and grounded in reality. It avoids turning planning into work, and instead focuses on keeping the next decisions clear.
It’s not “no planning”. It’s planning that prefers order, ownership, and finishing over prediction.
If you already have an account: sign in.
What calm planning optimizes for
- Clarity about what matters next.
- Flow from idea → decision → done, without ceremony.
- Focus by limiting parallel work and handoffs.
- Trust through visible progress instead of status theatre.
The core idea: plan by order, not prediction
Calm planning treats a plan as an ordered set of decisions, not a forecast. You keep the order current, you make the next choice, and you move work to done. The plan evolves as you learn.
Instead of spending energy on long-range certainty, calm planning invests in a short, stable horizon: what we are doing now, what we are doing next, and what we are not doing yet.
How it looks in practice
Calm planning can be run with a simple weekly (or twice-weekly) planning moment. The purpose is not to “estimate the future”, but to keep work moving and reduce uncertainty.
1) Keep ideas separate from work
Ideas, requests, and discussion belong in idea items. Work belongs in todos. Calm planning keeps these separate so that work stays actionable, and ideas keep their context.
2) Decide what becomes work
During planning, you pick the next few items worth doing, convert them into actionable todos, and assign ownership. Everything else stays as context until it is truly needed.
3) Limit work in progress
Calm planning protects focus. If too much is active at once, nothing finishes. Keep WIP low and finish before starting new work.
4) Measure progress by done
Progress is not “how much we talked about work”. Progress is what moves to done. Calm planning makes completion visible and uses it as the feedback loop for planning.
When calm planning is a bad fit
Calm planning is not designed for every situation. It can be a poor fit if:
- You need strict, long-range commitments with fixed scope and dates.
- Your organization requires heavy reporting based on estimates and forecasts.
- You depend on large upfront planning phases before any work can begin.
If you still want to try it, start small: one team, one project, and a short horizon. Let the results decide.
Next
No third-party login. Email + password only.