Rapid Change is no longer enough: why companies need Radical Change today

In recent years, many companies have learned to become faster: faster decisions, faster approvals, faster reactions to market shifts. That was necessary – and it is no longer enough. A company that only gets faster without asking whether its own capabilities still match its goals is optimising the wrong end of the problem.

In practice, this often looks like this: more projects run in parallel, more tools are in use, yet decisions still take longer. Responsibility is spread across several roles without anyone truly owning it. At the end of the reporting period there is a lot of activity – but little that shows up as actual impact. This is exactly the gap Radical Change addresses.

Reality check: a first look at your own situation

Before getting into models and terminology, it is worth taking an honest look at your own organisation. Six questions most leadership teams can answer within a few minutes:

Where do we lose time today because decisions take too long? Which important change has been stuck in a concept for months? Where are we trying to solve a structural problem with a new tool? Which capabilities are we actually missing? Is responsibility for implementation genuinely clear? And: which initiative produces activity but barely any impact?

Anyone who hesitates on two or more of these questions is probably facing a Radical Change situation – regardless of what the initiative is called internally.

What does Rapid Change mean?

Rapid Change describes situations in which external conditions shift so quickly that companies must remain able to act at short notice: a market shift, a regulatory intervention, a technology leap, a crisis. The term is about speed and pressure to adapt – the pace at which a company must react, not primarily how deep the change needs to go.

Why speed alone is no longer enough

Speed alone says nothing about whether an organisation is moving in the right direction. A company can react very quickly and still miss its own goals if its capabilities no longer match what will be needed tomorrow. Pure adaptation speed optimises how the present is handled, not fitness for the future.

The real question is therefore not only how fast a company reacts, but: is our company, with its current capabilities, actually still built to achieve what we need to achieve tomorrow?

Rapid Change versus Radical Change

Rapid Change optimises adaptability: deciding faster, shipping faster, reacting faster. Radical Change builds development capability: an organisation's ability to continuously adjust its own capabilities to new goals, instead of just increasing its pace. Radical Change is therefore not an intensification of Rapid Change, but a different level: Rapid Change asks how fast a company reacts. Radical Change asks whether the right capabilities exist at all to react to the right thing. Radical Change should be understood as an independent perspective of Hosang Consulting, not as an established scientific standard framework.

Three examples make the difference tangible. Business model: the Rapid Change question is "how quickly can we roll out a new offering?", the Radical Change question is "do we actually have the capabilities to serve a new customer segment with this offering long-term?". Organisation: Rapid Change asks "how do we speed up our approval processes?", Radical Change asks "are decision rights and responsibility distributed so that the right people can make the right decisions at all?". AI: Rapid Change asks "how do we automate this task faster?", Radical Change asks "what capability will our organisation need going forward, and should it be provided by a person, a team or an agent?".

What Radical Change is not

Radical Change is not a hectic overhaul, not an AI project for its own sake, and not a new transformation programme with 80 slides. It is not activism that mistakes busyness for progress, and not change that stays without named owners and an implementation plan.

Radical Change means addressing the necessary change exactly where capabilities, responsibility, decision paths or implementation logic no longer match the intended goal. Not more than that, but not less either.

From VUCA through BANI to SALTER

Since the 1990s, organisations have used the acronym VUCA (volatile, uncertain, complex, ambiguous) to describe why classic planning reaches its limits. 2020 brought BANI (brittle, anxious, nonlinear, incomprehensible), which focuses more strongly on the psychological and structural fragility of today's systems.

SALTER sits on this line: an orientation framework developed by David Fiorucci with his company LP3 (Biel/Bienne), which positions itself as an evolution of VUCA and BANI. In six letters, SALTER describes six fractures of the present – among them sensory overload, the loss of authenticity through screens and algorithms, unstable roles and identities, social tribalism, avoidance of responsibility, and a rupture with meaning and cohesion – and assigns a counter-movement to each.

SALTER as an external orientation framework

We regard SALTER positively and respectfully as an independent, serious contribution to the discussion around VUCA and BANI – as a language for something many leaders sense without being able to name it.

Binding distinction: Radical Change and QUENARIS are not an implementation of SALTER, but an independent, compatible perspective on the development capability of companies. There is no partnership, no technical integration and no joint product with LP3 or SALTER.

Radical Change starts with goals and capabilities

Radical Change deliberately does not start with the org chart, a process or a technology. The starting point is a single question: what must the company be able to do in future to reliably achieve its goals? Only afterwards does the question arise of which structure, process or technology best provides that capability.

Companies as capability systems

From this perspective, a company is not an org chart, but a system of capabilities: people, teams, classic software, automation and increasingly Agentic AI jointly provide what an organisation needs to be able to do. Development capability means deliberately designing and continuously adapting this system, rather than letting it grow only historically.

Agentic AI changes who provides capabilities

Agentic AI fundamentally changes this view. It is more than just another automation tool: it potentially changes the architecture of organisational capabilities itself – the question of who or what will provide a given capability in future.

The decisive management question is: which capability does the organisation need, and who or what will provide it going forward – a person, a team, classic software, automation or an agent?

Human responsibility remains central. Agentic AI can bring information together, prepare options and execute tasks – it does not decide autonomously on business-critical responsibility. That stays with the people in charge.

QUENARIS as a software solution and thinking tool

QUENARIS, developed on behalf of Hosang Consulting, is not pure management consulting but a software solution: a tool for changing thinking processes and a system that makes company development visible over time.

QUENARIS connects goals, required capabilities, existing capabilities, perceptions, information, decisions, knowledge, tasks, implementation, learning and adaptation into one coherent picture. Instead of viewing capabilities and decisions in isolation, QUENARIS makes their relationship to one another visible.

The QUENARIS Operation Center and development over time

The QUENARIS Operation Center is the layer on which development and decision histories are mapped over time. It shows not just a state, but a trajectory: which goals applied, which capabilities existed for them, which decisions were made, and how the company changed as a result. Internal architecture and agent details that are not publicly released are deliberately not described here.

How we approach such situations

A Radical Change initiative practically begins with a sober comparison: what is the goal? Which capabilities does it require? Which capabilities actually exist today? Where are the gaps? At Hosang Consulting, this runs through eight steps that carry different weight depending on the situation, but always make sense in the same order:

1. Understand the situation – without a premature solution. 2. Clarify the goal and the bottleneck – what should become achievable, and what prevents it today? 3. Review existing capabilities – across people, teams, software and automation. 4. Make missing capabilities visible – concretely, not in general terms. 5. Clarify responsibility – who decides, who carries implementation. 6. Structure decisions – governance instead of gut feeling. 7. Accompany implementation – not just planning, but staying the course. 8. Review impact – and adjust when the goal shifts.

The result is not a blueprint, but a concrete, prioritised change: the one capability gap that must be closed first so the company fits its own goal again. These eight steps are not a sales promise, but the way Hosang Consulting actually works through such situations.

Conclusion

Rapid Change remains important: companies must continue to react quickly to change. But speed alone does not secure future fitness. Radical Change adds the question that counts: whether a company's own capabilities still match its own goals – and how people, classic software, automation and Agentic AI jointly ensure that these capabilities keep growing with it.

The decisive question is not how much change a company can withstand. What matters is which change is necessary so that the most important goal actually becomes achievable with existing and developable capabilities.

FAQ

What is Rapid Change?

Rapid Change describes situations of fast external change in which companies must remain able to act at short notice – the focus is on pace and pressure to adapt, not on the depth of the change.

What is Radical Change?

Radical Change is Hosang Consulting's independent perspective on the necessary depth of change: an organisation's ability to continuously adjust its own capabilities to new goals, instead of just becoming faster.

What is the difference between Rapid Change and Radical Change?

Rapid Change optimises adaptability, Radical Change builds development capability. Rapid Change asks how fast a company reacts, Radical Change asks whether the right capabilities exist at all.

Why isn't classic change management enough for Radical Change?

Classic change management usually accompanies one specific initiative with a defined start and end. Radical Change concerns the continuous fit between goals and capabilities – an ongoing state, not a one-off measure.

What do VUCA, BANI and SALTER have to do with Radical Change?

They describe the growing complexity and fragility of the environment companies operate in today. Radical Change builds on this finding by asking which capabilities companies need to remain able to develop within it.

What is SALTER?

SALTER is an orientation framework developed by David Fiorucci and his company LP3, which positions itself as an evolution of VUCA and BANI and describes six fractures of the present along with corresponding counter-movements.

Who is David Fiorucci?

David Fiorucci is the founder of LP3 (Biel/Bienne) and the developer of the SALTER framework as well as other concepts in the field of conscious leadership.

How does our Radical Change perspective relate to SALTER?

We regard SALTER positively as an independent contribution. However, Radical Change and QUENARIS are not an implementation of SALTER, but our own, compatible perspective – without partnership or technical integration.

What role does Agentic AI play in Radical Change?

Agentic AI potentially changes who provides an organisational capability. The central question is which capability is needed and whether it is carried by people, teams, software, automation or an agent – responsibility remains with people.

What does it mean for a company to be a capability system?

It means viewing a company not primarily as an org chart or process landscape, but as an interplay of capabilities jointly provided by people, teams, software, automation and Agentic AI.

What role does QUENARIS play in Radical Change?

QUENARIS makes Radical Change operational: it connects goals, required and existing capabilities, decisions and knowledge into one coherent picture and makes development visible over time.

How does the QUENARIS Operation Center make development visible over time?

It does not just depict a state, but a trajectory: which goals and capabilities applied at which point in time, and which decisions led to which development.

How does this perspective differ from Leverage Experts' "Situations of Rapid Change"?

With "Situations of Rapid Change", Leverage Experts accompanies concrete, often acute situations of fast change such as strategy, crisis and M&A questions. Radical Change sets in one level further: at future capabilities, decision architecture, and the continuous interplay of people, software and Agentic AI.

How does a Radical Change initiative practically begin?

With a reality check: clarify the goal, determine the required capabilities, compare them against existing capabilities, name the gaps, and prioritise the one change that is needed next.

Radical Change is an invitation to take your own development capability more seriously than pure adaptation speed.