> 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/ideation/interaction-modelling.md).

# Interaction Modelling

Interaction modelling involves the creation and representation of the interactions between users and a system or interface.&#x20;

It focuses on understanding and designing the flow, sequence, and behaviour of user interactions with various components and features of a digital product or service. Interaction modelling helps define how users navigate through screens, interact with elements, and accomplish tasks within the system.&#x20;

It typically involves creating visual diagrams, such as wireframes, flowcharts, or interactive prototypes, to illustrate the user interface, input/output processes, and system responses.&#x20;

By employing interaction modelling, designers and developers can iteratively refine the user experience, anticipate user needs, and ensure that the interactions are intuitive, efficient, and aligned with the users' goals and expectations.

#### Further Viewing

{% embed url="<https://builtin.com/design-ux/interaction-model>" %}

{% embed url="<https://mltechsoft.com/blog/practical-guide-interaction-model-design/>" %}

{% embed url="<https://www.uxmatters.com/mt/archives/2012/01/defining-an-interaction-model-the-cornerstone-of-application-design.php>" %}


---

# 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/ideation/interaction-modelling.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.
