Notes from the operating layer

AI execution under real constraints

The writing reflects active operating work on AI execution: the leadership, infrastructure, reliability, cost, and governance systems that determine whether AI becomes durable business capability or organizational theater.

Read the operating thesis Operating context →
Entries316
Canon09
Covers2016–26
Written2026
Latest2026.06.10

A decade of practice, written down

These notes revisit ten years of operating work, from container reliability and security incident response to the AI operating model. The archive was written down and published in 2026 as a retrospective project; each entry is dated to the era it revisits (see the colophon). The throughline is the same discipline applied to a moving target.

26
25
27
25
31
31
30
30
30
26
35
’16 ’17 ’18 ’19 ’20 ’21 ’22 ’23 ’24 ’25 ’26
2016–2018 Infrastructure discipline Containers, databases, reliability: the production fundamentals.
2019–2021 Platform and scale Internal platforms, observability, multi-region, FinOps.
2022–2026 The AI operating layer When models met production reality, and discipline became the differentiator.

The recurring question

// The recurring question

What has to be true for this system, team, or strategy to keep working when the model, the vendor, the cost curve, or the organization changes?

The answer is rarely a better model. It is usually a clearer operating model. AI does not remove the need for operating discipline; it raises the cost of operating without it.

// Canonical reading

  1. No. 01 Build the System the Model Cannot Break AI-NATIVE OPERATING MODEL · AI-OPERATING-MODEL An AI-native company is not the one that adopts the model fastest; it is the one whose operating model the model cannot break.
  2. No. 02 The Throughput Engineer: Why Headcount Is a Lagging Metric THROUGHPUT CULTURE · AI-OPERATING-MODEL Headcount is a lagging metric; the real throughput ceiling is how fast an organization can decide.
  3. No. 03 The CTO Communication Protocol: Aligning Engineers, Executives, and Investors in AI Programs CTO COMMUNICATION PROTOCOL · AI-OPERATING-MODEL AI programs fail when leadership communication stays ad hoc instead of becoming an operating protocol.
  4. No. 04 Why Most AI Platform Teams Become the New Bottleneck PLATFORM BOTTLENECKS · AI-OPERATING-MODEL A central AI platform team becomes a liability when every workflow improvement has to wait in its queue.
  5. No. 05 How Great CTOs Design AI Roadmaps That Survive Contact With Reality REALITY-TESTED ROADMAPS · AI-OPERATING-MODEL An AI roadmap is only real if it can survive latency, ownership, and workflow constraints in production.
  6. No. 06 Decision Latency as a P&L Variable: The Leadership Metric Nobody Owns DECISION LATENCY · AI-OPERATING-MODEL Decision latency is a P&L variable because slow organizational decisions destroy AI leverage before the model does.
  7. No. 07 Designing the AI Leadership Bench: Roles, Interfaces, and Failure Boundaries LEADERSHIP BENCH · AI-OPERATING-MODEL Serious AI execution needs a leadership bench with explicit role interfaces, not a heroic single-threaded leader.
  8. No. 08 The Operating Cadence: Turning AI Leadership Interfaces Into Predictable Output OPERATING CADENCE · AI-OPERATING-MODEL Leadership interfaces only compound when the organization runs them on a predictable cadence.
  9. No. 09 The Post-Prototype AI Org: Operating Models That Survive Year Two POST-PROTOTYPE AI ORG · AI-OPERATING-MODEL The hard part of AI starts after the prototype, when the company has to become an organization that can actually run it.

Latest writing

/blog →
Decision Latency as a P&L Variable: The Leadership Metric Nobody Owns Canon post — · 2 min Decision latency is measurable and should be treated as a direct cost driver. leadership metrics strategy Designing the AI Leadership Bench: Roles, Interfaces, and Failure Boundaries Canon post — · 2 min AI scaling needs explicit leadership interfaces between product, platform, reliability, and governance. leadership teams ai The Operating Cadence: Turning AI Leadership Interfaces Into Predictable Output Canon post — · 4 min Interfaces describe who owns what. Cadence is what turns those interfaces into compounding output. leadership ai operations The Post-Prototype AI Org: Operating Models That Survive Year Two Canon post — · 3 min Year-two AI failure usually comes from org-design mismatch, not model-quality mismatch. The handoffs are where the system slows down. ai teams leadership The AI Vendor Negotiation Playbook for CTOs · 3 min Vendor leverage in AI comes from architecture readiness, eval data, and exit credibility — not procurement theater. ai vendors cost How to Run an AI Incident Review That Changes Architecture, Not Slides · 2 min Incident reviews should produce architecture deltas and control updates, not narrative theater. reliability ai governance How Great CTOs Design AI Roadmaps That Survive Contact With Reality Canon post — · 3 min AI roadmaps fail when they are sequenced around ambition instead of dependency, verification, and rollback cost. strategy ai leadership Hiring for AI Teams: The Operator Profile That Actually Scales · 3 min The highest-leverage AI hires are operators who can handle ambiguity, systems tradeoffs, and verification pressure. hiring ai leadership
See all 316 entries →

Coverage

Where the writing concentrates. Every topic is grounded in production work, not commentary.

AI Operating Systems 113 AI and Systems Architecture 68 Engineering 53 Go 53 Devops 49 Infrastructure 42 Security 38 Technical Leadership 35 LLM 34 Teams 28