पाठशाला Pathshala · संचालन Sanchālan, Operations · Lesson 08 · Start

Meetings that earn their time

Five people for an hour is a five-hour meeting. Count the hours, cut the meetings that fail three tests, give the rest an agenda, an owner and a pre-read, and measure what came back.

Pathshala, The Founder Library · 11 October 2026 · 7 min read

An empty conference room with black chairs around a long wooden table and glasses set out. — Photograph: Leandro Alamino · Pexels

Nobody in a startup decides to spend a third of the week in meetings. Each meeting is added for a good reason by someone who needed it once, and none is ever removed, until a twelve-person company finds that its most expensive activity is people listening to updates they could have read in two minutes.

This lesson prices meetings in the unit that matters, sets three tests a meeting has to pass, describes the agenda, owner and written pre-read that make the survivors work, and shows how to cut the load once and measure the hours that came back. The [operating cadence lesson](/library/founders-operating-cadence) sets out which fixed meetings a company should hold. This one is about everything else on the calendar.

Count the hours before you cut them

Basecamp’s guide to how it communicates makes the arithmetic plain: five people in a room for an hour is not a one-hour meeting, it is a five-hour meeting. The unit is the person-hour, and almost no founder has ever counted them. The ones who do usually find the total is larger than they guessed and growing. Leslie Perlow, Constance Noonan Hadley and Eunice Eun, writing in Harvard Business Review, cite research putting executives at about twenty-three hours a week in meetings, up from under ten in the 1960s, and that excludes the unscheduled ones.

The count takes an hour. Export the shared calendar for the last four weeks. For every recurring meeting write down the people invited, the length and how often it happens. Multiply. Add the one-off meetings as a single line. Then divide by the hours the company has: a ten-person company working forty-hour weeks has four hundred, so a count of eighty person-hours means a fifth of everything the company does happens in a meeting. Write the number at the top of a page in the wiki. It is the baseline against which everything in this lesson is measured.

Three tests every meeting must pass

It ends in a decision, or in input that cannot be written. A meeting whose purpose is to share information is a document with a calendar invitation. A document can be read at the hour each reader chooses, skimmed where it is familiar and kept for the person who joins next year. What cannot be written is disagreement that needs resolving, a judgement that needs several people’s experience at once, or a conversation where tone matters: a difficult piece of feedback, a customer escalation, a hiring decision. If the meeting is none of those, it is an update, and updates are written.

Two kinds of meeting are exempt from the purge that follows and should be protected rather than cut. Meetings with customers are the company’s revenue and its research at once, and nobody should need permission to hold one. One-on-ones between a manager and each direct report pass the first test by definition, since their whole purpose is the conversation that cannot be written; they are the meetings most often cancelled when calendars fill, and the first to be missed when someone quietly decides to leave.

One person owns it. The owner decides who comes, writes the agenda, chairs, and records the outcome. A meeting owned by everyone is owned by the most talkative person in the room. The owner also decides when it stops recurring, which is the decision nobody else will ever take.

The agenda is in the invitation. GitLab, whose handbook sets out its meeting rules in public, puts it in four words: no agenda, no attenda. Every work meeting has a single live document linked in the calendar invitation, and non-essential participants are marked optional. An invitation without an agenda may be declined without explanation, and the founder should be the first to decline one.

Agendas, owners and the written pre-read

A meeting that passes the tests still wastes time if people arrive cold. The fix is the written pre-read, and the best-known version of it is Amazon’s. Jeff Bezos’s 2017 letter to shareholders describes a company that does no slide presentations at all: narratively structured six-page memos, read silently at the start of each meeting in a kind of study hall. A ten-person company does not need six pages. It needs one, written by the owner, sent the afternoon before, stating the question, the options, the owner’s recommendation and what the meeting must decide.

The silent read solves the oldest meeting problem in India and everywhere else, which is that the pre-read was sent and nobody opened it. Start the meeting with ten minutes of reading in silence. Those who read it the night before use the time to write questions in the margin. Nobody pretends. The discussion that follows is about the decision, not about catching up.

Three smaller rules do the rest. Book 25 or 50 minutes, not 30 or 60; GitLab’s calendars are set to do this by default, and the five minutes at the end are the time people otherwise steal from the next meeting. Write the notes live in the agenda document, visible to everyone, so there is no second version later. And end with the record: what was decided, who owns each action, by what date. If the meeting decided nothing, write that down too. Two such entries in a row is the meeting telling you it should not recur.

The purge: delete everything once

Trimming meetings one at a time rarely works, because every meeting has an owner who can defend it. Shopify tried the other way in January 2023. As reported at the time, a bot removed every recurring meeting with three or more people from employees’ calendars; staff were asked to wait two weeks before adding any back and to be really critical about what they restored; and Wednesdays were declared meeting-free. The company said about 322,000 hours of meetings were removed, which its chief operating officer equated to adding roughly 150 people.

The startup version is smaller and the same in shape. On a Friday, the founder deletes every recurring meeting on the shared calendar except the fixed rituals of the operating cadence. For two weeks nothing recurring may be re-created. At the end of the fortnight any meeting can be restored, but only by an owner, with an agenda document in the invitation, and only if it passes the three tests. Most will not come back, because two weeks is long enough to discover that the update could be read.

A meeting that only shares information is a document with an invitation attached. Send the document and cancel the invitation.

Measuring the hours you got back

The purge is only worth doing if it is measured. Four weeks after it, export the calendar again and repeat the count: every recurring meeting, its people, its length, its frequency. Compare the total with the baseline. Then measure the second number that matters, which is the number of unbroken three-hour blocks each maker on the team had in a week. A cut that frees forty person-hours but leaves them scattered in fragments between meetings has freed less than it seems.

Sand runs through a glass hourglass against a dark background. — The hours a purge returns are only real once they are counted. Export the calendar again four weeks later and compare. Photograph: Towfiqu barbhuiya · Pexels

A worked example. A Bengaluru software company of twelve people counts ninety-six person-hours of meetings a week before the purge, including a Monday all-hands of twelve people for an hour, a daily product sync of seven people for thirty minutes, and three weekly status meetings of five people each for an hour. After the purge the all-hands becomes a written Friday update and a twenty-five-minute Monday meeting of the four leads; the product sync becomes fifteen minutes with four people; two of the three status meetings become written updates. The count four weeks later is forty-one person-hours. Fifty-five hours a week is more than one full-time engineer’s time, returned without hiring, and the engineers report two more unbroken mornings a week. The founder writes both numbers in the wiki next to the baseline.

The monthly meeting audit

On the first Monday of each month the founder, or whoever runs operations, spends thirty minutes on the calendar. Export the month. Recount the person-hours and write the total beside last month’s. List any new recurring meeting and check that it has an owner and an agenda document. Ask each owner of a recurring meeting whose last two records say nothing was decided whether it should continue. Check that the meeting-free day is still free. Once a quarter, delete everything again and let it grow back. The number should go down for the first quarter and then hold; if it creeps up for three months running, the company is growing faster than its writing, and the [writing culture lesson](/library/writing-culture-decisions-in-documents) is the next one to read.

The person-hour figures in the worked example are illustrative; run the count on your own calendar before setting a target. The sources are below.