F6

Implementation failing through organizational mismatch

Dramatic arc: forced landing

The scene

You bought a new ERP. Top implementer, 18-month budget, strong executive sponsor, dedicated internal team. All the planning is impeccable. At month 12, go-live. At month 14, the retail team uses in parallel three systems — the new ERP for reporting to the board, the Excel file shared on Teams for real decisions, and WhatsApp for what's urgent. At month 18, the project is declared "closed with success". At month 24, discussions begin about replacing the ERP.

It wasn't the system that was bad. The system was good. The organization wasn't ready to receive it. Its real level of procedural maturity — measured post-factum — was somewhere between 1.5 and 2.0 on the CMMI scale. The system was designed for a level 3 organization. The 1-point maturity gap cost 18 months, €4.2 million, and a trust you don't recover quickly.

This is F6. The failure isn't the implementer's, isn't the system's, isn't the sponsor's. The failure is the initial diagnostic that wasn't done. Nobody asked "at what real level of maturity does this organization function today?". Everyone assumed "if we want, we can". Maturity isn't decided. It's conquered in steps, and measured.

„The risk is double — either you overestimate capacity and the implementation fails, or you underestimate it and waste time on unnecessary steps." — Fundamental principle of the Organizational Profile

How you detect it in your own organization

  1. The last 2–3 major implementations (system, methodology, transformation) had the declared end of "success" but the real result below expectations.
  2. You don't have an objective measurement of the procedural maturity level at which you function today — you only have impressions and declarations of intent.
  3. Supplier/solution selection is done on functionality, not on adequacy to current maturity.
  4. The implementation decision is taken based on a business case, not also on an organizational capacity audit.
  5. After partial failures, the organization seeks culprits — doesn't ask for a reassessment of its procedural maturity level.

The instruments that address it

F6 doesn't "resolve" with an instrument. It opens for analysis and maturity diagnostic through a sequence:

  • Organizational Profile (S5). The mother instrument for F6. Maps the organization on 6 canonical dimensions (processes, people, technology, data, governance, culture). The output isn't a "good/bad" label, but a profile with 6 peaks that shows where you're ready and where not — so that the implementation is calibrated on the profile, not on ambition.
  • CMMI Maturity Advisory (S10). Parallel or successor step. Places the organization on an internationally standardized scale (CMMI levels 1–5). The difference from Organizational Profile: CMMI gives a global score comparable with the industry; the Profile gives a detailed internal profile. The two are used together in major decisions.
  • Stability Audit (S6). Adjacent step. Verifies if existing infrastructure can sustain the proposed change — not just if the organization "wants it", but if it can hold it after implementation.
  • Risk Audit (S3). Stress-test step. Names the specific risks of a concrete implementation, calibrated on the organizational profile and CMMI level. The output is a list of realistic vulnerabilities, not generic ones.

Recommended entry point: Recommended entry point: Organizational Profile before any major implementation decision (ERP, CRM, digital transformation, methodological change). 4–6 weeks of audit. The output is an objective profile that, presented to the board together with the business case, fundamentally changes how the decision is taken. The conversation with an OPS consultant starts from real territory, not from desired territory.

Re-anchoring note: The instruments above open the door to understanding fear F6. 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.

Two gates. You choose.

Informal regime — alone, free

Stability isn't the primary gate for F6, but it's the closest gate in the informal regime. The Stability manifesto + interactive questionnaire give you a first reading on the "transferability" level of your critical processes — which is one of the essential dimensions of organizational maturity.

Access Stability

Consultancy regime — with us alongside

For F6, the consultancy regime is the natural gate. Organizational Profile (4–6 weeks of audit, 6 canonical dimensions) plus CMMI Maturity Advisory (internationally standardized positioning) are the instruments that allow you to decide about a major implementation before it fails, not after.

Talk to us

F6 does not live alone

  • F8 — Ad-hoc processes — F6 is the punctual symptom of F8. An organization with ad-hoc processes can function in the current regime, but cannot receive a major intervention without rejecting it. Chronic F8 produces punctual F6.
  • F4 — Exploding promotion — particular version of F6: a major promotion is a mini-implementation. If the organization doesn't have the procedural maturity to sustain it, it explodes as in F4.
  • F3 — AI that lies — F6 is the eligibility filter for AI. An organization of maturity 1–2 that adopts generative AI without protocol is a certainty of F3.