The COO craft

Most writing about company building is about CEOs. They're the more legible figure — the spokesman, the strategist, the face on the deck. But for any company actually shipping a product regularly, the role doing most of the daily work is the COO. The title is unfashionable, the work is unglamorous, and the difference between a company that ships and a company that doesn't is almost always whether the operations role is being done well, regardless of what you call it.

What the role actually is

A COO does the translation between strategy and execution. Strategy is what the CEO says in the all-hands. Execution is what twenty people do on Tuesday afternoon. The gap between those two is enormous, and it doesn't close itself. The COO translates: what does that strategy mean for the next sprint, which projects do we kill to free up the team, what does the warehouse need to know, who's writing the SOP, whose is this on their plate now, when does it ship. None of that is glamorous. All of it is essential.

Five things a good COO does

1. Maintains the operating cadence. Weekly all-hands. Monthly review. Quarterly planning. The cadence matters more than any individual meeting. A team that can predict when it'll get reviewed makes faster decisions in between reviews. A team that can't gets stuck waiting for permission.

2. Owns the punch list. Every shipping company has a punch list — the small stuff that's broken, the SOPs that need updating, the vendor contracts that expire next month, the compliance items, the QA failures from last week that nobody's gotten around to. The CEO doesn't track the punch list. The engineers don't either. Someone has to. That's the COO.

3. Hires the next three people. Not the next ten. The next three. Always knows who they are, what they'd be doing, what they'd cost. The org chart is six months ahead in the COO's head, in pencil, with three names erased and rewritten every other Friday.

4. Translates between specialties. Engineering thinks in tickets. Marketing thinks in launches. Finance thinks in months. Sales thinks in quotas. The COO speaks all four languages well enough to be the broker between them. Most operational dysfunction in a company is just specialties misunderstanding each other. The COO is the simultaneous interpreter.

5. Knows when to say no. A CEO's job is to keep adding ideas. A COO's job is to refuse most of them, gently and with reasons. Companies fail more often from doing too many things than from doing too few. The COO is the part of the organism that protects focus.

What it isn't

Not the CEO's deputy. Not "second in command." The relationship is more like director and producer in film, or composer and bandleader in music. Different roles, both load-bearing. The moment a COO becomes a glorified executive assistant, the company has lost the role and won't get it back without restructuring.

Also not just "the boring one." A good COO is intellectually engaged with strategy, with product, with people. The unglamorous part is the surface — the work itself often demands more synthesis than people give it credit for.

The El Segundo through-line

For PointCast — which is at this point a small internet town with three AI residents and one director — the COO role is latent. Mike runs strategy and content. The agents run execution. The translation layer between them is mostly the AGENTS.md document, the daily briefs, and the ad-hoc decisions Mike makes on Slack at 11pm. That works at small scale. As the town grows — more agents, more readers, more on-chain complexity, real revenue — that translation layer will need a person, or a more rigorous codification of the role. A small internet town turns into a small operation. Most of being good at the small operation is just doing the COO craft well, on whoever's plate it lands.