Can a company work without traditional hierarchies?

Can a company work without traditional hierarchies? The question usually starts with a practical problem: too many layers slow decisions, managers become bottlenecks and people wait for permission to do work they understand.

Removing layers does not solve the problem by itself. Without clear criteria, responsibility and coordination, a flatter chart can produce more meetings, informal conflict and decisions made by whoever speaks most confidently.

A manager usually sets priorities, allocates resources, resolves conflict and owns results. If one layer disappears, those functions still need an owner. Separate hierarchy from authority: a position orders roles, authority defines who decides and responsibility defines who protects the result.

A flatter structure can help when expertise is distributed, decisions are frequent and people can access the information they need. It is harder when risk is high, dependencies are strong or the organization is changing quickly.

Replace command with explicit mechanisms. For every important topic, state who decides, who is consulted and who is informed. Publish priorities and define how disagreement is raised, examined and closed when the group does not converge.

The common danger is informal hierarchy. People may accumulate influence by controlling information or access to senior decision-makers. Make authority visible, assign an owner to each important result and test one workflow before changing the whole company.

Distributing decisions also requires a way to learn from outcomes. A decision can be reasonable with the evidence available and still produce a disappointing result. Review the assumptions and the process rather than treating the outcome as proof that nobody should decide independently.

A small decision log preserves this learning. Record the date, subject, owner, criteria, limits and review date. Over time it shows which questions keep returning to the top and which rules could be made simpler.

Delegation fails when the manager continues to request updates on every detail. Agree on a few signals instead: expected result, deadline, main risk and review point. The person closest to the work can choose the method unless an explicit constraint applies.

The right to refuse a competing request is part of a real mandate. Someone who must protect a priority but cannot reject additional work has responsibility in name only. Define how exceptions are negotiated and who decides when priorities conflict.

The same logic applies to temporary projects. A project manager may coordinate the work, but budget, quality, timing and customer commitments still need clear owners. A job title does not assign decision rights by itself.

Measure the change with simple signals: less waiting, fewer requests sent to the wrong person, fewer reopened decisions and clearer next steps. If nothing improves, revise the mandate before adding another control.

When a decision exceeds its threshold, escalation should arrive as a useful package: situation, options, recommendation, risk and decision required. This keeps senior people from becoming a manual routing system and lets them focus on choices that truly need their responsibility.

Explain the new way of working to people affected downstream. A rule is clear only when they know whom to contact, what information to provide and when to expect an answer. Communication is therefore part of implementation, not a final announcement.

Do not document every activity in the company. Start with one workflow that creates friction, test the mandate and observe a real case. Extend the model only when experience shows the same ambiguity exists elsewhere.

The aim is an organization where control remains where it matters and autonomy grows where the risk allows it. Leadership becomes more useful when it clarifies direction and boundaries instead of repeatedly replacing other people’s work.

Distributing decisions also requires a way to learn from outcomes. A decision can be reasonable with the evidence available and still produce a disappointing result. Review the assumptions and the process rather than treating the outcome as proof that nobody should decide independently.

A small decision log preserves this learning. Record the date, subject, owner, criteria, limits and review date. Over time it shows which questions keep returning to the top and which rules could be made simpler.

Delegation fails when the manager continues to request updates on every detail. Agree on a few signals instead: expected result, deadline, main risk and review point. The person closest to the work can choose the method unless an explicit constraint applies.

The right to refuse a competing request is part of a real mandate. Someone who must protect a priority but cannot reject additional work has responsibility in name only. Define how exceptions are negotiated and who decides when priorities conflict.

The same logic applies to temporary projects. A project manager may coordinate the work, but budget, quality, timing and customer commitments still need clear owners. A job title does not assign decision rights by itself.

Measure the change with simple signals: less waiting, fewer requests sent to the wrong person, fewer reopened decisions and clearer next steps. If nothing improves, revise the mandate before adding another control.

When a decision exceeds its threshold, escalation should arrive as a useful package: situation, options, recommendation, risk and decision required. This keeps senior people from becoming a manual routing system and lets them focus on choices that truly need their responsibility.

Explain the new way of working to people affected downstream. A rule is clear only when they know whom to contact, what information to provide and when to expect an answer. Communication is therefore part of implementation, not a final announcement.

Do not document every activity in the company. Start with one workflow that creates friction, test the mandate and observe a real case. Extend the model only when experience shows the same ambiguity exists elsewhere.

The aim is an organization where control remains where it matters and autonomy grows where the risk allows it. Leadership becomes more useful when it clarifies direction and boundaries instead of repeatedly replacing other people’s work.

Distributing decisions also requires a way to learn from outcomes. A decision can be reasonable with the evidence available and still produce a disappointing result. Review the assumptions and the process rather than treating the outcome as proof that nobody should decide independently.

A small decision log preserves this learning. Record the date, subject, owner, criteria, limits and review date. Over time it shows which questions keep returning to the top and which rules could be made simpler.

Delegation fails when the manager continues to request updates on every detail. Agree on a few signals instead: expected result, deadline, main risk and review point. The person closest to the work can choose the method unless an explicit constraint applies.

The right to refuse a competing request is part of a real mandate. Someone who must protect a priority but cannot reject additional work has responsibility in name only. Define how exceptions are negotiated and who decides when priorities conflict.

The same logic applies to temporary projects. A project manager may coordinate the work, but budget, quality, timing and customer commitments still need clear owners. A job title does not assign decision rights by itself.

Measure the change with simple signals: less waiting, fewer requests sent to the wrong person, fewer reopened decisions and clearer next steps. If nothing improves, revise the mandate before adding another control.

When a decision exceeds its threshold, escalation should arrive as a useful package: situation, options, recommendation, risk and decision required. This keeps senior people from becoming a manual routing system and lets them focus on choices that truly need their responsibility.

Explain the new way of working to people affected downstream. A rule is clear only when they know whom to contact, what information to provide and when to expect an answer. Communication is therefore part of implementation, not a final announcement.

Do not document every activity in the company. Start with one workflow that creates friction, test the mandate and observe a real case. Extend the model only when experience shows the same ambiguity exists elsewhere.

The aim is an organization where control remains where it matters and autonomy grows where the risk allows it. Leadership becomes more useful when it clarifies direction and boundaries instead of repeatedly replacing other people’s work.