Capital Efficiency: Asynchronous Operations for Small Teams

The meeting that ate the week

Here is a week for a two-person studio. It is an illustration rather than a measurement, but the shape of it is familiar to anybody who has run a small team.

┌──────────────────────────────────────────────────────────────────────────────┐
│  A WEEK, ILLUSTRATED                                                         │
├──────────────────────────────────────────────────────────────────────────────┤
│  MONDAY    9:00 stand-up call      2:00 client call about fonts              │
│             11:00 client call        4:00 "quick question" from the client   │
│            1:00 internal rework                                              │
├──────────────────────────────────────────────────────────────────────────────┤
│  TUESDAY   10:00 handover meeting   3:00 second client call                  │
│             12:00 unclear brief       5:00 re-doing work already done        │
├──────────────────────────────────────────────────────────────────────────────┤
│  WHAT THE WEEK LOOKED LIKE: 60 hours attended, arranged or explained.        │
│  WHAT THE WEEK PRODUCED: about 20 hours of finished work.                    │
└──────────────────────────────────────────────────────────────────────────────┘

Nobody in that week was idle. Everybody was busy. And most of the business came out of two narrow windows of actual building.

The owner of a small business is usually the first person to feel this, because the owner’s own attention is the scarcest thing the business has. Two hours of calls is two hours the owner cannot spend on the work that only they can do: the judgement call, the difficult client conversation, the thing the business is actually known for.

23 minutes to get back to the work

In a 2006 interview with the Gallup Business Journal, Gloria Mark, who studies interruption at the University of California, Irvine, reported that interrupted work which was resumed on the same day — 81.9% of it in her sample — was resumed after an average of 23 minutes and 15 seconds, with about two other tasks in between. That is not the time the interruption takes. It is the time it takes to get back, and most of it is spent working out what you were doing.

Mark’s controlled experiment, published as “The Cost of Interrupted Work” in 2008, found the same pattern in a lab: interrupted work was actually completed faster, but after only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort and pressure.

Run the arithmetic on the week above. Six interruptions across a working day do not cost six minutes. They cost considerably more than that, because each one lands on whatever was in progress.

The result is a familiar complaint from people who do careful work: they were at the desk all day and built nothing. They are not exaggerating. They spent the day being present, and presence is not the same as output.

What asynchronous work actually means

It is not a rule against talking. It is a rule about which medium each conversation belongs in.

┌───────────────────────────────────────────┬────────────────────────────────────┐
│  BETTER IN WRITING                        │  BETTER IN A LIVE CALL             │
├───────────────────────────────────────────┼────────────────────────────────────┤
│  Scope, prices and timelines              │  Disagreement with real stakes     │
│  Feedback on a design or a build          │  Anything emotionally loaded       │
│  Status, progress and what happens next   │   A decision nobody can make alone │
│   Questions that need a considered answer │  Bad news, delivered badly         │
│  Anything that should be kept on record   │  A welcome, a thank you            │
└───────────────────────────────────────────┴────────────────────────────────────┘

Four practices do most of the work in a small studio:

Write the brief before the call. If the work cannot be described in a paragraph, it is not ready to discuss. Writing it first removes the meeting that exists only to transfer a thought that was never finished.

Protect the mornings. Two people in a studio can easily agree that nothing is scheduled before 11:00. It is the cheapest productivity change available and it is the one that survives, because it protects the hours that are hardest to get back.

Record the walkthrough instead of running the demo call. A short screen recording of the work in progress answers most of the questions a status meeting raises, and the client can watch it on a Tuesday evening. It also exists afterwards, which a call does not.

Hold one scheduled check-in. Not daily, not on demand. One, with an agenda, and a written summary afterwards. If a decision cannot be made in that meeting, it becomes a written brief.

The arithmetic

Here is the same arithmetic for a small studio, using our own example figures, which you can replace with yours. Take a two-person team, forty hours a week each: eighty hours a week of capacity in total.

Suppose twenty of those eighty hours go to calls, messages and the rework caused by unclear instructions. Sixty hours go to delivery. At that rate a project priced at $1,500 and taking forty hours of delivery time bills about $37 an hour of your own capacity. If clarity recovers ten of those twenty hours each week, the studio has seventy hours of delivery time in the same calendar week, which is the same as saying it can deliver a second $1,500 project in a month without a second person.

Over a year, ten hours a week recovered is 520 hours. At forty hours of delivery time per project, that is thirteen projects a year that were always in the plan and never in the calendar.

┌──────────────────────────────────────────────────────────────────────────────┐
│  80 HOURS A WEEK, TWO PEOPLE                                                 │
├──────────────────────────────┬───────────────────────────────────────────────┤
│  20 hours: calls and rework  │  60 hours of delivery time                    │
│  40 hours each, minus 10     │  $1,500 project at 40 hours = $37 an hour     │
├──────────────────────────────┼───────────────────────────────────────────────┤
│  Recover 10 hours a week     │  70 hours of delivery time                    │
│  520 hours a year            │  13 more projects a year                      │
├──────────────────────────────┴───────────────────────────────────────────────┤
│  None of this is about working longer. It is about not paying for the same   │
│  hour twice.                                                                 │
└──────────────────────────────────────────────────────────────────────────────┘

A studio that is careful about this can hold its prices without becoming slow, and can take on a second project without taking on a second person. A studio that is not careful about it has to hire, and hiring is the most expensive way to buy more hours.

This is what capital efficiency means in small operations: not cutting the work, but getting more of the finished work out of the hours and the people already on the payroll. The alternative to a lean operation is a bigger one, and a bigger one is a slower decision every single time.

What it costs the client

The point of this is not only internal. Your client is also losing hours to the same problem, and they are usually paying for them.

A client who gets a written brief can read it, reply in their own time and forward it to a colleague. A client who gets a meeting has to book it, join it, and then explain it to somebody who was not in the room. Most of the frustration clients describe about working with agencies comes from a lack of written record, not from a lack of effort.

The honest cost of this approach is that it needs good writing. An unclear asynchronous message is worse than an unclear call, because the reader cannot ask a follow-up question until they have read everything. It also fails in one direction: a conversation where people disagree about something they both care about should be a call, and pretending otherwise just produces a long thread that ends where a twenty-minute conversation would have.

Where it stops

Asynchronous working is not a moral virtue and it is not a way to be clever about meetings. It is a response to a specific fact: interruptions are expensive, and some kinds of interruption are avoidable.

If your work needs a lot of clarification, you have a briefing problem, and no calendar arrangement will fix it. If your client needs to be walked through something complicated, walk them through it. The rule is simple enough to state in one line: write it down if it is a fact, and meet if it is a decision.

Done consistently, that one line is the difference between a team that is busy and a team that ships.

Want to see how a small studio actually works, end to end? Model your project with the estimator, or read communicating availability honestly.