PagePilot
Designed PagePilot's guide module to improve user activation

- Context
- PagePilot is a B2B product experience tool that helps teams add in-app guides, tooltips, and walkthroughs to improve product onboarding.
- Skills
- UX Research · Product Thinking · Interaction Design · Information Architecture · Prototyping · Iconography
- Team
- 2 UX Designers · 4 Developers · 2 Stakeholders
- Timeline
- 5 months
Problem
Product teams struggle to improve onboarding and feature adoption in their product. They want to guide users inside the product, but depend heavily on designers and developers, which slows iteration and makes updates costly. As a result, onboarding gaps remain.
Existing Guide Editor
To understand the current experience, I explored the existing guide editor developed by the team.

Key observations
- High cognitive load
- No guided creation flow
- Technical settings exposed too early
- Experience felt more like a rich text editor than a visual editor
- Difficult for non-technical users
Requirements
The editor needed to:
- Be simple and easy for non-technical users.
- Reduce dependency on developers for onboarding updates.
- Support both tooltips and product tours.
- Work across web and mobile products.
- Support reusable guide templates.
- Provide a reusable editor architecture across PagePilot modules.
- Work within the technical constraint that precise DOM-level element inspection was not feasible across multiple platforms.
Understanding the User
After defining the problem and understanding the product requirements, it became clear that the success of the guide module depended heavily on who would actually use it.

How might we make the guide creation experience feel visual and intuitive, rather than technical?
How might we support both simple tooltips and multi-step product tours without increasing complexity?
Research
Market Exploration: How Existing Tools Enable In-App Guidance

Key Insights
- Existing tools offer flexibility, but often at the cost of usability for non-technical users.
- Users frequently rely on tutorials or videos, increasing friction.
- Multiple steps and configuration screens slow down simple use cases.
- Users struggle to understand how guides will appear in their product while creating them.
- Combining tooltips and product tours can overwhelm first-time users.
Ideation
With these insights in mind, I began exploring possible solutions by mapping different user flows and structuring the information architecture.

How might we design a reusable editor that stays consistent across different PagePilot modules?

Working Within Technical Constraints
Since the existing editor was built on a plugin with limited customization, I worked closely with developers to understand what was technically possible and designed the system within those constraints.
Testing Early Concepts
Early wireframes helped surface usability issues before investing heavily in the final interface.

Key issues
- Users struggled to understand the difference between tours and tooltips during creation.
- Introducing multiple editor tabs too early increased cognitive load.
- Requiring product integration upfront negatively affected the first-time experience.
- Users wanted to explore and design the tooltip first and involve developers later when needed.
From Complex Editor to Guided Experience

Comparing the existing editor with the redesigned visual editor after usability improvements.
Solution
These insights shaped a simpler visual editor that guided users through creation while keeping advanced configuration out of the initial experience.

Simplified creation flow with guided, intuitive user interaction
Prototype Highlights

Impact
80%
Reduced User Confusion
40%
Higher Task Completion
35%
Faster Guide Creation
Scalable
Unified Editor
One editor architecture now supports multiple modules.
Learnings
This project taught me that product design is much more than designing screens. It helped me think in systems, test ideas early with users, and improve them before investing too much time. One of my biggest learnings was that good design starts with asking the right questions. The better I understood the business goals, user needs, and technical limitations, the easier it became to make the right design decisions.
It also showed me how important collaboration is in building products that are both useful and scalable.








