01 / UNDERSTAND
What is competitive analysis in design?
Competitive analysis examines how relevant alternatives address a defined need and what that means for your product or service. A UX comparison focuses on the experience of accomplishing an activity, while a business comparison may also examine positioning, channels and pricing. Define the decision before collecting examples.
Alternatives can include a direct competitor, an indirect service, a manual arrangement or choosing not to act. Comparing only products with similar interfaces can miss the option people already trust. The analysis identifies questions and possible differentiation; it does not prove demand for your proposal.
Why use Competitive Analysis?
A team can mistake a familiar interaction pattern for a requirement or a missing competitor feature for an opportunity. A consistent comparison helps separate observed behaviour, marketed claims and assumptions about user value. It also prevents one attractive screenshot from becoming an unexamined design brief. The scenario comparison below is an editorial application for a product decision, not a named or validated scoring framework.
When to use it
USE IT WHEN
A team needs to understand existing alternatives before framing a proposition.
An interaction or service model is being considered and its tradeoffs need comparison.
Stakeholders are requesting competitor parity without explaining the underlying need.
When to choose another method
Use User Interviews to understand why people choose or reject alternatives.
Use Heuristic Evaluation to diagnose usability problems within one interface.
Use Value Proposition Canvas to examine a proposed benefit after identifying relevant needs.
What you’ll need
Choose a user situation, market boundary and comparison date. Gather public information and inspect accessible experiences without fabricating identities or bypassing access controls. Record the plan, device, location and conditions used. Separate what you observed from what a provider claims. If a step cannot be inspected, mark it unknown instead of rating it poorly.
What a useful comparison needs
Keep the elements that help answer your question and support a decision.
The product or service choice this analysis should inform.
Direct, indirect and existing ways of meeting the need.
The same relevant activity and conditions across alternatives.
Consequences that matter to the person and the organisation.
Observed behaviour, dated claims and inaccessible areas.
Possible opportunities, tradeoffs and questions for research.
02 / PUT IT INTO PRACTICE
How to run a competitive analysis
Keep evidence and assumptions distinct. Revisit your work when new information changes your understanding.
01
Frame the question
Name the decision and the user situation. Exclude interesting but irrelevant differences.
Compare how a tutor and learner agree a changed appointment.
02
Select alternatives
Include current workarounds as well as similar products.
A shared calendar and a message exchange may be genuine competitors.
03
Set comparison conditions
Use an equivalent scenario and record differences that cannot be controlled.
Inspect the same cancellation situation on the relevant subscription plan.
04
Define criteria
Prefer consequences to feature counts. Explain why each criterion matters.
Can both people tell which time is confirmed?
05
Capture evidence
Document what happened and where information came from. Keep unknowns explicit.
A marketing page promises reminders; that is not an observed delivery event.
06
Explain tradeoffs
Identify what an alternative makes easy and what responsibility it transfers.
Flexible messages preserve nuance but leave confirmation work to participants.
07
Choose follow up research
Turn a comparison into a testable question rather than a copying task.
Investigate whether a shared confirmation rule would justify changing the current arrangement.
Example: comparing ways to reschedule a lesson
Fictional scenario: a team considers a scheduling service for independent tutors. It compares a booking product, a shared calendar and the existing message exchange. The same scenario is used: a learner requests a change after the original appointment has been confirmed.
The booking product offers structured choices but may require a new account. The calendar makes availability visible but does not necessarily explain whether the change is accepted. Messages allow exceptions but require somebody to reconcile the final time. These are invented comparison observations.
The opportunity is not simply to combine every feature. The team proposes investigating a lightweight confirmation arrangement within the existing channel. A lower feature count can still represent a better fit if it removes a consequential coordination problem without introducing unwanted account management.
03 / BELOW THE SURFACE
Below the surface: absence can mean restraint
A missing feature is not evidence of a neglected need.
ALTERNATIVE
What already works well enough?
Include a manual or existing arrangement.
ABSENCE
Why might this feature be missing?
List competing explanations rather than assuming neglect.
SWITCHING
What new work does our proposal create?
Examine adoption and ongoing coordination costs.
An alternative may omit automation because exceptions need negotiation, because data is unreliable or because customers prefer existing tools. It may also simply be incomplete. The interface alone cannot reveal which explanation applies.
For an apparent gap, write competing explanations before proposing a feature. Ask what the alternative preserves through its current arrangement and what new work your proposed improvement introduces. Differentiation should survive comparison with doing nothing. If the added benefit depends on a person maintaining another account, include that cost in the investigation.
The comparison becomes more rigorous when it ends with an uncertainty worth resolving rather than a verdict that your concept is better. Use research with people in the relevant situation to distinguish the explanations.
Competitive Analysis companion worksheet
The original two page comparison worksheet records the decision, alternatives, scenario, criteria, evidence and implications. The second page examines an apparent gap and the costs of changing the current arrangement. Use separate copies for different scenarios. It is a research record, not an automatic competitor ranking tool.
Practical tips
Date observations and record the plan or device used.
Include at least one current workaround where it is relevant.
Link every important conclusion to its evidence and uncertainty.
Common mistakes
Using a feature checklist as a substitute for a user scenario.
Treating unavailable information as a demonstrated weakness.
Copying a pattern without understanding the service conditions that make it work.
What you’ll get
A comparison that explains useful differences and their limits. Carry one consequential gap or tradeoff into user research or concept testing. The value of the analysis is the decision it clarifies, not the number of competitors inspected.