A. Microsoft PowerPoint

B. SAP Fiori.

C. Lego

D. Cardboard

A. Show the solution through the user's eyes.

B. Convince your audience with the prototype

C. Demonstrate functionality and the look and feel of your solution

D. Show as much detail as possible

A. Strategic advisory

B. Final go-live check

C. Incident management.

D. Technology opportunity identification

A. What people say is often not what they do, think or feel.

B. Take people out of their context and put them in an inspiring environment

C. Ask a lot of "why" questions to get valuable data

D. Focus on the users who represent your main customer group.

A. Plan several Design Thinking activities and workshops during the development project lifecycle.

B. Initiate Design Thinking related activities at the beginning of the development project.

C. Plan Design thinking workshops first for the business side and then for the IT side and repeat this throughout ^ the development lifecycle.

D. Plan Design Thinking workshops at the beginning and at the end of the development project.

A. By asking "why" questions

B. By observing the environment, tools used and body language

C. By asking binary questions.

D. By understanding the user types and the context of the challenge

A. Speed up the synthesis phase.

B. Collaboratively evaluate potential areas for a given project scope

C. Discuss with project sponsors if the scope is fuzzy or unclear Merge multiple

D. Design Thinking challenges into one

A. To identify interview results that lie outside of the problem space.

B. To identify common topics and understand the meaning of interview results

C. To crystallize key user types, needs and insights from interview stories

D. To frame the potential solution space of the challenge

A. To keep the project sponsors satisfied

B. To provide interesting insights

C. To include a diverse set of users

D. To reduce the number of interviews.