Small Daily Fixes Instead of One Big Quarterly Overhaul

Borrowed from lean manufacturing, a kata is a small, repeated practice: each day, someone on the team notices one point of friction in their own work, however minor, and either fixes it directly or logs it for a fix. The daily size matters. A commitment to find and address one small thing is achievable every single day in a way that a commitment to a bigger improvement rarely is, and consistency is what actually compounds over a year.

The word kata itself comes from a martial arts practice of repeating a small, precise sequence of movements until it becomes second nature, and the borrowed idea carries over cleanly here: the specific fix matters less than the discipline of doing the small practice consistently, day after day, without skipping.

The first few weeks of a kata practice should focus purely on noticing friction and writing it down, without pressure to fix everything immediately. Teams that jump straight to fixing often pick the easiest, most visible friction repeatedly while ignoring subtler but more costly patterns that take longer to notice. A simple running list, reviewed weekly, surfaces which friction points show up most often and deserve attention first.

Resist the urge to skip this phase because it feels slow. The teams that build a genuinely durable habit are almost always the ones that spent real time just noticing before their first fix, rather than rushing straight to action and burning out on the habit within a month.

A kata fix should typically take under thirty minutes: renaming a confusing field, adding a missing step to a checklist, fixing a broken link in a shared document. If a noticed friction point needs a bigger fix, that's fine, but it graduates out of the daily kata into a proper project with its own scope, rather than stalling the daily habit while someone tries to solve it all at once.

The discipline of graduating bigger items out, rather than letting them stall the daily habit, is what keeps the kata sustainable. A practice that occasionally demands a multi-hour fix stops feeling like a light daily habit and starts feeling like an unpredictable extra job.

A good daily kata fix meets these tests:

• It takes under thirty minutes, such as renaming a confusing field or fixing a broken link in a shared document.
• It addresses friction the person noticed in their own work, not a problem handed down from somewhere else.
• It is logged where the team can see it, so recent fixes build visible momentum.
• Anything bigger graduates into a proper project with its own scope, instead of stalling the daily habit.

A kata that lives entirely in one person's head or personal notes doesn't build team-wide momentum. A shared, lightweight log, even a simple running list in a tool like ClickUp, where anyone can see what's been fixed recently, turns an individual habit into something the whole team can see compounding, which reinforces the habit far more than doing it in isolation.

Seeing a teammate's small fix logged is often what nudges someone else to notice and log their own, especially in the early weeks before the habit has really taken hold across the team.

Individually, each kata fix is too small to notice. Collectively, a quarter's worth of small fixes is often substantial, and reviewing the accumulated list every quarter, what actually got fixed and what friction points are still recurring, gives the daily habit the same kind of periodic checkpoint a bigger initiative would get, without losing the daily cadence that makes it work.

This quarterly review is also where you catch a friction point that keeps appearing on the daily list without ever getting properly fixed, a sign it belongs in a real project rather than staying stuck as a recurring small annoyance nobody has time to solve properly.