In revenue leadership, you make decisions using information other people bring you. You cannot be in every customer conversation, team meeting, or cross-functional discussion. You depend on people to recognize when a concern needs your attention and raise it while there is still time to respond.

Your answers suggest that some information may be reaching you later, or with less context, than you need. A forecast update sounds reassuring until you hear about concerns that have been developing for weeks. A team issue appears to be recent, then you discover that several people had already been discussing it.

I call this pattern Delayed Truth.

The name describes how information reaches you. It does not establish that someone is being dishonest or that your leadership caused the delay. The next step is to understand what happened between a concern being noticed and being shared.

How a manageable concern becomes an urgent problem

Imagine a sales manager reports that the quarter is on track. At the following review, a significant portion of expected revenue is suddenly uncertain.

As you discuss the details, you learn that customer response times had slowed and several buying decisions had been postponed earlier in the month. The manager had been working with the team to recover the situation. They intended to bring you a clearer update once they knew whether those efforts would work.

From their perspective, they were managing the problem. From yours, you have lost time you could have used to reconsider commitments, inform other leaders, or help address an obstacle.

A reminder to bring concerns forward earlier leaves important questions unanswered. What did the manager believe warranted your involvement? Did they think an early update would sound like an excuse? Were they expected to arrive with a solution? Had you both agreed on what needed to be raised between scheduled reviews?

The answers help determine what needs to change.

What may be delaying the information

People believe they need a solution before raising a concern

You may reasonably expect your leaders to think through a problem and bring a recommendation. The difficulty arises when that expectation also becomes a reason to delay telling you that the problem exists.

Someone can be responsible for developing a response while keeping you informed about a material concern. They do not necessarily need to finish the first task before doing the second.

It helps to distinguish an early notification from a request for you to take over. A manager can explain what they have noticed, what they are checking, and when they expect to know more while continuing to lead the work.

The expectations for escalation are unclear

“Keep me informed” leaves considerable room for interpretation.

You may expect to hear when an early warning appears. A team member may believe you only want confirmed problems. Someone else may assume that mentioning a concern in a routine report is enough, even when its implications have changed.

The reporting route can also be unclear. A concern may be discussed across several teams, with each person assuming someone else has told you.

The useful agreement identifies which developments warrant an early update, how that update should reach you, and who remains responsible for responding.

Previous responses have made people cautious

Consider what happens when someone brings you information that is incomplete or unwelcome.

Do they have an opportunity to explain what they know and what remains uncertain? Are they immediately expected to defend every detail? Does an early concern become a public challenge to their competence? Do you take over the work before understanding what support they need?

These questions are worth examining without assuming that you are the source of the problem. Expectations elsewhere in the organization may also encourage people to sound certain, protect a forecast, or wait until they have an explanation that will survive scrutiny.

You can maintain high standards while making room for an accurate early account. The person still owns the responsibility to investigate, act, and update you.

Reporting routines leave out uncertainty

A summary can be technically accurate and still give you an incomplete picture.

“On track” might mean that the customer has confirmed a commitment. It might also mean that the team still believes the commitment is achievable, despite warning signs. If those meanings are not distinguished, you may be making decisions with more confidence than the information supports.

As updates move through several people, qualifications can disappear. The final version may retain the expected outcome while losing the concerns behind it.

Examine whether your existing reporting makes it easy to distinguish what is confirmed, what is expected, and what is still being investigated. You may be able to improve the information within the meetings and updates you already have.

If expectations were clear and material information was knowingly withheld or misrepresented, that requires direct accountability. A better reporting process alone will not resolve a repeated failure to meet an agreed responsibility.

A practical place to begin

Choose one recent concern that reached you later than you needed it. Review it in an existing one-to-one conversation with the person involved.

Stay close to what could reasonably have been known at the time. A disappointing outcome does not, by itself, mean someone should have predicted it.

Use these questions to reconstruct what happened:

1. What was first noticed, and when?
   Separate the initial observation from what became clear later. A missed reply, a changed timeline, and a confirmed loss are different stages of information.

2. What did you believe needed to happen before bringing it to me?
   Listen for expectations about certainty, having a solution, handling it independently, or waiting for the next scheduled review.

3. Where was the concern discussed before it reached me?
   Notice whether information stayed within one team, lost detail as it moved upward, or was assumed to have reached you through someone else.

4. What response did you expect when you raised it?
   Make room for an honest answer. The person may have expected useful support, additional demands, criticism, or the loss of ownership over the work.

There may be more than one explanation. You are looking for the specific point at which an earlier update would have been useful and what prevented it.

Agree on one clearer expectation

Use what you learn to improve the reporting agreement for that type of situation.

For the forecast example, you might say:

“If a customer moves a decision date that affects the forecast, flag that change before our next review. I don’t need a complete recovery plan in the first update. Tell me what has changed, what you’re still checking, and when you’ll update me. Keep leading the response, and let me know where you need a decision from me.”

The agreement gives the person a recognizable trigger, a clear expectation for the update, and continued ownership of the response.

When the next concern arrives early, respond consistently with that agreement. Ask enough to understand the implications, clarify what you need to decide, and allow the person to continue working through the parts they own.

If you ask for early information but react as though uncertainty itself is a failure, the new reporting expectation will be difficult to sustain.

What improvement can look like

Earlier reporting may initially mean hearing more concerns while they are still uncertain. Some will develop into significant issues. Others will be resolved by the person managing them.

Look at whether the information gives you a better opportunity to make a decision or provide support. People should be able to distinguish what they know from what they suspect, explain what they are doing next, and identify when your involvement is needed.

You may notice that fewer meetings are spent reconstructing when a problem began. A manager raises a concern while there are still several reasonable responses available. An executive update includes an uncertainty you would previously have discovered only after a commitment was missed.

For your own workload, notice whether you spend less time pursuing missing context or repeatedly checking because you do not trust that concerns will reach you.

The improvement should not require you to supervise every development. If earlier reporting simply creates a larger stream of routine decisions for you to manage, revisit the escalation criteria and clarify which judgments remain with the team.

When the pattern needs a broader look

If delays appear across several teams, examine the wider conditions around reporting.

There may be conflicting expectations from senior leadership, measures that reward an optimistic account, or processes that remove important context as information moves upward. You may need to discuss those conditions with your CEO or peers rather than treating each late update as an individual communication failure.

The aim is to understand where information is being delayed and establish expectations people can realistically follow. That includes holding them accountable for raising concerns, responding constructively when they do, and preserving their responsibility for the work.