Flat management can reduce layers of hierarchy. But when it removes the support, accountability and leadership that employees need to perform, the savings can become expensive.
Many organisations often operate under tight margins. Every hire matters, management capacity is limited, and adding another layer of supervision can feel like an unnecessary expense.
A flat management structure can be an effective response. It can shorten decision-making, give employees more autonomy and reduce bureaucracy.
But a flat structure is not the same as an absence of management.
In many organisations, I have observed two recurring situations that create very different problems but can lead to the same outcome: high employee turnover.
In the first, a relatively inexperienced employee is hired to keep costs down and is expected to learn on the job, often without sufficient structure or supervision.
In the second, an experienced specialist is hired to bring expertise into the business but is given so much autonomy that their contribution is evaluated almost exclusively through their individual output. Their ability to work with, develop and support others receives far less attention.
One employee needs more guidance. The other needs greater accountability for how they work with people.
Yet both situations expose the same management problem: the organisation has considered the cost of hiring but not the cost of creating the conditions in which that person can succeed.
1. The inexperienced hire: When learning becomes firefighting
Imagine a small organisation that needs someone to manage projects, coordinate clients or handle operational tasks. An experienced professional would be ideal, but the budget cannot accommodate one.
The organisation hires someone junior instead.
There is nothing inherently wrong with this decision. Hiring for potential can be a sound strategy, particularly when an organisation is willing to invest in development.
The problem arises when the organisation makes the lower-cost hire but expects the performance of an experienced professional.
The new employee is thrown into live work, learns through trial and error, and is expected to figure out the organisation’s systems while keeping daily operations moving.
When a problem arises, they receive instructions on how to resolve it. When another problem appears, they receive another set of instructions. Over time, their working life becomes a continuous cycle of reacting to whatever is most urgent.
They may become very good at putting out fires without ever developing the underlying knowledge required to prevent them.
The psychological cost of learning without structure
Learning on the job is valuable, but learning requires more than exposure to difficult situations.
Research on instructional scaffolding by Wood, Bruner and Ross (1976) describes how structured support helps learners perform tasks they cannot yet manage independently. As competence develops, that support can be gradually withdrawn.
The principle is relevant to the workplace: people need a bridge between what they can do now and what they are expected to do eventually.
For a junior employee, that bridge might include:
- Clear expectations about what they should know and be able to do.
- Documented processes, examples and reference materials.
- Regular reviews of their work, with specific feedback.
- Access to someone who can answer questions and explain the reasoning behind decisions.
- A progressive increase in responsibility as competence develops.
Without these elements, employees may accumulate experience without developing a coherent understanding of their role.
They learn how to handle individual incidents but struggle to recognise patterns, anticipate risks or make sound decisions independently.
This is not necessarily a problem of ability or motivation. It may be a problem of how the work environment supports learning.
Role ambiguity can also contribute to workplace strain. Research by Kahn and colleagues (1964) examined the relationship between organisational roles, role conflict and role ambiguity, establishing an important foundation for understanding how unclear expectations affect employees.
When someone does not know what good performance looks like, which decisions they can make or when they should escalate a problem, they spend energy trying to interpret the environment instead of performing the work.
When the employee becomes the organisation’s shock absorber
The consequences can be subtle at first.
The employee asks more questions. Tasks take longer. Project managers escalate issues. Quality becomes inconsistent. Management becomes frustrated that the employee is not becoming more independent.
Eventually, the employee may begin to lose confidence or disengage.
They might delay decisions because they fear making the wrong choice. They might stop raising concerns because previous attempts to obtain help have gone nowhere. They might focus on completing the immediate task rather than improving how the work is done.
The organisation sees an employee who is struggling to perform. What it may not see is an employee who has spent months navigating uncertainty without enough support to build competence.
You cannot expect independence to emerge from an environment that has not invested in developing it.
If the budget only allows for a junior hire, management must account for the additional supervision, training and review time that the decision requires.
The salary may be lower. The management investment cannot be assumed to be lower too.
2. The experienced hire: When expertise becomes an exemption
Now consider the opposite situation.
An organisation invests in an experienced specialist because it needs a particular skill set. This person has a strong track record, knows their field and can deliver work that others cannot easily replicate.
The organisation expects the specialist to improve the team’s capability, perhaps by mentoring junior employees, sharing knowledge or helping colleagues deliver better work.
But the specialist continues to operate primarily as an individual contributor.
They deliver their own work. They prefer to handle the important tasks themselves. They may become impatient with less experienced colleagues or resist the time required to explain their decisions.
When collaboration becomes difficult, management accommodates them because their expertise is valuable.
Deadlines are important. The specialist’s contribution is difficult to replace. The organisation cannot afford to lose them.
So exceptions begin to accumulate.
Feedback is softened. Behaviour is explained away. Junior employees are expected to adapt. Managers work around the specialist rather than addressing the problem directly.
Eventually, a familiar sentence enters the conversation:
“You know, X is normally like that.”
This sentence can sound like an acknowledgement of personality. In practice, it can become a way of making a recurring problem seem inevitable.
Individual competence is not leadership competence
One of the most important distinctions in organisational management is that being excellent at doing the work is not the same as being excellent at enabling other people to do it.
Many specialists develop their reputations through individual achievement. They solve difficult problems, produce high-quality work and become the people others turn to when something needs to be done well.
Those strengths are valuable.
But leadership introduces a different set of demands. It requires communication, delegation, feedback, conflict management, coaching and the ability to build trust across different levels of competence.
These skills do not automatically develop alongside technical expertise.
Laurence J. Peter and Raymond Hull’s The Peter Principle (1969) popularised the idea that people can be promoted beyond the level at which they are effective. Although the book is satirical rather than a definitive scientific account of management, it highlights a useful distinction: success in one role does not guarantee competence in a different role with different demands.
The same principle applies when an expert is expected to mentor, manage or lead without preparation.
A strong individual contributor may need explicit development to become an effective leader. If the organisation expects them to train junior employees, that responsibility must be treated as part of the role rather than as an optional favour.
When the organisation rewards output but ignores the method
The problem becomes more serious when an expert’s performance is assessed only by what they personally deliver.
Suppose a specialist completes their own assignments on time but struggles to coordinate dependencies, share information or secure cooperation from colleagues.
The specialist may still look productive on an individual scorecard. Meanwhile, the wider team experiences delays, repeated conflict and growing frustration.
Sometimes, the specialist delegates difficult conversations or pressure to another influential person in the organisation. Work may eventually get done, but the coordination cost is transferred to someone else.
The organisation gets the output while overlooking the conditions under which it was produced.
This creates a distorted incentive. Employees learn that individual delivery matters more than collaboration, knowledge transfer or the development of others.
And if the specialist is repeatedly excused from standards that apply to everyone else, the organisation communicates another message: some people are too valuable to be held accountable.
That message affects the whole team.
3. The warning signs are already in the workflow
These problems do not always announce themselves through formal complaints or an obvious breakdown in performance. Often, the first indications appear in everyday operations.
Signs that an inexperienced employee is not receiving enough support
- Junior employees become noticeably hesitant or fearful around particular leaders.
- Work that they previously completed competently begins to deteriorate in quality.
- Decisions are delayed because employees are uncertain about what they are allowed to do.
- Project managers escalate issues repeatedly, but the underlying blockers remain unresolved.
- The same mistakes recur because feedback addresses individual incidents without building broader competence.
- The employee appears busy and reactive but makes little progress towards independent ownership of their responsibilities.
None of these signs proves that inadequate supervision is the cause. Workload, unclear processes, personal circumstances and other factors may also be involved. They are prompts to investigate the working environment rather than reasons to label an employee.
Signs that an expert is not being held accountable for their impact on others
- Conflict between a specialist and their direct reports becomes a recurring pattern.
- Complaints about communication, treatment or collaboration are repeatedly dismissed.
- Management makes exceptions because replacing the specialist would be difficult.
- Other employees are expected to compensate for the specialist’s unwillingness or inability to collaborate.
- Knowledge remains concentrated in one person rather than being transferred to the team.
- The specialist delivers individual assignments but struggles with work that depends on coordination across people.
- The organisation continues to experience the same interpersonal problems without a clear improvement plan.
Again, the purpose is not to assume that the specialist is always at fault. Disagreements may be mutual, roles may be poorly designed, and management may have created conflicting incentives.
The important question is whether the organisation investigates the pattern and addresses its causes, or simply adapts around it.
When the same problem keeps recurring, the organisation needs to examine the system that allows it to recur.
4. Why one employee leaves while the other stays
The two situations can produce an especially damaging imbalance.
The junior employee may eventually leave because the role demands more than the organisation has prepared them to handle.
They are expected to take on substantial responsibility but receive little guidance, inconsistent feedback or insufficient support. The job becomes frustrating, development feels limited, and the effort required to keep up no longer seems worthwhile.
The organisation may interpret the departure as evidence that the employee lacked resilience or was not a good fit.
But it should also ask whether the role was designed to make success achievable.
The expert, by contrast, may remain because the organisation continues to need their specialist contribution.
Management fears the disruption of losing them. Their expertise is difficult to replace, recruitment takes time, and the immediate commercial consequences of their departure appear too great.
So the organisation tolerates behaviour it would not accept from someone with less influence.
This is where a short-term financial decision can become a long-term operational problem.
The junior employee’s departure creates recruitment costs, lost knowledge and repeated onboarding. The expert’s continued employment may preserve technical output while allowing collaboration problems to persist.
In both cases, the organisation is paying a price. It is simply paying through different channels.
Research on organisational justice and employee turnover provides a useful lens here. Employees form judgements about whether they are treated fairly, whether decisions are consistent and whether their contributions are valued. Colquitt’s (2001) work on organisational justice demonstrates the importance of distinguishing different dimensions of fairness, including procedural and interpersonal justice.
The practical implication is that employees do not evaluate a workplace solely by salary or job title. They also experience the organisation through its decisions, relationships and standards.
When support is unavailable to one employee but exceptions are repeatedly made for another, the organisation risks undermining the credibility of its own expectations.
5. What both situations require from management
The two employees do not need identical interventions. They need management to recognise the difference between a capability gap and an accountability gap.
For the junior employee: Build competence deliberately
If you hire someone who is still developing, do not confuse giving them responsibility with leaving them alone.
Start by defining what successful performance looks like. Identify the knowledge and skills they need, the decisions they should be able to make independently, and the situations in which they should seek guidance.
Assign an owner for their development. This person should monitor progress, review work and ensure that feedback translates into improved performance.
Create a progression from guided execution to independent ownership. As competence increases, reduce supervision accordingly.
Most importantly, management must remain involved long enough to determine whether the employee is progressing, whether the training is working and whether the role is realistic for their current capability.
Yes, this takes time.
That is the trade-off.
If the organisation cannot afford an experienced hire, it must be prepared to invest in developing the less experienced one. If it cannot provide either the necessary expertise or the necessary development support, it needs to reconsider the role’s scope and expectations.
For the expert: Make collaboration part of performance
If you hire an expert, define the full contribution the organisation expects from them.
If the role includes mentoring, knowledge transfer, delegation or leadership, these responsibilities should be explicit. They should have deliverables, time allocated to them and a clear way of evaluating progress.
Technical expertise should not exempt someone from standards of professional conduct.
Feedback about recurring interpersonal problems should be specific, evidence-based and directed towards observable behaviour. The objective is not to demand that someone change their personality. It is to establish what effective collaboration requires and whether the employee is meeting that standard.
For example, instead of saying, “You need to be less difficult,” management might explain that project decisions are being delayed because concerns are raised late, responsibilities are unclear or disagreements are handled in ways that discourage colleagues from contributing.
The next step is to agree on concrete changes and review whether they occur.
Trust is central to this process. Research on psychological safety, notably Amy Edmondson’s (1999) study of work teams, examines how a shared belief that interpersonal risk-taking is safe relates to team learning.
Employees need to be able to ask questions, admit uncertainty, raise concerns and discuss mistakes without expecting humiliation or retaliation.
That does not mean eliminating accountability. It means creating conditions in which problems can be surfaced and addressed before they become more expensive.
An expert who needs other people to deliver successfully must learn to work through them, not merely around them.
And management must model that expectation by addressing problems directly rather than relying on colleagues to absorb the consequences.
6. Flat management still needs clear ownership
A flat organisational structure can work well. It can give people autonomy, reduce unnecessary approvals and make it easier to communicate across a team.
But flatness should describe the structure, not the absence of management responsibility.
Employees still need to know:
- Who sets priorities and resolves competing demands.
- Who is responsible for training and development.
- Who makes decisions when teams disagree.
- What standards apply to everyone, regardless of seniority or expertise.
- How performance and conduct concerns are raised, addressed and reviewed.
These responsibilities do not necessarily require additional management layers. In a small organisation, one person may own several of them.
What matters is that the responsibilities are explicit and consistently exercised.
Without that clarity, the organisation can become dependent on individual personalities: the manager who happens to be available, the colleague who knows how to solve the problem, or the specialist whose cooperation everyone is reluctant to challenge.
That is not operational resilience. It is operational dependence.
And the more the organisation depends on informal workarounds, the harder it becomes to maintain consistent performance as the business grows.
7. The real cost of shortcuts
Every organisations must make trade-offs. They cannot always hire the most experienced candidate, build elaborate training programmes or introduce every management process that a larger organisation with more budget can afford.
The objective is not to eliminate constraints. It is to manage them consciously.
If you hire for potential, budget for development.
If you hire for expertise, define the responsibilities that come with that expertise.
If you choose a flat structure, make sure the necessary management functions still have owners.
If you expect employees to collaborate, evaluate how they contribute to the work of others, not just what they produce individually.
And if the same people problems keep appearing, do not assume that replacing the latest employee will solve them. Examine the conditions that may be producing the pattern.
The most expensive shortcut is not always the one that costs the most money upfront. Sometimes it is the one that transfers today’s savings into tomorrow’s supervision burden, rework, conflict and turnover.
A business can operate with a lean team, limited budgets and minimal hierarchy. But it cannot sustainably remove the support and accountability that make people effective.
You can choose where to spend your resources. You cannot assume that the costs you choose not to pay will simply disappear.
References and psychological foundations
The following sources support the article’s central concepts. They provide theoretical and research foundations, rather than proof that every situation described above has the same cause.
- Wood, D., Bruner, J. S., & Ross, G. (1976). The role of tutoring in problem solving. Journal of Child Psychology and Psychiatry, 17(2), 89–100. https://doi.org/10.1111/j.1469-7610.1976.tb00381.x
Relevant concept: Scaffolding—how structured assistance helps people perform tasks they cannot yet manage independently. - Kahn, R. L., Wolfe, D. M., Quinn, R. P., Snoek, J. D., & Rosenthal, R. A. (1964). Organizational Stress: Studies in Role Conflict and Ambiguity. Wiley.
Relevant concept: Role ambiguity and role conflict as sources of organisational stress. - Peter, L. J., & Hull, R. (1969). The Peter Principle: Why Things Always Go Wrong. William Morrow.
Relevant concept: The distinction between success in one role and competence in another, especially when promotion introduces different responsibilities. This is a popular management concept, not a standalone empirical theory. - Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999
Relevant concept: Psychological safety and team learning. - Colquitt, J. A. (2001). On the dimensionality of organizational justice: A construct validation of a measure. Journal of Applied Psychology, 86(3), 386–400. https://doi.org/10.1037/0021-9010.86.3.386
Relevant concept: How employees perceive fairness in organisational decisions, procedures and interpersonal treatment.
A note on interpretation
The scenarios in this article are observations about organisational patterns, not diagnoses of particular employees or managers. Employee turnover, conflict and declining performance can have multiple causes. The purpose of a psychological lens is to help organisations investigate those causes more carefully and design better conditions for performance not to assign a psychological label to an individual.
