the Internet of Things [green]

Student Project for INDS 3B09: Design Research, Insights & Innovation
For the Industrial Design Department of the Ontario College of Art & Design,
team mentor Matthew Jones, Research Associate, Beal Centre for Strategic Creativity

Monday, April 10, 2006

and now..

well guys, we did it!!

and we did it fabulously, i might add.
we should all be really proud of the work we did and everything we accomplished this semester.

it has just sunk in that we don't have another report or compelling presentation to prepare for IOT.

i hope you all find other things to fill your time [you will soon realise just HOW much time we put into this thing!!], and that you won't miss my obsessive emails flooding your inbox.

i really want to thank you all for being such an awesome group
and for all your hard work

who's up for weekly IOT meetings in the summer?? i'm thinking, tuesdays?? *kidding

it was fun being the team leader, i hope i didn't flood your inboxes too much

leslie.

Monday, April 03, 2006

timeline

ok guys

here's a breakdown of the timeline for the final deliverable for iot..
drumroll, please.

monday, april 3 - finish writing scenarios and disclosures [yeeehaw]

tuesday, april 4 - email your stuff to heather and kat [our official editors]
meeting with matt [hopefully]
pick 2-3 stories to present in class
decide on presentation strategy - begin assembly
begin assembly of report

wednesday, april 5 - editing complete, finish assembly of report [scenarios and disclosures]
finish presentation
sleep [lets try not to do an all-nighter..]

thursday, april 6 - final iot presentation [ do you miss it already?? ]
celebrate good times come on!

;)
leslie

Sunday, April 02, 2006

Ok, here's that list of characteristics of IOT...

hat i did a while ago. These work in IOT simultaneously, so it'll (hopefully) help us evaluate and expand our ideas.

The Always On Network

( Blogjects, Surveillance, Fridge connected to grocery store, Connection to Internet, Connection to data, Time, Universal Systems of Measure, Encyclopedias(those written by 1 person))

Latent: Desire for connection to others

desire for a collective system of reference/view of the world

Collective Intelligence/Beehive

(Includes collective intelligence between people, between things, and people and things; Includes Artificial Intelligence, smart mobs, wikipedia, )

Human Empowerment

(Intimate Objects, Project Oxygen, Teddy, Cyborgs, …

(Empowerment through: Human Augmentation + Automatization to replace human behaviour, )

Data dissolves into the environment(dissolves into the fabric of our lives)

New Environment & Death of Data subsections

(Merging of Virtual and Physical, Interactive Environment, Death of Data? , interaction of object to object surpasses interaction object to human,…)

New Social Infrastructure, New Systems or New Flow (Redefining institutions of Culture, Society, Government, Law, Economy, Education, Production/Consumption etc – basically HUMANITY AT LARGE)???

- objects become separate class

- privacy issues

-utopia/dystopia

Monday, March 27, 2006

Summary of what we have discussed during the meeting today.

IOT group meeting,

Discussing our problem from last project.

1. We were focusing on things that could be improved or thing could only about IOT. Things that only use IOT.
2. For our scenario should focus on IOT itself as ecology, Things that absolutely rely only on IOT.
3. We should base on the things. (Object and Object relationship and technology and technology talks) Object isolated as object. Ie) when you put down cock on the table, the chair automatically pull out for you, Cock and table talks to the chair.
4. Plot the scenario.
A) Do it in linear way. Figure out points, and plot them. It keeps you focus on the track. B): Actors: figure out who would all the character would be and how it will be converge.
5. Use POD as inspiration, Have a gripping line for the story.
6. Check out user scenario from the Alex’s file.
7. Emotional and discover deep progression from the writing.
8. Example of saving the money through of IOT. Keeping tracking of what people would buy, and what people would waste, if there is fridge and tell what they need to the producer, than value will be put in the …
- do we need even physical money? If you want to buy something and if it automatically detects you want to buy it, the bank will automatically charge for it. –
9. Scenario should highlight benefit for the user. It is more like services.
10. Making mood board – Final deliverable.
11. -Each write scenario and bring mood board: It sets the scene for what the feeling of the story would be: ex. Someone will write about service that puts the
what do I like? I wonder what other people would like it?

: Back casting: no Super futuristic: within 10 to 15 years make it somewhat little bit realistic so that reader can agree or picture that would happen within 15 years from now.


Ex taxi idea with pregnant women
Write based on your point of you. Conceptual: idea something that u ever experienced it before:
If you are writing about you, it should be more powerful. You know your experience better than anything.
Writing as object point of view.

Chairs communicate with technology.
People don’t have to do anything
Tech talk tech without any human interaction.
We are here to AD for IOT.
Object talks to object.



Let’s focus on the positive aspects of the scenario.
Come up with new Design opportunity.
Come up with different point of view.
POD departure be data transfusion: Writing story from DATA: All come up with different mood board and find pictures with it.

Do mood board as many as you can in power point format. Write many stories as you can.


Hope this helps, well at least it helped me understanding what exactly we need to do, I enjoyed the discussion today during the meeting!

see you all tomorrow,

Saturday, March 25, 2006

thursday's class

hey guys - here are my notes from thursday's class. also, please download the document "User Scenarios" from mycourses.

SCENARIOS
- to write an scenario, you must do cultural assessment, context analysis, motivation analysis, understanding.

- unless you are writing a purely conceptual scenario, you should not write about things you have not experienced.

- make sure the story is in the context of your audience so they can relate to it

- think bigger than you can possibly think.

- Do not go far ahead in time, because you still need a context people can relate to. [go 10-15 years in the future at the most in the final scenario]

- Try to inhabit each character you write about. If you can't inhabit the character, don't write it.

- Context Analysis - mapping the epxerience in order to understand it.

- Some examples of story styles:
  • News - practice with real news stories and replace all the facts.
  • Business Magazine - making stuff up that could possibly be read in a magazine
  • Letters/Journals - easier because they are directly from your point of view
  • Book Review - pretend that a book was written about your subject and turn the review into the scenario

- Always plot the story before you write it so you get all the crucial points in.

- Have a "line", and make sure you bring your story back to the same point you started from. This makes it more compelling and memorable.

- Point of View

  • the 3 dimensionality of the story - think of it like different cameras
  • writing stories from the POV of an object can be successful
  • how does the exact same story feel from different POV's? [make sure you have complete understanding of all the POV's]

- Scenarios

  • explain everything that cannot be drawn or modelled [emotions, experiences, etc]
  • they are task-oriented

- Prepare a document, compelling presentation, and a mood board

- Mood Board = discussion points [not scenarios] that help you write the scenarios

  • Ask as many questions as possible
  • Make this AND the scenario emotional
  • Create the tone for your team that will carry over into your scenario (create the context)

- Create a medium that is trusted, to tell your story - like Orson Welles on the radio [War of the Worlds]

- Make sure your scenarios state what the benefit is for the user.

- One way to start writing your scenario could be to start off going WAY in the future, and then back-setting it so it is more like 10-15 years. Matt suggested we try this to get us going.

*********

ok so those are my notes

MEETING ON MONDAY - 2pm, let's meet on the 5th floor.

MEETING ON TUESDAY with Matt - please everyone try to come, it is much more helpful if everyone hears the info. What times work for everyone? I am free until 6:30.

please comment asap

thanks guys,

leslie.

Thursday, March 23, 2006

yoink!

i am such a thief

Matt - I stole one of your comments from another IOT group's blog because I thought it would be really helpful for us too.. hope thats kool!! :)

MDJ said...
The unique power of a scenario is the power to explore the way a proposed situation feels to the users. But as you said in the last presentation, in the IoT paradigm, the technology will be mainly interacting with other technologies. So do not discount the value of metaphoric scenarios that explore anthropomorphic technologies - exploring these interactions from a humanized point of view sometimes reveals overlooked opportunities. For example if you give a technology the quality of self-doubt, then the scenario might examine how it feels it is succeeding/failing in its current interactions. This sounds silly but this self-analysis is really an look at the human experience that the technology enables.

Wednesday, March 22, 2006

Yay!! the last one!!

Since our last part is about scenario building, i went to look up the how to write scenrio, so i mean, this is not relevant to our specific topic of IOT, but at least this article gives a sense of how we should start to build, or write scenerio. HOpe this helps,(it has some examples as well)

http://www.hotwired.com/wired/scenarios/build.html

I wanted to upload some pictures.. but it is not working for me...awawaw~~!!!

story time. . .

hey guys

I just want to check in and see what everyone has been up to the past few days.

I've been away for two solid days for medical appointments so I apologize for not really being available.

I want to make sure everyone is clear on what the issue was with our last report, and although we don't have to re-submit any work, i think it would be really beneficial to re-work some of it for our own benefit.

The next stage is scenario-building. for those of you who haven't done it before, it's essentially telling a story that really captures the idea of our POD's and where we think the IOT could go.
although we are not ready to start writing the story yet, please start thinking of ways you would like to A) Tell the story and B) Present it. What are some effective ways of story-telling? What kinds of story-telling tactics do you find you respond to the most? What are some potential plots/story-lines that you think would really communicate our ideas and be captivating at the same time?

Please bring some stuff to class tomorrow - re-worked POD's, re-worked Amplifications about the IOT itself. Please also keep in mind the idea of IOT as an ECOLOGY as we do some re-working and planning for the next stage.

I also propose a group meeting ASAP. Anyone free on Friday afternoon - about 2:30pm?

please comment asap so we can arrange

ta ta,
team leader