Skip to main content

First Lecture

I attended my first lecture for the module Design, Development, Creativity yesterday and I found it fascinating and I am very much looking forward to engaging with the module over the course of the semester.

What stood out for me from yesterday's lecture was the activity we carried out in small groups on Buxton's avalanche case. The case described an event whereby friends skiing got caught in an avalanche and one of their friends, Saul was missing.

During their avalanche training, the friends were given instructions on which of their survival tools (probe, shovel, transmitter) to use in which order and how to go about the rescue triage (rescuing the most able individuals first before moving on to the least able).Having not followed the sequence of  their training in exact order, the group of friends still managed to save Saul within 10minutes.

What stood out for me from this exercise was the fact that systems are complex entities which comprise of many independent factors linked together. In the case of the avalanche, it was a mixture of tools, training and trust which led to Saul being rescued safely.

The exercise also taught me that although systems often have pre-defined instructions or rules for use, humans may not always see fit follow the rules correctly, meaning that systems need to be flexible and be able to adapt to human factors and unforeseen events. In this particular case, had the friends followed their training correctly, they may not have saved their friend in time.

The case also led me to reflect on the human versus machine debate and the notion of machines being able to out-smart humans. One wonders whether the friends knew that following the rules correctly would have led to an unsuccessful rescue of their friend Saul and so they used their intuition as well as the training they had learned to save their friend rather than relying on the training alone. Had they relied on the rules alone, they may not have been as successful in their rescue efforts.

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.