The BetaCodex: Leadership Without Hierarchy in Mid-Sized Companies

The BetaCodex is an organisation model by Niels Pflaeging and the BetaCodex Network that builds leadership on cells with their own accountability for results and moves decisions to where the information sits. It suits organisations with high complexity and close customer contact. In mid-sized companies the path works in four stages, provided senior management moves along with figures and incentives.
This article explains the BetaCodex from its primary source and names fields of use together with limits. It offers a maturity model with test questions and describes an introduction path that fits the size and leadership culture of the mid-sized company. It is written for managing directors and divisional heads who are examining whether less hierarchy would bring more delivery capability to their company.
What is the BetaCodex?
The BetaCodex is a framework of twelve laws for leadership and organisation, developed by the BetaCodex Network and shaped above all by Niels Pflaeging. Its roots lie in the Beyond Budgeting movement, which Jeremy Hope and Robin Fraser described in 2003. Beyond Budgeting criticises rigid annual budgets and fixed targets as well as individual bonuses, seeing them as instruments that lead to wrong behaviour in an uncertain market. The BetaCodex widens this critique into a model of the whole organisation and contrasts two operating systems.
The Alpha model steers through hierarchy and plans, with instruction on top. It assumes that managers know more than the employees at the customer interface. The Beta model steers through a network of cells that answer for results and align their resources with the market. The twelve laws describe the contrast for both sides, for example in targets, planning and incentives. Pflaeging set out the model in detail in his 2015 book “Organisation für Komplexität” (Organise for Complexity).
The argument behind the model runs as follows: the less predictable the environment, the less useful central planning becomes, and the more it matters that people in contact with customers are allowed to decide. The concrete rules follow from that logic. Targets are set relative to the market and to competitors, forecasts roll forward, resources are available on demand and bonuses reflect the success of the group.
What is the BetaCodex suited to?
The BetaCodex suits organisations whose work is complex: fluctuating demand and individual customer solutions as well as knowledge work and fast change in the market. A well-known example from the Beyond Budgeting literature is the Swedish bank Handelsbanken, which has operated without classic budgets since 1970 under Jan Wallander and moved responsibility to its branches. Such cases show that decentralised steering can work over many years, but they say nothing on whether it transfers to every company.
In the mid-sized company the benefit is often tangible. Mid-sized companies usually have short routes to the managing director, and yet many decisions end up there because responsibilities are unclear. The result is waiting time that customers and employees notice. Cells with clear accountability for results speed up decisions when three conditions hold: the figures are visible to the cell, the cell has access to the capabilities it needs for its result, and senior management accepts decisions it would have taken differently itself.
What is the BetaCodex not suited to?
The BetaCodex suits work that is stable, standardised and strictly prescribed less well, such as manufacturing safety-critical components with fixed test steps. There, central procedures secure quality, and local deviations would be a risk. It is also unsuitable as a savings programme: anyone who removes layers of hierarchy to cut costs, and moves neither decision rights nor figures, creates responsibility without authority. Finally, the precondition is often missing in the leadership team. Where managers see their role in control, any decentralisation fails at the first conflict.
The BetaCodex also remains a framework without a fixed procedure. Teams that need clear rituals and roles find them in Scrum as defined in the 2020 Scrum Guide. A comparison with other models appears in the article on the unFIX model, which describes organisational building blocks in place of fixed structures, and in the article on Sociocracy 3.0, which supplies decision patterns.
Which maturity levels lie on the way to the cell?
The way from the classic company to the cell structure can be divided into four maturity levels, and each level is a stable operating state in its own right. The model is a working aid of this article and is not described in the BetaCodex itself. It helps to answer where your company stands today and which step comes next.
Most mid-sized companies stand between level 1 and level 2. The first worthwhile step is level 3 in one part of the organisation, such as a business unit or a product line. There you can observe how speed and quality as well as satisfaction change before further units follow.
How do you introduce the BetaCodex in a mid-sized company?
Introduction works in five steps, each ending with a test question so that senior management can follow progress.
- Clarify the starting point: which decisions land with senior management today, and how long do they wait? An analysis of the last twenty decision papers with their lead time is enough.
- Choose a pilot unit: a unit with a clear customer link, manageable size and a manager who will walk the path. Test question: does the unit have a result it can influence itself?
- Set decision rights: senior management writes down what the cell may decide without consultation, such as spending up to a limit, day-to-day priorities and deployment of staff. Test question: can the cell take a typical decision without anyone outside the cell having to agree?
- Adjust figures and incentives: the cell sees its costs and revenues promptly, and pay rewards the group result in place of individual target achievement. Test question: does everyone in the cell know the three figures that determine their result?
- Evaluate after 90 days: lead time of decisions and customer satisfaction as well as employee feedback are compared with the baseline. Senior management then decides on extension.
This path demands more of managers than of employees. The leadership role shifts from instruction to shaping the conditions, and that shift needs support. Those who skip it often see a pattern described in the article on the Spotify model: the names of the structure change while the decision paths remain.
What role does delivery play in an organisation without hierarchy?
Delivery gains importance as hierarchy recedes, because coordination no longer runs through superiors. Cells need interfaces that make dependencies visible and procedures that coordinate work across cell boundaries. One practical aid is the Flight Levels of Klaus Leopold, which arrange work on levels of coordination. How this looks in practice is described in the article on Flight Levels. Without such procedures, a structure of individual cells emerges that are each fast and whose results do not fit together.
Working with Niehues Consulting towards an effective organisation
Niehues Consulting is a consultancy for AI management and organisation design from a delivery perspective, based in Düsseldorf. Founder Marin Niehues builds organisations that deliver, in projects from VC-funded scale-ups to DAX 40 groups and in more than 20 countries on six continents. In the service area of delivery management and organisation design, the work runs from analysing decision paths through roles and interfaces to supporting the introduction in operations.
The approach follows the Niehues Delivery Model with its three phases. Three test questions count for a change in leadership: who decides, who delivers, who uses? Who is responsible for operations from day one? Which metric shows after 90 days that the solution has landed? The scope and terms of an engagement are discussed in the free initial consultation, which you can arrange in 30 minutes via the contact form.
Frequently asked questions
What is the BetaCodex?
The BetaCodex is an organisation model of twelve laws that Niels Pflaeging and the BetaCodex Network have developed. It contrasts the hierarchical Alpha model with steering through cells accountable for results. Its roots lie in the Beyond Budgeting movement.
What is the difference between Alpha and Beta organisations?
Alpha steers through hierarchy and instruction, Beta through cells with relative targets and decisions close to the customer. The Alpha model relies on central knowledge, the Beta model on knowledge at the customer interface. Both have their field of use, and the BetaCodex applies to complex work.
Is the BetaCodex suitable for a mid-sized company?
The BetaCodex suits mid-sized companies with customer-facing, complex work. Three conditions matter: figures open to the cell, access to the capabilities it needs and a managing director who accepts the cells' decisions. For strictly regulated standard work it fits less well.
How do you introduce the BetaCodex?
The BetaCodex is introduced in a pilot unit that can influence results itself. Decision rights, open figures and adjusted incentives follow, and after 90 days the result is compared with the baseline. Extension to further units follows only after this evaluation.
What does leadership without hierarchy mean?
Leadership without hierarchy means decisions fall where the information sits, and managers shape conditions in place of issuing instructions. Roles remain, but their content changes. The company still needs accountable people, goals and rules for working together.
What is Beyond Budgeting?
Beyond Budgeting is a management approach by Jeremy Hope and Robin Fraser from 2003 that replaces rigid annual budgets and fixed targets with relative targets and rolling planning. The BetaCodex builds on it and widens it to the whole organisation.
Do cells still need bosses?
Cells need people who answer for results and conditions, but the role shifts from instruction to shaping. Senior management remains responsible for purpose and rules as well as the distribution of resources. An analysis of decision paths shows how these roles look in your company.
Does the BetaCodex work with Scrum?
The BetaCodex and Scrum complement each other: Scrum describes how a team works in short cycles, the BetaCodex how decisions, goals and figures are organised in the company. A team working to the 2020 Scrum Guide benefits when the organisation around it clarifies decision rights.
Part of the guide: Organisational design and delivery management: the guide for organisations that deliver
Let’s talk about your initiative.
In 30 minutes we clarify where your organisation stands and which step will pay off most now.
Book a consultation30 minutes · free of charge · no obligation



