A habit system is a staple of productivity methods. In my own system, it does not replace the Kanban: it complements it. The Kanban organizes tasks with a specific outcome to achieve, while habits let you track behaviors you want to repeat over time.
This distinction matters. If you are not yet familiar with the way I structure tasks, I recommend reading the article about the Kanban first. It explains the concepts of tasks, statuses, and DoD used here in more detail.
What defines a habit
A habit has two main characteristics.
The first is the absence of a DoD, or Definition of Done. In the Kanban, a task needs a clear finish line: a state from which you can say it is complete. A habit works differently. You assume that regularly repeating an action will be beneficial, without there necessarily being a point at which it is finished for good.
Walking 10,000 steps today does not mean that the habit of “walking” is complete. You will need to do it again tomorrow, then the day after that. Repetition is precisely the desired outcome: the streak becomes partly an end in itself.
The second characteristic is the simplicity of how it works. A habit generally does not need to change status, depend on another person, or have a long description. Tracking it is mostly up to you: you either perform the action or you do not, then record the result.
Some typical examples:
- Walk 10,000 steps a day;
- Avoid eating sweets;
- Complete one German exercise every day;
- Exercise for a set number of minutes;
- Spend a little time on an activity that helps you switch off.
The content can vary greatly from one habit to another. Some directly improve your health or a skill. Others are lighter, such as learning to solve a Rubik’s Cube. They are not necessarily priorities, but they can clear your mind, add a little play to the day, and make the overall system more enjoyable to follow.
Setting up a simple tracker
The tracking principle is very simple: create a tracker with one row per habit and one column per day, then fill it in regularly. Over time, this view reveals well-established habits, more difficult periods, and goals that may no longer fit your reality.
The most important thing is to choose a system that is quick enough to use every day. If updating the tracker takes several minutes, requires finding data in three different apps, or forces you to interpret complicated rules, it risks becoming a chore itself.
A binary measurement is often enough: you either followed the habit or you did not. This works perfectly for an action such as “complete a German exercise,” provided you have defined what counts as a valid exercise. The day’s result is then 10 if you performed the action and 0 otherwise.
Other habits deserve more nuance. In those cases, you can use a score out of 5 or 10. The scale itself does not matter, as long as it remains understandable and consistent over time. A day scored 8 should mean roughly the same thing the following week; otherwise, the average creates an illusion of precision without providing genuinely useful information.
In my system, I use a score out of 10. This lets me keep the same format for every habit:
- A binary habit scores either 0 or 10;
- A progressive habit receives an intermediate score based on the level reached;
- A negative habit starts at 10, then loses points whenever the behavior I want to avoid occurs.
For “avoiding sweets,” for example, the day theoretically starts with a score of 10. The score decreases if I eat something I was trying to avoid. This downward scoring system allows positive and negative habits to coexist in the same table without building two separate systems.
There is no need to aim for scientific accuracy, however. The value of the score is that it makes a trend visible and prompts a small moment of awareness when you fill in the tracker. If you need to write a twenty-line rubric to decide between 6 and 7, the measurement has become more burdensome than the habit itself.
The streak as a reward
The most immediate reward is often the streak: the number of consecutive days on which you followed a habit. Watching a streak grow makes you want to avoid breaking it and gives visible form to an effort that might seem insignificant one day at a time.
You can also track an average score over a week, month, or sprint, then compare it with a target. This approach is sometimes more flexible than maintaining a perfect streak. One bad day does not erase all the work that came before, and you can aim for realistic consistency instead of permanent perfection.
The two indicators do not tell exactly the same story. The streak rewards continuity; the average rewards the overall level. For a very simple binary habit, the streak is often meaningful. For a progressively scored habit or one subject to normal fluctuations, an average can be more useful.
There are many specialized apps that add reminders, rewards, and various forms of gamification. Habitica, for example, turns habits and tasks into elements of a game. This type of tool can be motivating if that framing appeals to you.
In my opinion, the app matters less than how easy the tracker is to access. One good option is to place it directly beside the Kanban, on the same screen. In my case, I use a custom app: a small panel appears to the left of the board. I can therefore review my tasks and update my habits in the same place, while keeping the two mechanisms clearly separate.
Why habits are powerful
Habits are often what make lasting change possible. A task can produce an important but one-off result. A modest habit, repeated over several months, can gradually transform your health, learning, or daily organization.
In my view, this even makes habits one of the most powerful levers in a personal system. A habit depends less on external conditions than a complex professional task. You cannot always control a client’s response, a delivery date, or a colleague’s availability. But you can decide to walk, complete an exercise, or follow a dietary rule today.
This control is obviously not absolute. A busy day, an illness, or an unexpected event can break a streak. The tracker should not become a tool for making yourself feel guilty. Its purpose is to observe the long term and make it easier to return to the habit, not to turn every lapse into a permanent failure.
It is also useful to choose habits that are compatible with one another. If they all demand a lot of time, the same kind of energy, or the same part of the day, they will quickly compete. A few foundational habits can, by contrast, coexist with smaller, lighter activities. Exercising every day may require real organization; learning to solve a Rubik’s Cube may simply offer a pleasant break.
Making habits and Kanban work together
Kanban tasks and habits are not managed in the same way. Tasks are structured, have a DoD, change status, and may depend on many people. Habits are repetitive, generally self-contained, and tracked with a score. Trying to force everything into a single model would make the system harder to read.
Even so, the two approaches complement each other very well. The Kanban helps move specific outcomes forward; habits sustain useful behaviors over time. Displaying them in the same place provides a shared view without confusing the two.
The boundary remains fluid. A habit can become a task when a one-off goal emerges. “Running regularly” belongs in a tracker; “running the Paris Marathon” has a clear finish line and deserves a card in the Kanban. Conversely, a task can give rise to a habit when you realize that the outcome mainly depends on regular repetition.
A habit can also directly support one or more tasks. Regular running sessions contribute to marathon preparation. Daily German practice can support the task “pass the B2-level exam.” In this case, the tracker measures consistency while the Kanban holds the preparation, registrations, deadlines, and final outcome.
Choosing habits for the right time horizon
Some habits are meant to remain for years. They correspond to stable principles: moving every day, maintaining a skill, or limiting a behavior whose negative effects you know.
Others can be temporary. You may decide to track a practice for a few weeks to support a goal, test its usefulness, or get through a particular period. A habit does not need to last forever to be relevant.
In my system, habits are selected or adjusted at the beginning of the sprint. This is a chance to check that they still fit the current priorities and available capacity. The point is not to change the whole list every time, but to ask whether a new habit is worth testing, whether an old one should be paused, or whether a target has become unrealistic.
I will explain sprints and their rituals in detail in a dedicated article. For now, it is enough to remember that this review prevents habits from piling up indefinitely. Like the rest of the system, the tracker should remain alive: stable enough to reveal trends, but flexible enough to evolve with your needs.
In summary
A habit is not simply a task without a date. It follows a different logic: there is generally no DoD, the outcome comes from repetition, and tracking can remain very lightweight. A daily tracker, a consistent score, and a few simple indicators are enough to observe progress.
The streak can provide immediate motivation, while the average offers a more forgiving and accurate view of the long term. In both cases, measurement should help you act, not become a complex exercise or a source of guilt.
Finally, there is no need to choose between habits and Kanban. Habits build continuity; Kanban drives tasks toward a specific outcome. Placed side by side and reviewed in time with your sprints, they cover two different but closely connected dimensions of the same productivity system.