Competitive matrix: comparing without copying
A competitive matrix compares your product with others on features and experience. How to choose competitors, score tasks, weight criteria, and avoid copying.
What is a competitive matrix?
It is a tool for seeing your product next to the others. A feature matrix puts capabilities in rows and products in columns, so gaps are visible at a glance. UXPin, in its competitive analysis guide, proposes a four-level scale for features (absent, basic, good, excellent), and a 1-to-5 severity scale when evaluating usability problems.
A UX competitive matrix goes a step beyond the feature list. It also measures experience: how easily a user can complete what they came to do in each product.
Why does it matter to a designer?
Because design decisions are always made in reference to something: “this is how X does it”, “this is how not to do it”. A matrix organizes that conversation and stops opinions about competitors from being based on a single product someone tried once.
It also protects you from a common error: copying another product’s interface without understanding why it works for its users. Nielsen Norman Group puts it well: the goal is to improve your design, and the aim is to beat the competition, not to copy it.
How do you choose competitors?
Nielsen Norman Group describes a typical competitive evaluation as focusing on two to four competitors. It suggests choosing those that offer similar content and functionality, those with the best experience, the most innovative ones, and the ones your customers actually compare. It also says to study sites with better usability than yours, even if they are only loosely related.
UXPin proposes four to six competitors, mixing direct and indirect ones, with at least one market leader and one emerging player. That way the matrix reflects not only your sector but also where it is heading.
Which dimensions should you use?
A useful matrix goes beyond a feature list. These are common dimensions; adjust them to the question you want to answer:
| Dimension | Question it answers | How it is measured |
|---|---|---|
| Features | Does it exist? | Absent, basic, good, or excellent |
| Key tasks | How many steps and how much effort? | Number of steps, success, and time |
| Usability | Is the path understandable? | Problem severity from 1 to 5 |
| Content | Do the language and information help? | Qualitative review |
| Accessibility | Does it work with keyboard and screen reader? | Review against criteria |
| Price and service | What is paid, and how is support provided? | Verified public data |
Contify, by contrast, cites price, customer service, product quality, and marketing as popular areas to compare. Both approaches are valid; what matters is that the matrix answers the business question you actually care about.
How do you score the experience and weight criteria?
A feature matrix is easy to fill in, but it says little about experience. To score it, Nielsen Norman Group proposes competitive evaluations in which each participant completes representative tasks on two or three sites, alternating which sites are paired and which is tested first. Metrics can include success scores, time on task, and subjective ratings.
UXPin proposes a comparative test with five to eight participants and counterbalanced order, measuring success, time, errors, and satisfaction. For satisfaction it cites scales such as SUS or SEQ in its UX benchmarking method.
A practical combination: use the feature matrix to map the terrain, and task evaluation to score the experience. The first tells you what exists; the second tells you what works.
How do you weight criteria?
Weighting means giving more importance to what matters most to your user. Contify proposes assigning each critical factor a weight from 0.1 to 1.0, multiplying it by the score, and adding up the results. It is a useful way to compare, but only if you document why each weight has the value it does.
That is a general competitive-analysis practice, not a standard of UX research. So if you weight, write the justification next to the table. A weight without a reason looks objective and is not.
When is a matrix the wrong tool?
A matrix does not replace your users. If your question is what people need, the matrix cannot answer it; interviews can. To widen the terrain before comparing, review the competitive analysis page. And do not build the matrix with unverified data: Contify warns that a matrix is only as good as the information in it.
Avoid using the matrix as a ranking, too. The goal is to improve your design, not to declare a winner.
Example
Illustrative example: a team designing an app for booking sports courts builds a matrix with three competitors. In the features row, all of them have online payments and reminders. But when they evaluate the task “book a court for tomorrow at 7 pm”, one competitor takes six steps and another takes three. With five participants, the team sees that users get lost in one competitor’s time picker. The matrix did not say a feature was missing; it said the booking experience was the weak point for all of them, and that is where the team can differentiate.
Common mistakes
- Filling the matrix only with features, without evaluating experience.
- Copying a competitor’s interface without understanding its user context.
- Comparing against too many competitors, which makes the table unreadable.
- Using unverified data, such as outdated prices or old screenshots.
- Weighting without justification, so the result looks objective but is arbitrary.
- Turning it into a ranking and forgetting the goal of improving your design.
If the matrix leads you to concrete usability problems, the heuristic evaluation report helps you document them with their severity, and heuristic evaluations explain how to run one. To decide which differences to prioritize, the Kano model separates what users expect from what delights them. And if the goal is to find new ideas without copying, SCAMPER structures ideation starting from what already exists.