> ## Content Index > Fetch the complete content index at: https://debugly.dev/llms.txt > Use this file to discover other available public pages before exploring further. # Meetings Are a Tax on the Maker Schedule - URL: https://debugly.dev/meetings-tax-maker-schedule/ - Published: 2026-10-09T12:46:00.000Z - Updated: 2026-10-17T05:56:39.000Z - Description: A calendar with a meeting every afternoon does not look expensive, because the cost is invisible: it is the morning deep work that never starts, fragmented… - Author: Rohit Bhadani - Tags: Opinion, Engineering Culture Here is the thesis. The two kinds of work in a software team run on incompatible schedules, and the calendar is where the manager schedule, which spends time in slices, routinely outbids the maker schedule, which spends it in long unbroken blocks, and because the cost of the fragmentation is invisible, it is never priced, never budgeted, and never defended. The result is a team that is busy every day and ships less every week, and a calendar that is the receipt for a tax nobody voted for. I am not arguing that meetings are worthless. Coordination, decision and alignment are real work with real value. I am arguing that their cost is systematically miscounted, because the cost is paid by a different person's attention at a different time than the meeting happens, and costs that are displaced in time and person are the easiest costs to ignore. ## The two schedules The manager schedule is in hour units, and an hour spent in a meeting is an hour spent, fully accounted, with the next hour standing ready. The maker schedule is in half day units, because deep work, holding a large mental model in RAM, debugging a race, designing a schema, requires a long ramp in which the model is loaded, and the value is produced in the hours after the ramp. A meeting in the middle of a maker block does not cost the meeting's hour. It costs the block, because the ramp is broken and the model must be reloaded, and the hour before the meeting is often too short to start, so it is spent in shallow work, and the hour after is a second ramp. One one hour meeting can consume a half day, and the calendar shows only the hour, which is the accounting failure at the centre of the tax. ## Why the cost is invisible The fragmentation is invisible for three reasons, and each is worth naming because each has a counter. The cost is paid in work that does not happen, and absent work leaves no artefact. Nobody sees the design that was not started, the bug that was not chased, so the loss is a counterfactual, and counterfactuals lose every budget discussion. The cost is paid by the maker while the meeting is attended by the manager, so the person spending the tax is rarely the person booking it, and the booking is free for the booker, which is the tragedy of every shared resource. And the cost is smoothed, because a fragmented day still feels busy, the maker answers messages between fragments and reads as productive, so the calendar looks full and the standup sounds fine, and the signal that deep work died is the missing large deliverable, which arrives quarterly, too late to connect to the calendar that caused it. ## The counterargument, fairly The honest defence is that coordination is not optional, and a team that never meets does not align, and the alignment failures, duplicated work, wrong direction, are also taxes, paid in rework, which is real. I accept it fully. The defect is not meetings, it is the absence of a price, and a team that has priced its coordination can have less of it and more, deliberately. There is also the junior engineer's reality, for whom meetings and pairing are the ramp, and the maker schedule defence can become a senior privilege that starves the people who need context transfer. The block protection should be distributed, not hoarded, and the maker blocks for juniors are where the teaching happens in depth. ## What priced coordination looks like The teams that handle this well share practices, and none of them abolish meetings. They make the block a visible, owned resource: maker blocks on the shared calendar, defended by default, so the block is an entry on the receipt, and booking across it requires a deliberate decision, which is the price appearing at the point of sale. They batch the slices: meetings clustered at the edges of the day or in designated coordination days, so the fragmentation is concentrated rather than sprayed, and the maker blocks survive intact, because ten meetings in one day cost one day, while ten meetings across five days cost five. They make the default async, and the meeting the exception that must state its decision, so a meeting that cannot name the decision it makes is cancelled, which is the review that separates coordination from ritual, the same discipline as [nobody reads your dashboards](https://debugly.dev/nobody-reads-your-dashboards/) applied to the calendar: if no decision changes, the meeting is decoration. And they read the calendar as a budget, in the retrospective, counting the fragmentation each maker experienced, because the receipt, read once a month, is the only place the tax becomes a number, and numbers are the only costs that get managed. ## The uncomfortable conclusion The team that is busy every day and ships less every week is not undisciplined. It is optimising the visible metric, attendance, while the invisible one, unbroken attention, is spent without record, and the calendar is the only document that shows the spending, and it is read as a schedule, not as a budget. The fix is not fewer meetings by fiat, which rebounds, but a price at the point of booking, a block that is owned, a default that is async, and a monthly reading of the receipt, so that the tax, which will exist, is at least voted for. ## The working rule A meeting's cost is the block it fragments, paid by a maker at a different time, and the calendar that shows the hour is undercounting by a half day. Price it: own the blocks, batch the slices, default to async, cancel the decisionless meeting, and read the calendar monthly as the budget it is. The deep work that dies is the product that never ships, and the calendar, read correctly, is the only ledger where the cause is written, which makes it, of all the artefacts on this site, one of the few that could have prevented the incident instead of merely recording it. --- Published on [debugly.dev](https://debugly.dev/) by [Rohit Bhadani](https://debugly.dev/about/) | Founder of [Krova Cloud](https://krova.cloud/?ref=debugly.dev)