About 28 years ago I was an early web programmer going through certification to teach ColdFusion. Part of the evaluation was standing up and actually teaching it.
In ColdFusion the pound sign was a special character, so writing a hex color like #FFFFFF meant escaping the pound sign with another pound sign. I taught that.
The evaluator stopped me. You are introducing the concept of ColdFusion. You do not need to go that deep.
Everything I had said was true and useful. It was also correct information delivered at the wrong altitude at the wrong moment, and for a beginner that is not education. It is noise, and it costs them the thread on the thing they came to learn.
It took me a lot longer than it should have to understand where else that applies.
The Blocker
Years later I was working with an enterprise account. One stakeholder was not moving on anything.
My read at the time was that he was a blocker.
He was not a blocker. He was buried. I had been handing him more to do than any person with an actual job could absorb, and the volume itself was the obstacle.
Sit with that for a second, because it is the entire post.
From inside your own head the volume always feels appropriate. You know every piece is necessary. You know why each one matters. You sequenced it in the order that makes sense given everything you already know.
So when it does not land, the pacing explanation is not available to you. What is available is an explanation about them. Resistant. Not technical enough. Not bought in. A blocker.
Once you have labeled the person, you stop adjusting the delivery. Which guarantees it keeps failing. Which confirms the label.
They Look the Same and They Need Opposite Responses
Overwhelm presents as resistance. From the outside the two are nearly identical, and almost everything you would do about one is wrong for the other.
A resistant person argues. They have a competing priority and they will usually name it if you ask directly. There is friction, and the friction has content in it.
An overwhelmed person agrees with everything and does none of it. Yes, sounds good, makes sense. Then nothing. They go quiet, because saying this is too much for me means admitting they cannot keep up, and almost nobody will say that out loud to a vendor.
The strongest tell is a change in slope. Someone who was engaged early and went flat later is not a character problem. Character does not change in 6 weeks. Load does.
And the wrong response to silence is more. More follow-up, more resources, another deck, a recap document. That is how you finish burying someone who was already under.
How This Gets Built Into the Program
Onboarding gets built by people who know everything, for people who know nothing, and it gets organized around the builder’s mental model instead of the customer’s sequence of problems. Feature tour. Module by module. Everything covered, in the order the product happens to be architected.
Comprehensiveness feels like generosity. It functions as an obstacle. And it is unusually hard to kill, because we gave them everything they need is technically true.
The failure is also invisible in the reporting. Completion rates look fine. People attend the sessions. People finish the modules. Completion is not absorption, and nothing in the funnel distinguishes between them.
The signature of it is a survey response that reads something like: I finished the training and I still do not know how to use this.
When you see that, the instinct is to add content. Better documentation. Another webinar. A longer academy. Every one of those makes the actual problem worse.
What to Do Instead
Something taught before it is needed is not learned. It is only heard. So the sequence has to follow the customer’s order of problems rather than the product’s order of features. The unit is not the feature. It is the moment they need it.
One thing per interaction, tied to a problem they have this week and not one they will have in month 4. One small action before the next touch, small enough that it actually happens.
Then check absorption instead of completion. Ask them to show you, or to explain it back to you. It takes 90 seconds and it is the only honest signal in the entire process.
Drip against milestones rather than against a calendar. Calendar-based drip is still organized around your convenience. It is just spread out.
And then the hard part. Withholding feels like under-delivering. Everything in you says the responsible thing is to give them all of it, right now, because you have it and they are paying for it. It is not.
Restraint Is Not Doing Less
There is an apparent contradiction in that, and resolving it is the whole point.
The operating question in customer success should always be what is the most we can do for our customers, not the least. More recently I have been asking a sharper version of it: what complexity can we absorb on their behalf that we used to push back onto them.
Giving someone everything at once is not doing the most for them. It is transferring complexity. You have moved the work of sorting, sequencing and prioritizing onto the person least equipped to do it, and then called it thoroughness.
Restraint in delivery is not doing less. It is absorbing the sequencing work yourself so the customer never has to.
That is the most you can do for them. It just happens to look like giving them less.
One consequence worth counting, because nobody does. A customer who never absorbed the first thing never reaches the point where the second thing becomes obvious to them. They do not argue with you about it. They agree, and they stall, and the account quietly produces nothing beyond what it started with. Buried customers do not expand, and the reporting will tell you they completed onboarding.
