Make the business case for a UX improvement
Builds a short, numbers-aware pitch that links a design fix to revenue, cost, or risk so leadership prioritizes it.
The prompt
Help me make the business case for a UX improvement.
The problem: [WHAT IS BROKEN AND FOR WHOM]
Evidence: [RESEARCH, SUPPORT TICKETS, ANALYTICS, DROP-OFF, QUOTES - only real data]
Proposed fix and estimated effort: [WHAT WE WOULD DO; DESIGN AND ENGINEERING TIME]
Decision-maker and what they care about: [e.g. "VP product, focused on retention this quarter"]
Competing priorities: [WHAT ELSE IS ON THE ROADMAP]
Numbers I can use: [e.g. tickets per month, cost per ticket, conversion rate, average order value, traffic]
Give me:
1. The impact model: link the fix to one primary business lever (revenue, cost to serve, retention, risk or compliance) and show the math with my numbers, e.g. tickets avoided x cost per ticket. Give a conservative, expected, and optimistic range with assumptions stated. Where I lack a number, use [ADD DATA] - do not invent figures.
2. The cost of doing nothing.
3. A low-risk way to start (smaller version, experiment, or phased rollout) and how we will measure success.
4. A one-page pitch: headline, problem with a user quote, impact range, effort, recommendation, ask.
5. Two likely objections and responses.
Keep the tone factual; avoid overstating certainty.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- WHAT IS BROKEN AND FOR WHOM
- WHAT WE WOULD DO; DESIGN AND ENGINEERING TIME
- e.g. "VP product, focused on retention this quarter"
- WHAT ELSE IS ON THE ROADMAP
- ADD DATA
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Plan user interviews or usability testsA research plan with goals, participants, discussion guide, and tasks.
- Explore several design directions for one UX problemGenerates distinct concept directions for a design problem, each with its core idea, layout sketch description, trade-offs, and what to test.
- Decide which enterprise features to build before moving upmarketA prioritized enterprise-readiness roadmap covering SSO, SCIM, audit logs, permissions, and admin controls, tied to deals.
- Design an app or website for older adults, children, or other specific usersDesign principles, layout and interaction rules, and a test plan for an interface built for a particular audience, such as older adults or children.