This week there were no seminar, and only two lectures. I went to one of the lectures since I had to prioritize something else on friday.
On the first lecture, that Haibo held, he structured is following five questions, namely:
How to come up with ideas?
How to filter ideas?
How to validate ideas?
How to evaluate ideas?
How to communicate ideas?
I had to go after half of the lecture, and during that time he only managed to cover the first question.
He talked about problem solving, and brought up an example of the student and teacher that encounters a bear in the wild. The teacher sees the problem as the two of them running away from the bear while the student, who sees the "real" problem, says that since the bear is satisfied eating one of them the student only needs to outrun the teacher. I guess this explains the main concept of actually defining a problem, and how it can be defined differently in the same situation.
The more interesting part here would be Haibo's own theory about how much time you should spend defining- and solving a problem. Solutions should always be more straight forward. If you can define the right problem a solution will present itself more easily and you will spend less time working on the actual solution. He put it this way; 90 + 10, if you spend 90% of the total time defining the problem to make sure you got the right problem you can spend less (here, 10%) time on actually solving it.
That's all I got from this week. We've had other courses where we stumbled upon this weeks theme as well.
Hello Måns! The 90%-10% theory that Haibo presented was very interesting indeed and one of the main points that I took with me from the lecture as well. Since you didn´t attend so much of the lectures I think your reflection could benefit from talking a bit about the articles ad your thought process of the theme in general during the week.
SvaraRaderaHi~
SvaraRaderaIt is great to see that you had a clear understand of this lecture through your reflection.
Almost every people are impressed by the theory of defining and solving a problem. After finding the right problem, catching up with appropriate solution is straightforward.
Good job!
Hi Måns!
SvaraRaderaI like that you start your post off with being honest about why you didn't attend the Friday lecture, however, I myself would have put it in different words. It's something about the way you say it that makes me feel like you don't really care about the course.
With that said, I think your reflections on Haibo's lecture are ok. You've understood it well and you're able to retell what you've learned during the lecture. I do miss some own reflections about what you thought of it (more than that the second part was more interesting).
Finally, I do think that your reflection might be a little short...
Hi Måns!
SvaraRaderaI think it was unfortunate that you missed the second lecture of the week because I think that showed a big contrast to the approach to design research that Haibo presented. However I think you got the most important things from Haibos lecture: to really put a lot of effort into defining the problem and you will probably be able to find a straight forward solution.
I think you could have benefit from analyzing more about the articles you read in preparation for this theme to show what you learned during the week. Another thing you could have done is ask someone else if you could have got their notes from the second lecture. Even if you might not have been able to understand everything I think you will have gaine something from it.
Hello.
SvaraRaderaI think the example with the bear, professor and the student is really interesting. You say that the real problem is to outrun the professor. Event though that may be the easiest solution it will end in the professor getting eaten, which is not very nice! I think it is important to search for the easiest solution and the real problem, but that does not mean that it always is the best solution. We also have to think about what is morally right and what everyone benefits from the most.