Run a Fixed Rotation, Not Whatever Company Is Loudest

Give each company a fixed slot in a repeating weekly rotation, and work that rotation instead of chasing whichever company is loudest. This is the single scheduling decision that keeps a solo portfolio from devolving into pure firefighting. Left to instinct, you attend to whatever is screaming: the angry customer, the broken deploy, the overdue invoice. The quiet companies get nothing until they start screaming too. A fixed rotation flips that. Every company gets guaranteed attention on a schedule, so problems get caught while they are small and nothing waits for a crisis to earn your time.

Why reactive scheduling fails

Reacting to the loudest company feels responsive. It is actually the worst allocation of attention available. The loudest company is not the most important one. It is just the one with the most acute symptom right now, and acute symptoms are often the least strategic problems. Meanwhile the company that is quietly stalling, the one where the leading input has been sliding for a month, makes no noise at all, so it gets ignored until the decline is irreversible.

I described the reactive trap in which venture gets attention today. The answer to that question should not be decided by volume. Loudness is a terrible prioritization signal because it rewards whichever problem is best at interrupting you, not whichever problem matters most.

How a fixed rotation works

I assign each company a recurring slot. Some companies get a slot every week, the ones that need active operating. Others get one every two weeks, or once a month, based on how much attention they actually require. The slot is on the calendar, it repeats, and it happens whether or not the company is making noise. That is the whole mechanism.

Two things fall out of this. First, nothing is forgotten, because every company has a guaranteed next touch. The quiet stalling company gets caught at its scheduled slot, weeks before it would have started screaming. Second, switching cost drops, because I know in advance which company I am loading context for and when. There is no whiplash of jumping between five companies in an hour because five things happened to break. I explained why that whiplash is so expensive in the context switching tax a solo operator pays.

Rotation is not the same as ignoring fires

The obvious objection: what about real emergencies? A fixed rotation does not mean I let a production outage burn until its scheduled slot. Genuine emergencies interrupt the rotation, as they should. The point is that the bar for interrupting is high and explicit. A real fire, a customer-facing outage, a legal deadline, those jump the queue. A vague feeling that a company needs attention does not. Most of what feels urgent is not, and the rotation protects me from confusing the two.

The rotation also gives me a place to put non-urgent issues. When something comes up that is not a fire, I do not drop everything to handle it. I note it and it gets handled at that company's next scheduled slot. This keeps interruptions from shattering my week while still ensuring the issue gets addressed soon. It pairs with the discipline in protect one deep work block a day, because a rotation only works if the slots are actually protected.

Make the rotation visible and automated

A rotation living in my head is a rotation that decays. It has to be on a real calendar with real recurring blocks, and each company's slot should surface exactly what needs review when the slot arrives: the metric, the open threads, the pending decisions. I run this off a shared operating surface at reflexware.com, so when a company's slot comes up, its current state is already assembled and I am not spending the first twenty minutes hunting for context.

The deeper win is that a fixed rotation converts operating a portfolio from an anxiety-driven scramble into a calm, repeating routine. You stop wondering whether you are neglecting something, because the schedule guarantees you are not. You stop being yanked around by whichever company is loudest, because loudness no longer sets your agenda. The calendar does. That predictability is what makes running twenty companies feel like a job you control instead of one that controls you.