> For the complete documentation index, see [llms.txt](https://process.mad.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://process.mad.co/project-work/design/brand-design-sprint-agenda.md).

# Brand and Web Design Sprint Agenda

The design sprint agenda will vary among the different projects and ultimate goals. However, there are is always an underlying structure in which we base it off off.

**Branding**

* Daily Agenda & Introduction
* Long Term Goal
* Long term Goal Questions
* What work and doesn’t work
* Expert interview
* Who

  *Coffee Break*
* Brand Pyramid
* Competitive Landscape
* Personality Slides

  *Lunch Break*
* Lightning Demos
* Solutions Sketching

  *End the day*

**Website**

* Daily Agenda & Introduction
* Long Term Goal
* Long term Goal Questions
* Personas workshop

  *Coffee Break*
* What work and doesn’t work
* Vote on what doesn’t

  *Lunch Break*
* How might we
* Solutions to How might we
* Journey Mapping
* Lightning Demos
* Solutions Sketching

  *End of Day*<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://process.mad.co/project-work/design/brand-design-sprint-agenda.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.