”SOLVING COMPLEX BUSINESS AND TECHNICAL CHALLENGES USING DESIGN

THINKING”

05. September 2013

Peter Weigt Manuel Zedel

INTRODUCTION

Manuel Zedel

Peter Weigt

ELEVATOR PITCH OF DESIGN THINKING

INTRODUCTION

“Design thinking is a human­centered approach to innovation

that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.”

—Tim Brown, president and CEO IDEO

©  SAP  2012    |    4  

DESIGN THINKING means…

…creating INNOVATION by combining diverse PEOPLE,

creative SPACE and an iterative APPROACH.

WHAT IS INNOVATION?

INTRODUCTION

©  SAP  2012    |    6  

INNOVATION Desirability + Feasibility + Viability.

DESIGN THINKING PIECES

INTRODUCTION

WHAT DOES IT NEED TO DO GOOD DESIGN THINKING?

©  SAP  2012    |    8  

IT`S ABOUT PEOPLE.

©  SAP  2012    |    9  

NO LONELY RESEARCHERS IN THEIR GARAGES.

©  SAP  2012    |    10  

INTERDISCIPLNARY TEAMS OF T-SHAPED PEOPLE.

©  SAP  2012    |    11  

INVEST IN TEAM-BUILDING This does not happen by itself.

DESIGN THINKING PIECES

INTRODUCTION

WHAT DOES IT NEED TO DO GOOD DESIGN THINKING?

©  SAP  2012    |    13  

…and the freedom to explore.

DESIGN THINKING PIECES

INTRODUCTION

WHAT DOES IT NEED TO DO GOOD DESIGN THINKING?

DESIGN THINKING APPROACH

DESIGN THINKING APPROACH

DESIGN THINKING APPROACH

Understand.

“Building something nobody wants is the ultimate form of waste.” – Eric Ries

©  SAP  2013    |    18  

DESIGN THINKING APPROACH

DESIGN THINKING APPROACH

Observe.

©  SAP  2013    |    20  

“A Developer needs to be curious and also develop empathy for

End Users ” – Hasso Plattner

©  SAP  2012    |    21  WATCH AND OBSERVE – Conduct Interviews

§  Look for details

§  Capture the atmosphere

§  Be curious and talk to people

§  Take photos and notes

§  Speculate: what if… ? §  Buy things, do things

§  Collect artifacts §  Write down your impressions §  Be polite and do not disturb §  Act as a guest §  ! ASK Open Ended Questions !

DESIGN THINKING APPROACH

©  SAP  2012    |    22  

Also look for extreme users.

DESIGN THINKING APPROACH

Point of View.

©  SAP  2012    |    24  WHY DEFINE POINT-OF-VIEW? ©  SAP  2013    |    24  

©  SAP  2012    |    25  

Address the right question …and create the right solution

REMINDER We still need to re-focus and make choices.

PROBLEM SPACE SOLUTION SPACE

©  SAP  2013    |    25  

DESIGN THINKING APPROACH

Ideate.

©  SAP  2012    |    27  WHY IDEATE?

©  SAP  2013    |    27  

©  SAP  2012    |    28  BRAINSTORMING RULES.

BUILD ON THE IDEAS OF OTHERS

FAIL  EARLY  AND  OFTEN  

THINK  USER-­‐CENTRIC  

DEFER  JUDGEMENT   STAY  FOCUSED  ON  TOPIC  

BE  VISUAL  

GO  FOR  QUANTITY  

ONE  CONVERSATION  AT  A  TIME  

GO  FOR  WILD  IDEAS  

DESIGN THINKING APPROACH

Prototype.

©  SAP  2012    |    30   WWHW  

What is a prototype?

§  Prototypes may show how something looks, feels, or works.

§  Prototypes make things tangible.

§  “Failure” of a prototype is simply a way of understanding and improving.

Why prototyping? §  Develop and iterate ideas.

§  Ensure early and regular feedback.

©  SAP  2013    |    30  

What is a prototype? Why protoyping?

The best way to experience an experience is to experience it...

TYPES OF PROTOTYPES

1.  Physical

2.  Paper (e.g. wireframes)

3.  Storyboards

4.  Acting

5.  Dark Horse Prototype

6.  Critical function prototype

7.  Experience

8.  Technical Prototypes (e.g. in software)

©  SAP  2013    |    31  

DESIGN THINKING APPROACH

Testing.

Why Test? •  To gather early feedback from users, stakeholders and experts,

to be able to iterate •  To learn about your ideas strengths and weaknesses •  To fail early

©  SAP  2013    |    33  

©  SAP  2012    |    34  

IMPLEMENTATION  

DESIGN THINKING MEETS IMPLEMENTATION

DT-PROTOTYPE

SPRINT

DAILY SCRUM

DELIVERABLES

SCOPE AGREEMENT

PROJECT SETUP SAP + CUSTOMER

BACKLOG

IMPLEMENTATION

Questions