
๐ Overview
SparkGPT is a generative AI tool built for Spark employees to access internal knowledge and automate tasks securely. But as adoption grew, so did a key issue: users werenโt always sure what SparkGPT could (or couldnโt) do.
โ
โ
โ ๏ธ The Problem
A deep dive into user feedback revealed:
- โ Users asked SparkGPT questions it couldnโt answer (like pulling live data)
- ๐ Many didnโt understand where its info came from
- ๐ค Frustration led to drop-offs and mistrust
โ
โ
๐จ My Role
- Led the feedback analysis across multiple touchpoints
- Synthesized recurring patterns in misunderstandings
- Designed and delivered the Suggested Prompting experience
- Collaborated with PMs and engineers to shape a scalable roadmap
โ
โ
โ
โ
๐งญ The Design Process โ Storytelling Through Research
โ
๐งช First Step: Listening to Feedback
Every few months, we collect feedback from:
- ๐๐ Thumb reactions
- ๐ In-app feedback forms
- ๐ฌ User interviews
In Q1 2025, I analyzed 100+ pieces of feedback.
Over 60% of negative feedback came from misunderstandings about how the tool worked:
- โWhy canโt it fetch this dashboard data?โ
- โThe answers seem made up.โ
- โWhat is this trained on?โ
โ
โ
โ
๐ What We Discovered
The main issue wasnโt the feature set โ it was user understanding. We needed to:
- Set clear expectations
- Teach prompting skills
- Build confidence with new users
โ
โ
๐ก What Can We Do to Build Confidence?
โ Make It Clear What SparkGPT Can and Canโt Do -Users needed a better mental model of the tool's capabilities.
โ Help People Prompt Better - Many didnโt know how to ask the tool questions effectively.
โ Build a System That Can Grow - We needed to test our ideas fast, but plan for smart, scalable prompting down the line.
โ
โ
๐ป Solutions We Rolled Out
โ
๐ฏ Static Suggested Prompts (Phase 1)
We started small (we work agile!)โ when a user lands on a new chat, they see helpful suggestions like:
- โWhat can I use SparkGPT for in my work?โ
- โIs my data private when I use SparkGPT?โ
- โSummarise this meeting: [paste notes]โ
- โDraft an email about [topic] in a [tone] tone.โ
โ
Why This Approach Works
- ๐ Better Engagement โ Users see relevant prompts upfront, making it easier to start.
- ๐ More Discoverability โ AI introduces use cases that users might not think of on their own.
- ๐ Scalable Learning โ The system adapts dynamically as users gain experience.
- ๐ Encourages Experimentation โ Users feel guided but also free to explore.
โ


๐ฎ Dynamic Prompting (In Progress)
Weโve laid the groundwork to:
- Adapt prompts based on user role (e.g., Product, Contract, Analytics)
- Suggest questions based on prompt history
- Recommend ways to improve poorly structured queries
๐ Goal: Build a machine-learning-driven backend system that dynamically suggests prompts based on user history, past interactions, and usage patterns.

๐ Outcomes
- ๐งญ Users began exploring SparkGPT more confidently
- ๐โโ๏ธ Drop in questions like โWhat should I do with this tool?โ
- โ๏ธ Prompt quality improved โ more structured and role-relevantโ
โ
My Achievements in This Project
- Translated qualitative feedback into actionable UX solutions to build trust and clarity in AI workflows
- Wrote, tested, and deployed the first round of static prompt suggestions with measurable success
- Helped establish the content and logic model for dynamic prompting, to scale AI usability
- Created alignment across teams for solving a behavioral UX problem, not just a feature request
โ