The Advice That Didn't Land
Every mentor has experienced this. The advice was correct, delivered clearly, in the right room, at a moment that felt opportune. The person on the other side nodded, asked a follow-up question, and left with what seemed like a genuine grasp of the thing.
Then nothing happened.
Not immediately, and not in the weeks that followed. The decision that had seemed so clear in the session sat unexecuted. Months later, the same person came back describing the same advice, almost word for word, as a realisation they'd recently arrived at.
The mentor's private reaction is honest and predictable. There's usually mild irritation: "I told them that months ago." There might be a small, proprietary satisfaction, the sense that the advice was eventually vindicated even if the credit went elsewhere. Sometimes there's a sharper edge of self-doubt: something about how it landed must have been off, or it would have taken hold sooner. A different framing, perhaps. A better example.
That self-doubt is understandable and almost always misdirected. Both the advice and its delivery were, in most of these cases, reasonable. Something else failed to be present, and it wasn't anything the mentor could have manufactured. That missing thing has a name.
Readiness as a Separate Variable
Whether advice produces change depends on two things operating independently of each other. The first is whether the advice is correct. The second is whether the person receiving it is in a position to use it.
Mentors have considerable control over the first. They have very little over the second
Correctness is about content: the diagnosis, the recommendation, the logic connecting them. Readiness describes the recipient's capacity, at a given moment, to recognise advice as applicable and to act on it. That capacity develops mostly through experience, rather than through better explanation.
Some things only become legible after someone has lived through the problem themselves. A founder who has never been overwhelmed by an undelegated workload can hear the case for proper delegation and understand it intellectually. The logic holds, but it doesn't press against anything real inside them. Then they spend six months handling everything themselves, come out the other side exhausted, and suddenly the same argument lands differently. The advice hasn't changed; what changed is the experience of the person receiving it.
This is where a common trap forms. When advice doesn't land, the natural response is to assume the problem lies in the advice itself or in how it was conveyed. The mentor rephrases, finds a better analogy, comes back from a different angle. Or, sensing futility, begins softening the advice, rounding its edges to make it more palatable in the room.
Neither response addresses what was actually missing. If the problem was readiness, more clarity doesn't help; the person isn't failing to understand; they're failing to have had the experience that would make the understanding useful. Treating them as though they simply haven't heard the message is a separate misreading of the situation.
Recognising readiness as a separate variable changes what a mentor's job involves. It means accepting a kind of timing that isn't theirs to set.
What This Means for How Mentors Judge Their Own Value
A mentor who measures their effectiveness by whether advice is adopted within days of being given is measuring the wrong thing. It seems rational enough: if advice is good, it should produce change; if change doesn't follow, something must be wrong. But that framework collapses when readiness is absent, because the feedback it generates is false.
Two reactions to failure follow. The first is escalation: repeating advice more insistently, reframing it endlessly, increasing the volume, on the assumption that the obstacle is comprehension or conviction. The second is dilution: sensing resistance, the mentor softens the advice, rounds it off, packages it to be easier in the room and less useful when it matters. Both responses treat the immediate moment as the site of the problem. Both degrade the mentor's practice over time.
The more useful measure is not whether advice is being acted on this week, but whether it's still available, intact and rememberable, when the person is finally in a position to use it.
Accepting this comes with real discomfort. A mentor often can't tell in the room whether something worked. The feedback loop between giving advice and seeing it produce change is long. Sometimes it never closes visibly at all: the person takes the advice, finds it useful years later, and the mentor never knows. This is a genuine cost of the role, not a problem to be designed away by better follow-up processes or more structured check-ins. It's structural.
The alternative, judging advice by how it lands in the first five minutes, produces worse advice rather than better mentors. Advice shaped for immediate comfort tends to lose exactly what makes it useful.
Recognising the Lag in Practice
The lag shows up in signals that are easy to overlook if a mentor isn't paying attention.
The most common is when someone returns to a point raised months earlier and presents it as their own recent realisation. The instinct to correct the record, to note that this was already said, is understandable, but it's beside the point. The advice landed; it connected with something real this time, which means the timing was finally right. That is the actual outcome, and it's the one that matters.
There's another signal: the temptation to keep repeating advice that hasn't been acted on yet. "They haven't done anything with this" can feel like evidence that the message hasn't been received, when it often means something else entirely. Sometimes the right response is to say a thing once, clearly, and leave it, because pressing harder doesn't make it land sooner; it creates noise around something waiting for its moment.
And there's hindsight, when it becomes clear that a piece of advice needed an experience underneath it before it could be used: an experience the mentor couldn't have manufactured or accelerated, however well-prepared they were.
None of this points toward saying things once and hoping for the best. The value of advice delivered well doesn't disappear just because nothing visibly follows. It remains available, for the moment when it's finally needed.
A Self-Check for Mentors
Most mentors, if they look, can find the lag in their own practice. The pattern tends to be common, and recognising it changes something.
Can you name a specific piece of advice you gave that took months, or longer, to be acted on? Not a general sense that some things take time, but a particular conversation, a particular person, and a gap you can roughly date.
When you recall that moment, what's the first thing you feel: relief that the advice eventually landed, or frustration at how long it took?
When a piece of advice isn't immediately adopted, do you find yourself returning to it in the next session, rephrasing it, pressing it harder? Or can you say a thing clearly once and trust that it'll keep working without your assistance?
And the harder one: can you honestly tell the difference between advice that hasn't been used yet and advice that was actually wrong? The two can look similar from the outside. The internal experience of each is usually different, but that distinction takes some practice to locate.
A mentor who has genuinely looked for the lag in their own practice tends to stop treating silence or delay as a verdict on their advice. That, in turn, changes the quality of what comes next.
The Limits of Patience
The lag doesn't explain everything. Some advice doesn't land because it was wrong. Some because it was poorly timed, or reasonably disputed, or delivered in a way that closed off rather than opened up the conversation. Mistaking any of those for "they just aren't ready yet" is a way of avoiding a harder conversation with oneself.
There's an honest tell that separates the two. Advice that was ahead of someone's readiness tends to resurface later in something close to its original shape. The person doesn't always credit it, but the substance holds: the formulation they arrive at is recognisably descended from the thing that was said. Advice that was actually wrong, or badly received for substantive reasons, tends not to resurface at all. Or it resurfaces changed beyond recognition, carrying none of its original structure.
Patience is not passivity. Waiting for readiness to arrive doesn't mean withholding directness now, or softening a message so it's more comfortable to defer, or declining to hold someone accountable for a decision they've already had enough information to make. Mentors still owe people clarity in the moment. The lag explains why clarity doesn't always produce immediate change; it doesn't excuse a mentor from offering clarity in the first place.
Understanding the lag should make a mentor more precise about what they say, and more patient about when it gets used. Not looser about either.
What Good Advice Is For
The test of good advice was never whether it changes something immediately. It's whether it's still there, intact and recognisable, on the day the person receiving it is finally in a position to use it.
For a mentor, this means tolerating a feedback loop that stays open for months, sometimes much longer. It means resisting the pull to compress that loop by repeating things, softening things, or reading silence as failure. It means holding a standard in the room that may not be acknowledged until long after the room is empty.
Patience, in this sense, isn't the absence of doing something. It's the harder skill mentoring actually requires.
Ady Coles works as a thinking partner and mentor to leaders and teams navigating complexity. His work centres on judgement, perspective, and the often-invisible work of translation - helping people understand their role in the system, make better decisions, and operate with confidence in uncertain environments.