Stratified Systems Theory

Organisations often confuse hierarchy with status.

This is one reason hierarchy has such a poor reputation.

People experience layers of approval, slow decisions, unclear
authority, political behaviour and managers who add little value. They
then conclude that hierarchy itself is the problem.

Sometimes it is.

But the deeper problem is usually not that the organisation has
levels.

The problem is that the levels are badly designed.

Stratified Systems Theory gives us a practical way to think about
this. It asks a simple but demanding question:

What level of complexity does the work require?

That question changes how we think about structure, leadership,
accountability, succession and capability.

It moves us away from titles and towards the real nature of work.

Work Has Different
Levels of Complexity

Not all work is the same.

Some work is immediate and concrete.

Some work requires coordination over weeks or months.

Some work requires designing systems that must hold together over
years.

Some work requires seeing patterns across markets, technologies,
institutions, people, capital and time.

The difference is not only seniority.

It is complexity.

A frontline role may require excellent judgement, discipline and
technical skill, but the time horizon may be short. The person must
solve real problems today, this week or this month.

A middle management role may require coordination across teams,
resources, dependencies and trade-offs over a longer period.

A senior management role may require building systems that will only
show their full consequences in years.

An executive role may require shaping the future of the whole
organisation under uncertainty.

These are different kinds of work.

When we ignore this, we create poor appointments and weak
structures.

We promote a capable operator into a role that requires system
design.

We appoint a strategic thinker into a role that requires daily
operational discipline.

We ask a manager to be accountable for outcomes while giving them
authority only over activities.

We create job titles that sound large but contain work that is too
small.

We create roles that are too big for the person, then call the person
a failure.

Stratified Systems Theory helps us separate the person from the
work.

First understand the work.

Then understand the capability required.

Then place, support and develop people more intelligently.

Time Horizon Is a Clue

One useful way to understand levels of work is to look at the time
horizon of the role.

What is the longest meaningful piece of work for which the role must
be accountable?

If the role is accountable for tasks that must be completed today,
the work sits close to immediate execution.

If the role is accountable for a three-month improvement cycle, the
work requires coordination, follow-through and local problem
solving.

If the role is accountable for a one-year operating plan, the work
requires resource planning, sequencing, trade-offs and management across
multiple moving parts.

If the role is accountable for a three-year capability build, the
work requires system thinking.

If the role is accountable for positioning the organisation over ten
years, the work requires strategic imagination and the ability to act
under deep uncertainty.

Time horizon is not the only measure of complexity, but it is a
useful clue.

The longer the time horizon, the more uncertainty must be
carried.

The more uncertainty must be carried, the more complex the role
becomes.

This is why short-term performance and long-term strategy often
clash.

They are not merely different priorities.

They are different levels of work.

The organisation needs both.

But it must not confuse them.

The Levels Must Add Value

A level of management is justified only if it adds value to the work
below it.

If a manager simply checks, delays, repeats, translates or protects
information, the level is not adding value.

If a manager integrates work, removes constraints, allocates
resources, clarifies priorities, develops people, improves systems and
carries a longer time horizon, the level is useful.

This is a hard test.

Every layer should answer:

What uncertainty do we absorb for the level below us?

What decisions do we make that the level below us cannot reasonably
make?

What resources do we provide?

What system do we improve?

What future do we hold in view?

What conflict do we resolve?

What accountability do we carry?

When these questions cannot be answered, hierarchy becomes
bureaucracy.

When these questions can be answered, hierarchy becomes a way to
organise complexity.

Capability Is Not the
Same as Performance

A common mistake in organisations is to confuse current performance
with future capability.

A person may perform very well in a current role because the work
matches their strengths, knowledge and time horizon.

That does not automatically mean they are ready for the next
level.

The next level may require a different kind of thinking.

It may require moving from doing to coordinating.

From coordinating to designing.

From designing to integrating.

From integrating to shaping.

This is why promotion is risky when it is treated as a reward.

The best performer in one level of work is not always the best
candidate for the next level of work.

Promotion should not only ask:

Has this person succeeded here?

It should also ask:

What level of complexity can this person currently hold?

What level of ambiguity can they work with?

How far ahead can they plan and still act practically?

Can they build systems, or do they only solve tasks?

Can they integrate multiple interests, or do they optimise only their
own area?

Can they create clarity for others, or do they create more noise?

This does not reduce people to a fixed category.

People grow.

People learn.

People mature.

But growth must be understood carefully. Development is not only
learning more content. It is also learning to work with more
complexity.

Why Some Roles Feel Too
Heavy

Many people have experienced a role that feels too heavy.

The work is not merely busy.

It is cognitively and emotionally heavy.

There are too many variables.

The path is unclear.

The consequences stretch too far into the future.

The role requires judgement that the person has not yet
developed.

This does not mean the person is unintelligent.

It means the work may be operating at a level of complexity beyond
their current capability, support or experience.

The opposite also happens.

Some people are trapped in work that is too small.

They become bored, frustrated, restless or difficult. They see
patterns that others are not yet asking them to address. They want to
solve larger problems, but the role gives them only small decisions.

The organisation then interprets this as attitude.

Sometimes it is a mismatch.

Good structure helps both problems.

It prevents people from being crushed by work that is too complex too
soon.

It also prevents people from being wasted in work that is too narrow
for too long.

Designing Roles Properly

A role should be designed around real accountability.

What must this role produce?

What decisions must it make?

What is the time horizon?

What level of uncertainty must it manage?

What resources must it control?

What relationships must it integrate?

What risks must it carry?

Only after these questions are answered should we write the job
title.

Many job descriptions begin in the wrong place. They list activities,
reporting lines, qualifications and generic competencies. They do not
describe the level of work.

The result is confusion.

Two jobs may have similar titles but very different complexity.

Two jobs may have different titles but similar levels of work.

One manager may be accountable for a whole system but have no
authority to change it.

Another may have a large title but spend most of the week approving
small transactions.

Stratified Systems Theory pushes us to ask whether the structure is
honest.

Does the work match the authority?

Does the title match the complexity?

Does the manager add value?

Does the person have the capability and support required?

Succession Planning
Must Look at Complexity

Succession planning often becomes a list of names.

Who can replace whom?

Who is ready now?

Who is ready in two years?

Who is on the talent list?

These questions matter, but they are incomplete.

The better succession question is:

What level of complexity will the future role require, and who is
developing toward that level?

This changes the conversation.

It is not only about loyalty, current performance, confidence,
charisma or educational background.

It is about the ability to hold larger problems.

A person being developed for senior leadership should not only be
given more work.

They should be given more complex work.

They should be exposed to longer time horizons, cross-functional
trade-offs, ambiguous decisions, resource constraints, people dilemmas
and system design problems.

The organisation should watch how they think.

Do they simplify without becoming simplistic?

Do they ask better questions?

Do they integrate information?

Do they see second-order consequences?

Do they create a practical path through uncertainty?

This is the real evidence of readiness.

The Human Risk

There is a danger in any theory of work levels.

It can become rigid.

It can become a label.

It can be used to limit people rather than understand work.

That would be a misuse.

The purpose is not to rank human worth.

People do not have more or less human value because they work at
different levels of complexity.

The purpose is to create better fit between people and work.

Every organisation needs people who can execute well.

It needs people who can supervise and coordinate.

It needs people who can manage systems.

It needs people who can lead functions.

It needs people who can shape strategy.

These are all valuable contributions.

The ethical use of the theory is to respect the difference between
these contributions and design work accordingly.

It should help people grow.

It should help managers stop pretending that everyone can do every
role with enough motivation.

It should help organisations stop wasting people by placing them
badly.

What Managers Can Do

Managers can use this thinking in practical ways.

Map the real levels of work in the organisation.

Look at the time horizons of key roles.

Check whether each management layer adds value.

Clarify accountability and authority.

Review promotions against the complexity of the next role, not only
performance in the current role.

Develop people through work that stretches their thinking.

Do not overload people with complexity without support.

Do not trap capable people in roles that are too small.

Use succession planning to build capability over time.

Ask whether the structure helps the customer, the team and the
strategy, or whether it merely protects the hierarchy.

The value of Stratified Systems Theory is not that it gives us
another model to admire.

Its value is that it asks us to look more honestly at work.

What is the work?

How complex is it?

How far into the future must the role think and act?

What decisions must be made?

What support is needed?

Who is ready for this level of uncertainty?

These are practical management questions.

When organisations answer them well, hierarchy becomes less about
status and more about usefulness.

Structure becomes a way to carry complexity.

Leadership becomes a way to create the conditions in which people can
do work that matches their capability and develops their future.

That is the discipline.

Not more layers.

Not fewer layers.

The right levels of work, clearly designed, properly supported and
honestly led.