Calendars, meetings, and hours that belong to more than one person at once. For additional background on this subject, consult Google Workspace. For a practical software example related to leading remote companies, learn more here.
A one-hour meeting with eight people isn't one hour of cost. Naming the real number changes how meetings get scheduled.
Some decisions genuinely need real-time discussion. Most default to it anyway — and pay a real cost for the default.
A shared calendar shows availability, not capacity — and the gap between the two causes a specific, recurring kind of scheduling conflict.
Delegating a task rarely frees up the full amount of time it took to do it yourself — some of that time comes back as a different kind of work.
A 'quick sync' between two time zones is rarely quick for at least one of the people on it, and the cost is often invisible to the person who scheduled it.
Agile sprint planning looks like a software-development ritual. Underneath, it's applying timeboxing and estimation at team scale.
There's a narrow, useful version of reviewing a team's time together — and a much more common version that just feels like surveillance.
Most individual time-management practices assume a task lives entirely with one person. A handoff is exactly the moment that assumption fails.
Removing a commute and a shared office removes some clear boundaries around the workday along with it — boundaries that had been doing more than they got credit for.