The Hidden ROI of Being Understood

May 30, 2026

10 min read

5 views

86%

When the Real Problem Is Not the Work

What if the hardest part of leadership is not deciding what matters, but getting other people to see why it matters in the first place?

That question sounds simple until you live inside an organization. One person is trying to put a dollar value on every initiative. Another is trying to understand how a team is really doing by talking to people beyond their direct reports. At first glance, these look like two different management habits. One is about justification, the other about connection. In practice, they are solving the same problem: making invisible value visible enough that a system can move.

Most organizational friction is not caused by bad ideas. It is caused by ideas that cannot travel. A good decision, a useful initiative, a worried employee, a subtle risk, all of it can sit trapped inside one person’s head, one team’s dashboard, one manager’s assumptions. Then leaders wonder why the organization feels slow, misaligned, or overly political. The real bottleneck is often communication, but not in the shallow sense of sending more updates. The bottleneck is translation.

ROI Is Not Just a Number, It Is a Translation Layer

When someone asks for ROI, it is tempting to treat that as bureaucratic resistance. But ROI, at its best, is not a demand for spreadsheets. It is a request for legibility. It asks, in effect: what changes if we do this, who benefits, what risk disappears, and what is the opportunity cost of doing nothing?

That is why vague enthusiasm rarely persuades. “This is important” does not always answer the real question: important to whom, relative to what, and with what confidence? Organizations are not machines that merely execute. They are arenas of competing priorities, limited attention, and incomplete knowledge. To move anything forward, you need a story that can survive contact with the people who control resources.

This is where many teams stumble. They present activity instead of outcome. They describe effort, not leverage. They say, “We need three weeks to build this feature,” when the real case is, “This feature reduces onboarding drop-off by 12 percent, which compounds into retained revenue and lower support load.” The first version is true. The second version is persuasive because it connects work to consequence.

ROI is not the enemy of meaningful work. It is often the language that lets meaningful work enter the room where decisions are made.

Think of it like a bridge. A bridge does not change the river. It changes whether people can cross it. In the same way, ROI is a bridge between the local truth of a team and the broader logic of the organization. If you cannot build that bridge, good work may still exist, but it will remain isolated, underfunded, or misunderstood.

The Skip-Level 1:1 Is the Missing Sensor

If ROI is the language of decision, skip-level 1:1s are the language of reality.

A manager who only listens to direct reports is like a CEO reading only the executive summary. The summary may be accurate, but it is still filtered. Every layer of management compresses information. Some compression is useful, because no leader can absorb every detail. But compression also distorts. Quiet frustration can look like normal engagement. A promising project can appear stable while it is actually running on exhausted goodwill. A process problem can masquerade as an individual performance issue.

That is why talking to people beyond your direct reports is so powerful. It gives leaders a better sense of how people are feeling and what is happening around the organization. More importantly, it reveals the gaps between the story managers think they are telling and the story employees actually experience.

A skip-level 1:1 is not just a friendly check-in. It is a diagnostic instrument. It tells you whether the organization’s language matches its lived experience. If leaders say collaboration is excellent but the people doing the work describe constant handoff confusion, that is not a morale issue in isolation. It is an operating-system issue. If leadership says priorities are clear but three different teams are independently reinventing the same solution, the organization is not aligned, it is merely optimistic.

A good skip-level conversation often surfaces the things that never make it into official reports: the workaround everyone relies on, the dependency no one owns, the manager who is excellent at task tracking but poor at clearing blockers, the feeling that a team’s work only matters when it is measurable in the narrowest sense. These are not soft concerns. They are the texture of execution.

The Deep Tension: Leaders Need Numbers, but Numbers Need Context

Here is the hidden connection between ROI and skip-level conversations: both are attempts to compress complexity without losing the truth.

ROI compresses complexity into a decision-ready frame. Skip-level 1:1s expand complexity back into human detail. One without the other is dangerous. If you only speak in ROI, you may end up with a beautiful business case for a broken reality. If you only gather stories, you may create empathy without action.

The best leaders move between these two modes fluently. They know when to ask, “What is the return?” and when to ask, “What is really happening?” They understand that numbers can tell you whether something matters at scale, but only people can tell you why it is hard, where it is failing, and what hidden costs the metric is missing.

Consider a team proposing an internal platform upgrade. On paper, the ROI may look modest, because the gains are distributed across many people and hard to attribute. But skip-level conversations reveal that engineers are losing hours every week to manual setup, sales demos are delayed by tooling friction, and new hires take longer to become productive. Suddenly the upgrade is not a convenience project. It is a compounding efficiency gain, a retention tool, and a morale intervention.

Now reverse it. Imagine leadership becomes captivated by a polished ROI case for a new initiative. It looks impressive until skip-levels reveal that the team expected to execute it is already overloaded, the required cross-functional support is fragile, and the “small change” depends on three hidden processes no one has documented. The numbers were real, but incomplete. The social and operational costs were invisible until someone bothered to ask.

The mistake is not caring about ROI or caring about people. The mistake is believing one can substitute for the other.

A Better Mental Model: The Organization as a Conversation Between Value and Experience

A useful way to think about this is to imagine every initiative moving through two filters.

The first filter is value logic: Does this produce enough benefit to justify the investment? This is the world of ROI, prioritization, resource allocation, and strategic tradeoffs.

The second filter is experience logic: Can the people responsible for this actually execute it well, sustainably, and with clarity? This is the world of morale, friction, trust, and informal reality.

Most organizations overweight one filter. Finance-heavy cultures obsess over the first and become blind to erosion in execution. Culture-heavy organizations obsess over the second and can become resistant to necessary tradeoffs. High-functioning organizations keep both in conversation.

This is why skip-level 1:1s matter so much. They are one of the few ways leaders can directly hear experience logic before it is sanitized by the hierarchy. And this is why ROI framing matters so much. It forces experience into a structure decision-makers can act on. Together, they form a loop:

Listen to the lived reality through skip-levels and other direct signals.
Translate that reality into value by connecting it to outcomes, risk, and opportunity.
Use that value story to secure resources or change priorities.
Verify again through direct conversation that the change is actually improving execution.

That loop is not just a management tactic. It is a theory of organizational health. It says that a company stays coherent only when leadership continuously converts between the human and the financial, the local and the strategic, the messy and the measurable.

Here is the subtle point: people do not resist ROI because they dislike rigor. They resist it when ROI is used as a weapon that erases context. Likewise, leaders do not resist skip-levels because they dislike people. They resist them when skip-levels become a theater of concern with no operational consequence. The real skill is not choosing one or the other. It is preserving meaning while increasing decision quality.

How to Make Your Work Legible Without Making It Hollow

If you are trying to persuade a manager who wants ROI on everything, do not fight the premise. Refine it. The goal is not to inflate benefits or force false precision. The goal is to make the chain of impact visible.

Start by answering four questions:

What changes if we do this?
Who experiences the change first?
What downstream effect should we expect?
What happens if we do nothing?

Those questions transform an initiative from a vague request into a causal story. They also force a useful honesty. Some work has direct financial ROI. Some has risk reduction ROI. Some has retention ROI. Some has decision quality ROI, meaning it makes future decisions better by reducing confusion or rework. Not every return is immediate, but every return should be describable.

If you are the person running skip-levels, do not treat them like status meetings. Ask questions that reveal structure, not just sentiment:

What is making your work harder than it should be?
Where do handoffs break down?
What do you think leadership misunderstands about your team?
What are people doing manually that should be systematized?
What would you stop doing if you could?

These questions surface friction that is usually invisible in performance reviews and quarterly reports. They also produce better ROI arguments later, because you are not inventing value in the abstract. You are naming the actual cost of dysfunction.

A practical leader should think like an interpreter. When an engineer says a tool is “annoying,” that may mean they are losing five minutes a day. It may also mean they are losing focus, context-switching constantly, and accumulating frustration that will eventually become attrition. When a manager says a team is “fine,” that may mean they are stable, or it may mean they have learned not to complain. The translation work is the job.

Key Takeaways

ROI is a language of legibility, not just finance. If you can connect work to outcomes, risk, or leverage, you increase its chance of being funded and supported.
Skip-level 1:1s are diagnostic tools. They reveal the gap between the organization’s official story and the lived reality of the people doing the work.
Good leadership translates between value and experience. Numbers without context miss the truth, and stories without structure rarely change anything.
Ask about causal impact, not just effort. Focus on what changes, who benefits, and what hidden costs disappear or appear.
Use direct listening to strengthen your ROI case. The best business cases are grounded in real friction, not abstract assumptions.

The Real Return on Being Understood

The deepest insight here is that organizations do not run on data alone. They run on shared understanding of what the data means, what the people are experiencing, and why any of it deserves attention. That is why ROI and skip-levels belong together. One asks for justification. The other supplies reality. One makes action possible. The other makes action wise.

So the next time someone asks for ROI, do not hear only a demand for metrics. Hear a request to make the invisible visible. And the next time you sit down with someone beyond your direct reports, do not treat it as a nice-to-have relationship exercise. Treat it as a way to hear the organization before it becomes a dashboard.

The companies that thrive are not the ones that measure the most or listen the most in isolation. They are the ones that learn how to turn listening into legible value, and value into a better experience of work.

That is the hidden ROI of being understood: not just better communication, but better decisions, better execution, and fewer expensive surprises hiding in plain sight.