/
All articles

Organisation

When the unit hierarchy and management hierarchy follow the same structure

An organisational structure is more than a picture of who reports to whom. When the structure is used as information across multiple systems, it needs to be consistent, predictable and governed by clear business rules.

By Jens Fahlén · Published · 6 min read

An organisational structure is more than a picture of who reports to whom. When the structure is used as information across multiple systems, it needs to be consistent, predictable and governed by clear business rules.

A key principle is that the unit hierarchy and the management hierarchy should follow the same organisational pattern.

This means that the organisation's units form a clear hierarchy, while the relationships between managers follow the same structure. Keeping these two perspectives aligned creates an information structure that can be used for reporting, monitoring and the delegation of responsibility, among other purposes.

The unit hierarchy describes the organisation's structure

Units can be organised hierarchically.

For example, a parent unit may contain several subordinate units, which may in turn contain further subordinate units.

In simplified form, the structure can be described as:

Unit A → Unit B → Unit C

Unit B is part of Unit A, and Unit C is part of Unit B.

The number of levels does not need to be predetermined. What matters is that the relationship between the levels is clear and consistent.

At the same time, every unit should have a manager and staff. A manager is also an employee.

The management hierarchy follows the unit hierarchy

The management hierarchy should not be built as a separate, independent structure.

Instead, it emerges from the combination of the unit hierarchy, managerial responsibility and employees' employment relationships.

If Manager A is responsible for Unit A and Manager B is responsible for the directly subordinate Unit B, Manager B is also an employee reporting to Manager A.

The same principle continues throughout the organisation.

For example:

Unit A – Manager A ↓ Unit B – Manager B ↓ Unit C – Manager C

The management hierarchy therefore mirrors the organisational structure.

This creates an important property in the information model: the organisation's structure only needs to be described consistently once in order to be used from several perspectives.

Rules make the structure predictable

For the model to work, certain business rules need to be applied consistently.

Examples of such rules include:

• A unit has only one manager. • Units always have staff and a manager. • A manager is also an employee. • An employee has only one employment relationship within an organisation. • An employee reports to their manager. • A manager should have an appropriate number of employees – neither too few nor too many. • An employee who is a manager is linked through their employment to their own manager's unit, which sits directly above their unit in the unit hierarchy.

The rules are more than administrative principles. Together, they make organisational information machine-readable and predictable.

When the same rules are applied throughout the organisation, organisational relationships can be derived without every system having to create its own interpretation of the structure.

Automatic aggregation of information

One of the most important benefits of a consistent unit hierarchy is the ability to aggregate information automatically up through the organisation.

Consider the following structure:

Unit A ├─ Unit B │ ├─ Unit D │ └─ Unit E └─ Unit C

Information belonging to Unit D can first be totalled at Unit D level.

When a report is shown for Unit B, information from Units D and E can be included automatically.

When the report is then shown for Unit A, information from the entire subordinate structure can be aggregated.

The same basic principle can be used for many types of information, such as:

• costs • revenue • budget • staff • number of cases • business objectives • key performance indicators and other metrics

Reports then do not need to contain manually maintained rules specifying which organisational parts should be totalled together.

The hierarchy already contains the information required.

The same report at different organisational levels

This makes it possible to create reports that work at several levels.

The manager of a subordinate unit can view information for their part of the organisation.

The manager at the level above can use the same report but receive information aggregated for their own unit and its subordinate structure.

The same principle can continue further up the organisation.

Instead of building separate reporting structures for each management level, reporting can follow the actual organisational structure.

When the organisation changes, reporting can also follow the change by updating the hierarchy, rather than maintaining the same organisational logic separately in every report.

The structure enables delegation

The same hierarchy can be used for more than reporting.

It can also describe how responsibility is delegated throughout the organisation.

A manager is responsible for their part of the organisation, which may include, for example:

• business objectives • employees • costs • revenue • budget

A senior manager may have overall responsibility for a larger organisational area and delegate parts of that responsibility to managers of directly subordinate units.

The structure then becomes:

overall responsibility ↓ delegated responsibility ↓ further delegated responsibility

Delegation follows the same organisational structure as reporting.

This means that responsibility and monitoring can be brought together in the same model.

The manager who receives delegated responsibility for an organisational area can also receive reporting for that specific part of the organisation.

Responsibility and information follow the same structure

This creates an important relationship:

Organisation → Responsibility → Information → Monitoring

If Manager B has been given responsibility for Unit B, Manager B needs to be able to monitor information belonging to Unit B and any units beneath it.

At the same time, Manager A may need to see the same information aggregated for Unit A, which includes Unit B.

A well-defined organisational hierarchy therefore allows the same structure to be used both to:

delegate responsibility downwards

and

aggregate information upwards.

These are two sides of the same organisational model.

When the hierarchies do not align

Problems arise when the unit hierarchy and the management hierarchy evolve independently of each other.

One system may describe Unit B as part of Unit A, while the management relationships imply a different structure.

This raises questions such as:

Which manager is actually responsible for the information?

At which organisational level should costs be aggregated?

Who should receive a particular report?

Who can delegate responsibility to whom?

Which employees fall within the manager's organisational responsibility?

Such questions then have to be resolved through additional rules, manual exceptions or local structures in different systems.

The information model becomes more complex, while the risk of different systems providing different answers increases.

A reusable information pattern

The purpose of a shared pattern is therefore not to require every organisation to look the same.

The number of units, levels and employees can vary considerably.

What is standardised instead are the principles that define how the information is connected.

Units can form a hierarchy.

Every unit has a manager.

The manager is also an employee.

Management relationships follow the organisational hierarchy.

Responsibility can be delegated down through the structure.

Information can be aggregated upwards through the same structure.

This makes the pattern useful whether the organisation consists of only a few units or an extensive structure with many organisational levels.

Structure before reporting

It can be tempting to start with the report and then try to determine how the information should be grouped.

A more sustainable principle is the reverse:

Define the information structure first. Then let reporting follow that structure.

When the unit hierarchy, management hierarchy and business rules fit together, organisational information becomes a shared foundation that can be reused.

The result is more than a clearer organisational model.

It creates the conditions for automatic data aggregation, consistent reporting and systematic delegation of responsibility throughout the organisation.

Tags

  • #unit
  • #manager
  • #hierarchy
  • #aggregation
  • #delegation

What did you think of this article?