A procurement officer once asked me to 'just send the CMMI certificate' so she could close her checklist. I asked if she wanted to know what we actually do differently on a Tuesday because of it. She paused, then said yes — nobody had ever offered. That conversation is this essay.
The common belief
In enterprise buying, CMMI Level 3 functions as a stamp: process maturity certified, risk box ticked, move on. Vendors treat it the same way — win the certificate, put it in the footer, change nothing. Both sides quietly agree it's theatre. That's the myth: not that CMMI is worthless, but that the certificate is the value.
Process exists so the team's worst week still ships something true — not to make slides for procurement.
What the appraisal actually bought us
Getting appraised was expensive and occasionally maddening — months of documenting how we estimate, review, test, and handle change. The certificate wasn't the prize. The prize was discovering, on paper, the three places our 'process' was actually folklore that lived in one senior engineer's head.
Defined process means the playbook survives people. When our delivery lead took paternity leave mid-project, the estimation and review cadence didn't wobble, because it wasn't his personal style — it was written down, trained, and audited. That's the whole point, and no certificate conveys it.
What process-that-works looks like
Estimation with memory: every project's actuals feed the next project's estimates. Vibes get corrected by data quarterly.
Reviews that block: code review and QA gates that can actually stop a release, including when the deadline screams. A gate you can skip under pressure is decoration.
Change control without bureaucracy: scope changes get written, priced, and approved in a day — the discipline is the writing-down, not the meeting count.
Honest retros: every project ends with what-we'd-do-differently, published to the whole team. Our case studies carry that section publicly for the same reason.
The counter-point
Plenty of brilliant two-person teams ship superbly with no framework at all — process can absolutely calcify into its own theatre. The test is simple: does your process change behaviour on the worst week of a project? Ours does; that's why startups in year two stop laughing at the phrase 'vibe coding'.
- Ask vendors what the certificate changes on a Tuesday.
- Write down the folklore; that's 80% of maturity.
- Gates that can't block aren't gates.
- Retros published beat retros performed.