> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/intro-to-informatics-and-web-development/3-1-intro-to-interaction-design.md).

# 3-1 Intro to Interaction Design

**Interaction design (IxD)**, focuses on the way people interact with products and services. Interaction designers use many different techniques to understand the goals of people and how to provide effective ways for people to accomplish those goals with interactive services.

## Standard Deliverable ✓

1. **Read** [**"What is Interaction Design?" by Teo Siang**](https://www.interaction-design.org/literature/article/what-is-interaction-design)**.**
2. **In small groups, choose an interactive product or service to analyze.** For example, you could choose a popular website, an ATM, a particular video game console, a mobile app, a mobile phone OS, a thermostat etc.
3. Use the 5 dimensions of interaction design to deconstruct your chosen product. For each dimension, carefully determine how your product uses that dimension.
4. Outline your findings in a one-page document or single slide to share with the class.
5. **Share with the class.** Challenge each other on the completeness of your analyses. For example, if a product uses GPS, what interaction design dimension does it affect?

## Advanced ✓+

Review the last section of the article with the heading "So what do interaction designers do?". Have each person search for a job position related to interaction design but not necessarily titled *interaction designer*. Add a brief description of each position your group found on a second page or slide. Consider using monster.com, indeed.com, glassdoor.com, or <http://ixda.org/jobs/> for your searches.


---

# 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://docs.launchboard.app/cxd/intro-to-informatics-and-web-development/3-1-intro-to-interaction-design.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.