A look inside how we shaped Ask Alfa — from uncovering user pain points to designing a confident, AI-driven experience.
User Interviews: Conducted sessions with portfolio managers and analysts to uncover perceptions, habits, and mental models around AI use
FullStory Analysis: Reviewed session recordings and heatmaps to spot friction points, hesitation moments, and common drop-off paths
Journey Mapping: Visualized a typical first-time interaction to capture the emotional curve from curiosity to confusion to disengagement
“Curiosity → Confusion → Frustration → Drop-off”
Before exploring solutions, I needed to understand why adoption was low despite strong AI capabilities. I combined qualitative and quantitative methods to identify where users struggled
After gathering insights, I brought everything together to find the root problem — users didn’t know how to start
After confirming the hypothesis,
I handed off the final Figma designs to the development team
AT that point it was a time to design these two features -– prompt library and Prompt improver
Over 70% of first-time sessions ended after a single query
When responses were vague or inconsistent, users lost confidence and didn’t return
Many didn’t know how to phrase questions or what data the AI could access
Users landed on a blank screen with no guidance, unsure what Ask Alfa could do
Over 70% of first-time sessions ended after a single query
When responses were vague or inconsistent, users lost confidence and didn’t return
Many didn’t know how to phrase questions or what data the AI could access
Users landed on a blank screen with no guidance, unsure what Ask Alfa could do
- Reduce Friction – help users reach value in the first minute
- Show, Don’t Tell – demonstrate capability through examples
- Stay Contextual – guide users directly within their workflow
DESIGN STRATEGY & PHILOSOPHY
- Users felt uncertain about what Ask Alfa could access or analyze
- The open text field created decision paralysis
dropped off after one session
of users didn’t know how to prompt efficiently
Around the same time, our Customer Success team built a detailed mind map of effective prompts for every major use case — turning cross-functional insights and research into clear, actionable design ideas
After analyzing interviews, FullStory sessions, and user journeys, I organized all insights in Notion
Since our CS team had already mapped out hundreds of strong prompts, the challenge was how to display prompts inside Ask Alfa. Users only needed a few relevant examples with an option to explore more
I worked closely with developers to ensure the feature was both technically feasible and aligned with the product’s tone.
Together, we explored different approaches for how Ask Alfa could detect unclear prompts and suggest improvements in real time
I explored several UI options for how users could accept prompt improvements. We chose the version with an explicit CTA button to clearly show what would happen on click
After finalizing the designs, I presented the Prompt Library and Prompt Improver to all stakeholders — including Product, Engineering, and Customer Success. The meeting got everyone
on board and gave the green light to move forward
Once approved, I handed off the final Figma files and walkthrough prototype to developers, detailing interactions, edge cases, and logic directly in Figma
I designed several variants of prompt snippets.
We chose the last version for its clean design, clear categories, and one-click access to explore further (See more)
Two solutions emerged from this synthesis — a Prompt Library to guide users with curated examples and a Prompt Improver to refine prompts through instant feedback