Getting Started Is Only Half the Work

When I started leading product onboarding, I thought activation and adoption were one problem. Get the customer set up, run a good kickoff, follow up, and usage would follow. It doesn't work like that. I've watched accounts with flawless kickoffs go quiet, and accounts I barely touched turn into daily users. It took me a while to see the pattern, but here it is: adoption isn't one engine. It's two, and they fail in completely different ways.

The first engine is process, everything I own around the product. The prerequisites before we start, the white-glove kickoff, the cadence of when I reach out and what I say, the timing of touchpoints so momentum doesn't cool between sessions, making sure the customer's own team is ready to do the work instead of watch a demo. All of it does one job: it carries someone to the value moment. Most people never cross the gap between "we bought this" and "I ran it and it worked" on their own. Process is my hand on their back.

The second engine is product, and it begins exactly where my control ends. It's whether the next step is obvious or I have to explain every click. Whether the output catches what a person would have missed, or needs so much correction it isn't worth the trouble. Whether the thing behaves tomorrow the way it did today. I can run a flawless session and time every follow-up perfectly, and none of it holds if the output is weak or the platform is shaky. I can earn the first run. Only the product earns the second.

Process and product don't compete, they take turns. Call it the yin and yang of the value moment: I spend everything getting someone to their first real result, then the product takes over and decides whether that result becomes a habit. Each has a ceiling the other can't lift. My best working session can't save a weak output, and the best output in the world doesn't matter if the customer never reaches it.

So when an account stalls, I ask one question before anything else: did they reach the value moment or not? If they never got there, that's process, and it's mine to fix. If they got there and didn't come back, that's product, and my job shifts to carrying that signal back to the people who can. Two engines, two failure modes. The real mistake is treating a stall as one problem, when the fix depends entirely on which engine died.