Two Field Guides.

Part VI · Risk and Operating Control — Chapter 42

Mission control and stewardship

The Complete Masterbook · pages 143–145

A serious operator does not run the company from memory, mood, or heroic rescue. He runs it from a small set of visible instruments reviewed before drift becomes damage.

At the beginning, you can hold the whole business in your head. That is convenient and dangerous. Your head is not a control system. It forgets the awkward invoice, softens the missed promise, overweights the exciting lead, and edits the decision after the outcome arrives. The business needs a cockpit: not bureaucracy, not dashboards for theatre, but the few instruments that tell you whether the machine is creating value responsibly. Mission control has one job: make reality visible early enough to act.

It should feel slightly boring when it works. The point is not to impress anyone with colours, software, or a founder vocabulary. The point is to make the same truth hard to avoid twice. If a number matters, it appears on the dashboard. If a promise matters, it has an owner. If a risk matters, it has a trigger. If a decision matters, it has a memo before the outcome arrives.

The weekly cockpit

Review the same categories every week, preferably at the same time:

InstrumentWhat it must reveal
Cashbank balance, protected reserves, collections, payables, runway, next payroll, tax/statutory obligations
Customerspromises made, value delivered, complaints, renewals, referrals, material harm or trust risk
Pipelineleads, qualified opportunities, proposals, decision dates, wins, losses, reason for loss
Deliveryquality, rework, cycle time, founder dependency, capacity, blocked work
Experimentsbelief tested, evidence observed, decision made, process changed
Peopleowners, missed commitments, capacity, conduct, conflict, escalation
Selfsleep, health, family strain, attention, decision quality, signs of avoidance

Numbers need definitions. A “lead” is not a name in a spreadsheet. A “qualified opportunity” is not someone who was polite. “Runway” is not cash divided by fantasy burn. “Revenue” is not collected cash. Mission control begins when definitions stop moving.

The one-page mission brief

For any material project, write the brief before work begins:

  • • task in one sentence;
  • • purpose, problem, and customer or internal user;
  • • definition of done with visible evidence;
  • • deadline and first checkpoint;
  • • owner and accepting authority;
  • • budget, quality, legal, ethical, safety, and reputation boundaries;
  • • decisions the owner may make alone;
  • • decisions requiring approval;
  • • explicitly out of scope;
  • • critical assumptions, base rate, smallest proof, bad plausible case, and kill/redesign criteria;
  • • amber and red escalation triggers.

The read-back matters. In under two minutes, the owner should repeat purpose, outcome, deadline, proof, largest risk, authority, and next update. Correct disagreement before leaving the room. Most expensive execution errors begin in the minute when two people believe they agreed.

Stewardship is the next job after ownership

Ownership asks, “What do I control?” Stewardship asks, “What am I responsible for because I control it?”

That changes the operating standard. Customer data is not “an asset” until you remember that a careless upload can become harm. Payroll is not “cost” until you remember families budget around it. A cap table is not “structure” until you remember trust and incentives live inside it. The company name is not “brand” until you remember that every employee, vendor, and customer lends reputation to it.

The steward counts what cannot be replaced: trust, lawful operation, customer safety, family stability, health, reputation, and the capacity to begin again. He still pursues growth. He simply refuses to finance growth by silently consuming the foundations that make recovery possible.

This is why mission control includes the founder’s condition. Your body, attention, and home are not private trivia unrelated to the company. They are part of the operating system. A founder who is sleeping badly, hiding numbers from family, and making decisions from urgency will eventually make that private disorder visible in contracts, hiring, promises, and cash.

Escalate by trigger, not by pride

Pre-agreed triggers remove shame from escalation. A cash floor breached, a security incident suspected, a customer harmed, a statutory deadline missed, a key person unavailable, a quality defect repeated, a debt covenant approached, a conflict of interest discovered: these should not wait for the founder to feel ready.

Use four lines:

1. Status: what is known now. 2. Impact: customer, money, law, data, people, reputation, or date. 3. Need: decision, resource, reviewer, or authority. 4. Next update: owner and time.

Early escalation feels uncomfortable because uncertainty becomes public. Late escalation feels comfortable because image is protected while options disappear. Choose the first.

Review decisions before memory edits them

Every meaningful decision needs a journal entry: decision, options, assumptions, emotional state, expected outcome, what would prove you wrong, review date, and worst case. Six months later, ask whether the process was sound, not only whether the outcome pleased you.

This is how judgment compounds. Experience alone does not teach. Reviewed experience teaches.

· LG pp. 100–109, 113–114 · GE chs. 34, 43 · ASC pp. 133–138. Mission-control tools are operating controls; adapt scale to risk and stage.