When the Organisation Outgrows Its Systems

There is a moment that many growing companies recognise, usually in retrospect.

The systems that built the company — the informal decision-making, the close-knit communication, the processes held in people's heads rather than documented anywhere — have become the constraint. They worked at thirty people. They are not working at one hundred.

The organisation has outgrown its systems.

The standard response is to build the systems that are missing: implement the project management software, document the processes, formalise the reporting structures, hire a head of operations.

This response is not wrong. Systems are necessary. But it is addressing the symptom without addressing the source.

Systems fail to scale not because they are badly designed. They fail because the operating natures that built them and the operating natures that are now required to run them are not the same.

The informal decision-making that worked at thirty people worked because the operating natures of the decision-makers were in close proximity and high mutual legibility. They could read each other. They could trust each other's shortcuts. The speed and informality of the system was supported by the depth of the mutual understanding.

At one hundred people, that mutual legibility does not exist. New people have joined. Functions have separated. The operating natures that are now present in the organisation are more diverse, less mutually known.

The informal system cannot carry what it was designed to carry. Not because it was bad design, but because its design assumed a specific configuration of operating natures that no longer applies.

The formal systems that replace informal ones tend to be designed, again, by the operating natures currently dominant at the leadership level.

A leadership team whose natures lean toward structure and process will design comprehensive, detailed systems. These systems may work excellently for operating natures that are similarly calibrated — and may create significant friction for the operating natures in the organisation that are more intuitive, less documentation-oriented, more relationship-driven.

A leadership team whose natures are more intuitive will design lighter-weight systems that preserve flexibility. These may work well for adaptive signatures and produce chaos for the people who need clear structure to contribute their best.

There is no system that works for all operating natures equally. This is not a design failure.

What changes the system design conversation is understanding the range of operating natures in the organisation and designing systems that create the conditions each type needs to contribute its particular quality of output.

This is more complex than deploying a best-practice system. It produces better results.

Before WHY, there is WHO.

The organisation that has outgrown its systems does not need better systems. It needs systems designed with the operating natures of its people in view — built for the actual humans who will use them, not for the ideal users the design team imagined.

When intuition stops scaling, but responsibility does not — there is a path.

Request Access.