Analysis Workshop

Facilitating the Analysis workshop

Note: this was previously 'Definition workshop - part one'

Schedule

We usually allocate a little longer than needed in the schedule to give time for running behind and having a break.

• 00:00 - Synthesise Research

• 00:40 - Mapping

• 01:00 - How Might We...?

• 01:15 - Consequence Scanning

• 01:30 - End

Synthesise research

The group will have separated for research, and now need to communicate their findings to one another.

We ask them to take three steps in doing this:

1. Write down notes on what they heard from the research

2. Organise those notes into themes

3. Write up statements of the research insights

Mapping the journey

This is a version of User Journey mapping. Developers should plan the main path through the application.

On the left hand side, they consider their user. And on the right, the goal of that user. These can both be lifted directly from the Problem Statement and don't need much thought. It's the product itself, the 'I need a way to...' that needs to be explored.

There's three main phases here:

• Discovery: finding the service

• Learning: Finding out what your service offers and how to use it

• Using: The regular steps the user will take when using the app Discovery is the least important step for us on the programme. It's worth considering but not for more than a minute or two.

There might be a few different avenues, or choices made along the way. But by the end of the exercise, the team should have a broad idea of what the app will do and the order the user will perform actions in.

How Might We...?

This is a speculative exercise which intends to get developers thinking about the challenges of building a Product which will respond to the needs they've identified so far. Asking questions, and not worrying about the answers, will help to shape the key challenges of building this product.

Consequence scanning

Developers are encouraged to think about the effects of building a product like the one they have in mind. What good could it do? And what harm might it cause?

Create a table with two rows and two columns. The rows can be labelled "Intentended" and "Unintended"; and the columns labelled "Positive" and "Negative". You'll then have four squares for the developers to add notes.

Developers should add notes to the relevant sections for different intended/unintedend and positive/negative consequences of the app. The consequences might be broad, and can be imminent or distant. The main idea here is to consider the impact of a certain digital product.