Uxpa design thinking workshop
•Download as PPTX, PDF•
17 likes•5,596 views
UXPA Austin Design Thinking Workshop
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Uxpa design thinking workshop
Similar to Uxpa design thinking workshop (20)
Recently uploaded
Recently uploaded (20)
Uxpa design thinking workshop
- 1. Austin UXPA IBM Design Thinking
- 2. Let’s jump right in…
- 3. Exercise 1: Design a vase
- 4. Exercise 2: Design a way for people to enjoy flowers in their homes
- 6. IBM Design Thinking: Principles and Core Practices Prototype Evaluate Understand Explore Sponsor Users Understand the User Experience Playbacks Collaborate. Align. Engage! Hills Invest for Market Outcomes
- 7. IBM Design Thinking: Principles and Core Practices Hills frame your releases around user- centric market outcomes, not feature requests. Sponsor Users help you design experiences for real target users, rather than imagined needs Playbacks align teams around stories that show the value of your offering to your users Sponsor UsersHills Playbacks
- 8. IBM Design Thinking: Principles and Core Practices Sponsor UsersHills Playbacks Hills frame your releases around user- centric market outcomes, not feature requests. Sponsor Users help you design experiences for real target users, rather than imagined needs. Playbacks align teams around stories that show the value of your offering to your users. user users users
- 9. Prototype Evaluate Understand Explore UXPA: Design Thinking Workshop Empathy Map As-Is Scenario Map
- 10. Design Challenge Design way for Extraordinary to carry a drink.
- 11. Goal: To move from observations to shared insights about our user. Exercise 3: Empathy Map
- 12. DO? THINK? SAY? FEEL? What does the Extraordinary: Exercise 3: Empathy Map Get to know your extraordinary!
- 13. 1. Select a key user of the experience that the team has decided focus on - draw them in the center of the circle and label with name and role. 2. Diverge. Each team member writes one observation per post-it note and puts them into the appropriate section on the map. 3. Annotate unknowns, assumptions and questions. Build off of others team members post-it notes. Exercise 3: Empathy Map Better understanding a users needs
- 14. Exercise 3: Empathy Map Better understanding a users needs 2 Minute Team Playback One team member walk the rest of the team through the results.
- 16. Exercise 4: As-Is Scenario Map Goal: To visualize the users workflow and to identify pain points, confusion and opportunities.
- 17. Exercise 4: As-Is Scenario Map 1. Choose a scenario within the experience the team is focused on. 2. Begin by outlining the “Steps” section with one sticky note for each each step starting at “Just before” and ending at the “Final Stage.” 3. Fill in what the user is doing, thinking and feeling for each step in the scenario. * Remember one item per post-it note. Findings the opportunities in the user’s current experience: Understanding a users current situation
- 18. Exercise 4: As-Is Scenario Map Understanding a users current situation 2 Minute Team Playback One team member walk the rest of the team through the results.
- 19. Austin UXPA Q & A
Editor's Notes
- Thank you for the nice introduction. Good evening and Welcome to IBM. Before we jump right in I would like to thank tonights food sponsor - IBM Recruiting…1-2 minutes. Thank you for fueling our workshop with the great sandwiches and salads. I would also like to introduce the IBMers ->
- Everyone grab a post-it note and a sharpie. here’s our first exercise.
- Take 1 minute and design a vase. everyone have a post-it note and a sharpie….ok, you have 60 seconds….GO! Quack! What did you come up with??? let’s see a couple…yea that’s a vase and that is a vase. I bet they all look a lot like this one…but this is crap. Its crap because the problem was framed with the solution. Historically product companies and teams have been asked to create vases, framing the problem with the solution. Add a button for email, a page for a new feature. Ok, crumple them up and throw them on the floor. Yea, just toss them. Let’s see what happens when we reframe the problem and this time not include a solution.
- Grab another post-it note and this time take 1 minute and design a way for people to enjoy flowers in their homes. everyone ready?….ok 1 minute starts now. TIMES UP - what did you come up with. Nice, i like that…All of our ideas immediately diverged and we got lots of really great ideas and even a few wild ideas. That is the core of Design Thinking.
- Design Thinking is an relentlessly iterative human center methodology that is built on a “fail-fast, learn fast” foundation. The Design Thinking framework has been practiced for 25 yrs at firms like Frog, IDEO and taught at the Standford D-School. At IBM we adapted this framework by adding ->
- -> the 3 core practices of Hills, Playback and Sponsor Users. These core practices solve many of IBM’s unique situations such as extremely scale within our own organization and within our clients organizations, massive legacy software, globally located teams, fast delivery cycles and highly technical complex problems.
- Hills - Hills frame releases around users rather than features. They are stated as an aspirational statement that the team works to take. A couple of weeks ago I was helping facilitate a Hills workshop where I helped three uniquely different product teams come together and create a shared path forward all focused on the users. Sponsor Users - are select clients who work alongside the product team. They bridge the gap between a persona and true intrinsic user empathy. As these relationships deepen the team often gain deeper insights then possible in user interviews or lab testing. They ensure that we deliver for our users because we are bringing them along during the release. Playbacks - happen at iconic milestones along the product release cycle, they ensure that the team, stakeholders and clients stay aligned to the mission throughout the release…for example tonight each team will have a playback at the end of each exercises to make sure the team has an aligned view. The one thing all three of the Core practices have is the ->
- USER. That’s huge for us here at IBM and in any large enterprise. For tonight we will be using just two of the methods within the Design Thinking framework to help us understanding the User. ->
- -> the Understanding Phase. We will be creating a Empathy Map and As-Is Scenario Map. Normally for a Workshop the team would bring in primary and secondary research to build off of but this evening we have given you ahead start. Each team has a very special Guest user to get to know. Since we only have 1 hour we will be using a design challenge but we won’t actually start designing anything. Tonights design challenge is to ->
- -> design a drink carrier for an Extraordinary. An Extraordinary is a larger than life character with Extraordinary needs. Such as a robot, a fairy, a giant, evil genius…you get the idea. We are really going to focus on becoming empathic with our user and making sure our team is aligned. So lets create some empathy for our Extraordinary by creating an ->
- -> Empathy Map An Empathy Map, helps a cross-functional teams - product owners, engineers, designers, etc - focus on the most important element of any product the people. An Empathy map rapidly aligns the team to the users problems and puts them in the shoes of the user by revealing the “why” behind the users actions, choices and decisions. By doing this exercise as a team the users situation and pain points are internalized in way that listening to a report readout can’t.
- To create an Empathy Map the team will start off by diverging individually - this part of the exercise should be silent - remember more writing than talking and more drawing than writing. Use a new post-it note to capture each thought, action, word or feeling the Extraordinary might have, the wilder the better. Post them into the corresponding area, as you come up with them. That way others can build off your ideas. Any questions?
- Ok, as you came in tonight you were assigned to either Team (point to each space) 1, 2, 3, 4, 5, 6, 7, or 8. In each team space you will find a set of pictures describing the Extraordinary, a template of the Empathy Map, lots of post-it notes and sharpies. Please keep in mind that the Sharpies aren’t to be used on the dry erase surfaces. Facilitators will be coming around to answer questions…Ok - ya’ll have you 12 minutes to work.
- Ok, time to do your team playback. One person will walk the rest of the team through the empathy map, address any questions or concerns. Time permitting - Ask a team to do their playback for the entire room. What did ya think? Did the team align on what the users problems are, do you all have empathy for your Extraordinary? Questions? Ok,
- we have to keep moving….
- Now we are going to build off the Empathy we just gained and create an As-Is Scenario Map is to identify opportunities, pain points, team confusion about the current state of the users experience and most importantly keep the team aligned.
- An As-Is Scenario Map represents the current steps in a specific user situation. Begin by selecting one of the pictures of your extraordinary and focus on that situation. List out each of the steps the user takes starting at slightly before the picture until slightly after. Write each steps on a individual post-it notes and placing on the template, it is alright if some of the steps do not involve your product. Once you’ve listed out the steps you can start adding post-it notes that reflect what the user is doing, thinking, feeling under each of the steps. Any questions? Facilitators will be coming around to answer questions…Ok - ya’ll have ####### minutes to work.
- Ok, time to do your team playback. One person walk the rest of the team through the As-Is Scenario Map, address any questions or concerns. Time permitting - Ask a team to do their playback for the entire room. What did ya think? Did the teams align on what the users problems are? Questions? The framework has many methods to handle the next steps depending on the teams alignment and needs. Methods like the To-Be Scenario map that map out the ideal user situation help propel the team into writing Hills.