Do me a favor. Right now, before you read another paragraph.

Write down every project you currently have open. Not planned. Not someday. Open. Started, not finished, and still technically alive in your head or on somebody’s list.

Include the client work. Include the internal stuff. Include the website redesign you started in April. Include the hiring process that’s been at the “write the job post” stage since June. Include the book, the podcast, the new offer, the CRM migration, the thing you told your wife you’d handle.

I’ll wait.

Most operators I do this with land somewhere between eleven and twenty three.

Now here’s the uncomfortable follow up. How many of those will ship this week?

Usually the answer is one. Sometimes zero.

You’ve got nineteen things open and one thing finishing. That’s not a productivity problem. That’s a math problem, and it has a solution that nobody wants to hear because the solution is subtraction and we’ve all been trained to believe the answer is addition.

The Math Nobody Runs

There’s a relationship in operations that’s about as close to a law of physics as business gets. It’s boring, it’s a hundred years old, and it will restructure how you think about your week.

How long something takes to finish is a function of how much you have open at once.

Not how hard you work on it. How much else is open.

If you can finish three things a week and you have three things open, each one takes about a week. If you can finish three things a week and you have eighteen things open, each one takes about six weeks. Same effort. Same talent. Same hours. Six times the wait.

And that’s the generous version, because it assumes zero switching cost. In reality every open item is also a tax. It’s a thing you think about in the shower. It’s a status you have to remember. It’s an email you have to re-read to remember where you left off. Nine things at forty percent attention is not the same as one thing at forty percent attention nine times over. It’s meaningfully worse, because the overhead of holding nine states in your head is itself a job.

You do not get partial credit for partial work. A project at ninety percent generates exactly as much revenue as a project at zero percent, which is none.

That last line is the one I’d tattoo on the wall of every office I’ve ever worked in. Value is binary. It exists on the other side of shipped. Everything before that is inventory, and inventory is cost.

So the operator running nineteen open projects isn’t ambitious. He’s holding nineteen units of expensive, decaying inventory and calling it a pipeline.

Why Starting Feels So Good and Costs So Much

Worth understanding why you do this, because “just focus” has never worked for anyone and it isn’t going to start working now.

Starting is a hit. New project, fresh energy, everything’s possible, nothing’s gone wrong yet. Nobody’s disappointed. The plan is still perfect because the plan hasn’t met reality.

Finishing is the opposite. Finishing means the last fifteen percent, which is the ugly part. Edge cases. Loose ends. The stuff you didn’t think about. And finishing means judgment, because now the thing exists and someone gets to have an opinion about it.

So we start. And starting is legible as progress. You can tell your team about a new initiative. You can’t tell them about the initiative you’re grinding out the last ten percent of, because that’s not news, that’s just Tuesday.

High performers are especially bad at this, and I include myself. The same appetite that makes you good at seeing opportunity makes you terrible at declining it. You see the opening, you know you could execute it, and saying no feels like leaving money on the table.

It isn’t. Every yes you give to a new thing is a tax you charge every other open thing on your list. You’re not adding an opportunity. You’re slowing nineteen of them down to make room.

The WIP Ceiling

Here’s the fix. It’s five steps, it’s uncomfortable for about a week, and then it becomes the thing you wonder how you lived without.

Step One: Take the Honest Inventory

You already started this at the top. Finish it properly.

One page. Every open item. The rule for what counts: if it has been started and not shipped, and if someone would be disappointed or inconvenienced if it silently died, it’s open. Write it down.

Include the ones you’re embarrassed about. Especially those. The half finished things you’ve stopped mentioning are the ones costing you the most, because they’re occupying a slot and generating nothing.

Next to each one, write a single date: when did this start? You’ll find things from eight months ago. That’s the point of the exercise.

Step Two: Set the Number

Your WIP ceiling is the maximum number of things allowed to be open at once. Personal ceiling for your own work, and a separate one for the team if you’re setting this at the org level.

For personal work, the answer is three. I’ve tested this on myself and on a lot of other operators and it’s remarkably consistent. Three active projects, one of which is the priority. More than three and everything decelerates.

For a team, take your honest weekly finishing rate and multiply by two. If your team genuinely completes four meaningful items a week, your ceiling is eight. That gives you a two week horizon, which is enough to keep people from idling and short enough that nothing rots.

The number will feel too low. That feeling is the whole reason the exercise works. If it felt comfortable, it wouldn’t be a constraint, and a constraint that doesn’t constrain is just a suggestion.

Step Three: Triage the Overflow Into Three Buckets

You’ve got nineteen and a ceiling of three. Now the hard part. Every item goes into exactly one of three buckets. No fourth bucket. No “sort of.”

FINISH. It goes in the active three. You are working on it this week and it ships. Choose these by asking one question: which of these, if completed, changes something? Revenue, risk, or a person’s life. Not which is most interesting. Which changes something.

PARK. It’s real, it matters, it isn’t now. Parking is not abandoning. Parking is writing down exactly where you stopped, what the next action is, and what condition has to be true for it to come back. “Comes back when the Q4 hire is onboarded.” Then it goes in a folder and out of your head. The write down is what makes parking work. Without it, parked things keep running in the background and cost you the same attention as active ones.

KILL. It’s dead. You’re not doing it. Say so out loud, tell whoever needs to know, and delete the folder.

Be honest about the kill bucket. Most people’s lists have four or five items that everyone quietly knows are dead but nobody has pronounced. The pronouncing is the whole value. A dead project that hasn’t been declared dead still costs you a status meeting, a slot in your head, and a small hit of guilt every time you see it. Declare it and get the slot back.

Send the kill list to your team. It’ll be the most relieving email they get this quarter.

Step Four: Install the Pull Rule

Here’s the rule that makes the ceiling real instead of aspirational.

Nothing new starts until something ships.

That’s it. Slot opens when a thing finishes, not when you feel like starting something. Your list is not a place you push work into. It’s a place work gets pulled from, one out one in.

The immediate effect is that finishing becomes the way you get to do new things. Which is exactly the incentive you want, because right now the incentive runs backward. Right now, starting is how you get relief from the tedium of finishing. Flip it and finishing is how you earn the fun of starting.

Put the three active items somewhere physical and visible. Whiteboard, index cards, sticky notes on the monitor. Not buried in software. The friction of physically removing a card and adding a new one is a feature, not a bug. Digital lists let you add an eleventh item without noticing. A whiteboard with three slots does not.

Step Five: Defend It at Intake

The ceiling will get attacked. Usually by you, occasionally by a client, frequently by an opportunity that’s genuinely good.

You need one sentence ready, and you need to say it without apology: “That’s a yes, and it goes in the queue behind these two. Want me to bump one of them for it?”

Notice what that does. It’s not a no. It doesn’t make you difficult. It makes the trade visible, and it puts the choice on the person asking. Nine times out of ten the answer is “no, finish those first,” because when someone has to actually name what gets delayed, most requests turn out to be less urgent than they sounded.

The tenth time, they bump something, and that’s correct too. That’s the system working.

The other half of defending your ceiling is making sure recurring work never occupies a slot in the first place. Anything that happens the same way every time should not be consuming human attention. The onboarding email sequence, the invoice that goes out on the first, the report you assemble from three tools every Monday, the lead that has to get from the form to the CRM to somebody’s inbox. That’s not work. That’s plumbing, and plumbing should be automated.

I run most of that on Make.com. It connects the tools you’re already paying for and handles the handoffs between them without anybody remembering to do it. The reason it belongs in this conversation and not in a tools roundup is that every process you automate is a permanent slot freed on your WIP board. You don’t just save the twenty minutes. You get the slot back forever.

The Objections, Handled

“My work doesn’t split into projects like that.”

Then use commitments instead. Anything you’ve promised someone, internally or externally, that isn’t done yet. Same exercise, same ceiling, same three buckets. The unit doesn’t matter. The count does.

“Some of my projects take months. I can’t ship in a week.”

Correct, and that’s a definition problem, not a WIP problem. Break it into pieces that produce something a human can look at. A month long project with no intermediate output isn’t a project, it’s a hope. Every two weeks something should exist that didn’t exist before, and somebody outside your head should be able to see it.

“I’ll lose opportunities.”

You’ll lose some. You’ll also finish six times faster, which means you’ll get to more of them per year, not fewer. Nineteen open projects at six week cycles is roughly seventeen finishes a year. Three open projects at one week cycles is over a hundred. You’re not turning down opportunity. You’re turning down simultaneity, and those are not the same thing.

The Bottom Line

Your output isn’t limited by how much you take on. It’s limited by how much you finish, and those two numbers move in opposite directions.

Nine things at forty percent is worth nothing. Three things at a hundred percent is worth three things. The arithmetic is not complicated. The discipline is, because the discipline requires you to look at a good opportunity and say “not while these two are open,” and that feels like loss.

It isn’t loss. It’s the price of finishing, and finishing is the only thing that has ever paid anybody.

Do This Today

Take your list. Circle three.

Everything else gets a P or a K next to it in the next ten minutes. Don’t deliberate. Your first instinct on each one is right about ninety percent of the time and the deliberation is just a way of avoiding the decision.

Then send one email. To your team, your partner, or your assistant. Subject line: what we’re not doing. List the kills.

Ten minutes. And I’d bet money it’s the lightest you’ve felt about work in a month.

Want the board and the scripts?

The WIP Ceiling comes as a one page board you can print, plus the triage decision tree, the parking template that actually gets things out of your head, and the four intake scripts for defending the ceiling against clients, team, partners, and yourself.

Reply with the word LIMIT and I’ll send it, plus details on the 8-Week Savage Gentleman Mastery System, which is where this stops being a trick you tried once and becomes how you run.

Refined. Relentless. Unapologetic.

Marcus