Sunday, 11 October 2015

Theme 5 - Reflection

There have two lectures in this week to talk about how to design research. The first lecture provided by professor Haibo Li on Wednesday, in the lecture professor Haibo Li was mainly talked about the process of problem solving. How to define a problem and how to solve the problem? In order to underline this process, Haibo Li gave an example of “hungry bear” which I think gave a clearly description for that. At first, when two people meet a hungry bear the first things comes up to their mind is run out of the bear as fast as possible, however human can never outran a bear.  So how to survive from a bear? Then the problem now is defined by yourself and all you need to do is just run out of the problem. Sometimes when you confused with the problem you met, just changing the view of the points you treat the problem maybe you will get more useful solutions. Related to this case you realized that, in order to survive, you should not outrun of the bear, you should just outrun the other one. The professor put forward his theory for problem solving process that defining a problem can occupied 90 percent of you time and solving a problem will just spent 10 percent time.

The second important part in this lecture I think is that how to filter ideas. You should know how to select and validate the useful idea from many of them. It not seems like easy cause sometime we are blind, we just want to see what we want, besides the idea maybe not the suitable one for you.  Professor Li mentioned different tools to filter ideas which are real world channel model, tunnel vision and high dimensional space. He also advice us to make a balance consider if the solution address the pain point of the problem or can we use our own existing knowledge and technology to solve it. With my personal opinions, the most important thing is to know who you are and what you can. Filtering ideas based on you own circumstances and effective use of the tools surrounding yourself, and choose the most conducive way to you can directly and faster to reach you goals. To validate a good idea, it would be better to make a proof of concept to check if the solution have feasibility can help to solve problem. When you want to evaluate an idea, the best way is to make a prototype. Thus, your idea could be tested in many times and you could find somewhere new ideas to make progress of you old one.


The second lecture provided by Anders Lundström, which mainly talked about what is prototype and how to use it in design research. I could say that I am not have a good understanding for this lecture, unfortunately there have no seminar in this week, I can not get more details for that, however I still can read others reflection post and to fetch up what I missed in this lecture. As I think, use prototype can help us gain a new knowledge. The purpose of research is finding an answer, solving a problem, testing theory. We design research to shape the prototype by gathering existing empirical data, and the prototype itself doesn’t to be a solution. But it could be continuously updated via gathering data or as a base for other experiments be tested again and again. That are all what I could say in the second lecture, I hope I could get more information from others posts..

7 comments:

  1. Hi,

    I think that you have a written a great summary of the lectures. I also found the example of the bear from the first lecture to be good in terms of clarifying the importance of defining a problem.

    To add to the discussion on the second lecture:

    It was also said that analysis is important in design research. He mentioned that if the paper from Fernaeus had not included a chapter about “lessons learned” the paper would give less knowledge and less new theories. He further explained a definition of the term analysis.
    I interpreted that analysis means to compare what has been done in the own research project, which is called the process, with theories that exist from earlier made research.
    (I think that earlier made research also can mean that it is possible to compare the different feedbacks made on the different versions of a prototype used in the same design research project.)

    Great summary with interesting explanations of your own perspective on the different methods that were mentioned!

    ReplyDelete
  2. Hi Haisheng!
    I also liked the bear example (although I've heard it before, but it's a good metaphor).

    It seems as if you have put a lot more energy on reflecting on Haibo's lecture since you've spent most of the post on it, and also highlighted words and such. I can't understand why your post has different formalia in the different sections?

    And even though I'll give you cred for understanding and reflecting a lot on Haibo's lecture, but I wish you'd used some more of your own words and tried to reflect on what YOU thought about the lecture and the concepts for this week.

    Otherwise, good job,
    keep it up!

    ReplyDelete
  3. Thank you for a good summary of week 5. You provide all the core information we got out of the lectures, I just miss some reflective thoughts of your own. However, since we did not have a seminar this week, some questions stayed probably unanswered. As you mentioned in your text, it can be rather confusing to find a solution to a problem, thus Haibo's approach on defining the actual problem might help to assist in finding a solution. I really appreciate this concept since it was news to me - the 90/10 ratio seems a bit intense though. What do you think?

    ReplyDelete
  4. Thank you for your good reflection and you made a good reflection on lecture 1.What interested me most during lecture 1 is the "tunnel vision".From that example I knew that we could not take everything for granted and find out the new idea behind our normal life.What he said about idea is that " defining a problem can occupied 90 percent of you time and solving a problem will just spent 10 percent time."But I think solving problem is still important.There are also many researches without shortcut.
    Thanks for your reflection.

    ReplyDelete
  5. Thank you for sharing your thoughts! You well summarized the first lecture, nonetheless, I am not sure to really well understand your point about: "the most important thing is to know who you are and what you can". Maybe you could write more about it !
    Moreover, I totally agree with you about the second lecture. I found it not really structured and not clear at all. About prototype, I would say that it is a possibility for you to test some ideas on it and see if it works or not. You can get feedbacks from potential future users and make some modifications according to them on the prototype.

    ReplyDelete
  6. This post reads mainly as a list of things the lecturers said. It's a god write up, and what thought you have is good and interesting, but there are few bits that read like your own reflections. The second lecture, to me, was about how to use and analyze data gathered from prototype testing, and some about how to do that testing in an effective way.

    ReplyDelete
  7. I thought the first lecture was a bit... Well, goofy, mostly, in the sense that it sounded like some odd get-together for people in a mid-life crisis rather than anything supposed to instigate a philosophical debate. The entire thing to me was mostly pseudo-inspirational motivational quotes, some of which you mention in your post - the 'knowing who you are' and 'following your dreams even if you're not capable'. Barely any argumentation to it, and therefore nothing that really managed to resonate.

    ReplyDelete