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

Iona Technologies

·        Iona was founded in 1991 by Chris Horn, Sean Baker and Anrai O’Toole ·        The company progressed from a Trinity campus company, releasing Orbix in 1992 and going public in NASDAQ in 1997 ·        Trinity College Distributed Systems Group (DSG) was a small group of academics and engineers conducting research and development into the problem of inter-network computing systems, essentially connecting systems which were developed as independent systems to work and communicate with one another ·        Their research was initially supported by Trinity and then the EU ·        They took a brave leap from academic to the commercial world due to the attractive opportunity of industries like banking and telecommunications embracing networks and internets ·        Iona found that their c...

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 ...

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.