📘 CASE STUDY — Part X: Operating Code in Action (Saying No, Protecting Health)
SECTION 0 — SCENARIO
Leadership asks for a risky launch in 3 days.
You know:
-
observability is missing
-
rollback plan is unclear
-
team is burned out
Top engineers protect long-term outcomes.
SECTION 1 — APPLY THE PRIME DIRECTIVE
I am responsible for the long-term health of the systems, people, and outcomes I touch.
So you don’t say:
- “No.”
You say:
- “Yes, if we meet safety requirements.”
SECTION 2 — DEFINE NON-NEGOTIABLES
-
feature flag
-
dashboards + alerts
-
rollback rehearsed
-
load test or capacity check
SECTION 3 — OFFER A SMALLER, SAFER PATH
-
ship to 1% internal users
-
measure
-
expand gradually
SECTION 4 — PROTECT THE TEAM
-
reduce scope
-
create on-call rotation clarity
-
avoid heroics
Senior rule:
Burnout is an engineering risk.
SECTION 5 — EXERCISE
Write the message you’d send:
-
risks
-
constraints
-
proposed safe rollout
-
what you need to proceed