Why should a team not run at full capacity?

Because something always comes up, and a team already at 100 percent has nowhere to put it. Running at about 70 percent leaves room to reach 80 when something slips and 100 when it is genuinely urgent, which is what makes the schedule hold rather than collapse.

Does planning at seventy percent mean getting less done?

In a given week, sometimes. Across a cycle, no, because the alternative is a plan that breaks in week two and takes the rest of the cycle with it. Consistent delivery at a controlled pace beats maximum delivery that only works when nothing goes wrong.

How do you actually plan at seventy percent?

Plan six hours of tasks into an eight hour day, and count planning and communication inside that six. The remaining two hours are the headroom. If you never need them the estimates were too cautious, and you can tighten next cycle.

What if leadership expects one hundred percent?

Show them the record rather than arguing the principle. Track how often planned work actually got completed under the old approach. A team that reliably finishes what it committed to is a better argument than any amount of theory about sustainable pace.

Run Your Team at Seventy Percent

A train at full speed cannot recover from anything. Neither can a team, and Chicago's commuter rail figured this out long before any of us did.

Joe Martin presenting on the predictable workday

Plan your team at about 70 percent of capacity, not 100. Something always comes up, and a team already at full stretch has nowhere to put it. Seventy leaves room to reach 80 when something slips and 100 when it is genuinely urgent. That headroom is not waste. It is the entire reason the schedule holds.

The Metra and the el

Chicago has two train systems and they solve the same problem in opposite ways.

The el runs around the city, picking people up every five to fifteen minutes. Frequency is the promise, so an individual train being late barely registers.

The Metra stretches out into the suburbs, and its promise is different. It runs methodically, on a published schedule, and people plan their mornings around a specific train at a specific minute.

Here is the part that matters: the Metra holds that schedule precisely because it does not run at full speed. The trains run at 60 or 70 percent of what they are capable of, which means they can go faster to make up time. Push to 80 when something slips. Push to 100 when it is really bad.

Run them flat out all the time and they lose the ability to recover from the smallest mix-up. The consistency disappears, and consistency was the whole product.

Teams are the same machine

We should not build a cycle where every person is expected to give 100 percent every day. We should run at the rate that produces the best consistency and results, not the rate that extracts the most hours.

Those are genuinely different targets, and most companies optimize for the second while claiming to want the first.

A team planned at 100 percent has one bad Tuesday and the week is gone. Then the week after absorbs the overflow and that week is gone too. By week four nobody believes the plan, and by week six the conclusion is that planning does not work here.

A team planned at 70 percent has a bad Tuesday and Wednesday absorbs it. Nobody escalates. The plan survives.

What seventy percent looks like on a sheet

It is not a vibe, it is arithmetic. Plan six hours of work into an eight hour day, and count planning and communication inside that six rather than treating them as free.

30 minutes of planning
+ 5.5 hours of email, meetings, and tasks
+ 4 breaks at 15 minutes each
+ 1 lunch at 60 minutes
= your 8 hour workday

Six planned out of eight available is 75 percent, and once you account for the days that go sideways it lands right about at 70.

If you find you never touch the headroom, your estimates were too cautious and you can tighten next cycle. That is a much better problem than the one where every cycle overruns and nobody can say why.

The trap of absorbing it yourself

I need to be honest about the version of this I got wrong for years.

When extra work landed, I absorbed it. Ten things on my list, five more added on Tuesday, and I would bust my ass to finish everything by Friday. For what? My bosses did not know I was overloaded, because I never told them. I just did it.

To them it simply looked like it worked. So next time they assumed the same thing was possible. And again. And again, until it quietly became the new standard.

That was on me, not on them. Every time I took on extra work without saying anything, I let the problem continue. What I should have said was straightforward: I cannot complete these additional tasks this week, but I can have them for you by next Friday.

If you are the person setting the plan, understand that your team is doing this too, and they will not tell you either. The headroom is what makes it unnecessary.

When someone misses regularly

Planning at 70 percent has a useful side effect: it makes real problems visible instead of hiding them under heroics.

If someone is consistently missing deadlines inside a plan that already has slack in it, you have one of two things. Either a person who is not able to do the job, or a manager setting unrealistic expectations. Both are worth knowing about, and both are much easier to see when the plan was not fantasy to begin with.

Time is not the metric here. Completion is. Six-week cycles make that distinction easier to uncover, address, and correct, which is a lot of what they are for.

The whole method is in the guide to running your work in six-week cycles.