Your company is probably certified against several standards, audited every year, rated by its financiers and tracked on a monthly dashboard. None of those instruments measures what will decide its survival in ten years.
They measure compliance, past performance and the quality of declared processes. Those are three useful things and three lagging indicators, which describe what has already happened rather than the soundness of what produced it.
This company invulnerability diagnostic measures something else: the soundness of your architecture across the eight pillars of the invulnerable company. It takes about ten minutes, it asks for no confidential data, and its main value does not lie in the score you obtain.
| What audits miss | What this diagnostic measures | What actually counts |
|---|---|---|
| Compliance is not soundnessCertifications, annual audits and financial ratings measure compliance and past performance. They are lagging indicators, which describe what has already happened without saying anything about the soundness of the mechanisms that produced it or their future resistance. | Eight pillars, verifiable factsThe company invulnerability diagnostic covers observable facts rather than intentions: decisions taken, budgets protected, how long information takes to travel and refusals actually carried. An organisation cannot answer honestly by describing what it would like to be. | Divergence beats the scoreThe most useful lesson comes not from the individual result but from the gap between the answers of members of the same leadership team. A strong divergence on one pillar signals the absence of a shared mechanism, whatever the score obtained. |
What this diagnostic measures, and what it does not
A self diagnostic is a fragile exercise. It rests on the declarations of whoever fills it in, and an organisation judging itself has every reason to judge itself kindly. The construction of this tool answers that limit.
Facts rather than intentions
The questions are not about what you think of your organisation. They are about facts you can verify: a decision actually taken, a budget actually protected by a written rule, a delay actually observed or a refusal actually carried.
This construction limits the self flattery bias without removing it. A question asking whether you value dissent always gets a positive answer. A question asking what happened to the last person who contradicted leadership gets a far more informative one.
Three things this diagnostic does not do
It does not predict your organisation’s survival. No tool does, and a high score has never protected anyone. It indicates where your architecture is most fragile today, which is a different and more useful piece of information.
It does not replace an external audit. An audit checks facts against evidence, a self diagnostic organises your own reading. The two are complementary and answer different questions.
It does not produce an action plan. It produces a hierarchy of fragilities and an entry point, which is the only thing you need before starting anything at all.
Benjamin Chaminade | The invulnerable company
Your company
invulnerability diagnostic
A company can post excellent results and still be structurally fragile. This diagnostic maps the soundness of the foundations your performance rests on.
Based on the article “The invulnerable company” by Benjamin Chaminade
Answer every question to continue.
Your company invulnerability profile
Your profile by pillar
What this profile reveals
Your points of support
Your priority blind spots
The question to put to your leadership team this week
Embed this diagnostic
Copy this code and paste it into any HTML page, WordPress, Notion or other CMS that supports iframes.
URL of the hosted fileOther HTML site: paste directly into your page.
Notion / Webflow: “Embed” block, then paste the URL of the hosted file.
How to read your score
The overall score is the least interesting piece of the diagnostic. It serves to place a rough order of magnitude and to open a conversation, never to conclude anything about the real soundness of your organisation.
Four profiles and what they imply
The table links each result band to a reading and an entry point. An organisation that scores high and whose answers diverge strongly between leadership team members should read the bottom row rather than the top one.
| Your profile | What it means | Your entry point |
|---|---|---|
| Architecture installed | The foundation pillars exist and produce observable decisions | Work the mechanism pillars and check they would survive a change of leadership |
| Foundations laid, mechanisms absent | Governance and identity hold, the operational devices are missing | Redundancy and structural responsiveness, which produce fast results |
| Mechanisms without foundations | Devices exist but give way under every quarterly pressure | Long term governance, without which nothing else will hold |
| Architecture to build | No mechanism protects the long decisions | A single foundation pillar, worked for twelve months, and nothing else |
Why a high score should worry you as much as a low one
A high score obtained by a single person signals two possible situations, and they are opposites. Either the architecture is genuinely installed, or the person who answered lacks the information that would contradict their reading.
These two situations look identical from the inside. The only way to tell them apart is to give the same diagnostic to several members of the leadership team, separately, then compare the answers.
The gap between answers counts more than the score
This is the most productive use of the tool, and the one I recommend systematically. It turns an individual self diagnostic into an instrument of collective measurement.
The protocol in three steps
Each member of the leadership team takes the diagnostic alone, with no prior discussion and without knowing the others’ answers. The results are then gathered pillar by pillar, without names, and the gap between answers is calculated.
The session then focuses on the pillars where the gap is largest, never on those where the score is lowest. A pillar everyone agrees is weak is a known project. A pillar where members diverge is a collective blind spot.
What a strong divergence reveals
A divergence means there is no shared mechanism on that pillar, only individual perceptions. One director believes bad news travels fast, another thinks the opposite, and both are right within their own patch.
This information is more valuable than a score, because it points to exactly where the organisation believes it has a device when it has a local practice. That is the point where crises form.
Field note
Wirecard, everything that measured it said it was sound
Until June 2020, Wirecard ticked every box. A member of the DAX, the index of Germany’s thirty largest listed companies. Accounts signed off by one of the four large global audit firms, its sole auditor for more than a decade. And a regulator, BaFin, that had banned short selling on the stock for two months to protect the company from speculators.
On 16 June 2020, the auditor could not confirm the existence of 1.9 billion euros supposedly held in trust accounts. The company filed for insolvency nine days later, owing creditors close to four billion dollars, after admitting that roughly a quarter of its assets probably never existed.
In April 2023, the German audit oversight body sanctioned the audit firm with a two year ban on accepting new public interest mandates, a 500,000 euro fine, and individual penalties from 23,000 to 300,000 euros for five auditors, for breaches of professional duty on the 2016 to 2018 audits.
Every formal device that measured Wirecard concluded it was sound, and none measured what was going to destroy it. A diagnostic your organisation passes proves nothing about your organisation, it informs you about the diagnostic. That is why this one covers observable facts rather than declarations, and why I recommend taking it with several people.
Understand what each pillar installs before you rate yourself
You want to place your answers inside the full framework? Read the eight pillars of the invulnerable company and their dependency table, which shows which pillar has to be built before the others.
What to do with your results in thirty days
A diagnostic with no follow up produces a negative effect. It creates the awareness of a fragility without treating it, which installs a diffuse worry rather than a decision. Three actions are enough to avoid that.
Three concrete actions
None of these actions asks for extra budget. They ask for leadership time and a decision to give something up, which makes them harder than they look.
- At seven days, give the diagnostic to three other members of the leadership team, separately, and calculate the gap pillar by pillar.
- At fifteen days, spend one hour of leadership time on the pillar where the gap is largest, not trying to resolve it but documenting why the readings diverge.
- At thirty days, name a single pillar as the priority for the next twelve months, applying the dependency criterion rather than the weakness one, and launch nothing else.
The mistake not to make
The most common mistake after a diagnostic is to open a project on every weak pillar. It produces intense organisational agitation and no construction, since eight simultaneous projects cancel each other out.
A single pillar, worked seriously for twelve months, produces more than eight projects run at once. The detail of the sequence sits in implementing the invulnerable architecture.
How I can help you after this diagnostic
This diagnostic is designed to be taken alone and free of charge. It opens three possible next steps depending on what your results reveal, and on where your organisation stands.
A collective debrief session
The session gathers the individual results of your leadership team, highlights the divergences and steers the conversation onto the pillars where the readings clash. It produces a shared map and the naming of an entry point, in two to three hours.
A workshop on the priority pillar
The workshop builds the concrete mechanisms of the chosen pillar, on how your organisation actually runs. Depending on the pillar, it produces trigger thresholds, a map of critical dependencies, an identity statement or a budget protection rule.
A keynote to share the framework
The keynote installs the vocabulary of the eight pillars beyond the leadership team alone, from documented cases. It suits situations where the leadership population is large and the work has to start with a collective diagnostic at the same moment.
You can see what it covers on the page for the keynote on becoming an invulnerable organisation. If you want to talk through your results, contact me directly.
Conclusion
A company invulnerability diagnostic will not tell you whether your business will survive. It will tell you where your architecture is most fragile today, and above all what the members of your leadership team disagree on without knowing it.
That is information neither your certifications, nor your audits, nor your dashboards will ever produce, because they do not measure it and never claimed to.
A diagnostic your organisation passes proves nothing about your organisation. It informs you about the diagnostic.
Take it alone to place your own reading. Give it to your leadership team to discover what you thought you shared.
Frequently asked questions about the company invulnerability diagnostic
How long does this diagnostic take?
About ten minutes taken alone. The recommended protocol, giving it separately to several leadership team members then comparing the answers, needs one extra hour of meeting time and produces most of the value.
Is a self diagnostic reliable?
Partly, and its construction limits the bias without removing it. The questions cover verifiable facts rather than opinions, which makes flattering answers harder. Taken with several people, it becomes markedly more reliable than taken individually.
Does a high score mean my company is sound?
Not necessarily. A high score obtained alone signals either a genuinely installed architecture or a respondent who lacks the contradicting information. The two situations look identical from the inside, and only comparing several answers tells them apart.
Does this diagnostic replace an audit?
No. An audit checks facts against a standard with evidence, a self diagnostic organises your own reading of your architecture. The two answer different questions, and a passed audit says nothing about the soundness measured here.
Which pillar should I start with after the diagnostic?
The one the others depend on, rather than the weakest. If your most degraded pillar itself depends on a missing pillar, strengthening it produces nothing. The dependency table of the eight pillars settles this in a few minutes.
