Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

EUVI > Design Thinking > Flashcards

Design Thinking Flashcards

1
Q

What is Design Thinking?

A

An iterative process in which we seek to understand the user, challenge assumptions, and redefine problems to identify alternative strategies and solutions that might not be instantly apparent with our initial level of understanding

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Motivation behind Design Thinking

A
  • Knowing deeply your user
  • By observing and developing empathy with the user
  • Through the process of questioning
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Design Thinking Phases

A
  • Empathise – with your users
  • Define – your users’ needs, their problem, and your insights
  • Ideate – by challenging assumptions and creating ideas for innovative solutions
  • Prototype – to start creating solutions
  • Test – solutions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Design Thinking Phases - Empathise

A
  • Gain an empathic understanding of the problem (observing and interacting with people to understand the problem).
  • Depending on time constraints, a considerable amount of time should be spent in this phase
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Design Thinking Phases - Define (the problem)

A
  • Gather the data collected from previous phase
  • Aim at defining the problem statement
  • Team should produce ideas for the functions that will solve the problem
  • Try to respond to questions framed like: “how could/might we …?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Design Thinking Phases - Ideate

A
  • Start to generate ideas
  • Summing up: you started by understanding users and their needs in Empathise Phase, then you gathered, analysed the data in Define Phase, ended up with a human-centred problem definition
  • Now it is time to think out of the box!
    Techniques: Brainstorm, Brainwrite, Worst Possible Idea, SCAMPER, etc.
  • Get the maximum of ideas at this stage!
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Design Thinking Phases - Prototype

A
  • Construct a number of cheap versions of the product, or of some features of the product in order to investigate the solutions achieved.
  • Each solution should be tested against the users’ experience and needs in order to be accepted, revised or rejected.
  • At the end of this stage, the team should have a clear idea of how users will behave when interacting with the product
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Design Thinking Phases - Test

A
  • Test the complete product achieved with the best solutions identified in previous phases
  • This is the final phase but … it is an iterative process so some results may lead to redefinition of the problem a let’s start again
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Emphasise with your users

A

Emerge in users’ environments
Adopt a beginner’s mindset: leave all your assumptions at home ☺

Ask 3 questions: what? how? Why?
* What?: details of what happened during observations
* How?: how the person is doing what she is doing
* Why? Try to figure out the motivations and emotions with the users
* Methods: Photo and Video User observations, Personal Photo and Video Journals, Interviews, Share Stories, Bodystorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Define the Problem and Interpret the Results

A

Definition of a meaningful and actionable problem statement

Analysis and synthesis of observations

Analysis: breaking down complex concepts and problems into smaller, easier-to-understand constituents.

Synthesis: creatively piecing the puzzle together to form whole ideas,
when we organise, interpret, and make sense of the data we have gathered to create a problem statement.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Why is a problem statement important?

A

Because it will guide you and your team, and provides a focus on the specific needs that you have uncovered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What makes a good Problem Statement?

A
  • Human-centered: problem statement should be about the people the team is trying to help, rather than focusing on technology, monetary returns or product specifications.
  • General for creative freedom: Should not focus on a particular way of implementing, preventing the achievement of good solutions
  • Narrow enough to be manageable: should have enough constraints to be manageable and achievable (not good example: Irradicate poverty!)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

How to? [Problem Statement] - Space saturate and Affinity Diagrams

A

You space saturate to help you unpack thoughts and experiences into tangible and visual pieces of information that you surround yourself with to inform and inspire the design team.
You group these findings to explore what themes and patterns emerge and strive to move toward identifying meaningful needs of people and insights that will inform your design solutions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How to? [Problem Statement] - Empathy Mapping

A

An empathy map is a collaborative visualization used to articulate what we know about a particular type of user.

It externalizes knowledge about users in order to
1) create a shared understanding of user needs, and
2) aid in decision making.

4 quadrants:

Says – contains what the user says out loud in an interview or some other study, e.g.: “I want something reliable”, “I don’t understand what to do from here”

Thinks – captures what the user is thinking throughout the experience, e.g.: “This is really annoying”, “Am I dumb for not understanding this?”

Does – encloses the actions the user takes, e.g.: Refreshes page several times

Feels – portrays the user’s emotional state, e.g.: confused: too many contradictory prices, worried: they are doing something wrong

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How to? [Problem Statement] - Point of View

A

A Point Of view (POV) is a meaningful and actionable problem statement, which will allow you to ideate in a goal-oriented manner. Your POV captures your design vision by defining the RIGHT challenge to address in the ideation sessions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How to? [Problem Statement] - How might we? (HMW)

A
  • After establishing the POV it is important to try to generate new ideas
  • How might we (HMW) questions are questions that have the potential to spark ideation sessions.

e.g.
How might we make trip planning more collaborative
How might we help users inform others about trip details

17
Q

How to? [Problem Statement] - Why-How Laddering - WHY

A

Generally, asking ‘why’ yields more abstract statements and asking ‘how’ yields specific statements. Often abstract statements are more meaningful but not as directly actionable, and the opposite is true of more specific statements.

That is why you ask ‘why?’ often during interviews – in order to get toward more meaningful feelings from users rather than specific likes and dislikes, and surface layer answers. Outside an interview, when you think about the needs of someone, you can use why-how laddering to flesh out a number of needs and find a middle stratum of needs that are both meaningful and actionable.

18
Q

How to? [Problem Statement] - Why-How Laddering - HOW

A

When considering the needs of your user, start with a meaningful one. Write that need on the board and then ladder up from there by asking ‘why’. Ask why your user would have that need and phrase the answer as a need.

For example, “Why would she need to see a link between a product and the natural process that created it’? Because she needs to have confidence that something will not harm her health by understanding where it came from’.” Combine your observations and interviews with your intuition to identify that need.

Then take that more abstract need and ask why again, to create another need. Write each on the board above the former. At a certain point you will reach a very abstract need, common to just about everyone, such as the ‘need to be healthy’. This is the top of that need hierarchy branch. You can also ask ‘how’ to develop more specific needs.

Climb up (‘why?’) and down (how?) in branches to flesh out a set of needs for your user. You might come up to one need and then come back down.

In the previous example, you climbed up to the ‘need to understand where a product came from’. Then ask ‘how’ to identify the ‘need to participate in the process of creating a product’. There will also be multiple answers to your ‘whys’ and ‘hows’ – branch out and write those down. The result (after some editing and refining) is a needs
hierarchy that paints a full picture of your user or composite user.

19
Q

Ideate

A

“Ideation is the mode of the design process in which you concentrate on idea generation. Mentally it represents a process of “going wide” in terms of concepts and outcomes. Ideation provides both the fuel and also the source material for building prototypes and getting innovative solutions into the hands of your users.”

Use creativity and innovation to develop solution.

20
Q

Aim of Ideate

A
  • Ask the right questions and innovate.
  • Step beyond the obvious solutions and therefore increase the innovation potential of your solution.
  • Bring together perspectives and strengths of team members.
  • Uncover unexpected areas of innovation.
  • Create volume and variety in your innovation options.
  • Get obvious solutions out of your heads and drive your team beyond them.
21
Q

Ideation - Brainstorm

A

Generate many ideas by leveraging the collective thinking of the group, by engaging with each other, listening, and building on other ideas

Rules:
* Set a time limit
* Start with a problem statement, point of view, possible questions, a plan, or a goal and stay focused on the topic
* Stay on topic
* Defer judgement or criticism, including non-verbal
* Encourage weird, wacky and wild ideas
* Aim for quantity
* Build on each others’ ideas
* Be visual
* One topic at a time

22
Q

Methods to Select Ideas

A
  • Post-it Voting or Dot Voting
  • Four Categories Method
  • Bingo Selection
  • Idea Affinity Maps
  • Now Wow How Matrix
  • Six Thinking Hats
  • Lean Startup Machine Idea Validation Board
  • Idea Selection Criteria
23
Q

Methods to Select Ideas - Post-it Voting or Dot Voting

A

Each one places a post-it or a dot on its preferred idea

24
Q

Methods to Select Ideas - Four Categories Method

A

Divide ideas into 4 categories:
- Most Rational
- Most Delightful
- Darling
- Long Shot.

  • Then have the team select a few ideas from each category.
  • This method ensures that you cover more ground and include different types of ideas.
25
Q

Prototype

A

Prototyping offers designers the opportunity to bring their ideas to life, test the practicability of the current design, and to potentially investigate how a sample of users think and feel about a product.

The results generated from these tests are then used to redefine one or more of the problems established in the earlier phases of the project, and to build a more robust understanding of the problems users may face when interacting with the product in the intended environment.

26
Q

Low-Fidelity Prototypes

A

Basic model of the product being tested, may be incomplete
* May be developed in wood, paper, or metal for a plastic product.
* Can either be models that are cheaply and easily made, or simply recounts or visualisations of them.

Examples:
* Storyboarding
* Sketching
* Card Sorting
* Wizard of Oz

27
Q

Low-Fidelity Prototypes - Pros

A
  • Quick and Unexpensive
  • Allows fast changes and rapid new iterations
  • Throw-away
  • With minimum time, it is possible to gain a good understanding of the product acceptance
28
Q

Low-Fidelity Prototypes - Cons

A
  • Inherent lack of realism
  • Depending on your product, the production of low-fi prototypes may not be appropriate for your intended users.
  • Such prototypes often remove control from the user, as they generally have to interact in basic ways or simply inform an evaluator.
29
Q

High-Fidelity Prototypes

A

High-fidelity prototypes are prototypes that look and operate closer to the finished product.

For example, a 3D plastic model with movable parts (allowing users to manipulate and interact with a device in the same manner as the final design) is high-fi in comparison to, say, a wooden block

30
Q

High-Fidelity Prototypes - Pros

A
  • Engaging: the stakeholders can instantly see their vision realised.
  • User testing involving high-fi prototypes will allow the evaluators to gather information with a high level of validity and applicability
31
Q

High-Fidelity Prototypes - Cons

A
  • Take much longer to be produced than low-fi
  • When testing, may lead users to focus on aesthetics rather than functionality
  • May oblige many hours to be produced and then changes are needed
32
Q

Prototypes Guidelines

A
  • Just start prototyping
  • Don’t spend too much time
  • Remember what you are testing
  • Aim the prototype at the user
33
Q

Test

A
  • Testing can be undertaken throughout the progress of a Design Thinking project
  • Most usual attached with Prototyping stage.
  • Testing, in Design Thinking, involves generating user feedback as related to the prototypes you have developed, as well as gaining a deeper understanding of your users.
  • When undertaken correctly, the Testing stage of the project can often feed into most stages of the Design Thinking process: it allows you to Empathise and gain a better understanding of your users; it may lead to insights that change the way you Define your problem statement; it may generate new ideas in the Ideation stage; and finally, it might lead to an iteration of your Prototype.
34
Q

Guidelines of Planning a Test

A
  • Let users compare alternatives: produce multiple prototypes and vary some functionalities to allow the choice of the users
  • Show, don’t tell
  • Ask users to talk through their experience
  • Observe
  • Ask follow up questions
35
Q

End Goal

A
  • Desirability focus on humans: centre the design in the user. It
    must fulfil his needs, emotions and behaviours.
  • Feasibility focus on technology: is the design technically possible,
    but try not to restrain by technology impositions
  • Viability: is there a business model behind your solution?

EUVI (13 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions