Rannie photojunkie gathered 20 couples on 20 couches. What's the Difference? Simple and beautiful. You may see some familiar faces.

20 x 2 : What's The Difference? from photojunkie on Vimeo.

Holm Friebe and Philipp Albers delivered a presentation at LIFT on a topic that's close to my heart: the future of work, exploring new forms of self-organizing "unorganizations" of creative free agents. Of course, I've been thinking about similar issues as I consider how to scale Remarkk! Consulting, so I took particular interest and had a great conversation with the guys over fondue. (which, btw, is the best part of LIFT!) Friebe's book, Wir nennen es Arbeit ("We call it work") is a bestseller in Germany that has been described as "youth economic manifesto". They organized a conference in Berlin also called Wir nennen es Arbeit Festival-Camp, which looked like tremendous fun and is possible inspiration for a Toronto FreeAgentCamp or Future of Work conference. These guys apparently invented Powerpoint Karaoke (fact check anyone?), and put on events like a poetry slam with sms voting and electro-shock feedback. They are looking to develop coworking spaces to accommodate their starfish adhocracy.  This is not your father's creative agency. Presentation notes after the jump... Notes: Digital Bohemia: The end of work as we know it; people want to work in new structures; how do you integrate individuals with strong sense of self-determination, people fed up with hierarchies; The Penguin Paradox. Their "company" is called Zentrale Intelligenz Agentur (Central Intelligence Agency) which they describe as "a capitalist-socialst joint venture, designed to establish new forms of collaboration". People are contributing in Berlin and around the world. They described the operating principles with seven (or so) rules. Seven Rules: Rule 1, The 7 Nos - No office. No employees. No fixed costs. No pitches. No exclusivity (company doesn't own your life). No working hours (results only). No bullshit. Rule 2: Work-Work Balance - balance projects for clients with your passion projects, given equal priority and attention. Rule 3: Instant Gratification - profit immediately with work; no salaries, billable time/project, always keep 10% of profit for the company for play money; pay bills immediately as well Rule 4: Pluralism of Methods - tech solutions for social problems, use online tools for collaboration; Skype, Google calendar, Google Docs Rule 5: Fixed Ideas - live up to your intellectual obsessions and dark desires at work; take them seriously; don't be afraid to offend people; Rule 6: Responsibilities Without Hierarchies - each project as to have one person incharge, but it can be anybody; beginning of year retreat in the country; rethink the business model; sift through projects and leaders take them on; Rule 7: The Power of Procrastination - don't try to be too efficient; good deas will adapt and catch on, even if you neglect them for a while; they have to ripen; there is a natural Darwinism of ideas Rule 7.5: Marketing by Feuilleton - no adverstising, no PR; do something interesting and press coverage will be yours; they get coverage in the culture section Conclusion - A Hedonistic Company not only changes the nature of work, it shifts the domain of that work.

Lifters underground at CERN, originally uploaded by Kooze.

I had a fascinating tour of the Large Hedron Collider at CERN on Saturday. This was one of the last opportunities for members of the public to get inside this amazing, mind-boggling project probing the frontiers of physics and our understanding of the universe before it gets switched on this summer. Something to tell the grandkids.

Our guide Bilge Demirköz is a research fellow at CERN who is searching for evidence of dark matter. She gave a tour through not only the facility, but also across the history of particle physics through 30 Nobel prizes. Her passion for the subject was infectious, as you could sense the excitement of scientific exploration at the frontiers.

Pedro Custodio did a great workshop, an "Online Communities Clinic". Good material, really solid foundation for thinking about and planning user interactions for online communities. Once the slides are on Slideshare I'll update this post and embed. (If you want to see them when uploaded, leave a comment on this post.)

My rough notes follow after the jump....

Overview

Communities need to bring together a unity of goals and actions; they should display internal policies that guide social behaviour; online communities lay on top of computer systems that support the social interaction

Communities necessarily have boundaries; something ambiguous will not be joined; although it is necessary to have boundaries, those boundaries need to be permeable to encourage adoption and movement/adaptability

Online communities architecture:

virtual space -> user interaction -> virtual community -> information

Users Profiling:

Visitors - start as observers
Consumer - as interest raises, so does the involvment at tthis point users
Member - fully active, producing materials, engaging and helping others

Sort communities by kind of Interaction:

Low social interaction - users only interact with the platform, not with each other: e.g. Digg, Last.fm
Built upon "products" - Flickr, YouTube, Threadless - because of the tool, not the users
Highly collaborative communities - real-world communities, moving online for some reason,

...by level of Commitment:

Communities of interest; very specific; will not be active for your whole life, but will join when you need it
Communities of passion; subtype of interest,
Communities of purpose; common short-term goal; afterwards it will dissolve
Communities of practice;

Better Usability means Better Communities? Not only user-centered interfaces...we need community centered interfaces! Need to plan ahead for the behaviour

Communities are conversations; so look for Conversational Maxims; Apply the same ground rules that run daily interactions in real life:

Quantity - the amount of information that each party should provide; should limit how users interact; length and frequency of posts
Quality - deals with truth and authenticity; credit and reference to expertise
Relation - relevancy of participation
Communicate in a fast and reliable way: post message, was it delivered?
Interface should be as transparent as possible; the tool mediates, but it shouldn't get into the way
Allow user to cancel

Community Design Pattern Types:

1. Community support - sustains the community itself
2. Group support
3. Communication support
4. Awareness - perception of the others, part of something bigger

Community Support Patterns:

Quick Registration: as quick and lightweight as possible, very important for them to enter quickly to evaluate the community; but still protect the community from strangers; leave profile info as a later process, noncontingent; need to track the process in order to identify dropouts; PROBLEMS - fear of commitment, because trust has not been established; BOTs are problematic - Catchas, email verification;

Login: force users to identify themselves before using/entering the community; easy recovery mechanisms

Welcome Area: list new members of a community and present them to other members, ensuring that new members won't go unnoticed; e.g. email communities, introduce themselves to each other; USE WHEN: a long-standing community who know each other very well, large collective history, subgroups inside the larger community, resistance to entrance of new members; PROBLEMS: newcomers may not want to attract so much attention at first; veterans have to be made sensitivie;

User Profile: virtual presentation; a personality and skills aggregator; the bridge between the real and the virtual individual representing the user across all interactions with the community; Digital Identity Mapping image - FredCavazza.net;

User Gallery: USE WHEN: hesitation on first contacts, hard to remember who's a member of a community; you know their names, but want to know more about them; PROBLEMS: must be searchable, carefully balance amount of public information without further involvement or identification (user levels-> information levels)

Buddy Lists: friends list is the new centre of the universe; "through others I define myself"; "Tell me who you go out with, and I'll tell you who you are!";

Group Support Patterns:

Groups: need ways to form, short-term and long-term communications; shared repositories; group awareness - feeling of being part of something; E.g. Flickr - friends or family, that's it; USE WHEN: send out multiple artifacts to same users multiple times; select multiple users before interactions; users don't clearly know who they interact with; PROBLEMS: by interacting with groups of users, one might not develop group awareness - no awareness outside the ; additional workload for users; group create strong borders within the community; group moderation;

Invitations: allow user to plan interaction with others; PROBLEMS: time to turnaround; rejection fear; need to sort out

Shared Editing: allow users to edit simultaneous user of data/documents; USE WHEN: need for collaborative editing; missing group collaboration in context of isolated user actions; PROBLEMS: single-user applications don't help collaborative environments; WYSIWIS - what you see is what I see

Reputation and Differentiation: metrics to store reputation, a projection of their status; users with more friends, more photos, more music;

Messaging: provide ability for direct messages within community

Chat: allow users to communicate synchronously; if messages aren't being responded to quickly;

Comments: on specific artifacts; not a message to you in particular, to the community about an artifact;

Forums/Blogs: provide means for persistent, asynchronous conversations; important role for newcomers, a way to learn about the community; persistent nature of the community;

Patterns for Awareness:

Overview: Give users a sense of the other; understanding or realizing the others' activities; communities with high awareness are highly collaborative; creates the feeling that there are many others, than they are; you are just a dot, but you're not alone

Neighbours: proximity pattern; providing information about user's interactions with the platform; Last.fm - people who played similar music; keyword discovery for people you want to meet; Proximity: six degrees of separation concept;

Interactive user Info: make information about others users clickable and connect it with means of communication; quick action spots

Activity Logs: record information about users activity; most famous - Wikipedia tracked changes; memory; users don't have a lot of time, can't be on all the time; need a reminder of what's been happening; merging past and present activities it's hard; scale - ensure many users can update simultaneously; ensure users know what activity is tracked

Timeline: e.g. Facebook news feed;

Period Reports: inform users at regular intervals of relevant changes/actions; weekly what happened in the community - brief;

Aliveness Indicator: show an indicator on the virtual environment that reflects user's activity

Conclusions:

It is about identity; the more I know about the others, the more I feel engaged in/by the community; Features for more advanced users will scare off less advanced users; overlap the experience level profile with the adoption of the features; Foster personalization, production and sharing of content; Plan the social interactions

Scalable Platforms: Can never know when your community will explode; can't predict; development, support, moderation; Open and well documented APIs; the Social Graph;

I made a commitment to myself to be a better, more regular blogger. I'm in Europe right now, heading to Geneva next week for the LIFT Conference for my second year. Described as a conference dedicated to exploring the social impact of new technologies, LIFT is fantastic - great sessions, big beautiful brains, fun interactive art and yummy fondue - what's not to love? I will try to blog from LIFT this year, or you can follow me on Twitter.