# Iteration Workshop

The iteration workshop is a two-hour workshop consisting of exercises you are already familiar with, it is simply an extension of the presentation. 

The following is a quick guide on how to run it.

## Quick Intro & HMWs

`Duration: 10 mins`

The Iteration workshop starts similar to a final presentation. The Facilitator introduces the work done so far and makes sure everyone is paying attention.

{% hint style="info" %}
Ask the participants (especially the team) to **keep writing HMW notes** as a person presents. The first is the Product Designer and then the User Researcher. If you are the Facilitator, keep mentioning this repeatedly.
{% endhint %}

## Prototype Presentation

`Duration: 5-10 mins`

The Product Designer shares their screen to show the latest version of the prototype and narrates their creative decisions while pointing out how it looks. Once done, there is no discussion and they pass on the presentation to the User Researcher.

## User Research Presentation

`Duration: 30 mins`

The User Researcher moves on to present their slides describing the user feedback. 

{% hint style="info" %}
Ask the participants to write HMW notes as the team needs to work with notes over the following hour. The presentation slides will only be reference material for the future.
{% endhint %}

You can refer to [details on the presentation here](/teams-departments/deep-work-studio/roles/user-researcher/researcher-skill-tree.md#level-13-lead-presentation-expert-user-researcher). 

## Vote and Prioritise

`Duration: 10 mins`

In case of an iteration workshop, the team can start voting and prioritising the notes. This exercise is identical to the [HMW exercise](/teams-departments/deep-work-studio/roles/workshop-facilitator/facilitator-skill-tree.md#level-8-intro-hmws) from the first workshop of a Hypersprint. If the are not too many notes, you don't need to categorise them.

![](/files/-MXSEKV2PLvlgUWAK63A)

## Storyboard existing prototype

`Duration: 50 mins`

After prioritising, use the screenshots of the prototype as a [storyboard](/teams-departments/deep-work-studio/roles/workshop-facilitator/facilitator-skill-tree.md#level-9-facilitate-storyboard) and distribute the up-voted notes across the screens. This gives an initial indication for the areas requiring improvement. Make sure to focus on the most difficult UX challenges, rather than easy fixes and copy.

![](/files/-MXSER1eh2URA_64qjai)

After going through a rough overview, go into more detail on each screen and use the Miro tools to visibly alter the interface. The changes need to be clearly distinguishable from the original prototype.

![](/files/-MXSE9tChlTP3f4WjGF8)

{% hint style="success" %}

### This concludes the iteration workshop. You're done!

{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.deepwork.studio/teams-departments/deep-work-studio/roles/workshop-facilitator/facilitator-skill-tree/hypersprint-iteration-facilitation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.