The document outlines Joachim Tesmer's process for solving problems by the July 29th deadline. It involves understanding the problem by listening to people involved like teachers and students. Drawing from 18 years of software development experience and discussing similar problems in an agile development approach. The process also includes creating a common understanding through sketching ideas, storyboarding, decomposing the story into tasks on a task board, and getting feedback on prototypes to check for ease of understanding, missing parts, and ways to improve before the deadline.

1. How to Solve
Problems
Problems
Joachim Tesmer
for
Design Thinking Lap
Juli 2013

2. The Problem
I have to explain how
I‘m solving problems
till 29-07-2013

3. In a Hurry
how to solve problems

4. That‘s Not MY way
--> Retry

5. Understanding Problem

6. Listen to People
Teacher
Students

7. Resources
18 Years of
Software
Development
Only few days
for delivery

8. Similar Problems
Agile Software Development
Discuss
with
On
DT Lab
Look
Inside

9. Story
Teacher and Students
will visit my
ProblemResolver
to catch
my process

10. From Story to Tasks
Common
Understanding
Sketching Ideas
Story Board
Story Decomposition
Task Board

11. Prototype & Review
Easy to Understand?
Missing Parts?
How to Improve?

12. Web(TV) Sales
Slides and Webinar
• visual: power messages
• speech: tell own story