I spent time last week watching how people onboard to PersonalizeWP. Not in a creepy way, but in the way you do when you’ve got heat maps, session recordings, and actual conversations with people who’ve just installed the plugin. It’s been eye-opening, and it’s shifted what we’re shipping in the next release.
The conventional wisdom about personalisation tools says: help users define segments, show them how powerful targeting is, teach them the business case. That’s the theory. Build the right segments, and you can deliver relevant experiences to different visitors. It sounds obvious.
The reality is almost different. People install PersonalizeWP, and the first thing they do is look for something to personalise immediately. They don’t want a 15-minute tutorial on segment-building. They want to set up a rule. Now. They want to see it work. They want to know that their effort just changed something on their site.
The people who succeed in the first 10 minutes are the ones who have one specific problem in their head. I want to show new visitors a discount code. I want to hide a form that only members should see. I want to show different images to mobile and desktop visitors. They come in with intent, find the UI, build the rule, refresh the site, and see the result. Those people are happy. They’re already thinking about what comes next.
The people who struggle are the ones who come in thinking “I should personalise my site” without a target. They click around the dashboard, read the intro content, try to understand all the options at once, and then close the tab because it feels abstract. They’ll probably come back when they have a specific need, but the momentum is lost.
What this means for us is that our onboarding is backwards. We’ve been leading with the philosophy. Explain what segments are. Explain what rules are. Then let people build. But the plugin doesn’t actually want that. It wants people to build a rule first, understand why it matters through the feedback of seeing it work, and then care about the deeper stuff.
So we’ve been rebuilding the first-run experience. The new version leads with “What do you want to personalise?” rather than “Let’s build a segment.” You can set up a quick rule in three clicks. You don’t have to understand advanced audience composition to do it. Then, once you’ve built the thing and refreshed and seen it work, we introduce the next layer of depth. Segments. Conditions. The machinery that makes it all possible.
The other thing the research is showing us, and I think this generalises beyond PersonalizeWP, is that people care more about the outcome than the mechanism. They don’t care that they’ve created an audience rule using a sophisticated conditional logic engine. They care that their new visitors now see the message they wrote. Show them the outcome first, teach them the system later.
This is probably obvious to anyone who’s done product work, but we’re still learning. We talk about building segments and designing experiences and measuring uplift. We talk about the architecture. But most users don’t care about that. They care about solving the one problem that brought them to the tool in the first place.
The shift in our thinking isn’t wildly different. It’s just “start with what people came here to do, not with what you want to teach them.” People who build something in the first five minutes stay. People who read about the philosophy and then try to figure it out themselves leave.
It’s a good reminder that the best product documentation and the best product UI is usually the same thing: remove the gap between intent and action. Your user knows what they want. Your job isn’t to teach them your way of thinking about it. It’s to make their way of thinking about it actually work.
—