F8

Ad-hoc processes that work only for heroes

Dramatic arc: house on sand

The scene

Friday evening, 7:40 PM. The phone rings. "We have a crisis at the central warehouse, you need to come." You get in the car. You arrive at 9:15 PM, you fix it, you're home at 1 AM. Saturday morning you get a thank-you message from the director: "Without you we were lost."

This happens 4–6 times per quarter. Every time, you are the solution. Every time, without you it would have been a disaster. Every time, the organization learns that, when there's a crisis, you resolve. Nobody builds the process that resolves without you.

Then comes your two-week vacation. Two weeks. On return, you find 47 accumulated problems, of which 11 are already escalated to the board as major incidents. The board's question isn't "why did they happen?". The question is "where were you?".

This is F8. It's not that people are incompetent. They're very competent — within the limits of their roles. The problem is that the organization doesn't have rules that function independently of the heroes' presence. Its apparent stability comes from the overlapping of individual intelligences, not from the architecture of transferable processes. The moment one of the heroes leaves, is absent, gets sick — the system collapses in the direction of that hero's vulnerability.

„Stability is not achieved through individual competence. It is achieved through rules that work regardless of who executes them." — Fundamental principle of Stability

How you detect it in your own organization

  1. There are 2–4 people about whom everyone says "without X we couldn't". Do you have a registry of them? Or just a silent dependency?
  2. Critical processes (escalations, emergency decisions, incident closures) are written and annually reviewed — or do they exist in the minds of those who execute them?
  3. Can a new employee in a key role fulfill the role with 80% efficiency in 30 days just from existing documentation, or do they need 6–12 months of tacit mentoring from "those who know"?
  4. The most recent 3 operational crises were resolved through process or through one person's intervention? What's the ratio?
  5. If the most indispensable person would leave tomorrow, do you have a documented transition plan or do you have a panic?

The instruments that address it

F8 doesn't "resolve" with an instrument. It opens for analysis and construction of procedural discipline through a sequence:

  • Stability (S6). The mother instrument for F8. Maps existing critical processes, evaluates them against 4 criteria (written, transferable, tested, reviewed), and produces a list of structural fragilities — not a remediation plan. The plan comes from the consulting that follows, calibrated on priorities.
  • CMMI Maturity Advisory (S10). Parallel step. Places the organization on the CMMI scale — which, in essence, measures the degree of F8. Level 1 = everything depends on people, level 5 = everything depends on processes. The road from 1 to 3 is the road out of F8.
  • Organizational Profile (S5). Adjacent step. Identifies which of the 6 dimensions (processes, people, technology, data, governance, culture) is the weak point that maintains F8. Often it's not the "processes" dimension — it's the "culture" dimension (the organization values heroism more than discipline).
  • Risk Matrix (S3, component). Prioritization step. Among the fragile processes identified by Stability, ranks them by the probability × impact of a crisis caused by the hero's absence. So that consulting attacks first the processes where dependence on the hero is most risky.

Recommended entry point: Recommended entry point: Stability Audit (free combo with Risk Matrix). 1 session of 90 minutes, process mapping, short list of priority fragilities. From here, the conversation with an OPS consultant starts from an honest mirror — not from a "where to start?" question.

Re-anchoring note: The instruments above open the door to understanding fear F8. Solving it properly comes through an OPS consultancy intervention calibrated on what the instruments have evidenced. No instrument, alone, substitutes for the analysis and human decisions that follow.

An observation that appears only here

F8 never produces a visible crisis on its own. It produces all the other crises through the background erosion it institutes. This makes it the hardest fear to sell — because the beneficiary doesn't feel it as a pain, but as a normal reality. If the reader reaches F8 and doesn't recognize the situation "without X we couldn't", it's probably because they don't have X yet — or because X is them.

Two gates. You choose.

Informal regime — alone, free

Start with Stability. Doctrinal manifesto on operational standard + interactive questionnaire that maps your critical processes according to 4 canonical criteria (written, transferable, tested, reviewed). The output: a list of priority fragilities. F8 is the primary fear for which Stability was built.

Access Stability

Consultancy regime — with us alongside

For F8, the consultancy regime is the long road, but the only real road. The Process Stabilization Program — Phase 1 (Organizational Profile + documentation of the 3 most fragile critical processes) — is probably the first time your company will truly have written processes. It's an emotional experience, not just a professional one.

Talk to us

F8 does not live alone

  • F6 — Implementation failing — Chronic F8 produces punctual F6. An organization that functions on heroes cannot receive a major intervention without rejecting it. F8 is the structure, F6 is the symptom.
  • F1 — The invisible customer crisis — F8 is the certainty of F1. Without a weekly process of reading weak signals, F1 isn't a probability; it's an inevitability.
  • F4 — Exploding promotion — F8 is the background mechanism. One promotion passes, one explodes. The difference is a heroic intervention present or absent. F8 makes randomly what should be systematic.