The unnamed governor who taught restraint
Marcus Aurelius credits an early “governor”—likely an appointed household tutor responsible for discipline and formation—with a set of habits that anchor the rest of his life. The man is anonymous, which suits the lesson. No philosophy seminar, no grand rhetoric. Just a steady presence who taught a future emperor to keep his feet on the ground: avoid the circus factions, endure labor, want little, use his hands, mind his own work, and refuse slander. The instruction is modest, almost domestic. Its effects are structural.
Refusing the circus
In Meditations Book I, Section 5, Marcus remembers being taught to stay out of the “green” and “blue” teams at the games and to avoid picking sides in the gladiator schools. Stoicism treats factionalism and spectacle as distractions from reason. They borrow your attention and lease your judgment to the crowd.
Modern equivalents are everywhere:
-
Corporate tribes and professional “religions” (framework vs. framework, methodology vs. methodology)
-
Social timelines optimized for outrage
-
Hype cycles that reward alignment over understanding
A leader who needs clarity cannot afford to be colonized by these systems. Detachment is not apathy; it is conservation of agency. The point is to remain available to reality rather than to a party line.
Endurance and wanting little
“Endurance of labor” and “to want little” sound austere, but they are strategic. In any complex system—ships, software, organizations—fragility creeps in through dependence. If you can only function on your optimal day, in ideal conditions, you’re not ready for real conditions.
Endurance means you can keep working when schedules slip, when the weather shifts, when the database fails. Wanting little reduces leverage against you: fewer comforts required, fewer concessions made, fewer compromises on standards. Leaders who need less can say no more often and say yes with intention.
This isn’t ascetic theater. It’s operational independence. In the field, the most reliable operator is the one with a quiet metabolism—steady, hydrated, unentitled, hard to rattle.
Work with your own hands
For a knowledge worker, “hands” are keyboards, terminals, design tools, notebooks. For a captain, they’re lines, fittings, and charts. Either way, the lesson is identical: stay in contact with primary reality.
-
If you architect systems, you should read the logs, run the scripts, and push a small fix now and then.
-
If you set policy, you should experience the workflow you regulate without an entourage cleaning the path.
-
If you command a vessel, you should be able to tie the knot, read the water, and service the gear you rely on.
Direct engagement limits self-deception. It shuts down theater. It also makes you harder to mislead by metrics, slide decks, or selective summaries. In leadership, this is a form of antifragility—you can absorb more truth because you’ve handled the material.
No meddling, no slander
Not meddling is not withdrawal; it is respect for boundaries and ownership. It keeps responsibility paired with authority, which is the backbone of any functional system. Meddling erodes accountability; tasks become “ours,” then no one’s.
Resisting slander is a security practice. Gossip is a low-cost attack on reputations and cohesion. It distorts sensing, scrambles priorities, and creates hidden states in the organization—unspoken assumptions that drive real behavior. Stoic composure here is not a personality trait; it’s governance.
Practical rules:
-
Do not pass along claims you cannot source.
-
Separate incident review from character judgment.
-
Prefer first-hand observation to third-hand narrative, especially under time pressure.
-
When accusations surface, slow the loop, increase evidence, and document process.
-
Build channels for quiet correction so that escalation isn’t the only option.
Guardrails for leaders navigating faction and spectacle
A few practices I’ve found durable across software, ships, and teams:
-
Establish “non-alignment” as a norm. On polarized topics (tools, vendors, methods), write explicit decision criteria and sunset dates. Evaluate by outcomes, not identity.
-
Design attention budgets. Limit meetings and feeds that trade in performance. Replace status theater with dashboards tied to real-world signals: latency, fuel, customer response time, safety events.
-
Maintain minimum manual competency. For every system you own—codebase, vessel, process—define a small set of tasks you can execute personally. Review and refresh quarterly.
-
Adopt a rumor protocol. Claims about people go to a specific, trained channel. Everything else gets documented, time-stamped, and verified before distribution.
-
Practice deprivation reps. Periodically remove a convenience (a tool, a report, an integration) and confirm you can still operate. This is “wanting little” as a test, not a slogan.
-
Keep AI as an amplifier, not an arbiter. Use it to summarize logs, surface anomalies, and check blind spots. Do not outsource moral judgment, ownership, or the interpretation of ambiguous human signals.
Restraint and independence, learned and practiced
In Book I, Marcus Aurelius is mapping the foundations of character: restraint from faction, independence from spectacle, self-sufficiency through disciplined labor, and a refusal to feed on gossip. These are not abstract virtues. They are operating parameters that keep a person—and a system—available to truth.
Most of what fails in leadership fails quietly first: attention gets sold to the crowd, comforts harden into requirements, work drifts from reality, and rumor replaces observation. The course correction isn’t dramatic. It’s the quiet governor’s regimen—do the work, own less, see for yourself, and stay out of the circus.
If this line of inquiry helps your own practice, follow The Rissler Perspective for future essays on leadership, systems, and judgment under real conditions.
