> 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/2-4-personas.md).

# 2-4 Personas

Personas summarize the goals, desires, and frustrations of users to guide the design of a product or service. Below are two videos explaining personas.

Personas are useful for ensuring that we design for the people we are trying to serve and keep them at the center of our design decisions.

## Standard Deliverable ✓

For this exercise your interview findings will help you **create two personas** that describe two fictional (but realistic) users of a messaging app. Create personas that are loosely based on the people you interviewed. You may combine characteristics of two interviewees into one persona or any variation you think is appropriate. Use [this template](https://docs.google.com/document/d/10xYLagRUFZwWxgDa0PXRwbRKCHx73rhREC4lomihaZQ/edit?usp=sharing) as a starting point, but feel free to customize it as you like. Remember to create two personas. They can be submitted in a single document.

> You want your persona to be descriptive and to the point with elements like...
>
> * A persona name and representation (character sketch)
> * Demographic information like age, occupation etc.
> * A list of frustrations and needs.
> * A scenario that describes a success for the persona.

## Advanced ✓+

Simply create a third persona as an advanced deliverable.


---

# 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/2-4-personas.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.