DESIGN THINKING

COURSE DESCRIPTION
Agile methods emphasize flexibility and adaptability, and the Agile
framework lends itself well to projects where requirements and solutions
evolve with time. Scrum, with its inherent simplicity and lightweight
processes, is the most popular way of introducing Agility to a project. 
 COURSE OUTCOME
COURSE OUTCOMES
 On completion of this course, the students shall be able to

CO1 Explain how IBM Design Thinking works and using

loop Model to understand present and envision
future 
 COURSE OBJECTIVE
Describe the importance of Design Thinking and Use of IBM
Design Thinking Framework.

Understand concept of History of Design Thinking

 What is Design Thinking
• Design Thinking is an iterative process in which we seek to
• understand the user
• challenge assumptions
• redefine problems
in an attempt to
• identify alternative strategies and solutions that might not be instantly
apparent with our initial level of understanding.
• At the same time, Design Thinking provides a solution-based
approach to solving problems. It is a way of thinking and working as
well as a collection of hands-on methods.
• the more I pondered the nature of design and reflected on my recent
encounters with engineers, business people and others who blindly solved
the problems they thought they were facing without question or further
study, I realized that these people could benefit from a good dose of design
thinking.[… ]
• Most important of all, is that the process is iterative and expansive.
Designers resist the temptation to jump immediately to a solution to the
stated problem. Instead, they first spend time determining what the basic,
fundamental (root) issue is that needs to be addressed. They don't try to
search for a solution until they have determined the real problem, and even
then, instead of solving that problem, they stop to consider a wide range of
potential solutions. Only then will they finally converge upon their proposal.
This process is called "Design Thinking.
Don Norman
FIG 1
FIG 2
Some authors are less optimistic when considering the
amount of iteration r e q u i r e d
FIG 3
IMPORTANCE OF DESIGN THINKING
 Empathiz
e
• “deep understanding of the problems and realities of the people you are
designing for”
• 3 steps
• Observe
• How users interact with their environment.
• Capture quotes, behaviors and other notes that reflect their experience.
• Notice what they think, feel, need
• Engage
• Interviews scheduled or ad-hoc
• Learn how to ask the right questions
• Immerse
• Find ways “to get into the user’s shoes”
• Best way to understand the users’ needs
 Empathize tools
• Assume a beginner’s mindset
• Ask What-How-Why
• Ask the 5 whys
• Empathy map
• Conduct interviews with empathy
• Build empathy with analogies
• Use photo and video user-based studies
• Use personal photo and video journals
• Engage with extreme users
• Story share-and-capture
• Bodystorm
• Create journey maps
 Empathize - Beginner’s mindset
• Forget your assumptions and personal beliefs
• Misconceptions or stereotypes limit the amount of real empathy you
can build.
• A beginner’s mindset allows you
• to put aside biases and approach
• Design with fresh eyes
• What you should do
• Don’t judge
• Question everything
• Be truly curious
• Find patterns
• Listen without thinking how you’re going to respond
 Empathize – Ask What – How - Why
• Tool to help you better observe
• Especially good for analysing photos
• What you should do for a specific observation
• Divide a sheet into 3 parts – What / How / Why
• What = write what you observe the user is doing without making assumptions
• How = understand what the user is doing. Is it positive or negative, does it
require effort? Use plenty of adjectives
• Why = now you have to interpret; guess motivations and emotions, make
assumptions that you have to test with users later
 Empathize – Ask the 5 whys
• Repeating the Why question 5 times to identify the root cause of a
problem
• Some useful rules
• Write down the problem and make sure that all people understand it.
• Distinguish causes from symptoms.
• Pay attention to the logic of cause-and-effect relationship.
• Assess the process, not people.
• Never leave "human error", "worker's inattention", "blame John" etc., as the
root cause.
• When you form the answer for question "Why" - it should happen from the
customer's point of view.
 Empathize – Conduct interviews with
empathy
• Ask why.
• Never say “usually” when asking a question.
• Encourage stories
• Look for inconsistencies.
• Pay attention to nonverbal cues.
• Don’t be afraid of silence.
• Ask questions neutrally and don’t suggest answers.
 Empathize - Build empathy with analogies
• Use analogies to gain a fresh way of looking at an environment,
and in instances where direct observation is hard to achieve.
• analogies allow us to express our ideas or to explain complex
matters in an
• understandable and motivating way.
• Start by identifying the aspects of a situation that are most
important, interesting, or problematic.
• Find other experiences that contain some of these aspects — it
will help you gain a better understanding of your users’
problems, and it will also spark new ideas to improve their
experiences.
• Create an inspiration space for analogies. You can do so by
pinning photos and anecdotes of the analogous experiences
you have found.
 Empathize - Use photo and video user-based
studies
• Use video recordings of users performing their regular activities
• Try to make the study as casual as possible so that the user doesn’t
feel any pressure
• Use different techniques like how-what-why to examine the videos or
photos or frames taken from the videos
 Empathize - Engage with extreme users
• Determine who’s extreme.
• https://www.youtube.com/watch?v=5R3pKV9ucBc&t=607s
• Engage.
• Observe and interview extreme users just like other folks. Look for work-
arounds (or other extreme behaviors) to spark inspiration and uncover
insights.
• Look at the extreme in all of us.
• Look to extreme users to spur wild ideas. Then narrow in on what resonates
with the primary users that you’re designing for.
 Empathize - Bodystorm
• Bodystorming is a unique method that spans empathy work, ideation, and
prototyping.
• technique of physically experiencing a situation to derive new ideas.
• requires setting up an experience - complete with necessary artifacts and
people - and physically “testing” it.
• can include physically changing your space during ideation.
• you're focused on here is the way you interact with your environment and
the choices you make while in it.
• Example: when thinking about a product for blind people try to actually
experiment not using your eyes during an experiment and try to see what
you can achieve and what are your needs
 Empathize - Create journey maps
• Visual representation of the process a customer or prospect goes
through to achieve a goal with your company/products
• Identity the customer’s needs and pain points
• Steps:
• Set clear objectives for the map.
• Profile your personas and define their goals.
• List out all the touchpoints (places in the app/site where you can
interact with
the customer)
• Identify the elements you want your map to show.
• Take the customer journey yourself.
• Make necessary changes.
 References
[1]Turk, Daniel, and Robert France. "Assumptions Underlying Agile Software Development Processes." Journal of  Software and Systems Modeling 17 (2003): 19-25. Print.
 
[2]Heeager, Lise Tordrup . "INTRODUCING AGILE PRACTICES IN A DOCUMENTATION-DRIVEN SOFTWARE DEVELOPMENT PRACTICE: A CASE STUDY." Journal of Information Technology Case and Application
Research 14.1 (2012): 3-24. Print.

[3]Abdelshafi, Ibrahim. "Primavera Gets Agile: A Successful Transition to Agile Develo." IEEE Software 22.3 (2005): 36-42. Print.
https://youtu.be/WjwEh15M5Rw