> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/competitor-analysis.md).

# Competitor Analysis

{% hint style="info" %}
AKA Competitive Usability Evaluations, Competitive Audit, Competitive Analysis
{% endhint %}

Competitor analysis is the process of studying and evaluating other businesses or organisations that operate in the same industry or offer similar products or services. It involves gathering information about their strategies, strengths, weaknesses, market position, and customer base.&#x20;

By conducting competitor analysis, businesses gain valuable insights into their competitors' actions and can identify opportunities and threats in the market. This analysis helps inform decision-making, refine business strategies, differentiate offerings, and gain a competitive advantage by understanding how to better serve customers and stand out from the competition.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/competitive-usability-evaluations/>" %}

{% embed url="<https://www.dhl.com/discover/en-ie/small-business-advice/starting-a-business/competitor-analysis-guide>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=0KyCAcV_y7o>" %}

{% embed url="<https://www.youtube.com/watch?v=wBxS2EqoanM>" %}

{% embed url="<https://www.youtube.com/watch?v=G2kpQGNxkRc>" %}

{% embed url="<https://www.youtube.com/watch?v=xaIeoPtHnuY>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/ux-methods/discovery/competitor-analysis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
