Maker Time Versus Meeting Debt
How UK product engineering teams can quantify calendar load and reclaim deep-work hours without gutting collaboration.
Most engineering calendars grow by accretion. A stand-up here, a sync there, a status forum that never ended — and suddenly senior developers protect their only quiet hours after 18:00. Measuring meeting debt starts with a blunt inventory: total recurring hours per role, percentage of context switches mid-block, and the average gap between meetings that is too short for real work.
Once you have numbers, set a maker-time floor. For feature-heavy squads we often recommend protecting two consecutive half-days each week for individual contributors, with leads absorbing the coordination load in defined windows. The policy only sticks when product and engineering leadership publish the same rule and honour it when stakeholders ask for “just a quick call.”
Pair this with an async review culture. Pull requests that wait for a live walkthrough create invisible queues. Written context, annotated diffs, and a 24-hour review SLA usually beat another hour on a video link. Track both meeting hours and median PR wait time for a quarter; the correlation is rarely subtle.