My houseplant does not become well cared for because I open the watering can cupboard.
This is an extremely modest observation. I keep returning to it when a product report treats the first login as a complete onboarding success.
Opening the service matters. The person has arrived, the credentials work, and the invitation has led somewhere. But the useful moment depends on what the service is for.
If it helps someone plan a week, perhaps the first meaningful action is preparing a plan they can use. If it helps organise a task, perhaps it is arranging enough of the task to make the next step easier. We need to understand that before choosing an event and calling it activation.
Otherwise the watering can remains on the shelf while the report celebrates excellent access to the cupboard.
What did the customer come to do?
I would begin with a simple description from the customer's perspective. Somebody joined because they wanted help with something. What would make their first session feel worthwhile?
That does not always mean completing the whole task immediately. A considered setup can take time. A first session might be useful because the person understands what to prepare next or can see how the service fits their situation.
The relevant action should reflect that purpose. It should also be something the team can describe consistently, rather than an appealing event name chosen because it already appears in the analytics menu.
For a fictional planning tool, I tried writing the first useful action as “created a plan.” Then I looked at the example more closely. A blank plan with a cheerful title existed, but the person still hadn't put anything into it.
The better question was whether they had assembled enough information to use the plan for the next day.
That gave us something more sensible to review in the onboarding flow.
Let the first visit have a human pace
People arrive with different levels of preparation. Some already have the information needed. Some are exploring whether the tool suits them. Others have been interrupted halfway through the signup by an ordinary event, such as lunch.
I am reluctant to treat all delay as failure. I do want to know whether the product has left somebody wondering what to do.
Read the instructions. Try the unfamiliar task. Check whether a person who stops can return with their work intact and a clear next step.
The welcome message also deserves a look. An enthusiastic greeting is pleasant. It does not replace an explanation of the first useful thing to try.
I have written copy that sounded encouraging while being wonderfully unhelpful. “Get started” is friendly enough; it just leaves the small question of how.
Keep the evidence connected to the purpose
A team can compare whether people reached the agreed action and what happened afterwards, giving the experience enough time to unfold. That can inform an experiment.
It does not mean one event will explain every future renewal. The person may have found an alternative, needed the service briefly or encountered another problem later. Keep those possibilities in view.
I prefer a modest conclusion that fits the evidence. A clearer setup may have helped more people reach a useful first action. Good. We can investigate the next part of the journey from there.
That feels more productive than claiming that a successful login solved retention.
Also, apparently I still have to water the plant. Reporting on the cupboard hasn't helped a damn thing.
A thought worth keeping?
