---
title: "Heuristic Evaluation for SaaS Products | Utkarsh Panwar"
description: "Heuristic evaluation for SaaS: Nielsen's 10 heuristics on real product screens, a 0 to 4 severity scale with examples, and where expert review falls short."
url: https://www.utkarshdesign.com/guides/heuristic-evaluation-saas
author: Utkarsh Dhairya Panwar
updated: 2026-10-08
---

# Heuristic evaluation for SaaS products

Guide · 7 min read · By [Utkarsh Dhairya Panwar](https://www.utkarshdesign.com/about) · Updated 8 Oct 2026

**A heuristic evaluation is an expert review: evaluators walk the main tasks, log where screens break known usability principles, and rate each problem's severity. In SaaS, aim Nielsen's 10 heuristics at permissions, setup, errors and empty states. It's fast, but only users can tell you if they want the product.**

## Running one in an afternoon

1. **Pick three to five tasks**: Choose the ones the business depends on, like connecting an integration, inviting a teammate, acting on a result or paying. Don't tour every screen.
2. **Choose the roles**: Walk each task as the admin and again as a member without admin rights. In B2B products the second walk usually finds more.
3. **Evaluate alone first**: Each evaluator logs problems on their own: the screen, what happens and which heuristic it breaks. Comparing notes too early makes everyone find the same things.
4. **Merge and rate**: Combine the lists, remove duplicates and give each problem a severity from 0 to 4. Each disagreement about severity deserves about five minutes of discussion.

One evaluator finds a fair share of the problems and three find noticeably more, which is why Nielsen recommends several. A solo founder can still get most of the value by doing the pass twice, a week apart.

## The ten heuristics, translated for SaaS

The list is easy to find. Spotting the problems on your own screens is harder, so the second column shows what each one tends to look like when it's broken in a B2B product.

| Heuristic | What to look for in a SaaS product |
| --- | --- |
| 1. Visibility of system status | Syncs, imports and payments with no visible state, so people can't tell whether something is running, done or stuck |
| 2. Match between system and the real world | Labels in your team's internal vocabulary instead of the words users already know from the tools they connect |
| 3. User control and freedom | Steps a user reaches but can't finish or leave, especially when someone else holds the permission |
| 4. Consistency and standards | The same table, filter or modal built three ways across the product |
| 5. Error prevention | Limits, one-time actions and irreversible steps that only explain themselves after the user commits |
| 6. Recognition rather than recall | Tours that ask people to remember where five features live, instead of linking to them when needed |
| 7. Flexibility and efficiency of use | No bulk actions, saved filters or shortcuts for the people who use the product every day |
| 8. Aesthetic and minimalist design | Setup pages that show every platform's instructions to everyone |
| 9. Recognise, diagnose, recover from errors | Different failures that share one generic message, so the user can't pick the right fix |
| 10. Help and documentation | Setup that only exists as reference docs, outside the product |

## Five of them from my own work

- Heuristic 3 at CodeAnt AI: a developer without org admin rights reached the GitHub install and had nowhere to go. The fix let them email the admin or share an invite link.
- Heuristic 4 at CodeAnt: 18+ UI patterns did similar jobs in different ways, until I folded them into one system.
- Heuristic 5 at FamPay: one-time-use vouchers lost their leftover value and users found out afterwards. The rule moved above the Buy Now button, which my guide to reducing support tickets with UX covers in full.
- Heuristic 8 at CodeAnt: self-hosted setup was one dense page for every platform. It became a flow that only shows your platform's steps.
- Heuristic 9 at FamPay: a timeout, a bank decline and a retry looked alike on iOS. Each got its own message inside one shared error pattern.

![GitHub-style Install and Authorize dialog with options for all or selected repositories, a list of read and write permissions and a green Install and Authorize button](https://www.utkarshdesign.com/images/QWzAhleILakb0CawY3pUt5lphEE.webp)

_Heuristic 3 in practice. For an admin this dialog is fine. For a developer without org rights it's a dead end._

## Severity: Nielsen's 0 to 4 scale, with SaaS examples

Nielsen rates severity on three factors: how often the problem happens, how hard it is to get past, and whether it keeps coming back. For SaaS I add one more question: does it sit before or after first value? A problem after first value costs patience. One before it can cost the customer.

| Rating | Meaning | Typical SaaS example |
| --- | --- | --- |
| 0 | Not a usability problem | An evaluator prefers a different icon |
| 1 | Cosmetic; fix if there's time | Inconsistent capitalisation in a settings menu |
| 2 | Minor; low priority | A filter that resets when you go back to a list |
| 3 | Major; high priority | An error with no next step on a common task |
| 4 | Catastrophe; fix before release | A setup step some users cannot complete at all, like the admin wall |

## Where heuristics miss in B2B products

CodeAnt's onboarding would have passed most screen-by-screen reviews, because each screen was clear on its own. The failure sat between two people: the developer who wanted the product and the admin who had the access. A heuristic review looks at one screen at a time, and B2B products often fail at the hand-off from one person to the next.

![Four-step diagram: a developer discovers CodeAnt, is blocked at an admin wall outlined in red, the org admin has access, and only then is the repo connected](https://www.utkarshdesign.com/images/aU20VqOCAkvTLldgRFUIL0s6d4.webp)

_A problem no single screen shows: intent and access belong to different people._

So I walk tasks per role, and I read the funnel before rating anything. When the data shows a cliff at a step that looks fine, the cause is usually who is on that screen rather than how it's laid out. How heuristic review fits next to audits and usability tests is covered in UX audit vs usability testing.

## A log you can copy

A spreadsheet or FigJam board with one row per problem works better than a long document. These columns are enough:

- Task and role, for example "connect repo, as non-admin".
- Screen, with a screenshot or frame link.
- What happens, in one sentence.
- Heuristic number.
- Severity from 0 to 4, and whether it's before first value.
- Suggested fix.
- Evaluator initials, so you can see which problems more than one person found.

To turn the log into a ranked fix list for the whole product, see my UX audit process guide.

## Questions people ask

### What are Nielsen's 10 usability heuristics?

Visibility of system status, match with the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency, minimalist design, error recovery, and help and documentation.

### How many evaluators does a heuristic evaluation need?

Three to five is the classic advice, because each one finds different problems. One careful evaluator who walks every task in each role still catches the worst ones.

### Are there heuristics specific to SaaS?

Nielsen's ten still cover most problems. For B2B SaaS I add two checks: can each role finish the task alone, and does the problem sit before or after first value.

### How long does a heuristic evaluation take?

For three to five tasks, about an afternoon per evaluator plus an hour to merge and rate. Bigger products take longer, mostly because there are more roles to walk.

## Sources

1. [10 Usability Heuristics for User Interface Design](https://www.nngroup.com/articles/ten-usability-heuristics/), Nielsen Norman Group
2. [Heuristic Evaluations: How to Conduct](https://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/), Nielsen Norman Group
3. [Severity Ratings for Usability Problems](https://www.nngroup.com/articles/how-to-rate-the-severity-of-usability-problems/), Nielsen Norman Group

## Working on this?

Tell me what you're building and where it's stuck: [book a 30-minute call](https://cal.com/utkarsh-design/30min), email [work@utkarshdesign.com](mailto:work@utkarshdesign.com) or [send a brief](https://www.utkarshdesign.com/contact).

## Related

- [How to do a UX audit, step by step](https://www.utkarshdesign.com/guides/ux-audit-process)
- [UX audit vs usability testing: which to do first](https://www.utkarshdesign.com/compare/ux-audit-vs-usability-testing)
- [UX audit report template](https://www.utkarshdesign.com/templates/ux-audit-template)
- [How to run usability testing on a budget](https://www.utkarshdesign.com/guides/usability-testing-startups)

---

Utkarsh Dhairya Panwar, Founding Product Designer and Design Engineer (IIT Roorkee; Founding Designer at CodeAnt AI, YC W24). Email: work@utkarshdesign.com · Book a call: https://cal.com/utkarsh-design/30min · Hire: https://www.utkarshdesign.com/hire · About: https://www.utkarshdesign.com/llms.txt