Sony research group demo an 'augmented surface'
Spurred by Miranda's reference to Malcolm Gladwell's article, The Social Life of Paper and other articles on the subject ( MIT Press' The Myth of the Paperless Office, Passion for Paper and Bill Gates' paperless working methodology), i thought i'd throw in my $.02.
I really can't see a case for paper in the workplace outside of enhancing co-located group sessions/workshops (i've described some below - Gladwell points one out as well). I'm trying, but i don't see it. At least for software development, though i believe this view is defensible for a range of industries.
One of paper's great advantages lies in its physicality. As a result of its portability it can potentially radiate information to multiple people in different locations without any technology requirements other than a pen/pencil. It's spatially flexible and provides a low barrier to authorship.
When you access paper-based information, subtle authorship traits are clear (handwriting and drawing styles communicate myriad things to us which digital typography and rigid outlines do not). Paper media retains these traits so well because the paper/pen combination provides one of the greatest interfaces mankind has ever come up with. It allows for much self-expression. From an accessibility perspective, the printed press gives you high resolution fonts you can take to bed with you. No eye-strain included.
So it's not all bad for paper. But the paper-less office isn't a myth. I don't use any paper at work. The only pieces of paper i have touched involve HR processes such as holiday forms (arcane admin rituals).
I use OmniGraffle or a whiteboard for quick visualization of ideas. Whiteboards beat paper hands down for radiating information to groups in the workplace (see Cockburn). Textual collaborative, dynamic information resides in the web browser - accessible by all, manipulable at all times. Wikis, chat-rooms and project management tools sit there. The browser is our core communication medium.
For notes, I have OmniOutliner which i also use to deconstruct large problems into identifiable tasks. Technical designs can be drawn in applications pretty quickly. These designs can then be uploaded for others to comment, in their own time. I can re-organise and re-prioritise my tasks at a keystroke. I can take notes on a meeting with others, during a presentation (backchannel). Put all this together and paper is starting to look a little ragged.
In the processes of archiving and organising (search/sort), paper also makes a weak case for itself. Digital alternatives exist for tracking ideas, dialogues, designs, tasks and most other everyday information. The notion that paper is a more secure information storage mechanism is also often mistaken and i can only assume comes from a misunderstaning of modern technology (stories of giant electromagnetic guns and hackers making people nervous).
In contrast examine the issues that arise from using paper instead of digital tools, and accumulate these over time (no versioned history of events, unsearchable, restricted ability to re-organise, closed access). It's a cludge. Moreover, it's potentially harmful; paper is, after all, the medium of bureaucracy. Solutions to everyday design problems require agile, accessible information. You need to be able to mix and match approaches, sculpt them in a group environment and change them on the fly. Your chosen media should reflect this.
The only place i see for paper in software dev is in CRC cards and planning sessions (blitz planning, sprint planning or xp planning games) - specialized techniques peculiar to the field (though kaizen-blitz sessions are widespread in the manufacturing industry). Broadly speaking, these are group processes taking place in one location, in which members pursue a single goal of identifying and organising many discreet chunks of information in real-time. Paper's spatial properties come to the fore here. Note that the paper is often thrown away after the session is complete and results captured.
All of these group operations could be carried out on a screen, but screens are interfaces to personal computers, which are designed with the individual in mind. Personal Computers are not for groups (as the name suggests), and a network of such computers does not constitute a true group interface. Turkle has alluded to the solipsistic design of the modern computer in the past. I think as better groupware interfaces are commoditized, such as augmented surfaces (sony research video), the use of paper even in these group processes will become optional and ultimately deprecated.
Spimes are manufactured objects whose informational support is so extensive and rich that they are regarded as material instantiations of an immaterial system.
- Bruce Sterling's southern drawl re-enforces the notion of a spime in his Internet of Things eTech keynote. It's an insightful, articulate rant on the language of emerging technology, how RFID will replace barcoding and the state of physical objects in the near future. If you didn't catch this talk a while back it's well worth the podcast.
Getting your head around all the WS-* stuff is like trying to eat an elephant.
- Joe, commenting on Loud Thinking.
So David has pointed out the reality split between the industry led WS-* 'standards' pap and Restian principles. I deal with XML-RPC & Soap API's on a daily basis, and i find our Soap calls in particular over complex. The move from procedure call to state transfer is in sync with the natural architecture of the web. It forces you to think about your web application as an open data architecture from the offset (e.g. Delicious) and that can only be a good thing.
Did i say simple & open?
In a network, simple & open standards always win. This is true at all levels of the stack - from protocols to data architectures to data formats. This is the lesson. We are learning it.
A call to bloggers. Start writing 'how to switch from MS ____ to ____' articles. Simple. Effective. Some ideas:
- How to switch from Hotmail to Gmail
- How to switch from MSN Messenger to a Jabber account
- How to switch from Office to Open Office
- How to switch from ie to Firefox/whatever.
- How to switch from Entourage/Outlook to Mail/Thunderbird (ahem) *
- How to switch from Frontpage to Notepad/BBEdit (um)
- How to switch from Windows to Linux (uh, perhaps a list of links here will do)
- How to switch from Intel to PowerPC (quick! in the next 12 months)
* I'm doing Entourage -> Mail.
They should cover data import/export and the enhancements that come as a result of the switch. They should cover both Mac/PC users if applicable. Screenshots would be nice.
This all sounds basic to developers, but the most important thing here is that MANY PEOPLE are still locked on MS software, mainly due to having an abundant amount of information zipped up in it. I'm amazed every time I see a perfectly smart person using Hotmail. They are often unaware that some software in the world is designed with the user's well-being, flexibility and freedom in mind. All they need is a little guidance and they'll happily switch. Tutorials exist, but this iniative could be useful if approached the right way.
It'll take a developer 30 minutes to knock up an article. It could switch dozens of people. You will sleep soundly for an entire week. Come on, don't tell me you're busier than me. I won't believe it.
The deal is to aim this at a completely non-tech audience without patronizing people.
Everyone can obviously post on their own blogs but I'll try to aggregate links here. The idea is to synchronize the posts to go up on an MS Reshuffle date. I'm suggesting an MS Reshuffle date of 15th July, 2005.
If you know anyone who might be interested in participating in this please direct them here.
Update - New Ideas
- Windows Media Viewer to VLC
- .NET to Open-source architectures
