A full calendar tells you that time has been allocated. It tells you very little about whether the business is working well. Before celebrating being at capacity, look at what that capacity produces—and what it costs to maintain.

The working map
  1. 01Map the work
  2. 02Find the constraint
  3. 03Change one thing
  4. 04Measure again
01

Define what “full” actually means.

Capacity can mean booked appointments, committed production hours, a queue of unfinished projects or a founder who approves every decision. Those are different constraints. Hiring another person will not necessarily solve a queue that exists because nobody can approve the work.

Start with one recent week. List the work delivered, the time spent delivering it, the time spent coordinating it and the work that had to be repeated. Include the invisible jobs: chasing inputs, clarifying briefs, moving information and waiting for decisions.

The point is to replace “everyone is busy” with a specific account of where time goes. A service that looks profitable against delivery hours alone can look very different once revisions and coordination are included.

02

Find the part that sets the pace.

Imagine a studio with enough designers but only one person authorised to sign off a concept. Adding another designer may create a longer review queue. In that example, the first experiment is clearer approval criteria or delegated sign-off, not more production capacity.

Now imagine a service where every customer receives a different process at the same price. The constraint may be the offer itself. A tighter scope, a separate price for exceptions or a repeatable delivery sequence could change the economics of the work.

These are diagnostic examples, not promises of a particular result. The useful question is: which part of this business would still hold everything back if the other parts became faster?

03

Choose a change that matches the constraint.

Use a small intervention that you can observe. If information arrives incomplete, improve the intake. If work returns for avoidable revisions, define acceptance criteria. If the founder is the queue, specify which decisions someone else can own.

Automation belongs after that diagnosis. Automating a task with unclear inputs can turn occasional confusion into a repeatable problem. First decide what should happen, who owns exceptions and what a correct result looks like.

  • Demand exceeds a sound delivery process: consider capacity or pricing.
  • Work stalls between people: clarify handoffs and decision ownership.
  • The same task is repeated consistently: assess whether it can be automated.
  • Every job is an exception: revisit the offer and scope.
04

Measure the space you get back.

Compare completion time, rework and delivery cost before and after the change. Watch customer experience as well: making an internal step faster is not an improvement if customers now have to do the missing work.

A full calendar may be exactly what you want. The test is whether it supports the income, quality and working life you intended to build. If it does not, identify the constraint before sending more demand into it.

Share this article

Continue the thread

System Maps

Remove unnecessary work before automating the sequence.

System Maps

Ask questions that reveal how someone does the work.

System Maps

What is the founder’s hour actually doing?