📊 CORE KPI: Level of Disturbance
The Level of Disturbance shows the proportion of tasks that were not originally planned at the beginning of the takt, but were still processed or completed within the takt. This KPI acts as an early warning indicator for operational instability, ad hoc work, or gaps in planning.
🔍 Contents
-
What does the Level of Disturbance show?
-
How is it calculated?
-
Example
-
Data sources and system behavior
-
Notes on takt planning changes
-
Tips & best practices
-
FAQ
✅ What does the Level of Disturbance show?
This KPI helps identify how many tasks are being added spontaneously during a takt. It highlights potential weaknesses in planning or unexpected workload and is useful for improving process stability.
-
0 %: All completed tasks were originally planned
-
> 0 %: Some completed tasks were added during the takt (unplanned)
🛠️ How is it calculated?
The Level of Disturbance is calculated automatically when the takt is closed. It considers all tasks that were not in the "Current Takt" column at the beginning, but were moved there and completed during the same takt.
📐 Formula:
Disturbance Level (%) =
(Number of unplanned completed tasks / Total number of completed tasks in the takt) × 100
📥 Requirements:
-
The takt must be closed using the “✅ Close Takt” button
-
Only tasks completed in the current takt (moved to Done) are included
-
Tasks are considered unplanned if they were added from Buffer or Next Takt during the ongoing takt
🧾 Example:
At the beginning of a takt, there are 8 tasks in the Current Takt column.
During the takt, 3 additional tasks are moved in from the Buffer or Next Takt and completed.
In total, 11 tasks are completed in this takt, including 3 unplanned.
Calculation:
Disturbance Level = (3 / 11) × 100 = 27.3 %
🗃️ Data sources and system behavior
| Component | Description |
|---|---|
| Planned tasks | Tasks that were already in “Current Takt” at the beginning of the takt |
| Unplanned tasks | Tasks moved from “Buffer” or “Next Takt” into “Current Takt” during the takt |
| Completed tasks | Tasks moved to “Done” during the same takt |
| Update frequency | Automatically calculated at each takt closure |
⚠️ Notes on takt planning changes
If a planned task is removed from “Current Takt” during the takt (e.g. moved to “Next Takt”), the system recognizes this as a takt plan change and shows a message:
“Do you really want to change your takt planning? Already planned tasks will still be included in the KPI calculations for Hitrate and Level of Disturbance.”
This means: Even if a task is removed after the takt starts, it still counts as part of the original plan and affects KPI calculations accordingly.
✨ Tips & Best Practices
-
Use the disturbance level to reflect the quality of your planning
-
Identify recurring unplanned tasks (e.g. rework) and integrate them into future takt planning
-
A decreasing disturbance level indicates increasing process stability and planning reliability
-
Combine this KPI with the Hitrate to get a full picture of takt performance
❓ FAQ
How does it differ from the Hitrate?
→ Hitrate measures: Were planned tasks completed?
→ Disturbance Level measures: Were unplanned tasks added and completed?
What counts as unplanned?
→ Any task that was not in “Current Takt” at the start but was added during the takt and completed.
Do tasks from Buffer or Next Takt count?
→ Yes, but only if they were moved into “Current Takt” and completed within the same takt.
Are there filter options?
→ No, this KPI does not currently support filtering by task type, assignee, etc.