An organisational structure that actually works

Most companies do not suffer from a shortage of talent, capital or good intentions. They suffer from a structure that quietly works against them. When responsibilities overlap, when processes cross departmental borders without a clear owner, and when job descriptions live only in a drawer, the organisation starts spending its energy on internal friction instead of results. This is precisely why organisational architecture is the number-one factor that determines the desired behaviour of the organisation as a whole — and therefore its ability to deliver the desired results in a specific business environment.

Architecture as the number-one factor

Organisational architecture is not an org chart. It is the way you connect three layers that are usually viewed in isolation: business functions, core business processes and organisational structure. When these three layers are aligned, the behaviour of employees naturally gravitates towards company goals. When they are not, even the best people produce misaligned outcomes, because the system steers them that way.

“Organisation is not something you see. It is a pattern of relationships.” — Buckminster Fuller

Thinking of structure as architecture changes the question you ask. Instead of “who reports to whom”, you ask “what should the optimal organisational structure of our company look like so that it delivers the desired results”. That is a design problem, not an administrative one.

The three layers that must connect

Effective organisation design begins with analysis, not with drawing boxes. In practice we examine several areas that together form an integrated whole:

• Revenue and supply sources — where value truly comes from and what determines it.
• Business functions — whether each function exists for a reason and whether identified gaps have been closed.
• Core business processes — how interconnected they are and where the flow of work breaks down.
• The existing structure — which anomalies it already carries and what they cost.

Only once you understand how revenue, functions and processes actually behave does structure stop being an abstraction and become a tool for directing behaviour.

Balancing remit, authority and accountability

The heart of a healthy structure is the balance of three concepts that are often confused. Remit is the scope of work you are charged with. Authority is the right to make a decision and commit resources. Accountability is answering for the outcome. Dysfunction arises when these three are separated.

The aim of design is that, for every significant piece of work, there is one person in whom remit, authority and accountability converge. That is what makes a structure “work” rather than merely exist on paper.

From the top of the pyramid to the workplace

An optimal structure is built from the top of the pyramid downwards — from top management, through business functions (subsystems), down to the level of individual roles. Each level inherits the logic of the one above it, so that an individual role is not an isolated point but a link in the value chain.

An organisation design project is not considered complete until interconnected job descriptions are finalised and specific people are placed into positions in the new structure. A job description is not a bureaucratic formality — it is a contract of contribution that tells each person what is expected of them, what they have at their disposal and what they answer for.

Why the work is done with company leadership

Structure design is always led with the company’s chief executive and the team of top managers. Subsystem structures are worked out with key people from individual departments, but the final solutions are adopted by the full management team. This is not a matter of hierarchy but of ownership: a structure the team designs itself is a structure it will defend.

Typical anomalies of existing structures

Before you design something new, it pays to recognise what is already holding you back. The most common anomalies we encounter:

1. Functions without a process owner — no one answers for a flow that crosses departmental borders.
2. Stacked layers of management that slow decisions and dilute accountability.
3. Improvised positions built around people rather than around the work.
4. Outdated or non-existent descriptions that leave everyone interpreting their role differently.
5. Centralised authority while accountability is pushed downwards.

Each of these anomalies produces predictable, undesirable behaviour. The good news is that predictable behaviour can also be redesigned.

Conclusion

A structure that actually works is not one that looks tidy on an org chart, but one that leads people to do the right things in the right way. It is the result of deliberate design in which functions, processes and structure are connected, and in which remit, authority and accountability are balanced — from the top of the pyramid to the very last role. If you recognise any of these anomalies in your company, it is time to treat structure as a lever for growth rather than a legacy. Book a strategic conversation and let us build an architecture that delivers the desired results.