Most leaders have sat through a business review where everything feels broadly reassuring. The dashboard is largely green; the transformation programme is on track; AI adoption is improving; customer complaints are down; and employee engagement appears steady. There are a few issues, but they have owners, timelines and mitigation plans, so the room moves on.

The more difficult question is what the same company feels like a few levels below that review. The AI tool may have been “adopted”, but only because people have been told to use it. The new process may look efficient because someone is manually fixing it every evening. A customer issue may seem resolved because it has stopped travelling upward. A team may look resilient in the numbers while people are quietly exhausted.

That does not always mean leaders are being misled. More often, the organisation has learned how to edit reality before it reaches them.

Every scaled company has two versions operating at the same time. The reported organisation is the one represented through dashboards, presentations, business reviews, board updates and town halls. The lived organisation is what employees, managers and customers experience every day through systems, meetings, incentives, culture, handoffs and informal workarounds.

The reported organisation is essential. Senior leaders, boards and investors cannot work only with raw reality; they need summaries, metrics and a manageable version of what is happening across the business. That is how scale works. The problem is that every act of summarising also involves choices. A dashboard decides what will be counted. A review decides what deserves attention. A presentation decides what story will be told. A town hall decides what can be simplified for everyone. Over time, the things that get left out can become just as important as the things that are captured.

A recent Harvard Business Review article by Irina Wolpert, who leads Egon Zehnder’s North America fintech practice, gave me a helpful language for this. She describes the “two-organisations problem”: the gap between the organisation that gets reported upward and the organisation people experience every day.

I liked the phrase because it captures something many leaders recognise instinctively. At a certain scale, the company you review is not always the same as the company people are living inside. The issue is not that reporting exists. It has to. The issue is when leaders start treating the reported organisation as though it is the whole organisation. Name one thing your team believes that the executive team does not Name one thing your team believes that the executive team does not

So, this week, let’s explore the space between these two versions of the company. Where do they diverge? Where does the gap become wider? And how can leaders stay close enough to the daily reality of the company while still using the reporting systems that scale requires?

In a scaled organisation, the act of reporting upwards naturally opens a gap. Not because people are dishonest, but because truth gets translated many times before it reaches the top.

Truth gets translated as it travels upward

A concern that starts on the frontline rarely reaches the senior team in its original form. It gets discussed in a team meeting, folded into a functional update, summarised for a review, and eventually converted into a slide that fits the broader leadership narrative. By then, the issue may still be present, but much of its original texture — the frustration, hesitation, urgency or uncertainty — has often been lost.

At every stage, someone has to decide what matters, what needs softening, what can be left out, and what should wait until there is a solution. Each decision may be perfectly reasonable. In fact, it may be responsible. A leader cannot send every raw signal upward. But five or six layers later, the version that reaches the top may be technically accurate and materially incomplete.

This is one reason leaders can feel close to the business and still miss what is changing underneath. They may be seeing the right numbers and hearing the right updates, but not always the hesitation, confusion, fatigue or workaround sitting behind them.

People learn what kind of news travels safely

There is also the incentive effect. People learn quickly what kind of news travels safely. If raising concerns leads to blame, defensiveness, delay or endless interrogation, people do not suddenly become dishonest. They become careful.

They may wait a little longer, add more caveats, make the tough message more palatable, or present the problem only after they have a partial solution. They choose words that will not create unnecessary heat.

As Wolpert puts it:

“In organizations that reward green dashboards, dashboards are green.”

This is human, not sinister. Most people are trying to do their jobs, protect their teams and avoid creating unnecessary noise. But when everyone is making the message just a little safer, the final version can become much more comfortable than the reality it represents.

Leaders also shape what reaches them

The reported organisation is also shaped by the preferences of senior leaders, especially those who have been in the role for a long time. People learn what a leader likes to hear, which arguments work, which numbers matter, which people are trusted, and which concerns tend to get dismissed. The leader may believe they are seeing the organisation clearly, while the organisation has quietly learned how to present itself to that leader.

That is one of the subtler risks of seniority. The longer you lead, the more influence you have. But the longer you lead, the more the system also learns what to show you, when to show it, and how to say it.

Once this editing process gets embedded into dashboards, the problem becomes harder to see. Dashboards feel objective because they are full of numbers, but they are still shaped by human choices: what to measure, what to ignore, how to define success, and what behaviour the metric ends up rewarding.

Dashboards are only part of the picture

Dashboards are useful because they create focus, rhythm and accountability. They help leaders compare, track and act. The problem is that their limitations are easy to miss precisely because the format feels so objective.

Dashboards can create false comfort because they make some parts of the business highly visible while leaving other parts harder to see. They may show what has been made measurable, but not always what has become fragile.

The consequences build slowly. The damage usually does not appear in one dramatic moment. It accumulates quietly. Leaders approve strategies based on a version of reality that has already been cleaned up for them. Problems that could have been addressed early arrive later as escalations. The people who best understand the gap often grow tired of explaining it, and sometimes leave before the organisation fully understands what they knew. Boards, too, can end up judging the company through the most polished version of its story.

The problem is not only what dashboards miss. Metrics also shape behaviour. Once a measure becomes a target, people start managing the measure. A customer service team may reduce call time while leaving customers less satisfied. A sales team may increase meetings while the quality of pipeline weakens. A transformation team may show pilot adoption while real behaviour remains unchanged.

That does not mean metrics are bad. It means leaders need to keep asking a second question. Not only what the metric is showing, but also what behaviour the metric is creating.

AI is accelerating the disconnect

This is where the issue becomes even more important.

Generative AI makes reporting faster, cleaner and more persuasive. A messy review can become a crisp summary. Fragmented inputs can become a coherent update. A rough first draft can become a polished board note. A complicated transformation can be turned into a confident narrative within minutes.

That is genuinely useful. Leaders are overloaded, teams are overloaded, and anything that improves clarity and saves time has value. The risk is that some of the messiness that used to reveal reality may now disappear before it reaches senior leaders.

Earlier, a leader might notice hesitation in a review, an awkward caveat in a slide, a contradiction between two updates, or the roughness of a first draft. These were not just inefficiencies. Sometimes they were signals. They showed where people were unsure, where the story had not settled, or where reality was resisting the narrative.

AI can remove many of those signals before a senior leader ever sees them. The reported version of reality may become more fluent and easier to consume, but that does not necessarily make it closer to what people are experiencing. In some cases, the very polish that makes the summary easier to read may also make it harder to challenge.

The risk is not only that AI may hallucinate. The deeper risk is that organisations may use AI, even unintentionally, to make edited reality more convincing. A dashboard that misses context is one problem. A beautifully written summary of that dashboard may be an even more difficult one, because it can give incompleteness the confidence of a finished answer.

As technology makes partial truths easier to package, the distance between reported and lived experience could grow unless leaders deliberately look for what has been smoothed away.

Other factors also have an impact

The gap also tends to be wider in some parts of the organisation than others, especially where leaders are relying more heavily on second-hand information.

It is often wider in functions that senior leaders have not personally lived in. A CEO who grew up in sales may sense revenue issues quickly, but miss engineering fatigue. A finance-background leader may catch margin leakage, but underestimate customer experience friction. A product-led founder may see product issues before anyone else, but misread people systems.

Our instincts are sharper where we have spent time doing the work ourselves.

The gap also widens around personal convictions. When a leader really wants a strategy to work, people may find it harder to surface signals that challenge that view. Not because they lack courage, but because they can read the room.

Transformation efforts can amplify this further. AI transformation, digital transformation, restructuring, culture change and cost programmes all carry pressure to show progress. Milestones can move faster than habits. Language can change faster than behaviour. Steering committees can feel more successful than the work itself.

Handoffs are another place to look. Sales to delivery. Product to engineering. Corporate to field. Headquarters to regions. Family ownership to professional management. Many lived-organisation problems sit between teams, while dashboards usually report each function separately.

There is also a counterintuitive risk in cultures that talk a lot about transparency. A company can become fluent in the language of openness. People may know how to sound candid in public while still being careful in private. They may say the right things about challenge, truth and psychological safety, but avoid the one issue that would create real discomfort.

In those situations, transparency itself can become part of the reported organisation. People know how to perform openness, while the hardest truths continue to travel through side conversations.

Closing the gap between the “two organisations”

No leader can eliminate this gap completely, and it would be a mistake to run the company only through informal signals. Dashboards, reviews and reporting rhythms matter. The challenge is to make sure they do not become the only version of the company that leaders trust.

The better question is how leaders can create enough alternate channels for reality to keep finding its way upward.

Here are six practical habits that help.

1. Go where the work is messy, not only where it is reviewed

Spend time in the places where work actually happens. Join a product planning session. Sit in on a customer service huddle. Listen to a few customer calls. Visit a regional office. Spend time with a team three or four levels below you. Watch how a process actually moves across teams.

The key is to avoid turning these moments into another presentation. If every visit is choreographed, you will only meet the reported organisation in a different room. The value comes from seeing the small frictions: the workaround nobody mentioned, the handoff that keeps failing, the tool people avoid, the meeting where everyone knows the real issue but no one quite says it.

This is not about catching people out. It is about seeing the work before it has been cleaned up for leadership consumption.

2. Ask questions that are easier to answer honestly

Broad questions usually get broad reassurance. “How are things?” often produces “All good.” “Any concerns?” usually produces a polite pause. More specific questions create a safer path to the truth.

What is taking more effort than our current reporting suggests? What looks good on the dashboard but feels off on the ground? What are we celebrating too early? What are we calling a people problem that is actually a process problem? What are customers experiencing that we are not seeing in the numbers? What would your team say we are underestimating?

These questions work because they do not ask people to be dramatic. They ask them to describe reality. And once people share something uncomfortable, the leader’s response matters enormously. Thank them. Ask follow-up questions. Do not become defensive. And where possible, act on what you heard.

People watch what happens after truth is spoken. That teaches the organisation more than any speech about openness.

3. Listen for patterns, not just anecdotes

One conversation may only be an anecdote. But when several people at similar levels describe the same issue in different parts of the organisation, a pattern is probably forming.

Speak with multiple people at similar levels, preferably in smaller and more private settings. Ask them similar questions. Notice where their answers converge and where they differ.

If three mid-level managers in different teams describe the same issue, it is probably not a one-off complaint. If people at the same level give sharply different versions of reality, that too is worth understanding.

Wolpert suggests a simple recurring question to a rotating group of mid-level managers:

“Name one thing your team believes that the executive team does not.”

That is a powerful question because it surfaces the gap directly. It does not ask what is wrong in a generic way. It asks what is known below that has not yet travelled upward.

The answers may not always be comfortable, which is usually what makes them worth paying attention to.

4. Make challenge part of the operating rhythm

Reality checks should not depend only on brave individuals or occasional skip-level conversations. They need to become part of the way the organisation reviews itself.

A quarterly review could begin by asking what the team learned that surprised them. A transformation update could include what has not changed yet. An AI adoption review could ask what is being used because it is useful, and what is being used because people have been told to use it. A product review could ask what customers are working around. A leadership meeting could ask what the team would stop doing if it were willing to admit that something was not working.

These rituals do not need to be heavy. In fact, they work better when they are simple and repeated. The aim is to make challenge feel like part of how the organisation learns, not an act of personal risk.

5. Reward the people who surface problems early

Most organisations say they value transparency, but the real test is usually visible in the moment someone brings bad news early.

Do they get thanked or labelled negative? Do they get support or more scrutiny? Does the issue get addressed, or does the messenger become the issue?

Leaders shape truth-telling through these moments. Recognise the team that flags declining customer satisfaction before it shows up in quarterly results. Appreciate the manager who admits that a new process is not working. Celebrate the business unit that stops an initiative instead of continuing to defend it.

This is not about rewarding failure. It is about rewarding early contact with reality. When transparency carries reputational value rather than personal cost, leaders get a much clearer view of the lived organisation.

6. Help the board see beyond the deck

Boards usually see the most refined version of the company. They receive pre-reads, polished decks, rehearsed presentations and carefully selected metrics. That is understandable. Boards should not try to run the company, and they should not bypass management casually.

But good boards can still help leadership stay closer to reality by asking questions that test the gap between the reported and lived organisation.

Where is this dashboard least reliable? What are employees experiencing that is not yet visible in the numbers? Which part of this transformation looks better in reporting than in actual usage? What would our strongest middle managers say we are underestimating? What has surprised you recently? Where might we be seeing activity but not real change? What are we not hearing because people have learned it is too hard to say?

These questions are not meant to catch management out. They are meant to help the board understand whether the reported version of the company is close enough to the one employees and customers are experiencing.

Leading both versions

In organisations beyond a certain size, no leader can see everything directly. Reporting systems are necessary and valuable. Dashboards, reviews, operating rhythms and AI summaries all have a role to play.

The danger arises when these repeatedly edited outputs become the only version of the company leaders trust.

Good leaders do not assume they are being told the whole truth simply because people are not lying to them. They keep asking where the reported organisation and the lived organisation may be drifting apart, not because they are suspicious, but because they understand how organisations work.

Every large organisation edits itself. The leader’s task is not to eliminate that gap completely. That may be impossible. The task is to notice when the gap is widening and to create enough channels for reality to keep finding its way back up.

The company in the slides matters. But the company people experience every day is where the real work, risks and possibilities usually live.