> For the complete documentation index, see [llms.txt](https://university.obvious.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.obvious.in/strategy/sprints/sketch.md).

# Sketch

## 👋 Introduction

Day 2 includes divergent thinking to bring out your best ideas. Start with gathering inspiration, and then carry forward to flex your visual communication muscles by sketching out potential solutions. Emphasise critical thinking over artistry.

***

## 1️⃣ **Lightning Demos**

Get inspired by other solutions, and look at how others are solving the same problem. Its like playing with Lego bricks—gather useful components, and then convert them into something original and new.

<figure><img src="/files/pCKk0HFCYJEYVx1KWGle" alt=""><figcaption></figcaption></figure>

> Searching for solutions to the same problem across different industries will broaden what you think is possible, and lead to an innovative solution.

{% hint style="success" %}
**Quick Facilitation Tip:** Remind the team early and often about what problems they're tackling. This will help them ground their sketches and generate meaningful solutions.
{% endhint %}

***

## 2️⃣ Four Part Sketching

It’s time to transform abstract ideas into concrete solutions. There will be no brainstorming as a group. Instead, work individually and try to put your thoughts down on paper. This will help make your ideas tangible.

### Part 1: Take Notes

Refresh your memory before you commit to a solution. You’re allowed to use your laptops to look up references, or research specific details on older solutions.

<figure><img src="/files/oqAGFluiwPwfS7CaqVyK" alt=""><figcaption></figcaption></figure>

> Collate your version of everything that’s happened so far. You will use this as a quick reference when you start sketching solutions.

### Part 2: Sketch Ideas

Start jotting down rough ideas. Think of this exercise as a scratch pad for your ideas.

<figure><img src="/files/UbKIpAmPQXMpG8WTh5QA" alt=""><figcaption></figcaption></figure>

> This could be anything that gives form to an idea or thought. Don’t worry about interfaces yet. It’s okay to be messy and incomplete.

{% hint style="success" %}
**Quick Facilitation Tip:** Remind people that sketching isn't about creating a perfect drawing or showing off artistic skills. It's just a way to make their ideas tangible.
{% endhint %}

### Part 3: Crazy 8’s

Rapid sketches force you to push past initial ideas & get to stronger alternatives, quick.

<figure><img src="/files/iYpdEZMiMErqwaYnu0n6" alt=""><figcaption></figcaption></figure>

> Think quickly and spend more time generating solutions to the problem, and not on beautifying each sketch.

### Part 4: Solution Sketch

Bring your solution to life. This three-part storyboard turns the customer into an actor in your story, with the product acting like a scene that they interact with.

<figure><img src="/files/uxZtrk08QagX1RGQW3Ha" alt=""><figcaption></figcaption></figure>

> Use words and comments to illustrate your sketch. The quality of your solution matters more than the artistry of your drawing.


---

# 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://university.obvious.in/strategy/sprints/sketch.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.
