Share
Embed
How To Start Thinking Like A Designer
Presentation for Brigham & Women's Primary Care Residency Workshop on Design Thinking
With thanks to Mad*Pow colleagues Dan Berlin, Adam Connor, and Mike Hawley for sharing supporting materials for this presentation
Jamie Thomson Pate
November 07, 2014
Transcript
55 slides
-
How To Start Thinking Like a Designer Brigham & Women’s
Primary Care Residency Workshop #1 Presented by Jamie Thomson, Senior Experience Designer, Mad*Pow [email protected] / @uxjam Nov 7, 2014 With many tipped hats to Dan Berlin, Adam Connor, Mike Hawley, and AC4D -
Wikipedia What is Design Thinking? PART 1 How do I
get started? PART 2 What is design research? PART 3 -
Design Thinking is an abstraction of the process that designers
use to solve problems -
Synthesize Create / Refine Observe & Analyze Goal / Ideal
State TODAY’S AGENDA -
Analysis The process of breaking down a complex topic or
substance into smaller parts to gain a better understanding of it. Observation The active acquisition of information from a primary source. Synthesis The process of making sense of data and insights through categorization, comparison, pattern recognition, and pruning. Wikipedia -
Design Thinking is also a mindset – a way of
approaching problems -
Optimism Seeing potential for what might be, rather than constraints
of what is. Iteration The act of repeating a process with the aim of approaching a desired goal, target or result. Empathy Feeling what someone else feels, in order to relate to their behavior and attitudes. Wikipedia; Austin Center for Design -
Empathy in design focuses on the user as a person,
not just a consumer.” “ Ralph Caplan -
How do I get started? Know thyself & know thy
user PART 2 -
Sometimes the problems you’re asked to solve aren’t the ones
you need to solve. -
There is surely nothing quite so useless as doing with
great efficiency that which should not be done at all.” “ Peter Drucker -
Tips for “Crispifying” the Problem ê Talk to everyone you
can (within reason) – users, their family & friends, your executive stakeholders, thoughtleaders, admins, customer support staff… ê Call out any assumptions or “sacred cows” within your organization. ê Be honest. Take a careful look in the mirror at your organization, from the inside, and consider what our goals are for your product or service at large. Some of them might sound less than altruistic, but it’s important to know where you stand. ê Solidify your findings into opportunities, objectives, and themes. Be specific about your scope. Challenges that are too vague can lead to stagnation in coming up with ideas or not enough criteria to determine how to proceed. ê Context is king. Get to know the people, places, and things that relate to your creation by visually mapping the ecosystem. -
In order to utilize and reference findings throughout the design
process, various foundational elements are often created. -
Principles Desired qualities or characteristics of the final creation. Ex:
Decide for me but let me have the final say. Take your best guess and act rather than asking first. Too many choices and decisions make people unhappy. Just in case you get it wrong, allow for 'undo'. Goals Desired, measurable outcomes from someone interacting with the creation. Can be user oriented, business oriented, or both. Ex: Increase utilization of internal learning resources by 20% principle example from Android Design Principles -
Personas & Journey Models User archetypes that describe their average
behaviors, needs, goals, expectations, senses, knowledge, etc. Personas are snapshots, while journey models follow a user over a long period of time, through multiple scenarios. Journey models are often used to compare the present vs. ideal states. Ex: see next 2 slides Use Cases & Scenarios Describes a task or tightly linked set of tasks someone will accomplish by using your creation. Ex: Finding something to read/watch/etc. – How does a user find something to read appropriate to their current needs (topic, time available, learning style)? -
Contextual Model Visualization of people, places, things, forces, and relationships
that comprise the problem space and surround your future creation. Ex: two slides ahead – plus, you’ll create one soon! Interaction & Service Blueprints Detailed flow documentation of the specific systems, channels, touchpoints, interactions, and back-of-house processes in question. May document the current state, or depict the design of a future solution. Ex: see next slide -
Contextual Modeling Austin Center for Design Flow Model Cultural Model
Physical Model Artifact Model Sequence Model -
Synthesis requires deep, tacit understanding of the context of a
design opportunity.” “ Jon Kolko -
What is design research? Design thinking is based on observed
human needs, which are captured through research PART 3 -
What we made had to fit into the contours of
their lives, their emotional states, and their conversations…” “ Andrew Hinton -
What people say and what they do aren’t necessarily the
same (But there’s still a lot of value in talking with people) -
What someone actually does Discovered by: Observation What someone says
they do or think Discovered by: Interviews & Surveys What someone really thinks and feels Discovered by: Meaningful human connections and conversations -
Qualitative Used to gather deeper information on individuals’ thinking, feeling,
and motivations. Ex: Interviews, Focus Groups Quantitative Used to identify and measure patterns in thinking ad behavior among groups of people. Ex: Surveys, Data Mining -
Formative Interviews, ethnography, diary studies, surveys, participatory activities, collaging, card
sorts How far along are you? Summative Usability, ongoing online assessments, analytics, user community comments Evaluative Usability, A/B testing, eye tracking, surveys, desirability studies, tree tests -
What’s the difference? Incremental Usability Testing ê Small studies throughout
the product lifecycle ê Qualitative; 5-8 participants per demographic ê Learn user needs and expectations and use these to guide design ê “These are ideas for improving usability” Usability Validation for FDA Submission ê Fewer, larger studies closer to product launch ê Quantitative and qualitative; >30 participants ê Validate that the product is indeed usable for the target audience ê “This is usable” Feasibility Studies ê Small studies to determine potential usefulness and impact on health measures ê “This is an idea worth pursuing” Clinical Trials ê Statistically significant samples, rigorous randomization and blind/double-blind protocols ê “This is effective” -
Typical Usability Study Results Positive: Users were able to find
the “Buy Now” button. 3 out of 8 participants mentioned that the picture had no relevance to them. Consider: replacing this with an infographic or another picture that may draw in users. 6 out of 8 participants mentioned that the text in the buttons was hard to read. Consider: increasing the contrast of the text to ease readability. -
FINDING RECOMMENDATION Participants said that the text was hard to
read Increase the contrast of the text Participants were unable to locate the product; they said they expected it under Products & Services Move XYZ product to the Product & Services area Participants were unable to discern the top from the bottom of the vial Include a visual cue as to which is the top and bottom of the vial Participants were able to figure out how to use the insulin pump, but said that the instructions were very hard to follow Add detail throughout the instruction manual, including photos or diagrams Typical UX Research Results -
Tips for Interview Questions ê Avoid leading questions that limit
or hint at a desired answer: “Did you do this?” ê Ask open-ended questions starting with Who, What, When, Where, How and Why. ê Encourage people to talk more: “Tell me more about that…” ê Be quiet and listen. Let them do almost all of the talking. ê Resist the urge to come up with ideas on how to solve the problems. ê Consider asking how they think the problem might be solved. But don’t take it as a command; use it to dive deeper. -
Defining study goals Good Study Goals ê Learn stakeholder project
goals ê Understand users’ wants and needs for the interface ê Learn if users can perform business critical tasks on the interface ê Determine how users interact with the interface in a real-world setting Bad Study Goals ê Learn if users like the design’s colors (too specific) ê Learn about potential users (too vague) ê Understand how users expect a certain interaction to work (having users design) ê Determine how users think other people will use the interface (hearsay) -
Formalize the problem & study goals ê Problem: < people
with this behavior > < have this problem >. ê Objective: < brief description of what we’re looking to change >. ê Ideal State: We will know we’ve succeeded when < quantitative and/or qualitative metric >. ê Target Behaviors: < long list of all the potential behaviors that may be relevant to the problem you want to solve > ê Study Goals: We would like to … < learn / understand / determine > < something(s) >. questions based on worksheets from Dustin DiTommaso and bit.ly/ux-recipe -
Interview Questions < who / what / when / where
/ why / how … > ê What is the value to you (patient) of learning your medications? ê How can I know when you have truly absorbed and understood this information? ê What behavior or action do I want to happen? ê Where will this happen? -
Thanks for listening & participating! Keep in touch: @uxjam //
[email protected] // linkedin.com/in/jamiethomson