Search

d.Maps: Design Cultural Maps Lab 1

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    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

    Favorites, Groups & Events

    d.Maps: Design Cultural Maps Lab 1 - Presentation Transcript

    1. d.Maps: Design Cultural Maps Lab 1 [email_address]
    2. House Keeping
      • Units
      • Skillsets
      • Logistics
      • Equipment Access
      • Tech- Blog and Backlight
    3. Units
      • Contact [email_address] if you need units under another department
    4. Skillsets
      • Post Its Exercise
    5. Logistics
      • We may need to meet in d.school on Monday depending on class size
      • Stay tuned for d.school handout with guidelines etc.
    6. Tech
      • Blog login culturalmaps.org/wp-admin/
      • Username/Password via email
      • Sign up for Backlight.org ASAP using primary Stanford email address listed on our contact list
    7. Equipment Access
      • You can check out equipment from Bruce Boyd at the d.school anytime you can catch him in addition to Meyer
      • Depending on our needs we may have a dedicated set of equipment
      • Submit any wishes to Enrique asap!
    8.  
    9.  
    10.  
    11. Synthesize Empathy Learnings
      • 3 Biggest Learnings
      • Quotes & Defining Words
      • Actions & Behaviors
      • Thoughts & Beliefs
    12.  
    13.  
    14.  
    15.  
    16.  
    17.  
    18. Synthesis Methods Summary
      • 2x2
      • Empathy Map
      • Grouping
      • Journey map
      • Why laddering
    19. Synthesis: Methods
    20. Synthesis: Methods speed: slow fast
    21. Synthesis: Methods franticness: calm totally frazzled
    22. Synthesis: Methods emotion: stoic embroiled
    23. Synthesis: Methods social: anti- hyper-
    24. Synthesis: Methods routine: consistent dynamic
    25. Synthesis: Methods Safety: Safe Risk
    26. Synthesis: Methods Public Art: Non-Interactive Interactive
    27. Synthesis: Next Step?
      • Once you've organized your information, what's the next step?
    28. DEFINE
    29.  
    30. What is DEFINE?
      • The goal of this mode is to come up with at least one actionable problem statement. This actionable problem statement (often referred to as a POV) is the guiding statement that focuses on the insights that you uncovered from real users.
    31. Goal of DEFINE
      • To expose new innovation opportunities by looking at problems differently
      • To guide innovation efforts
      • To help a team confirm that what they've identified is something worth working on
    32.  
    33.  
    34.  
    35.  
    36.  
    37. Define Methods Summary
      • Metaphor
      • Mad lib
      • Personal ads
    38.  
    39. Let’s go through an example… REDEFINE THE MAP EXPERIENCE FOR THE NEXT GENERATION
    40.  
    41.  
    42.  
    43. SYNTHESIS METHODS Tools to draw out NEEDS, INSIGHTS and SURPRISES
      • Label Axes
      • Try Placing Elements w/ Post-its
      • See what insights, needs, surprises are discovered
      • Repeat!
      SYNTHESIS METHODS
      • Pick an artifact/process
      • Make a timeline of it’s life
      • See what needs, insights, are discovered
      • Repeat!
      SYNTHESIS METHODS
      • Objective: To find patterns
      • Group users in as many ways as you can
      • Keep a list of the groupings (these are your user groups)
      • See what needs, insights, surprises are discovered
      SYNTHESIS METHODS
    47.  
    48.  
    49.  
    50.  
    51. Grover needs NOUN a job that starts at 10:30am. to be allowed flexibility. VERB ✔
    52. User + Need + Insight Empathetic language Deep! Emotions! Surprise! Only know from observations/conversations
    53. Why POV?
      • Provide focus/Frame the problem
      • Inspire your team
      • Provide a reference for evaluating competing ideas
      • Empower your team to make decisions independently in parallel
      • Fuel brainstorms by suggesting “how might we” problem statements
      • Capture the hearts and minds of people you meet
      • Save you from the impossible task of developing concepts that are all things to all people
      • Be something you revisit and reformulate as you learn by doing
    54. Define
      • distill it even further
    55. Define
      • distill it even further
    56. Define
      • distill it even further
    57. Define
      • distill it even further
      • (we call this a POV)
    58. Define
      • What do you think makes for a good point of view?
    59. Define
      • What do you think makes for a good point of view?
      • generative
    60. Define
      • What do you think makes for a good point of view?
      • generative
      • suggests evaluation criteria
    61. Define
      • What do you think makes for a good point of view?
      • generative
      • suggests evaluation criteria
      • testable (and reshapable)
    62. Define
      • What do you think makes for a good point of view?
      • generative
      • suggests evaluation criteria
      • testable (and reshapable)
      • doesn't imply specific solution - PRESERVES AMBIGUITY
    63. Define
      • What do you think makes for a good point of view?
      • generative
      • suggests evaluation criteria
      • testable (and reshapable)
      • doesn't imply specific solution - PRESERVES AMBIGUITY
      • but narrow enough that it focuses your project
    64. Define: Mousetrap
    65. Define: Mousetrap Sue needs a better way to deal with her mouse problem.
    66. Define: Mousetrap Sue needs a better way to deal with her mouse problem.
    67. Define: Mousetrap What if…?
    68. Define: Mousetrap Sue needs a better way to deal with her mouse problem.
    69. Define P O V
    70. Define Priorities O V
    71. Define Priorities Objectives V
    72. Define Priorities Objectives Vision
    73. Define: Quick Formula USER + NEED + INSIGHT
    74. Define: Activity Time!!
    75. EXPERMENT 2- STEP BY STEP
      • Empathy : Observe and interview follow ups from Experiment 1
        • Refine your observation and question strategy
        • Try different perspectives and roles
      • Define : Synthesize data from empathy work and create POV(s)
        • Use new synthesize and define techniques covered in this presentation
      • Ideate : Brainstorm ways to solve the needs of your POV(s)
        • Share your POV(s) with someone outside of the seminar
      • Prototype : Create at least 1 non-digital prototype
        • Feel free to use any material at the d.school!
        • I’ll be prototyping on Sunday night
      • Test: Show your prototype to your POV(s)
        • Try to iterate and be prepared to discuss in our seminar
        • * Don’t worry if you’re unsure how to brainstorm or prototype, we’ll cover this in our next seminar
        • *Document the process by uploading any inspirations to culturalmaps.backlight.org in the Experiment 2 Gallery
    76. Credits
      • Material adapted from dschool.stanford.edu
      • Special thanks to Carly Geehr, Rich Crandell, Susie Wise, Erica Estrada for allowing shamelessly stolen inspiration
    SlideShare Zeitgeist 2009

    + d.Maps: Design Cultural Mapsd.Maps: Design Cultural Maps Nominate

    custom

    236 views, 0 favs, 1 embeds more stats

    d.Maps: Design Cultural Maps Lab 1

    *Material ada more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 236
      • 229 on SlideShare
      • 7 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 10
    Most viewed embeds
    • 7 views on http://culturalmaps.org

    more

    All embeds
    • 7 views on http://culturalmaps.org

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags

    -->
    Search
    RSS Feed
    What's new?

    © 2009 SlideShare Inc. All Rights Reserved