Personalization opportunity
They logged in to an empty screen, not what they came to do.
Make the first screen about what they said they wanted.
Step 1 · Signals
What do we know about this person?
Declared
Signup job, role, or "I'm here to…" answer.
Connected
Plan, invite source, or the page they came from.
Example eligibility rule
Show the job-first empty state when the account has a declared use case, has not completed its first-value event, and the selected job is available on the current plan. Use the default empty state for "explore," conflicting answers, or accounts that already contain work.
Step 2 · The need
What’s really going on?
Signup or a "what will you use this for" question already happened. The empty state is still a feature parade instead of a first action built around that answer.
Avoid this assumption
A personalized welcome tooltip is not a different first experience. This case chooses the right first action. "They signed up. The first screen still looks like someone else's demo." makes the example or proof feel relevant.
Step 3 · Worth it?
Do the math before you build.
Activation personalization is a different first job, not a longer checklist. Role- and use-case-based first screens are how people reach value in minutes instead of a day.
Reach
How many eligible people can you reach in the chosen channel and time period?
Cost
What will content, delivery, QA and ongoing maintenance cost?
Return
What incremental outcome would cover that cost, and what is it worth?
Planning inputs, not measured results. Estimate reach × incremental outcome rate × value per outcome, then subtract cost. Use a range and a consistent time period.
Step 4 · The response
Pick how you help.
Example format: Sequence
Reorder the first three actions around the stated job, with skip.
Compare lighter and deeper responses
Choose the lightest response that solves the need.
Assist: Offer useful help
Keep the default empty state. One module that names the job they chose.
Adapt: Change a meaningful part
Reorder the first three actions around the stated job, with skip.
Transform: Tailor the journey
A first-run assembled from the job, then a path back to the full product.
What to watch out for
- Twelve-item checklists dressed as personalization.
- No way back to the full product.
- Treating "explore" as a mandate to hide navigation.
Step 5 · The moment
Did it help? A/B test it.
Control
Default empty state and tour.
Treatment
Job-first empty state for the same signup answers.
Success measure
First-value event in session one, then activation at day 7.
Guardrail
Skip rate and time-to-full-product. If they cannot reach the rest, you over-narrowed.
Win or lose, record what worked, for whom and why. What you learn becomes the next signal.
Tools that can deliver the response
- Appcues In-product engagement platform for building targeted flows, tooltips, checklists, and announcements without engineering.
- Pendo in-app guides Product experience platform combining usage analytics with in-app guides targeted by user or account segments.
- Userpilot In-app flows, checklists, and multi-channel workflows targeted by behavior and segment, built without code.
- Customer.io Event-triggered lifecycle messaging across email, push, SMS, and in-app, built on a customer profile and behavior-data layer.
Try the framework on another situation
They said why they came. You showed the homepage. Show them that next, not everything.
They paid. Then they never started setup. Give them one first step. Not a tour of everything.
They signed up. The first screen still looks like someone else's demo. Show an example that looks like their world, not a stock screenshot.
Work through it in the hub
Score your personalization program, explore more customer situations, and compare the tools that can deliver them.
.svg)
