UI/UX & Website Prompts

SaaS Dashboard UX Reviewer

Review a SaaS dashboard for clarity, visual hierarchy, navigation, and professional design quality with prioritized fixes.

✱ By PiSkill TeamFreeClaudeChatGPTGeminiMicrosoft Copilot

Best for

Product designers, founders, and product managers who want a structured, honest UX critique of a SaaS dashboard before a design or development sprint.

Suitable LLM groups

FrontierReasoning

Prompt

You are acting as a senior product designer who reviews SaaS dashboard interfaces for clarity, usability, and professional polish. You must not invent user research findings, analytics data, or usage statistics that I have not provided. Base your review only on the description or screenshot details I give you.

Here is my information:

Description of the dashboard or its layout: {{input_text}}
Who uses this dashboard: {{audience}}
Main tasks users need to complete: {{goal}}
Known pain points or complaints, if any: {{context}}
Design constraints, such as brand guidelines or existing component library: {{constraints}}
Devices this needs to support: {{examples}}

If you need more detail about the layout, user tasks, or existing design system before giving a useful review, ask me clarifying questions first.

Please produce a structured UX review with the following sections:

1. UX summary: A brief overall impression of the dashboard's usability based on the information provided.
2. Visual hierarchy issues: Identify problems with how attention is directed, such as competing elements or unclear emphasis.
3. Navigation issues: Identify problems with how users move between sections or find what they need.
4. Content clarity issues: Identify confusing labels, jargon, or unclear data presentation.
5. Professional UI improvements: Suggest specific changes to make the interface feel more polished and trustworthy.
6. Mobile and responsive notes: Note any concerns or recommendations for smaller screens, based on what was described.
7. Prioritized fixes: Rank the top five recommended fixes in order of impact versus effort.

Do not invent analytics numbers, user testing results, or satisfaction scores. If such data would strengthen the review, note that it should be gathered through real user testing rather than assumed.

How to use

Describe your dashboard layout, users, and their main tasks in the placeholders.
Mention any known pain points or complaints from real users.
Run the prompt in your preferred AI tool.
Answer clarifying questions if the layout or user tasks are unclear.
Use the prioritized fixes section to plan your next design sprint.

Example input

Dashboard description: a main dashboard with six widgets of similar size showing revenue, users, tickets, and other metrics with no clear primary metric. Navigation is a left sidebar with ten items, some rarely used. Users: operations managers checking daily metrics. Pain points: users say they cannot find the report export button quickly. Devices: desktop primarily, some tablet use.

Example output

UX summary: the dashboard presents information without a clear priority, which likely slows down the daily check-in task operations managers rely on.
Visual hierarchy issues: six equally sized widgets compete for attention with no dominant metric, making it unclear what the user should look at first.
Navigation issues: a ten-item sidebar likely overwhelms users, especially if several items are rarely used, increasing time to find common actions like exporting a report.
Content clarity issues: without a clear label or grouping, users may not immediately understand which metric matters most for their daily task.
Professional UI improvements: introduce a primary metric card at the top of the dashboard, group secondary metrics below it, and reduce the sidebar to core sections with a collapsible or grouped secondary menu for rarely used items.
Mobile and responsive notes: for tablet use, consider collapsing the sidebar into a top navigation or hamburger menu, and stack widgets vertically in priority order rather than a fixed grid.
Prioritized fixes: first surface the report export action more prominently since it is a known pain point, second establish a clear primary metric, third simplify the sidebar navigation, fourth reorganize widget hierarchy, fifth test the layout on tablet screens.

Customization tips

— Attach or describe a screenshot in detail for a more specific review.
— Mention your design system or component library so suggestions stay consistent.
— Ask for the review to focus only on one section, like navigation, for a deep dive.
— Request mockup-style text descriptions of the suggested layout changes.

FAQ

No, a detailed written description of the dashboard is enough, though more detail produces a more specific review.

Rate this prompt

How helpful was this?

Comments

Sam O.

Used this to ship 6 SEO articles in a week — the FAQ block alone is worth it.

Ines P.

Wish it had a Spanish voice preset, but overall very solid.

Related skills coming soon — browse all skills.

Related articles coming soon — visit the Learn hub.