Pillar
Operations
Cadence, process, decisions. The systems that make a business answerable to itself.
Operations is the layer of the business that decides whether the strategy survives contact with Tuesday. Most operating problems are not strategic. They are cadence problems: the meeting that became status instead of decision, the dashboard that has been green for two years while the business deteriorated, the standing meeting that has cost forty thousand dollars and produced one decision.
The essays here cover the rhythms — weekly, monthly, quarterly — that compound into a company that is answerable to itself, and the rituals that imitate the rhythm without producing the answer. The forecast meeting. The 1:1 that became status. The Friday deploy that broke Monday. The integration nobody owned.
Operations is where the founder finds out whether the company can run without them being the answer to every open question. The essays below are what that test looks like from the inside.
Start here
-
The Tuesday Standup
Twelve people, fifteen minutes, every Tuesday for three years. The meeting outlived the project it was built for by twenty-eight months.
-
Two Hires That Saved $2M (and the One That Cost $4M)
The two hires that mattered most last year did not produce a press release. The hire that did produce a press release nearly broke the company.
-
The shadow IT stack you didn't know existed
The official tooling list had 12 subscriptions. The card statements had 47. The other 35 were a stack the company didn't know it was running.
More on operations
- Don't re-commit the OKR you keep missing
- Your SOC 2 Will Take Twice as Long
- The bug backlog nobody decides on
- A Stable Dashboard Is the One to Worry About
- SOC 2 takes eight months, not six weeks
- The billing system only a former contractor understands
- Shipped Tuesday, marketed three weeks late
- 87 items, 12 shipping, zero commitments
- Don't Ship an Integration You Can't Assign
- When the Escalation Path Ends at the CEO
- Your Support Team Is Hitting Every SLA and Failing
- The internal tool nobody used
- Same Three Problems, Every Six Weeks
- Eight engineers, fifteen minutes, zero re-plans
- Stop telling new hires to scroll back