Skip to main content

"Inside IDEO"


During the course of this module, we watched a documentary, “Inside IDEO”, a design firm based in Palo Alto, California. This documentary introduced a concept which we revisited often during the module: “fail often to succeed sooner”.

Watching this documentary, reminded me of personal work-related experiences working with design teams, in that the IDEO workplaces appeared chaotic and that everyone, no matter their experience or seniority in the business, had an equal say in the design process. As David Kelly, founder of IDEO stated, “it is unlikely that the boss will always have the great idea”. In IDEO, status arises from those with the best ideas, not those in the company the longest or those with superior experience.

What I learned most from watching this documentary, was the businesses approach to failure. My prior experience would suggest that failure is something which is discouraged and something which should not be reflected on and instead, “swept under the carpet”.  Those at IDEO, in contrast encourage failure and see it as a learning experience. In the documentary, we see that instead of disregarding failures, they keep each failed invention.

Watching this documentary, taught me the importance of prototypes. This is something which was also encouraged in the Game Thinking module I had previously taken. After the team had narrowed down their designs to a few options, the team were split up into smaller groups, to each build a mock-up of each idea so as to bring the idea to life. Having a tangible prototype of each of the ideas, aided the overall team in refining features and selecting the best option for the problem at hand: redesigning the traditional shopping cart.


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.