Wikis vs. E-mail

Appreciate architecture? Visit the Vancouverism show in the foyer of the new Woodwards bldg. Beautiful & inspiring work. (Link)

SuperPower: Visualising the internet. (Link)

Boys and their toys. (Link)

Beautiful packaging, it's simple and does a great job showcasing the product. (Link)

Have we mentioned that @LikemindVan has a group page on LinkedIn too? (Link)

RT @gdcbc: To honour fallen designer Leo Obstbaum, please contribute to Emily Carr's Memorial Award in his name: (Link)

RT @gdcbc: CBC's tribute to Leo Obstbaum, deceased designer responsible for the 'look' of the #Vancouver2010 #Olympics: (Link)

RT @MarkBusse: People often say I have a big head, but that's hogwash. This photo proves my head is just right: (Link)

Love this diagram of the creative process as a continuum from research (uncertainty) to design (clarity). (Link)

Our newest designer Dana is awesome. You should hear her talk to marketing people when they call. Don't mess with the Dana.

This is the best Olympic training video I have seen to date ;-) (Link)

Missed what it was like to be in Vancouver when Crosby scored the winning goal this weekend? Watch (and listen) to THIS! (Link)

Google acquires Picnik, thus expanding it's dominance in the cloud computing domain. Who needs PhotoShop anymore! (Link)

RT @MarkBusse: @TimeFox is now on Twitter and has released an iPhone app! I just updated some projects hours I forgot to log. #productivity

RT @MarkBusse: How do you define professional success? For me, it has to be working with people that feel more like family than employee ...

Tags

Categories

Wikis vs. E-mail

Confused by Wikis? Rather just use e-mail? Check out this graph and see if your opinion changes. (via Tantek Çelik on Twitter)

Tags: ,

2 Responses to “Wikis vs. E-mail”


  • Ben Garfinkel (July 21st, 2008)

    This model, the one on the right, also could easily represent collaboration using Google docs. Obviously not as powerful for some projects, but seeing as the model is using Word doc icons…


  • steve (July 21st, 2008)

    The model on the right really represents much of 2.0 collaboration. By centralizing resources online in one singular place, you can eliminate multiple versioning (and confusion caused by working off archaic versions) and accessibility as anyone with web access (and permissions) can participate in the process.

    Does this mean we can sell the carrier pigion?

Leave a Reply

«
»