Your company isn’t running the way you think it is

Ask a leadership team how work happens in their organisation and they may describe a clear, reasonable process.

Requests go through the correct channel. Responsibilities are understood. Managers communicate priorities. Systems provide visibility. Staff know where to find information and raise problems when something is not working.

Ask the people carrying out that process every day, and you may hear a completely different story.

Requests arrive through messages, meetings and last-minute conversations. Priorities depend on who asks most recently. Information is scattered between tools. Responsibilities overlap. People have created private trackers, informal shortcuts and unspoken rules to keep the work moving.

Neither group is necessarily lying.

They are simply experiencing the organisation from entirely different positions.

Leadership sees the structure. Staff experience the friction.

Senior leaders tend to experience work through:

• plans and objectives

• dashboards and reports

• management updates

• completed outputs

• formal processes

• scheduled meetings

• escalated problems

Employees experience the same organisation through:

• the information they receive

• the decisions they wait for

• the interruptions they absorb

• the systems they have to navigate

• the exceptions they handle

• the people they need to chase

• the extra steps required to get something finished

Leadership may see that a report was delivered on Friday.

The person producing it may see three days of chasing missing data, manually reconciling two systems and correcting a recurring error that nobody outside the process knows exists.

The final output looks successful. The effort required to create it remains invisible.

That is how inefficient processes can survive for years while appearing perfectly functional from above.

A completed task does not prove that the process worked

Capable employees are very good at compensating for poor systems.

They notice when information is missing and find it themselves. They remember which colleague needs to be reminded. They create templates, trackers and workarounds. They stay late, switch priorities and quietly correct mistakes before they reach the client.

From a leadership perspective, the work continues to get done.

That can create the impression that the process is working.

In reality, the process may be relying on people repeatedly protecting the organisation from its weaknesses.

The more capable and conscientious the team, the longer this can remain hidden.

When employees consistently absorb the friction, leadership sees the outcome without seeing the cost.

That cost may eventually appear through:

• slower delivery

• avoidable mistakes

• inconsistent quality

• duplicated work

• employee frustration

• burnout

• resistance to new initiatives

• dependence on particular individuals

• people leaving with essential knowledge

By then, the problem may be treated as a sudden decline in performance.

Often, it has been present for much longer.

Information changes as it moves upwards

Operational reality rarely reaches leadership in its original form.

It passes through several filters.

An employee tells a manager that a process is becoming difficult. The manager summarises it as a capacity concern. A department lead reports that the team is busy but managing. Leadership hears that delivery remains on track.

At each stage, the information becomes shorter, cleaner and less emotionally charged.

This is not necessarily deliberate. Managers are expected to interpret, prioritise and condense information. They may also want to avoid escalating a problem until they have attempted to solve it themselves.

But the result is that leadership often receives a sanitised version of what is happening.

“The team has a few process frustrations” may mean:

We manually repeat the same task every day, nobody knows who owns it, and people have stopped reporting it because nothing changes.

“The deadline is challenging” may mean:

The deadline was agreed before anyone checked how long the work takes, and the team knows it will have to work late again.

“There has been some resistance to the new system” may mean:

The system removed features people relied on, added extra steps and was introduced without understanding the existing workflow.

By the time the message reaches the top, the operational detail that would explain the problem may have disappeared.

Employees learn what is worth saying

Leaders sometimes assume that staff will raise important issues.

After all, there are meetings, surveys, one-to-ones and open-door policies.

But the existence of a feedback channel does not guarantee honest feedback.

Employees pay attention to what happens after they speak.

If previous concerns were dismissed, minimised or explained away, they may decide that raising them again is not worth the effort.

If the person asking for feedback also controls their workload, progression or performance review, they may soften what they say.

If leadership responds to every problem by asking the team to work faster, communicate better or be more positive, employees learn that feedback will be turned into a judgement about their attitude.

If no visible change follows repeated conversations, people stop expecting change.

Silence can then be mistaken for satisfaction.

A manager may believe:

Nobody has raised a serious concern.

The team may believe:

We have mentioned this repeatedly, but nothing happens.

Both statements can coexist.

Different roles create different versions of the truth

Leadership and frontline employees often use the same words while referring to different things.

“The process is clear”

Leadership may mean that a written procedure exists.

Staff may mean that the procedure does not cover the situations they encounter most often.

“The system gives us visibility”

Leadership may mean that a dashboard shows the current project status.

Staff may mean that the status is only accurate because someone manually updates the same information in several places.

“The team has autonomy”

Leadership may mean that employees can decide how to complete their work.

Staff may mean that they are expected to make decisions without the information or authority required.

“Priorities are communicated”

Leadership may mean that priorities are discussed in management meetings.

Staff may mean that they receive several conflicting urgent requests from different people.

“People are resistant to change”

Leadership may mean that staff have not adopted a new tool or process as expected.

Staff may mean that the change created more work, removed something useful or failed to address the original problem.

These differences are not just communication issues.

They reveal that people are evaluating the organisation from different levels of detail, responsibility and power.

Why managers may genuinely not know

It is easy to frame this as detached leadership failing to listen.

Sometimes that is true. But often the situation is more ordinary.

Managers may be managing several workflows without spending enough time inside any one of them to see the daily friction.

They may have previously performed the role, but the work has changed since then.

They may only become involved when something has already gone wrong.

They may see the standard cases while employees handle the messy exceptions.

They may assume that a problem has been resolved because a new process or tool was introduced.

They may also be absorbing pressure from above and passing it down in ways they do not fully recognise.

The perception gap does not require a bad manager.

It can develop naturally whenever decision-makers become further removed from the practical experience of the work.

Staff suggestions are not always the answer—but they are evidence

Employees usually know where a process hurts.

That does not mean every suggested solution should be implemented exactly as proposed.

A team may ask for another person when the deeper issue is duplicated work. They may request a new tool when the existing one is poorly configured. They may want to remove an approval stage that exists for a legitimate risk reason.

But even when the proposed solution is not right, the frustration behind it is still useful evidence.

The important questions are:

• What problem are they trying to solve?

• How frequently does it occur?

• What do they currently do to work around it?

• What information or authority is missing?

• Who else is affected?

• Why has the existing process not resolved it?

Frontline feedback should not be treated as a list of instructions for leadership.

It should be treated as operational information.

How to see the company from both perspectives

Closing the gap does not require a company-wide investigation.

Begin with one workflow that seems slower, more frustrating or less reliable than it should be.

Ask leadership to describe the intended process

What should happen? Who owns each stage? What systems should be used? Where are decisions made? What does good performance look like?

This establishes the organisation’s intended model.

Ask staff about a real recent example

Avoid asking only, “How does this process usually work?”

People often respond with the version they know is expected.

Instead, ask them to walk through the last time they completed it.

Where did the request arrive? What information was missing? Who did they need to contact? What did they track elsewhere? Where did they wait? What did they have to correct?

Specific examples reveal far more than general descriptions.

Make feedback safer

Where practical, gather input confidentially and report themes collectively.

This is particularly important when employees are being asked about processes owned by their manager or leadership team.

Confidentiality does not mean promising perfect anonymity in a team where individual examples may be recognisable. It means being clear about how responses will be used and avoiding unnecessary attribution.

Compare perceptions

Look for places where leadership and staff describe the same stage differently.

Those differences may reveal:

• invisible manual work

• conflicting expectations

• unclear ownership

• incomplete information

• bottlenecks leadership cannot see

• risks that staff are quietly managing

• systems that work well for reporting but poorly for delivery

• policies that are not practical in real situations

The objective is not to decide which group is correct.

It is to understand why their experiences differ.

Do not use employee insight to identify who is “the problem”

A workflow review loses credibility quickly if staff believe their feedback will be used to find difficult individuals.

The purpose is to understand the conditions shaping how people work.

That may include management behaviour, but it may also involve unclear objectives, competing incentives, unsuitable tools, missing decisions or responsibilities that have never been properly defined.

The most useful question is rarely:

Who failed to follow the process?

It is:

What made following the process difficult, impractical or insufficient?

That distinction creates better information and better solutions.

The gap is where the useful insight lives

Leadership has information employees may not have: commercial pressures, strategic priorities, legal constraints and broader organisational context.

Employees have information leadership may not have: where work stalls, what gets repeated, which systems create friction and which unofficial actions keep delivery functioning.

Neither perspective is complete on its own.

When they are brought together, the organisation can distinguish between:

• what leadership believes has been implemented

• what managers believe has been communicated

• what staff believe they are being asked to do

• and what actually happens when the work begins

That is often where the real explanation for delays, frustration and inconsistent performance is found.

Your company may not be running in the way its policies, dashboards or management meetings suggest.

That is not an accusation.

It is a normal consequence of people experiencing the same system from different positions.

The risk lies in never looking closely enough to discover the difference.

Eave compares the intended workflow with confidential insight from the people carrying it out, revealing hidden steps, conflicting expectations and operational friction that may otherwise remain invisible.