How the 80/20 approach worked
In a 37-hour week, that meant 29.6 hours for customer work and 7.4 hours for everything else. We used those figures to plan the team's time. An individual developer's week could look quite different.
How the remaining time was used
When the buffer was not needed for unexpected tasks, it could be used for upskilling, knowledge sharing and team activities. We also set aside every other Friday for learning. That gave the team room to work with new methods and tools without having to hide the time in a customer task. I experienced more calm and better retention, and employees stayed four to five years on average. I cannot reduce that to a single cause, but it supports my experience that planning and wellbeing go together.
When priorities changed
I have prioritised the work together with my partner Lasse Ingerslev Koitzsch and with a Product Owner, and aligned needs, quality and capacity with our customers' decision-makers. A plan only creates value when everyone knows what matters most, what can wait and who decides. That conversation can be difficult, but it is better than a promise the team cannot keep.
In a new team I'd first ask what usually interrupts a working week. Their answer matters more for planning than the percentage we used at Modified Solutions.
Contact: kontakt@tomc.dk · +45 299 297 67