Ex rev

SUMMARY.md

@@ -16,31 +16,31 @@
 ## Exercises
 
 - [List of Exercises](list-of-exercises/README.md)
-  - [The Five Whys](list-of-exercises/the-five-whys.md)
-  - [The Bigger Picture](list-of-exercises/the-bigger-picture.md)
-  - [Problem Statement](list-of-exercises/problem-statement.md)
-  - [How Might We](list-of-exercises/how-might-we.md)
-  - [Mapping](list-of-exercises/mapping.md)
+
   - [Assumptions Table](list-of-exercises/assumptions-table.md)
   - [Assumptions to Questions](list-of-exercises/assumptions-to-questions.md)
+  - [The Bigger Picture](list-of-exercises/the-bigger-picture.md)
   - [Common Areas](list-of-exercises/common-areas.md)
-  - [User Research Scripting](list-of-exercises/user-research-scripting.md)
+  - [Dot Voting](list-of-exercises/dot-voting.md)
+  - [The Five Whys](list-of-exercises/the-five-whys.md)
+  - [How Might We](list-of-exercises/how-might-we.md)
+  - [Idea Generation](list-of-exercises/idea-generation.md)
   - [Identifying Key Insights](list-of-exercises/identifying-key-insights.md)
   - [Inspiration](list-of-exercises/inspiration.md)
+  - [Mapping](list-of-exercises/mapping.md)
+  - [Problem Statement](list-of-exercises/problem-statement.md)
+  - [Product Backlog](list-of-exercises/product-backlog-workshop.md)
   - [Sketching](list-of-exercises/sketching.md)
-  - [Idea Generation](list-of-exercises/idea-generation.md)
-  - [Zippy 8s](list-of-exercises/zippy-8s.md)
   - [Solution Sketch](list-of-exercises/solution-sketch.md)
-  - [Dot Voting](list-of-exercises/dot-voting.md)
+  - [User Journeys](list-of-exercises/user-journeys.md)
   - [User Personas](list-of-exercises/user-personas.md)
+  - [User Research Scripting](list-of-exercises/user-research-scripting.md)
   - [User Stories](list-of-exercises/user-stories.md)
-  - [User Stories Workshop](list-of-exercises/user-stories-workshop.md)
-  - [User Journeys](list-of-exercises/user-journeys.md)
-  - [User Testing](list-of-exercises/user-testing.md)
-  - [Product Backlog](list-of-exercises/product-backlog-workshop.md)
+  - [Usability Testing](list-of-exercises/usability-testing.md)
+  - [Zippy 8s](list-of-exercises/zippy-8s.md)
 
 ## Extra resources
 
-- [Finding a Tech Partner](extra-resources/finding-a-tech-partner/README.md)
+- [Choosing a Tech Partner](extra-resources/finding-a-tech-partner/README.md)
 - [Glossary](extra-resources/glossary.md)
 - [Supplementary Resources](resources.md)

list-of-exercises/README.md

@@ -7,14 +7,15 @@ description: >-
 
 Here are a list of all exercises found in the design sprint workshops. Each exercise is adaptable and can be reorganised into the Discovery and Definition sections of the programme. Refer to the list here to read specifically about each activity.
 
-### For facilitators (?)
+### For facilitators
+
 Each of these exercises are adaptable and can be reorganised depending on the needs of the group you are facilitating. Tailoring the workshop by cherry picking specific exercises and arranging them in a certain order is a really powerful way of helping your user group process their problem areas and solutions. Your workshops become bespoke but still follow the design sprint structure.
 
 ### What you will find out for each exercise
 
-* Introduction
-* Required Materials
-* Workflow (how to facilitate)
-* Collaboration
-* Resources
-* Facilitator Notes
+- Introduction
+- Required Materials
+- Workflow (how to facilitate)
+- Collaboration
+- Resources
+- Facilitator Notes

list-of-exercises/assumptions-table.md

@@ -12,7 +12,7 @@ Examining the assumptions that a Product Manager is making will encourage them t
 
 ### Required Materials
 
-Paper and Pen.
+A table with two columns
 
 ### Workflow
 

list-of-exercises/common-areas.md

@@ -10,20 +10,25 @@ description: >-
 
 This workshop is intended for groups of Product Managers who are working in a shared problem space - for example, a group of charities who work with people who have experienced domestic abuse.
 
-The idea behind this exercise is to promote a discussion amongst participants on where their user research might converge or whether they have a shared user group. This workshop can help to encourage a shared experience during the Discovery Phase. 
+The idea behind this exercise is to promote a discussion amongst participants on where their user research might converge or whether they have a shared user group. This workshop can help to encourage a shared experience during the Discovery Phase.
 
 ### Required Materials
 
-Participants must have already discussed their ideas to some extent openly. We recommend conducting [The Bigger Picture](the-bigger-picture.md) before this exercise.
+Participants must have already discussed their ideas to some extent openly. We recommend conducting [The Bigger Picture](the-bigger-picture.md) or [Mapping](mapping.md) before this exercise.
 
-Post-it Notes and a Whiteboard can be useful here. 
+Post-it Notes and a Whiteboard can be useful here.
 
 ### Workflow
 
 1. Compare notes from previous discussion and look for areas which are common between all Product Managers.
 2. This may not necessarily be the same problem area but could involve similar research techniques, user groups or inspirations.
-3. Product Managers should each suggest an item which they believe is common between all participants. 
-4. These should be formulated on a whiteboard or on Post-its where all participants can see. 
+3. Product Managers should each suggest an item which they believe is common between all participants.
+4. These should be formulated on a whiteboard or on Post-its where all participants can see.
 
-Product Managers should be encouraged to use the common areas to formulate user-research questions that could be asked to each of their user groups. This will encourage collaboration in the moment as well as later on if the same Product Managers are given opportunity to compare results. 
+Product Managers can be encouraged to use the common areas to formulate user-research questions that could be asked to each of their user groups. This will encourage collaboration in the moment as well as later on if the same Product Managers are given opportunity to compare results.
 
+### Collaboration
+
+### Resources
+
+### Facilitator Notes

list-of-exercises/dot-voting.md

@@ -6,3 +6,14 @@ description: >-
 
 # Dot Voting
 
+### Introduction
+
+### Required Materials
+
+### Workflow
+
+### Collaboration
+
+### Resources
+
+### Facilitator Notes

list-of-exercises/how-might-we.md

@@ -26,3 +26,7 @@ _Or for remote delivery:_ Using Miro, or a similar service, create one space wit
 ### Collaboration
 
 Taking time to think individually gives each organisation an opportunity to consider the problems their users' face and the challenges of building something which addresses the needs of these users. Once everyone has had the chance to reflect on the questions they each have - coming back together to theme the Post-its gives a clear indication of where commonalities lie between the organisations involved. The theming also offers a shared space for collaborating - this step of moving notes in physical (or online) space brings forth a spirit of collaboration among the minds of participants.
+
+### Resources
+
+### Facilitator Notes

list-of-exercises/idea-generation.md

@@ -16,16 +16,19 @@ Pen and paper.
 
 ### Workflow
 
-1. Individually, Product Managers should spend about ten minutes drawing, doodling, and writing different ideas on an A4 sheet of paper. They should aim to fill the sheet of paper with doodles, sample headlines, diagrams, stick figures doing stuff - anything that gives form to their thoughts. 
-2. After each Product Manager has had the chance to sketch some ideas, the group should be brought back together to discuss what they drew. 
+1. Individually, Product Managers should spend about ten minutes drawing, doodling, and writing different ideas on an A4 sheet of paper. They should aim to fill the sheet of paper with doodles, sample headlines, diagrams, stick figures doing stuff - anything that gives form to their thoughts.
+2. After each Product Manager has had the chance to sketch some ideas, the group should be brought back together to discuss what they drew.
 3. Each participant should pass their sheet of ideas to the person on their left hand side.
 4. Once everyone has someone else's work in front of them, the group should discuss what stands out to them from the sheet in front of them.
-5. Participants can add dots, stars or circle pieces of work that stands out to them in particular. 
-6. After the discussion is over, the participants should pass back the sheets to their original owners. 
+5. Participants can add dots, stars or circle pieces of work that stands out to them in particular.
+6. After the discussion is over, the participants should pass back the sheets to their original owners.
 
 ### Collaboration
 
-When participants have another person's work in front of them they should feel more inclined to speak about someone else's ideas than their own. Trading sheets means that everyone has a new set of ideas in front of them which will help them to see the problem as viewed by someone else. 
+When participants have another person's work in front of them they should feel more inclined to speak about someone else's ideas than their own. Trading sheets means that everyone has a new set of ideas in front of them which will help them to see the problem as viewed by someone else.
 
-If the group has a hard time finding points to discuss, facilitators could suggest swapping a second time or bringing all the sheets of paper together in the centre of the table or on a whiteboard. 
+If the group has a hard time finding points to discuss, facilitators could suggest swapping a second time or bringing all the sheets of paper together in the centre of the table or on a whiteboard.
 
+### Resources
+
+### Facilitator Notes

list-of-exercises/identifying-key-insights.md

@@ -8,7 +8,7 @@ description: >-
 
 ### Introduction
 
-This exercise takes a Product Manager through identifying what was common, unexpected or illuminating from user research. They'll then group these into themes and use these themes to generate statements of the key insights. 
+This exercise takes a Product Manager through identifying what was common, unexpected or illuminating from user research. They'll then group these into themes and use these themes to generate statements of the key insights.
 
 This method will give a list of key insights supported by data, quotes and observations. Breaking the workshop down into four steps allows the Product Manager to focus on each step and understand the process of synthesis.
 
@@ -18,14 +18,17 @@ Post-its
 
 ### Workflow
 
-1. Product Managers should each write the most common, unexpected or illuminating stories that came from user research on separate Post-it notes. It is important to think about underlying behaviours and motivations of the user. Also, they should include things which falsified their previous assumptions. 
-2. One at a time, each Product Manager should then add all the Post-its to a board where everybody in the room can see. 
+1. Product Managers should each write the most common, unexpected or illuminating stories that came from user research on separate Post-it notes. It is important to think about underlying behaviours and motivations of the user. Also, they should include things which falsified their previous assumptions.
+2. One at a time, each Product Manager should then add all the Post-its to a board where everybody in the room can see.
 3. As a group, the Product Managers should re-arrange the Post-its into groups based on commonality.
 4. Now, name the themes, identifying what it is that links the Post-its in each group. This should be done as a group with the Product Manager leading. Other Product Managers can suggest different phrasing or highlight where an observation seems out of place.
-5. Create a statement for each group that would transform the theme into a core insight. This should encompass all of the data, observations and quotes within the group. It should also read differently to the quotes, observations and data from which it came - the insight statement should be a broad analysis of the detailed research. 
+5. Create a statement for each group that would transform the theme into a core insight. This should encompass all of the data, observations and quotes within the group. It should also read differently to the quotes, observations and data from which it came - the insight statement should be a broad analysis of the detailed research.
 6. Now, repeat steps 3 to 5 for each Product Manager's research.
 
 ### Collaboration
 
-Asking the Product Managers to work together in synthesising their research will encourage a fresh perspective from outside of the organisation. This helps to avoid bias in the grouping and will provide a deeper insight statement at the end. Allowing the Product Manager to lead and be supported by other participants will encourage collaboration and mediation between participants. 
+Asking the Product Managers to work together in synthesising their research will encourage a fresh perspective from outside of the organisation. This helps to avoid bias in the grouping and will provide a deeper insight statement at the end. Allowing the Product Manager to lead and be supported by other participants will encourage collaboration and mediation between participants.
 
+### Resources
+
+### Facilitator Notes

list-of-exercises/inspiration.md

@@ -8,21 +8,24 @@ description: >-
 
 ### Introduction
 
-By looking at similar solutions, design elements or apps that they like, Product Managers will begin thinking about how the solution they'd like to create may look like. It is key here to have already discussed the goal or insights that a Product Manager has formed before embarking on finding inspiration. 
+By looking at similar solutions, design elements or apps that they like, Product Managers will begin thinking about how the solution they'd like to create may look like. It is key here to have already discussed the goal or insights that a Product Manager has formed before embarking on finding inspiration.
 
 ### Required Materials
 
-A laptop or computer - ideally one each but this could be done on one device. 
+A laptop or computer - ideally one each but this could be done on one device.
 
 ### Workflow
 
-1. Thinking about one idea at a time, Product Managers shall research similar solutions or design aspects which could help them in their own design work. 
-2. Add detail to a shared document \(Figma, Creately, Google Doc\). This can include: images, icons, bullet points, headings, inter alia. Anything that can help to form an idea about how to solve the Product Manager's problem. 
-3. The group should discuss ideas around what is shared on the document. If one participant brings up a solution, another Product Manager might know of something similar. Often the ideas will not be solving the same problem but could solve a similar problem or even simply represent information in a pleasing way. 
+1. Thinking about one idea at a time, Product Managers shall research similar solutions or design aspects which could help them in their own design work.
+2. Add detail to a shared document \(Figma, Creately, Google Doc\). This can include: images, icons, bullet points, headings, inter alia. Anything that can help to form an idea about how to solve the Product Manager's problem.
+3. The group should discuss ideas around what is shared on the document. If one participant brings up a solution, another Product Manager might know of something similar. Often the ideas will not be solving the same problem but could solve a similar problem or even simply represent information in a pleasing way.
 
 ### Collaboration
 
-During this exercise it is important to facilitate the collaboration of idea sharing. One Product Manager might have a lot of ideas about how their product should look but there will be apps, websites or design aspects they have never seen before. Sharing ideas amongst the group will encourage a democratic and inclusive approach to problem solving. 
+During this exercise it is important to facilitate the collaboration of idea sharing. One Product Manager might have a lot of ideas about how their product should look but there will be apps, websites or design aspects they have never seen before. Sharing ideas amongst the group will encourage a democratic and inclusive approach to problem solving.
 
-It is important to have the document of inspiration somewhere that all participants can see. This means that everyone can contribute and can build upon one another's ideas. 
+It is important to have the document of inspiration somewhere that all participants can see. This means that everyone can contribute and can build upon one another's ideas.
 
+### Resources
+
+### Facilitator Notes

list-of-exercises/problem-statement.md

@@ -12,19 +12,19 @@ By formulating a problem statement from the perspective of the user, the Product
 
 These should be in the form:
 
-_As a..._ 
+_As a..._
 
-_I would like a way to..._ 
+_I would like a way to..._
 
 _So I can..._
 
 This can be explained as:
 
 _THE USER_ would like a way to _DO SOMETHING \(THAT ADDRESSES THEIR NEED\)_ so that _SOMETHING HAPPENS \(THAT BENEFITS THEM\)_.
 
-Giving the Product Managers an example will help them understand the format of the problem statement. It should always be written from the perspective of the user. The example we give is: 
+Giving the Product Managers an example will help them understand the format of the problem statement. It should always be written from the perspective of the user. The example we give is:
 
-_As a teenager who struggles to connect with others, I’d like a way to learn social cues so I can find friends and build relationships with my peers._ 
+_As a teenager who struggles to connect with others, I’d like a way to learn social cues so I can find friends and build relationships with my peers._
 
 This example was written for a product addressing the needs of teenagers with Autism Spectrum Conditions - this is not identified in the problem statement since a user would not refer to themselves in these terms.
 
@@ -35,7 +35,12 @@ Paper and pen
 ### Workflow
 
 1. The Product Managers should be presented with the structure of a problem statement.
-2. Give an example of a problem statement to the Product Managers. 
-3. Ask the Product Managers to formulate their own problem statements. 
-4. After giving enough time to formulate these ask participants to read them back to the group and allow other Product Managers to offer advice on each problem statement. 
+2. Give an example of a problem statement to the Product Managers.
+3. Ask the Product Managers to formulate their own problem statements.
+4. After giving enough time to formulate these ask participants to read them back to the group and allow other Product Managers to offer advice on each problem statement.
 
+### Collaboration
+
+### Resources
+
+### Facilitator Notes