Skip to main content

Week 2 Design thinking - Build the right thing


This week focused around building the thing right as opposed to building the right thing. Great design has always been concerned with the whole experience of interaction.

One of the most interesting topics emerging from the class was prompted by a quote from Alan Cooper. It prompted discussion around what do you get when you cross a computer with a camera? A phone? A plane? With a car? A ship? You get a bigger computer.  The products we use on a daily basis are becoming ever more like software.

Allen stressed that we need to develop an annoyance and radar for bad design and an appreciation for superior design. He showed us a variety of good and bad design examples and showed examples of how users will highlight the problems in your products or else they will leave marks e.g. a sign telling the user how to interact correctly with a product / service


During the lecture, we also watched a video "Inside IDEO" which followed the IDEO design team revolutionizing the shopping cart. It was amazing to see their design process. It appeared chaotic and messy and yet they were able to create some fantastic creative designs. It was evident that the organization stresses a lot of importance on sketches and iterative design.

One quote mentioned during the video which stood out for me was "fail often in order to succeed sooner." This resonated well with me and reminded me of a previous module I had taken, Game Thinking where there was an emphasis on iterative design, paper prototypes and brainstorming to create a product from design through to working proto-type in just five days. The module co-coordinators stressed the importance of failing many times before reaching our desired product.


Although it appeared that everyone's voice was heard in the organization, it is not a place I would like to work in. During challenging times or when decisions need to be made, the decision making process remains with the senior leadership team and other members of the organization are treated like children.

Comments

Popular posts from this blog

Research Essay

A major assessment component for the Design, Development and Creativity module was conducting a research essay which involved working individually or in pairs. Myself and my partner, Beth conducted our research essay on updating a digital product, the UCD student portal through the introduction of a digital collaboration tool as a core offering for all students studying at the University. This essay involved conducting both primary and secondary research. In terms of primary research, we conducted a questionnaire, interviews and observational research to understand how students currently interact with the UCD student portal and how it can be improved. Once we understood the problems associated with blackboard and how it could be updated by making it a more engaging site, we conducted secondary research, studying existing literature and case studies on the topics of collaboration and utilising collaborative tools. Upon decision on the update required, a usability, requi...

Week 4 Lecture

Introduction During this lecture, we discussed different methods for software development including waterfall and Agile. Waterfall is a rigid way to approach software development. It can be beneficial to projects where there are little to no unknown factors as it is a rigid, structured and organized process Releasing iteratively is a useful way to approach software development projects when there is an element of uncertainty. It allows for feedback and changes throughout the development lifecycle.  Required Readings During the lecture, we reflected in small groups on the readings. A reading which stood out for me this week was the Brooks "No Silver Bullet" paper. I enjoyed the metaphor of the werewolf which was used to describe the complexities associated with SDLC which teams don't envision from the onset of the project. The paper stresses that investing in good developers is far more important than attempting to find a solution or a "silver bu...

Designing a Robot

In week 9, we worked in small groups to create a robot using an instruction manual and upon creating our robot, we were tasked with creating a "run" function so that our robot could drive around and "guard a base." (for the purpose of the class, the base was a large white box) This exercise was great fun, but at times stressful as we were required to create our robot within a short time constraint. To create our robot within the allotted time, my group divided the tasks amongst us. One individual called out the required materials needed and where they were to be placed, one found the necessary materials and two individuals put the robot together. As requested by our lecturer, we switched roles frequently so that each member got experience working on each of the tasks required. Dividing the roles out amongst ourselves enabled us to create our robot more quickly than if we had completed each of the tasks together as a group.