Do we really have to choose between VUCA and BANI? Is the rise of BANI going to push VUCA out? I must have missed the memo, because I thought that had already happened.
I also assumed that after VUCA we were finally done with brightly coloured acronyms inherited from the nineteen nineties. Apparently not.
My slightly sarcastic side is inclined to believe that consultants who have lived with VUCA for two decades, watching it finally reach the mainstream, spotted a well-timed opportunity to stay relevant with fresh words like non-linear and disruption. That reading is unfair to Jamais Cascio, who wrote BANI carefully and never sold it as a replacement. It is entirely fair to a good deal of what has been built on top of it since.
So here is the VUCA vs BANI comparison, done properly, with the dates corrected and the table you came for. Then I want to spend the second half on something no other comparison bothers with. The two acronyms describe the same world from two different positions, and the position you speak from decides which one comes out of your mouth.
| The question asked | The usual answer | The variable nobody compares |
|---|---|---|
| Which acronym describes the world betterThe VUCA vs BANI debate asks whether volatile, uncertain, complex and ambiguous still holds, or whether brittle, anxious, non-linear and incomprehensible has replaced it. Both are descriptions of an environment rather than methods for acting inside it. | VUCA is structural, BANI is humanAlmost every published comparison lands in the same place. VUCA is presented as external and strategic, BANI as internal and psychological, and BANI as the natural successor. The distinction is accurate and stops short of being useful. | The position of the speakerBenjamin Chaminade’s reading is that the two acronyms were written from different places in a hierarchy. VUCA comes from the command position and BANI from the receiving position, so the word an organisation reaches for reveals where the speaker sits rather than what the world is doing. |
What VUCA and BANI each actually say
VUCA and BANI are both four letter descriptions of an operating environment. VUCA names volatility, uncertainty, complexity and ambiguity. BANI names brittleness, anxiety, non-linearity and incomprehensibility. Neither one prescribes an action, which is the source of most of the confusion around them.
Before comparing them it is worth stating each one cleanly, because a surprising number of published comparisons misdefine one or two of the letters.
VUCA, four conditions and a military classroom
VUCA describes an environment through four conditions: volatility, meaning rapid and large swings, uncertainty, meaning outcomes that cannot be predicted from what is known, complexity, meaning many interacting variables, and ambiguity, meaning facts that support more than one reading. It entered management vocabulary through United States military education after the Cold War.
The context matters more than the letters. This vocabulary was built to teach senior officers how to plan when the map no longer matched the ground. It assumes a planner, a chain of command and a decision to be taken.
Each condition has its own operational consequences, which I have covered separately in the articles on volatility, uncertainty, complexity and ambiguity.
BANI, four conditions and a futurist’s essay
BANI describes an environment through four different conditions: brittleness, meaning systems that look solid and shatter without warning, anxiety, meaning the psychological state produced by living inside those systems, non-linearity, meaning effects out of proportion to their causes, and incomprehensibility, meaning the point where more information stops producing more understanding.
Jamais Cascio is an American futurist and scenario planning specialist who created the acronym. His writing is careful about what it claims, describing BANI as a sense-making lens rather than a management method.
He has also published a matching response set he calls positive BANI, pairing each condition with a counter-quality: bendable, attentive, neuroflexible and interconnected. Those four belong to him, and they are frequently repackaged elsewhere without the credit. The full definition of BANI sits in its own article.
The date almost every comparison gets wrong
Most VUCA vs BANI comparisons date BANI to 2020. Cascio has written that he coined the acronym in 2018 and put it in front of the public in 2020 through an essay on facing an age of chaos. The two year gap matters, because it separates the idea from the pandemic that is usually credited with producing it.
This correction is worth making for a practical reason. If BANI were a pandemic artefact, it would age out with the pandemic. It was written before, which makes it a description of a structural condition rather than a reaction to one event.
VUCA vs BANI, the comparison in full
Set side by side, VUCA and BANI differ on origin, on what they place at the centre of the picture, on the response each implies and on the kind of organisation each was written for. They agree on more than the comparison industry admits, because both describe an environment that refuses to hold still.
Read the table once for the facts, then read the origin row again. That row explains most of the rest.
Reading the VUCA vs BANI table by origin and by focus
Origin and focus are the two rows that carry the comparison. VUCA emerged from military planning education and focuses on the predictability of an environment. BANI emerged from futures work and focuses on the fragility of systems and the state of the people inside them. Everything else follows from those two facts.
| Dimension | VUCA | BANI |
|---|---|---|
| Meaning | Volatility, uncertainty, complexity and ambiguity | Brittle, anxious, non-linear and incomprehensible |
| Origin | United States military education, adopted into business vocabulary after the Cold War | Coined by futurist Jamais Cascio in 2018 and published publicly in 2020 |
| Centre of the picture | The predictability and stability of the environment | The fragility of systems and the emotional state of the people in them |
| Implied response | Plan, gather intelligence, clarify intent and stay agile | Build slack, reduce anxiety, think in systems and accept partial understanding |
| Written for | A planner with authority over the system | A person experiencing the system from inside |
| Main weakness | Assumes enough analysis will restore predictability | Describes the condition without indicating what to do about it |
| Best used when | A decision has to be taken and the options need framing | A team has stopped believing the plan and needs its experience named |
Where the two frames genuinely disagree
The real disagreement sits in one assumption. VUCA holds that better information and sharper analysis reduce uncertainty, which is why it pairs so naturally with scenario planning. BANI holds that some situations stay incomprehensible however much information arrives, which changes what a leader should even be attempting.
That single difference has practical consequences. Under VUCA, a leadership team responds to confusion by commissioning more analysis. Under BANI, the same team responds by building slack into the system and deciding faster on less.
Everything else the comparison industry lists as a difference is a difference of emphasis rather than substance.
The variable nobody compares, who is doing the describing
VUCA and BANI describe the same events from different positions in a hierarchy. VUCA was written from the position of someone commanding a system and deciding how to move through it. BANI was written from the position of someone inside a system, absorbing what it does to them. The acronym an organisation reaches for reveals that position.
Once you see this, the question of which framework is more accurate stops being interesting. Both are accurate about the position they were written from.
VUCA speaks from the command position
Every VUCA condition is phrased as a property of the terrain facing a decision maker. Volatility is something the environment does. Complexity is something the environment contains. The implied speaker stands outside the turbulence with a map, a staff and the authority to choose a route.
This is why boards find VUCA comfortable. It flatters the position they occupy, describing difficulty as a navigation problem rather than an experience.
It is also why VUCA language tends to survive in strategy documents long after it has stopped meaning anything to the people executing them.
BANI speaks from the receiving position
Two of the four BANI conditions describe a state of mind rather than a state of the world. Anxiety is something a person feels. Incomprehensibility is a failure of understanding located in the observer. The implied speaker stands inside the system with no authority to change it, describing what arrives.
This explains the speed at which BANI spread through workplaces after 2020. It gave people words for an experience their organisation’s official vocabulary had no room for.
Australian data gives that experience a cost. Mental health conditions now account for 12 per cent of all serious workers’ compensation claims, after a 161 per cent rise over ten years, with a median time lost of 35.7 working weeks against 7.4 weeks across all serious claims.
Why one event produces two vocabularies
A single disruption reaches a board and a delivery team through completely different channels. The board receives it as a variance in a report, weeks later, already summarised. The team receives it as a shift that changes what Tuesday looks like. Same event, two experiences, two vocabularies.
The gap widens when the workforce carrying the disruption has the least security. The ABS counts 2.4 million casual employees and 1.1 million independent contractors, with 17 per cent of employees holding no minimum guaranteed hours.
Those people experience volatility as a roster. Nobody in that position has ever described their week as ambiguous.
Field note
The same disruption, described twice
I ran a session with an Australian services organisation where the executive team and a group of frontline team leaders were in the building on the same day for different reasons. I asked both groups the same question in separate rooms. Describe, in your own words, what happened to this business over the last eighteen months. No prompts, no acronyms offered, no framing.
The executive answers came back in the language of conditions and choices. Market shifted. Client mix changed. We had to reposition. Every sentence had the organisation as its subject and a decision at the end of it. The team leader answers came back in the language of things that happened to them. Rosters moved. People left and were not replaced. Nobody could say what next quarter looked like. Same eighteen months, same firm, two entirely separate accounts. When I put the two lists on the same wall, the executive group went quiet, and the first thing one of them said was that they had assumed the messages had landed.
The operational lesson is that the vocabulary gap is a measurable governance signal rather than a communication problem. Run the exercise before you choose which frame to present, because a leadership team speaking pure VUCA to a workforce living pure BANI will be heard as denial, whatever the slides say.
Measuring the vocabulary gap in your own organisation
The gap between how leadership describes a disruption and how the frontline describes the same disruption can be measured directly, in about an hour, with no survey tool. Ask both groups the same open question separately, then compare the grammar of the answers rather than their content. The difference is the finding.
This shifts the unit of analysis. Instead of debating which acronym fits the world, you measure which acronym fits each level of your own organisation.
A protocol you can run this month
The protocol has five steps and needs two rooms, two facilitators and one shared question. Keep the groups apart until the comparison, and resist the urge to offer either acronym as a prompt. The whole value sits in the words people choose without help.
- Pick one real disruption the whole organisation lived through, recent enough to remember and settled enough to discuss.
- Ask each group separately to describe what happened, in their own words, with no framework offered and no leading questions.
- Capture the answers verbatim, including the grammar, since the subject of each sentence carries the finding.
- Sort each sentence by whether the organisation acts or is acted upon, which separates command language from receiving language.
- Put both lists on the same wall in front of both groups and let the silence do the work.
Repeat it once a year against a different disruption. A gap that narrows shows your communication is landing, and a gap that widens shows the opposite regardless of what your engagement survey reports.
What the gap tells you about governance
A wide gap means decisions are being taken on a description of reality that the people executing them do not share. That is a governance failure rather than a morale issue, because it produces plans built on conditions nobody at the delivery end recognises. The plan then fails for reasons the board reads as poor execution.
The correction is cheaper than most leaders expect. Adopting some of the receiving vocabulary in board papers changes what gets discussed, because language decides which problems are even sayable.
Under Australian model work health and safety law, psychosocial hazards including job insecurity and workload are matters an organisation must manage. The legal effect varies by state and territory, so take proper advice on your own obligations.
Turn the description into a decision
Ready to stop comparing acronyms and start choosing? Read my full method for building a BANI strategy and find out where each strategic option relocates your organisation’s fragility.
How to choose which frame to put in front of your leadership team
Choose the frame by audience and by purpose rather than by accuracy, since both are accurate. Use VUCA when a decision needs framing and the room has authority to act. Use BANI when a group has stopped believing the plan and needs its experience named before any plan will land.
This section is decision support rather than a recommendation. Two organisations of the same size can reasonably reach opposite answers.
The criteria that actually decide it
Four criteria settle the choice: the authority of the room, the emotional temperature of the group, whether a decision is due, and whether the audience has already been given the other acronym in the last two years. That last one matters more than anyone admits, because a repeated frame stops being heard.
A board with a decision on the table and no visible distress is a VUCA audience. A management layer absorbing a restructure it did not design is a BANI audience.
Mixed rooms are the hard case. In a mixed room I name both, explain the position each was written from, and let people place themselves. That move does more work than either acronym alone.
Signals that you have chosen the wrong frame
Three signals show up quickly when the frame misses. The room agrees politely and asks no questions. Someone reframes your point back to you in their own vocabulary, which is a correction rather than a compliment. Nobody uses the language again after the session ends.
The third signal is the reliable one. A frame that fits gets borrowed within a fortnight, usually in a meeting nobody planned.
If none of it sticks, the problem is rarely the acronym. It is that the organisation has been given vocabulary when it wanted a decision, which is a distinction I explore further in my work on the age of fragility.
How I can help you use these frames without the jargon
I work with executive teams and boards on the gap between the language of the decision and the language of the delivery, using VUCA and BANI as diagnostic instruments rather than as slideware. The work runs as keynotes, executive sessions, facilitated workshops or a short diagnostic, depending on how wide the gap already is.
The test I apply is simple. If your people leave repeating an acronym, the session failed. If they leave describing their own situation more precisely, it worked.
Keynotes and executive sessions
A keynote suits a conference or a leadership offsite where a large group needs a shared reference quickly. An executive session suits a smaller room with a live decision, where the frame has to do work the same afternoon. Both run in Australian English with Australian data.
I bring the ABS, Safe Work Australia and sector-specific figures relevant to your industry rather than generic international examples that nobody in the room can act on.
The deliverable is a shared vocabulary the group actually uses, tested in the room before anyone leaves.
Workshops and vocabulary gap diagnostics
The diagnostic runs the protocol described earlier across two or three levels of your organisation, then reports the gap with the verbatim language attached. It suits organisations heading into a restructure, a merger or a strategy refresh, where the cost of a hidden gap is highest.
Workshops go further and rebuild the shared vocabulary, which usually means retiring several phrases the leadership team is fond of.
Where the work sits inside a broader resilience agenda, it connects directly to building a company that stops breaking in the same place.
Conclusion
Another four letter arrangement will arrive. It will be explained in ten minutes, badly, and it will describe the same world these two already describe. You do not need a new gadget for that.
What you need is the understanding that your degree, your past experience and your hundred year old employer put nobody in safety. Both acronyms say so in their own dialect, which is the only thing they genuinely agree on.
So stop running the VUCA vs BANI argument as though one of them wins. Ask instead which one your board speaks, which one your frontline speaks, and how far apart those two answers have drifted. That distance is the finding, and it is the only part of this comparison that will change what happens on Monday.
Frequently asked questions about VUCA vs BANI
Are we in a post-VUCA world?
We are in a post nothing at all. Many professionals are only now meeting VUCA for the first time, and BANI is one option among several. The useful move is staying curious and accepting that what worked before belongs to before.
Is BANI going to replace VUCA?
BANI extends VUCA rather than cancelling it, adding the fragility and psychological dimensions the older acronym left out. Both remain in active use in Australian organisations. The VUCA vs BANI question is better answered by audience than by accuracy.
Who created VUCA and who created BANI?
VUCA entered management vocabulary through United States military education after the Cold War, with no single widely agreed author. BANI was created by American futurist Jamais Cascio, who has written that he coined it in 2018 and published it in 2020.
Which framework should I use with my leadership team?
Use VUCA when the room has authority and a decision is due, since it frames options for a planner. Use BANI when a group is absorbing change it did not choose, since it names the experience first. Mixed rooms need both, with the difference explained.
Are there alternatives to VUCA and BANI?
Several exist, including RUPT and TUNA, and each rearranges similar observations into new letters. Adding acronyms rarely improves decisions. The more productive question is which vocabulary your organisation already uses at each level.
