The Statement
Postcards don't give enough options to describe an experience
or the location, and text messages or emails don't always
give a personal touch to the communication.

What we're gonna' do
Explore the possibilities of describing experiences or characteristics of
a city by mailing >torontohelsinki< city recipes. The results will be
posted and conclusions will be made towards potential products.
All information and innovations will be a part of the summer print
edition of _project.

Date: Tuesday the 7th of August until the 21st of August.

To: Send your mailing address to jeremiah@idgrid.org

Receiver Scan and post impressions on the _project.
(note: if you don't have access to a scanner - seek your nearest idgrid
member who does and throw a party. :)

Details: come out to habbo meetings (see news sec.) or contact us.




posted by [j] at 02:59

>torontohelsinki< prt3
breaking down what we've got:
- members in toronto and helsinki
- cities which have similar/different characteristics
- person to themselves experience recording
- person to person or person to group experience sharing

breaking down where we could go:
- 2 weeks of preliminary research
- would like it to end up as a product (research package included :)
- statement should reflect what we are at the moment - ie. >torontohelsinki<
- city recipe: could continue the fiction - discussing what the
new city would include what would its magazine be like, its cultural
atmosphere - what else?
- using easily accessible tools - ie. stamps, pics, smells...


re: >experience capturing
I like the post by greg: it brings up some
interesting points to discuss. In the high to
low tech. versions, I'd like to go back a few
steps on the design of the system. A lot of high - low tech.
travelling tools seem to create systems of use which bind
rather than free. Some of the first designs I was creating in
the Netherlands were criticized by my professors as having
predictable results because I included a single or too tightly
focused variable. In this case, if the use of the product/service
has too many rules then the results may not be as surprising
or fun -> especially to a large audience.

What might be interesting is to explore the mystery outcome
in a journey or experience. The product's initial system could
be more about inspiring a habit or routine. So then the process
of capturing an experience would also prevent (as much as possible)
'filtering' by the product. :)





posted by [j] at 05:19