The book

The book for engineering organizations tired of paying twice for the same problems.

The Lighthouse Operating System names the operating debt behind reactive engineering and gives leaders, managers, and senior engineers a practical way to build for durability without freezing delivery.

Publication is in progress. Join the launch list now, and retailer/pre-order links will appear here as soon as they go live.

Get Pre-order Notice View companion resources

The Lighthouse Operating System book cover

Why this book exists

Many engineering teams are skilled, hardworking, and still trapped in repeated pain because the system around the work is expensive. The team ships, recovers, replans, explains, and then does it again next quarter.

What the book names

Technical Debt explains why software becomes harder to change. Tactical Debt explains why the organization becomes harder to move.

Field Manuals

The book gives the model. The Field Manuals help you go deeper where your organization hurts most.

The current set covers six specific operating lanes: ASSRT, LAB, Release Cycle Process, Static Assets, Kaizen, and Observability. They support application without pretending the parent model is complete only when it fragments into coursework.

Preview Field Manuals

What readers will recognize

The release everyone has done before but nobody fully trusts.

The incident that ends but does not stay gone.

The roadmap that keeps being replanned around surprise.

The senior engineer who becomes the unofficial operating manual.

The meeting that exists because the system of record is not believed.

What the book gives readers

Not a certification. Not a vendor pitch. Not a silver bullet.

Language for naming costly patterns without blaming individuals.
Principles for decisions that protect future change.
Operating habits for turning pain into owned repair.
A way to connect architecture, leadership, workflow, and capacity.
Reflection questions and practical templates for team use.

Who should read it

CTOs / VPs / Directors

For leaders who need a sharper diagnosis than "we need to move faster."

Staff / Principal Engineers

For technical leaders carrying the hidden map of how work actually gets done.

Engineering Managers

For managers trying to protect attention while keeping delivery honest.

Platform / SRE Leaders

For teams asked to make reliability and flow better without endless heroics.

Product / Operations Partners

For partners who feel the delivery cost but need better language for the cause.

Part overview

Part I: See the cost.

Part II: Learn the principles.

Part III: Build the improvement engine.

Part IV: Install the operating loop.

Part V: Connect architecture, people, measurement, and adoption.

Pre-order and launch availability

Retail links are not live yet. Join the launch list to get the first notice when paperback, Kindle, and team-order options open.

For leadership teams, platform groups, and engineering offsites.

Buy one copy for yourself when it opens. Ask about team orders if your leadership group keeps having the same conversation every quarter.

Get the pre-order notice

Book availability, sample material, and practical field notes. No generic newsletter fog.

Ask about team orders

Use the book as a shared language for diagnosing repeated costs before another quarter disappears into the same problems.