I run engineering across roughly eight products with a team of fifteen. People hear that and assume the answer is some elaborate system, a wall of dashboards and a color-coded life. The truth is closer to the opposite. The more I have to juggle, the fewer and simpler my rules have to be, because a complicated system is just one more thing to maintain. These are the five I actually keep, the ones that survived contact with real weeks.
1. One list, not eight
Every product wants to be its own world, with its own backlog and its own urgency. The moment I let each one own a slice of my attention, I lost. So there is one list, across everything, ranked against everything else. InventoryPath does not compete with its own backlog. It competes with ERPClaw and with sleep. Forcing every priority onto a single ladder is uncomfortable, which is the point. It makes me admit what actually matters this week.
2. Context-switching is a tax, so batch by mode, not by product
The instinct is to spend Monday on one product and Tuesday on the next. It feels organized and it is quietly ruinous, because the expensive switch is not between products. It is between modes of thinking. So I batch by mode. Deep building in one block regardless of which product it serves, shallow review in another, conversations in a third. Switching products inside a mode is cheap. Switching modes is the thing that empties the tank.
3. If it is not written down, it is not a decision
With this many moving parts, my memory is a liability and a verbal agreement is a rumor. Anything that matters gets written, briefly, where the relevant person will see it. This sounds bureaucratic and is the opposite. Writing a decision down takes two minutes and saves the half-hour meeting where three people discover they remembered it differently.
Across eight products, the scarce resource was never time. It was the ability to hold a clear thought without four others elbowing in.
4. Protect the maker's morning
The single rule I break least: the first part of my day belongs to building, not to other people. I have written about the deep-work ritual at length, but the short version is that the work which compounds is fragile and slow to start, and if I let the morning fill with everyone else's priorities, the compounding work simply never happens. Afternoons are for the world. Mornings are mine.
5. Decide what you are willing to do badly
This is the rule nobody likes. You cannot do eight things well at once, so the honest move is to choose, on purpose, what you will let slip this week, rather than failing at everything by accident. Some weeks the social channels go quiet. Some weeks a tidy refactor waits. Choosing your dropped ball in advance is the difference between a deliberate trade-off and a guilty surprise. I would rather decide what I am neglecting than discover it.
That is the whole system. One list, batch by mode, write it down, defend the morning, choose your dropped ball. Five rules, because the sixth would be the first sign I had started managing my productivity instead of doing the work. When you are running everything you build, the goal is never to feel productive. It is to still be thinking clearly at the end of the week.