Intro Names and 1 artistic or cultural thing you noticed on the way to this course?
Find a “cool” professor willing to give you independent study units
Summary will be sent out in private Contact List spreadsheet
Private contact list distributed via email, please make sure it’s up to date
Results from class dump
Print me as a cheat sheet
Print me as a cheat sheet
Print me as a cheat sheet
Print me as a cheat sheet
Print me as a cheat sheet
You should be familiar with the empathy map by now
the first way i try to break things down is into spectra - helps you identify themes across users and solutions and call out metrics you might use to make design decisions the way i might try to understand my map /culture/art interviews: speed, franticness, emotional, social, routine
the first way i try to break things down is into spectra - helps you identify themes across users and solutions and call out metrics you might use to make design decisions the way i might try to understand my map /culture/art interviews: speed, franticness, emotional, social, routine
For example, think of people that have hectic lives and are sleeping in a different place every night – what are the reasons behind that? you’ve just found something that a homeless person, businessman, and prostitute have in common. it’s finding links like those and asking questions that no one has asked before that gets you to exciting insights.
How does the safety of use of a map or a artistic cultural experience?
How do the affordances of public art change things?
Print me as a cheat sheet
Print me as a cheat sheet
Print me as a cheat sheet
Print me as a cheat sheet
Print me as a cheat sheet
Here is an example process of how you might get to a POV. This can be used in conjunction with (to tee up) the Path to POV Activity.
Don’t necessarily take 5 minutes to demonstrate Space Saturation—this is specific for the in-class Path to POV activity. But this is the moment where you quickly demonstrate Space Saturation. Have some pre-printed pictures of the Empathy stages of the Next Gen workforce project ready to post on a rolling whiteboard. Briefly tell each user’s story, and put quotes up on post-its that you want to remember.
Next step is to synthesize some of the data to reveal needs and insights.
This is the tee up to demonstrate three types of synthesis modes. These are by no means exhaustive, but are three that might be useful to define a POV.
Demonstrate what a 2x2 might look like in the context of the NextGen Workforce. See ‘Path to POV Demo’ notes page for ideas.
Demonstrate what a Journey/Process Map might look like in the context of the NextGen Workforce. See ‘Path to POV Demo’ notes page for ideas.
Demonstrate what user grouping might look like in the context of the NextGen Workforce. See ‘Path to POV Demo’ notes page for ideas.
During Synthesis, it is up to the design team to pick what methods to try. I might first try 2x2 and then a Journey/Process map…
…or user grouping followed by laddering….it doesn’t matter. The important thing is for the team to be aware of their process and for the facilitator to move onto another method when the need + insight finding has become dry.
This might be used as a way to get a group brain dump of all the users, needs and insights they have uncovered. Demonstrate what this might look like.
Why can’t a need be a solution? Well, try to ideate and innovate on needs that are solutions. For example, Grover needs a job that starts at 10:30am. Ok, so you make his job start at 10:30am. What’s so innovative about that? Too obvious.
How most people frame their problems Usually only include a statement of user and need. User - usually a general and analytical statement Need - usually stated as a solution
give your project an anchor
we give you a starting point
it’s your job to turn that into a vector
give your project an anchor – we call this a POV
and, if found to be lacking, it has the ability to be re-shaped
there’s a danger in being too vague – you don’t to throw your specific insights out the window.
say through your needfinding, you've discovered that your user has a terrible mouse problem. they're everywhere, and her mousetraps just aren't working, for whatever reason. you're super proud of yourself for identifying this need, and you might say that your POV is that sue needs a better mousetrap - or if we're being careful to avoid using nouns, as you should, sue needs a better way to deal with her mouse problem.
sure that's ok.. but does it give you enough information? how will you know you've hit on something great? how will you start coming up with ideas?
point is, there isn't much here to work with. "better" isn't exactly the most meaningful, generative word.
what if.... you dug a bit deeper, found a bit more behind the mouse problem – your user’s values, wishes, behaviors… you tried to design the most humane mousetrap? the greenest? the fastest? the easiest to use? the cheapest? the most beautiful? one made entirely of tinkertoys? a child-safe mousetrap?
each of these falls under the "better" category but they're all so much juicier - much more inspiring – they give you an anchor, and a nudge in the right direction
the best way i've found to keep myself on track is another acronym: Priorities Objectives Vision
the best way i've found to keep myself on track is another acronym: Priorities Objectives Vision
the best way i've found to keep myself on track is another acronym: Priorities Objectives Vision
the best way i've found to keep myself on track is another acronym: Priorities Objectives Vision
so, using our mousetrap example, we might say user: sue need: a better way to take care of her mouse problem insight: she feels terrible about hurting them but really wants them gone