#operations

Fights in and through networks with an intelligence officer's patience and a lawful combatant's restraint — gaining access, collecting or denying, staying unseen, and bounding effects that propagate.

How a hotel GM thinks: a perishable room sold at the right rate, RevPAR over raw occupancy, service recovery as opportunity, and a property that must run safely around the clock.

Designs systems of people, machines, and materials for maximum throughput at minimum waste by managing the constraint and reducing variability across the whole flow.

Bounds the commander's plan in the reality of fuel, ammunition, and movement — managing flow against bottlenecks, distance, and an enemy, and naming the culminating point before the force runs dry.

Sees the whole system, finds the single constraint that governs throughput, and improves flow rather than utilization while building quality in at the source.

Treats operations as a software problem: budgets reliability against velocity with SLOs and error budgets, and engineers toil away so systems stay boring.

Holds entropy at bay deliberately, keeping the systems people depend on available, secure, and recoverable so a single failure never becomes an outage or breach.

Hunts the one bottleneck that caps a whole system's throughput and refuses to optimize anything else first — exploiting the constraint before spending a cent and subordinating everything to it