Price the meeting before you trust the seat time

The calendar shows a block. The day also loses the prep and the stretch after, when the last problem is gone. Three calls that look like two hours can erase an afternoon.

Until your log says otherwise, price a live hour at about one and a half times the invite. Sixty minutes, plus about fifteen to prepare and fifteen of notes, is about ninety. A pairing you already prepared may cost close to seat time. An unprepared status round often costs more. Treat the number as a planning habit.

Example. Assumptions: one engineer, start at 09:00, the work that matters is a bug that needs a long stretch, calendar holds 09:45 standup, 11:00 design review, 13:00 stakeholder sync, and 15:00 planning. The afternoon looks open. From 09:00 to 09:45 you cannot enter the bug. From 10:00 to 10:45 you collect screenshots for 11:00. The calendar records one meeting and you paid for the prep and a morning that never started. The hole before 15:00 is residue. After planning, yesterday's branch is cold.

Do not assign a feature to that kind of gap. The unnoticed time is part of the real cost of context switching. Work that should not be a call follows async communication for distributed teams. Whether the hour is fair follows timezone collaboration without chaos. A 21:00 slot for one region is not cheap. The multiplier does not include the sleep.

If nothing changed on a ticket, a document, or a calendar, the hour was social. Name it that way. People can decline social time. A sync takes a speech.

Set a weekly meeting budget by role

A meeting budget is a planning input. A week over budget for an incident is a week to repair. A week over budget that shipped nothing is a week to cancel or shorten. Write the number next to the overlap hours. A figure in someone's head loses to every invite.

Edit these ranges, then publish them. An engineer or designer: about 6 to 10 live hours in a heavy week, and two mornings with no meetings. Those mornings are a norm, not a favor, and not the block you offer for a roadmap tour. If every deadline eats them, they were never real. A lead may sit higher, still caps status, and protects one decision block inside overlap. A week that is only status is buying the wrong artifact.

A freelancer takes calls only as the contract states, inside a window you chose. Outside it, price the call or send the decline note. "Happy to jump on" turns two calls into five without a change order. A product manager across regions uses pairwise overlap. No brief, no live decision, and the hour returns to the budget.

Batch reviews the way you batch a deploy: adjacent, one prep window, a contiguous block on the other side of the day. Five scattered calls spend the multiplier five times. The same hours after lunch spend it once. Over budget by Wednesday, the next yes names which series you will skip. "I will make it work" hides the cost on Thursday night.

Run the meet-versus-async test on the invite

Ask what the hour is for, and whether writing had a fair chance.

Information is a document or a recording. If people cannot open it, fix access. Do not read it aloud. A choice between two options starts as a brief plus a comment deadline. Go live only when one round still ties two defensible options and the comments were filed. Silence means the default applies. Meeting because nobody commented rewards the skip.

A bug starts as logs, steps, and what you tried. Share a screen when a written reproduce still fails. If the steps are only in your head, write them first. Hard feedback is a 1:1 inside overlap, not a trailing item on group status. A brainstorm with no owner is theater. Name the owner on the invite, or do not book it. Status is an end-of-day note. Buckets: end-of-day status update. Visibility is the note and the filter.

The longer test is in when a remote team needs a meeting. Written disagreement that is still stuck uses when async disagreement needs a live call. Tension is not an exit line. Two named options are.

Before you accept, read the description. Brief, exit line, required versus informed, fair overlap for every required person. If those fail, decline. Missing pre-read and missing exit: propose the brief, or accept fifteen minutes that adds both and ends. Two required declines on the same thin invite in a week means cancel it. Send the note. Reading it is faster than the call.

Replace the daily round-robin with a written note

Example. Assumptions: eight people, four time zones, a daily 30-minute video standup, tickets already hold the state, and the slot regularly puts Manila or Berlin on the edge of the day.

For two weeks, replace the call with ticket comments plus Done, Open, Blocked, and Next. Watch one question: which escalations still cannot travel in writing?

If you cannot name one, the series stays cancelled. If you can, restore only that slice: a weekly 25 minutes on blocked items, exit line that each blocker has an owner and a UTC date. Do not bring the daily round back because the weekly review felt friendly.

The swap fails when tickets are empty and people conclude that writing does not work here. Fill the fields. A recurring sync with no agenda is the same hole. Cancel it or write the brief the agenda never had.

When the note must transfer ownership overnight, use a handoff, not a status. Fields: leave work someone else can continue. Status buckets omit the verify step. A full handoff, when you still own tomorrow, is extra document nobody was asked to pick up.

Name the replacement before you delete the invite. A status round becomes the four buckets. A quick alignment becomes two options and a comment deadline. A roadmap preview becomes a short recording and a question thread with a UTC deadline. A brainstorm becomes silent writing, then twenty live minutes only if the clusters still tie. A forty-minute lecture becomes the recording. Live time is for objections after people have watched. One series, two weeks. Bring back only the slice that broke, and bring it back smaller.

Put an exit line on every invite past fifteen minutes

Anything longer than fifteen minutes needs five items, or the invite waits.

Purpose is one of decision, review, pairing, or unblock. "Sync" is not a purpose. Two purposes means two slots, or a document for one of them.

The pre-read is opened before join. Across zones that do not share a morning, send it one workday ahead. A link twenty minutes prior is a prop. Screen-sharing it cold spends the budget on silent reading.

The exit line is a sentence you can paste on the ticket. "We leave with A or B chosen." Or "the pull request is approved, or the change list is written down." "Align" will not paste.

Each topic has a timebox in the doc. When it ends, decide or move it to writing. Do not steal the next topic's minutes. That is how the real decision dies on "we are at time."

Name one note owner. The decision is on the ticket within an hour. If it is missing the next day, the meeting did not finish. Collect it in writing. Do not book a second hour to remember the first. Shrink the series instead.

A usable title: "Choose checkout provider A or B. Pre-read linked. 25 minutes. Exit: the decision is on PAY-200."

Start on time. Point late joiners at the doc. Cameras are optional. End when the exit line is met. "While we are here" becomes next week's agenda. Required and optional are separate. Optional people get the summary. If you cannot write it without them, they were required.

Nobody read it? Cancel the read-aloud:

We are missing the pre-read. Comments go on the doc before Thursday 15:00 UTC. We meet only if A and B are still tied.

In a hybrid room, every person uses their own laptop, including people who share an office. Call remote names first. A remark that never hits the doc did not happen. If a room camera is unavoidable, rotate a remote advocate whose job is to interrupt when the room goes opaque. Record only when someone absent needs it, and pair the recording with the written decision. A recording alone makes the next person watch the hour to learn what you chose.

Copy the decision note template

Price the meeting before you trust the seat time The calendar shows a block. The day also loses the prep and the stretch after, when the last problem is gone. Three calls that look like two hours can erase an afternoon. Until your log says otherwise, price a live hour at about one and a half times the invite. Sixty minutes, plus about fifteen to prepare and fifteen of notes, is about ninety. A pairing you already prepared may cost close to seat time. An unprepared status round often costs more. Treat the number as a planning habit. Example. Assumptions: one engineer, start at 09:00, the work that matters is a bug that needs a long stretch, calendar holds 09:45 standup, 11:00 design review, 13:00 stakeholder sync, and 15:00 planning. The afternoon looks open. From 09:00 to 09:45 you cannot enter the bug. From 10:00 to 10:45 you collect screenshots for 11:00. The calendar records one meeting and you paid for the prep and a morning that never started. The hole before 15:00 is residue. After planning, yesterday's branch is cold. Do not assign a feature to that kind of gap. The unnoticed time is part of the real cost of context switching. Work that should not be a call follows async communication for distributed teams. Whether the hour is fair follows timezone collaboration without chaos. A 21:00 slot for one region is not cheap. The multiplier does not include the sleep. If nothing changed on a ticket, a document, or a calendar, the hour was social. Name it that way. People can decline social time. A sync takes a speech. Set a weekly meeting budget by role A meeting budget is a planning input. A week over budget for an incident is a week to repair. A week over budget that shipped nothing is a week to cancel or shorten. Write the number next to the overlap hours. A figure in someone's head loses to every invite. Edit these ranges, then publish them. An engineer or designer: about 6 to 10 live hours in a heavy week, and two mornings with no meetings. Those mornings are a norm, not a favor, and not the block you offer for a roadmap tour. If every deadline eats them, they were never real. A lead may sit higher, still caps status, and protects one decision block inside overlap. A week that is only status is buying the wrong artifact. A freelancer takes calls only as the contract states, inside a window you chose. Outside it, price the call or send the decline note. "Happy to jump on" turns two calls into five without a change order. A product manager across regions uses pairwise overlap. No brief, no live decision, and the hour returns to the budget. Batch reviews the way you batch a deploy: adjacent, one prep window, a contiguous block on the other side of the day. Five scattered calls spend the multiplier five times. The same hours after lunch spend it once. Over budget by Wednesday, the next yes names which series you will skip. "I will make it work" hides the cost on Thursday night. Run the meet-versus-async test on the invite Ask what the hour is for, and whether writing had a fair chance. Information is a document or a recording. If people cannot open it, fix access. Do not read it aloud. A choice between two options starts as a brief plus a comment deadline. Go live only when one round still ties two defensible options and the comments were filed. Silence means the default applies. Meeting because nobody commented rewards the skip. A bug starts as logs, steps, and what you tried. Share a screen when a written reproduce still fails. If the steps are only in your head, write them first. Hard feedback is a 1:1 inside overlap, not a trailing item on group status. A brainstorm with no owner is theater. Name the owner on the invite, or do not book it. Status is an end-of-day note. Buckets: end-of-day status update. Visibility is the note and the filter. The longer test is in when a remote team needs a meeting. Written disagreement that is still stuck uses when async disagreement needs a live call. Tension is not an exit line. Two named options are. Before you accept, read the description. Brief, exit line, required versus informed, fair overlap for every required person. If those fail, decline. Missing pre-read and missing exit: propose the brief, or accept fifteen minutes that adds both and ends. Two required declines on the same thin invite in a week means cancel it. Send the note. Reading it is faster than the call. Replace the daily round-robin with a written note Example. Assumptions: eight people, four time zones, a daily 30-minute video standup, tickets already hold the state, and the slot regularly puts Manila or Berlin on the edge of the day. For two weeks, replace the call with ticket comments plus Done, Open, Blocked, and Next. Watch one question: which escalations still cannot travel in writing? If you cannot name one, the series stays cancelled. If you can, restore only that slice: a weekly 25 minutes on blocked items, exit line that each blocker has an owner and a UTC date. Do not bring the daily round back because the weekly review felt friendly. The swap fails when tickets are empty and people conclude that writing does not work here. Fill the fields. A recurring sync with no agenda is the same hole. Cancel it or write the brief the agenda never had. When the note must transfer ownership overnight, use a handoff, not a status. Fields: leave work someone else can continue. Status buckets omit the verify step. A full handoff, when you still own tomorrow, is extra document nobody was asked to pick up. Name the replacement before you delete the invite. A status round becomes the four buckets. A quick alignment becomes two options and a comment deadline. A roadmap preview becomes a short recording and a question thread with a UTC deadline. A brainstorm becomes silent writing, then twenty live minutes only if the clusters still tie. A forty-minute lecture becomes the recording. Live time is for objections after people have watched. One series, two weeks. Bring back only the slice that broke, and bring it back smaller. Put an exit line on every invite past fifteen minutes Anything longer than fifteen minutes needs five items, or the invite waits. Purpose is one of decision, review, pairing, or unblock. "Sync" is not a purpose. Two purposes means two slots, or a document for one of them. The pre-read is opened before join. Across zones that do not share a morning, send it one workday ahead. A link twenty minutes prior is a prop. Screen-sharing it cold spends the budget on silent reading. The exit line is a sentence you can paste on the ticket. "We leave with A or B chosen." Or "the pull request is approved, or the change list is written down." "Align" will not paste. Each topic has a timebox in the doc. When it ends, decide or move it to writing. Do not steal the next topic's minutes. That is how the real decision dies on "we are at time." Name one note owner. The decision is on the ticket within an hour. If it is missing the next day, the meeting did not finish. Collect it in writing. Do not book a second hour to remember the first. Shrink the series instead. A usable title: "Choose checkout provider A or B. Pre-read linked. 25 minutes. Exit: the decision is on PAY-200." Start on time. Point late joiners at the doc. Cameras are optional. End when the exit line is met. "While we are here" becomes next week's agenda. Required and optional are separate. Optional people get the summary. If you cannot write it without them, they were required. Nobody read it? Cancel the read-aloud: We are missing the pre-read. Comments go on the doc before Thursday 15:00 UTC. We meet only if A and B are still tied. In a hybrid room, every person uses their own laptop, including people who share an office. Call remote names first. A remark that never hits the doc did not happen. If a room camera is unavoidable, rotate a remote advocate whose job is to interrupt when the room goes opaque. Record only when someone absent needs it, and pair the recording with the written decision. A recording alone makes the next person watch the hour to learn what you chose. Copy the decision note template

Decision:
Options considered:
Chosen because:
Owner / next step / date (UTC):
Out of scope today:

Fill it before you leave, or within the hour, and paste it on the ticket in the exit line. Chat can announce the note. The ticket keeps it.

Example. Assumptions: 25 minutes, Berlin and New York required, the pre-read compared two providers, Manila optional and reading this at the start of their next day.

Decision: Ship checkout with provider A for PAY-200
Options considered: A (lower fees) and B (stronger EU SCA defaults)
Chosen because: legal has not flagged an SCA gap, and A is cheaper at the current volume
Owner / next step / date (UTC): Berlin engineer updates the ticket owner by Thursday 16:00 UTC
Out of scope today: migrating existing subscribers

If "Chosen because" will not fit in one or two sentences, you did not decide. You agreed the topic is complicated. Put the open question back on the doc, name the missing fact, and stop. More time will not supply the fact.

"Out of scope today" stops the next meeting from retrying a neighbor topic. Write the neighbor down. Otherwise it appears in the last five minutes, the note owner hesitates, and the decision you made ships with a fog around it.

Send the decline note before you accept the hour

A client call often stands in for control. Give a standing window, for example Tuesday 14:00 to 15:00 in their zone, and keep delivery outside it. Written status carries one decision ask. The contract names the emergency channel and the reply time. Without that, every anxious message is the emergency. Send the boundary at kickoff:

I batch client calls on Tuesdays. Urgent blockers go by email with BLOCKED in the subject. I reply within four business hours.

A bare no teaches people to route around you. A no with a deadline, or with a draft, teaches the next invite to arrive in better shape. Shrink when the topic is real and the format is bloated. Pass when you were invited to watch. Use the doc deadline when nobody has written the two options yet.

Can we resolve this in the doc by Thursday 17:00 UTC? I will book 20 minutes if the comments still tie.

I am optional for context. Please send the decision note. I will read it async and comment only if the exit line names me.

I can do 15 minutes if we leave with an owner and a UTC date. I cannot do 60 minutes of open sync.

Put the decline on the invite, next to the buttons, not only in a side message. If you are required and the local time is outside 08:00 to 18:00, say that, offer the next overlap hour, and offer the written path if that hour is too late. Do not apologize for a zone the series already knew about.

An exception without an end date becomes the calendar. Write the end date, or do not make the exception.

Score every recurring series and cancel one

Export every recurring invite. Score the artifact, not the vibe. Talk about culture after the export, or the series will survive the conversation.

Keep a series that produced an exit and an artifact last month, then shorten it to the smallest length that still produces them. Rewrite a real need in a weak shape: pre-read required, spectators cut, note owner named. If you cannot cut anyone, required and optional are still mixed. Cancel status-only series, and series nobody can defend by naming what breaks. Say the replacement in the cancellation: Done, Open, Blocked, and Next where state already lives. Move a series that puts one region outside a normal day every time. Rotate the late hour in public, or it is an assignment.

Example. Assumptions: you lead the team, the daily standup is status, a quick sync has no agenda, planning is 60 minutes with no exit line. Week one, replace the standup with written Done, Open, and Blocked, and write down any escalation that still needed a voice. Week two, cancel the quick sync. A real decision gets a brief and a short slot. A wish to watch people work gets the written note. Week three, cut planning to 25 minutes with an exit line. Week four, keep only the slice that broke.

Keep planning and review when they create tickets people use. A refinement block with no exit becomes a brief plus a short overlap for ties. A three-hour backlog tour means the backlog is the document. Batch sales and engineering intros. Send the brief first. Engineers are optional unless the exit line needs a technical choice live.

On a back-to-back day, keep ten minutes for the note. A shorter gap is residue. How that fits the week is in plan a week of remote work. After a heavy day, stop at one artifact and a pickup note.

Four questions: exit line met, decision on the ticket within a day, required list honest, pre-read used. Three no answers, cancel or redesign. Do not add a series to discuss the series. Protect meeting-free mornings and one batched coordination day. People cannot decline what you keep inviting them to. The number to take upward is contiguous maker time left, or an export that shows the old series had no artifact.

Cancel or rewrite a series that fails twice across two months. Pair that with clearer requests from async communication for distributed teams and a fair clock from timezone collaboration without chaos. Delete the meeting and leave the writing weak, and the work comes back. A two-week written replacement that breaks nothing you can name is a deletion. If it breaks something, name it in one sentence and fix that sentence with a smaller live touch.