1.1. The system should be designed with the right affordances
The system should be designed with the right affordances to explicitly tell users its purpose(s).
Colombo and Pasch's 10 Heuristics for an Optimal User Experience were published as a practical synthesis of older heuristic work, tuned specifically for web products and digital services. The pair reworked classic usability principles into a list that leans heavily on user experience — factors like emotion, engagement, confidence, and trust alongside the traditional efficiency and error-prevention criteria.
This guideline is a good fit when you suspect a product has a "soft" problem: measurable task completion is fine, but retention is low, reviews are mixed, or users churn without a clear objection. Colombo and Pasch's heuristics give evaluators explicit language for flagging the things a stopwatch-and-clickstream analysis doesn't catch.
Because the list is a modern synthesis rather than a foundational framework, it works well as a standalone evaluation for consumer web products, e-commerce flows, and content-led experiences — or as a second pass after a more tactical review like Nielsen's 10 or Shneiderman's 8.
1.2. The system must be functional
The system must be functional, meaning that it must fulfill the purposes highlighted by the affordances and meet users’ expectations.
1.3. Additional features are welcome
Additional features (other than the core ones) are welcome, even better if they foresee possible alternative uses of the system: a product that is actually exceeding users’ expectations is often a predictor of a good user experience.
2.1. The system should provide steady and prompt feedback
2.2. The feedback should be as less obtrusive as possible
2.3. Obtrusiveness of feedback should be based on priority
The “obtrusiveness” of the feedback should be proportional to the level of priority (to establish a sort of hierarchy).
3.1. The system must be usable
3.2. The system should provide feedback
The system should provide feedback that is relevant and meaningful for the task at hand.
3.3. The system should avoid distractions
The system should avoid distractions, namely stimuli that are not relevant for the task at hand.
4.1. The system should be ergonomic
The system should be ergonomic, it should fit users’ skills and activity purposes.
4.2. The system behavior should be consistent and predictable
4.3. The system should be designed with aesthetic integrity
The system should be designed with aesthetic integrity, in other words the design should be visually appealing and common principles of good design should be followed: it should also provide a graceful flow, namely the interaction between users and the system should be smooth and graceful.
5.1 The system should be customizable and manipulable
The system should be, to a certain extent, customizable and manipulable by users in both its appearance and its functionality.
5.2. The customization process should be easily accessible
The customization process should be easily accessible, and with a predictable outcome.
5.3. Provide users with multiple choices
Provide users with multiple choices for interacting with the system (doing the same activity in many different ways).
6.1. The system should have a steep learning curve
The system should have a steep learning curve to help novice users.
6.2. The system should encourage users to explore it
The system should encourage users to explore it and to discover all the features and opportunities for interaction.
6.3. The system should provide advanced features
The system should provide advanced features or extra functions (e.g. accelerators, macros, advanced settings, etc.) and make them accessible for intermediate/advanced users.
7.1. The system should help users to improve their skills
The system should help users to improve their skills and to reduce the margin of error in performing the activity.
7.2. The system should not make users feel trapped
The system should not make users feel trapped. Avoid (as far as possible) constraining users’ actions, provide them an exit strategy and make the actions easily reversible.
7.3. Enable or disable automatic processes
Users should be always allowed to enable or disable automatic processes or system aids.
8.1. The system’s pace should be suitable
The system’s pace should be suitable for the activity for which it was designed.
8.2. The experience should not be interrupted by the system
The experience should not be interrupted by the system but users should be allowed to suspend the interaction and to restart it from the point of achievement he reached.
8.3. The rhythm of the interaction
Users should be allowed to speed up or slow down the rhythm of the interaction.
9.1. The system should be designed by looking at final users
The system should be designed by looking at final users and the activity they seek to accomplish, this means that you should know them first.
9.2. The system should be flexible
Knowing all the possible users and activities is impossible, so the system should be flexible in order to adapt to various users for various activities and in different contexts.
9.3. The system should satisfy the basic psychological needs
When applicable, the system should help users to satisfy the three basic psychological needs (in a broad sense): need for competence, autonomy, and relatedness.
10.1. The system should provide a certain degree of novelty
The system should provide a certain degree of novelty and variety to users.
10.2. The result of a trade off between innovation and tradition
The system should be the result of a trade off between innovation and tradition, where tradition is meant as consistency with familiar systems and compliance to standards.
10.3. The system should ensure interoperability
The system should ensure interoperability to seamlessly integrate into the existing content.
See it in action
Colombo & Pasch's heuristics, on a live URL, in one click.
Click anywhere on a real page, drop a heurio, pick the Colombo & Pasch's heuristics rule it violates. No screenshots, no Loom, no separate doc.