Understanding the problem space
I co-facilitated a workshop with Al Sinoy for Twist as part of my industry project at the Centre for Digital Media. Participants: 1 product owner, 1 scrum master (me), the dev team, the client and Al Sinoy (agile coach). The aim of this post is to present an overview of our workshop along with the key learnings I got from it.
Twist is a fitness company that focuses on “forward-thinking nutrition and medicine” and fitness. Twist approached the CDM to develop a digital solution around the themes of wellness and health. We organised a brainstorming workshop in week 2 of the project to gain clarity on the project goals and further define the target audience.
We started by defining the OARRS of the meeting: Objective, Agenda, Roles (Fig 1.), and rules (Fig 2.). We then defined our vision of success for the project. These first exercises allowed us to 1) get to know everyone better, 2) clarify the goals of the meeting and 3) reach alignment regarding the project.
We then attempted to define the target audience through user profiles (Fig 3.) and user journeys (Fig 4.). Twist did not have a specific demographic in mind, this is why we decided to choose 2 profiles (Jane and Thomas), with opposite needs, motivations, desires and expectations regarding health and fitness. Even though those profiles might not represent the target audience that Twist will eventually aim for, they allowed us to start ideating.
How might we...
This leads me to our next step: the "How Might We" exercise. With our personas in mind, we individually came up with questions that framed the pain points that were identified in the previous exercise. Here's an example: "How might we help Jane reach her daily goals?". Once all the questions were shared; we grouped them and formed categories silently. The purpose of the silent sorting was to avoid unnecessary, lengthy and biased discussions. We aimed to push the participants to read other people's ideas and concerns.
We finished the workshop with an exercise named "Crazy 8" which consists of sketching/drawing/writing 8 ideas (Fig 5.) in 3 minutes. The ideas should address the questions written in the "How Might We" exercise.
The stakeholders agreed on a first draft for the user profiles, their pain points, and solutions that could potentially address them. The next step for the team was to take those ideas and pain points back to the project room, continue ideating and start producing the first prototypes.
1) breaking into smaller groups helps increase ownership (over process and product) and fosters participation, 2) the user/target should always be the focus, 3) timeboxing each activity is key, it helps the participants focus on what matters, 4) having a variety of activities fosters creativity and collaboration.
Read about my process: here.