The BANI model and IT projects 

In the world of IT projects, which is characterized by unpredictability and complexity, the BANI model offers a new perspective that goes beyond the VUCA model. For the first time emerged dthe BANImodel 2020 in an article by Jamais Cascio. Is it a step forward, or does it just describe familiar relationships in different words? We present it to you:


B - Brittle

The vulnerability of previously stable systems to cracks and fractures has become increasingly apparent. Volatility becomes a risk of collapse.

Communicate within the team if you find weaknesses. This will help you to stabilize your IT project. Strengthen each other when things go haywire in the project. The strength to withstand the pressure together strengthens your resilience for future IT projects.


A - Anxious

Every decision in an IT project harbors the risk of new pitfalls in this uncertain terrain. Fear of potential risks can be paralyzing.

Accept that it is normal to want to hold on to the familiar and avoid change at first. It is part of the process to slowly approach constant learning and change in your organization. Talk about it. By understanding concerns, you can bring your strengths to bear in a more targeted way.

N - Non-linear

The causes of certain effects in your IT project can no longer be traced back in a straight line. This makes it difficult to remove obstacles and plan with confidence.

Be creative - perhaps the unconventional solution is the one that will get your IT project back on track.

I - Incomprehensible

The clear direction is lost in the abundance of information and noise in your IT project. You find it difficult to find the starting point for change.

Use technological advances, among other things, to make the causes transparent. Then choose the most effective method for your biggest problem.

Identify challenges in your IT project

The reasons for the problems in your IT project can be hard to find. In your team possibly structures need to be re-establishedto eliminate the difficulties. Change is always possible and mmeanwhile necessary in order toan IT project successfully. This is because the BANI model is not a definitive solution. is according to Cascio a reactionthat gives hope of finding suitable measures. Also Mattenberger from the Zurich School of Economics finds, dthat such models create claritythat can guide us through change. can.

From our project experience we can confirm: It helps helps in every IT project to first give the child a name. We can thereby contradictions and different opinions within the team. Thisthis management task mustumust according to Weinert does not always mean to overcome these contradictions totoresolve them.

Tackling problems and finding solutions

Thanks to the clear identification of the problems, we can work on improvements in a more targeted way. If we stopped at naming the problems, we would get nowhere. The question of which model is best suited to your IT projectYou can only through more context and identifying concreter problems answeren. We are happy to support you if you help need help!