Dave Pollard on the art and science of Weblogging.

	Monday, December 21, 2009

This Blog Has Moved After nearly 7 years at this site, How to Save the World moved on December 20, 2009 to a new WordPress-based site. Please change your bookmarks/favourites to http://howtosavetheworld.ca/ First time you visit the new site you can resubscribe to How to Save the World's posts (RSS feed) in your aggregator and/or by e-mail, on the right sidebar. My brilliant brother Alan has moved the entire archive of 2,500 posts, and 14,000 comments, to the new site, so everything can be accessed on the new site right back to the start of the blog in 2003. In the transition, some font sizes came out a bit wonky (my old text editor used some old html conventions that are no longer supported) and there's a bit of clean-up to do, but if you notice anything terribly wrong, please let me know by e-mail. Thanks for your patience during the reconstruction period, and for putting up with the old comments server -- the new one is much better. 5:35:37 PM  trackback []  comment []

	Sunday, September 13, 2009

Google Wave (continued): The Conversation Becomes the Process, and Even the Product Back in June, I wrote about the new (it's being rolled out, slowly, starting this fall) GWave product as representing "the wikification of conversation." The more I think about it, and play with it, the more I become convinced that this tool will not only revolutionize how we communicate on-line, but how we work. And by "work" I mean everything we do collaboratively that isn't done face-to-face. Just to re-cap, here's a story from the previous post that illustrates how GWave works: One of our tasks is to provide guidance on how the transition of Canadian companies to IFRS (the new global accounting standards) will affect IT departments, and specifically how financial and reporting systems will have to change to accommodate these new standards. We've prepared an online training program (a webcast), a recorded interview with some IT experts who have implemented IFRS in Europe (a podcast), and an article in our association magazine. These three resources have been posted to our website, but we're struggling to get the intended IT audience to visit the site, because they're not aware of it. Marketing is, alas, not our strong suit. Suppose we had done all of this in 2011 instead of 2009. In 2011 we will have access to Google Wave, a new tool that integrates the functionality of e-mail, IM, wikis, blogs, Twitter, and other social networking tools. Here's what we would do instead of our 'IFRS for IT' web page, and what might happen as a result: We set up a 'wave' (a container for a conversation) entitled 'IFRS for IT'. We post a text summary of the webcast, podcast and article to the wave. We embed the webcast, podcast and article (not just links to them) below the text summaries. One of the audience members of the webcast and podcast, who has put these two recordings through a voice recognition software tool, posts a text transcription of them underneath the embedded casts. The built-in Google Wave semantic spell-checker auto-corrects spelling and homonym ("there" vs. "their") errors. We use the built-in Google Wave translation tool to simultaneously post a French language translation of the transcriptions. The twelve of us (the 'core group') involved in the project each independently "subscribe" people and groups we think might be interested to the wave. They receive the entire 'conversation' to date (the content and messages in the above steps). They can, if they wish, 'rewind' it and see each step as it was added in turn. Several of the invitees post IMs right in the text of the articles and transcriptions -- comments, clarifications, suggestions, and questions. The entire wave is a wiki -- people have full 'author' privileges to make changes (which are ascribed to them, and which can be reversed or amended, wikipedia-style, by a member of the core group if necessary). Other invitees, and core group members, join in the conversation, adding replies to the questions and to the suggestions. A whole new section of the article, dealing with specific IFRS IT issues for the banking industry, called a "wavelet" is contributed by one invitee, who invites other bank IT executives to contribute to this 'wavelet'. One banker embeds a YouTube video in the wavelet, a transcription for it is added, and several discussions about it ensue. One invitee solicits 'best practices' in transitioning IT departments to IFRS, and posts a 'form' (essentially a database) for replies to the invitation, using the built-in Google Wave form generator. Within days, fifty practices have been posted to the database. Some people begin and reply to conversations about some of the specific practices in the database. Someone starts a Twitter tag called #IFRSIT and, using the Twave widget of Google Wave, embeds a real-time feed of tweets containing this tag into the wave. One of the bankers wants a conference call on IFRS IT implications for that industry. He posts a form soliciting participants for the call, several people enrol, the call is scheduled and held, and a recording and transcription of the call are immediately posted to the banking industry wavelet. Some remarkable things have happened here. There is no marketing involved. People invite people who invite others, and all are immediately included and engaged in the conversation. They can subscribe to the whole wave or just wavelets. They can have sidebar conversations, with full discretion over whether they are public or private. There is a complete, organized transcription of the entire 'conversation'. The conversation is collectively managed and collectively edited and formatted to suit the needs of the self-selecting participants, and it's easy to follow the threads. Updates and notifications occur in real time, and several people can be changing any part of the wave at the same time. With Google Voice (also new from Google), voice conversations can be recorded and transcribed and fed into the wave as well. Now suppose you have decided upon a new project, that involves activities such as project team selection, doing a needs assessment, conducting research, brainstorming to develop innovative solutions, pilot testing, sourcing supply, production, logistics, communication, measurement and evalution. This could be either for a commercial project, or analogously for a community improvement or other not-for-profit project. How might this project be enabled by the use of GWave? Let's assume this is 2011 and that GWave has become ubiquitous -- just about everyone has it on their desktop. Here's how the project might evolve the old way, versus the new GWave enabled way. First, here's a typical commercial organization's new product development process, the old way and the new way: Project Phase 2009 Process 2011 Process 1. Selecting project team Project director hand-picks team of employees. Invitation is sent to initial list by GWave, passed on to others. Team members volunteer and are approved by director. Team includes employees at all levels, customers, suppliers and other stakeholders, as well as members of the company's internal innovation group, a total of over 100 people, mostly volunteers. 2. Needs assessment Marketing is assigned to do a survey of 20 closed-ended questions to assess needs and appetites for 5 proposed new products on a 10-point scale. The self-selecting team members interview others through GWave voice, IM and other tools using open-ended questions and 'what ifs'. A total of 40 unmet needs are identified, along with over 300 ideas, challenges and criteria to consider in addressing them. This entire archive is captured and embedded in the GWave. 'Wavelets' for each of the 40 unmet needs are established. 3. Conducting research Research department does a SWOT analysis of competing products. The research and SWOT analysis has already been done as part of the phase 2 teamwork. 4. Innovating solutions New product development brainstorms and designs  a total of 15 product alternatives that deliver on the needs and new product ideas identified in phase 2 and exploit the competitors' weaknesses identified in phase 3; they also include some ideas from the company's internal innovation group. New product development has been involved in the conversations on each of the 40 unmet needs from the outset. They coordinate both online and real-space brainstorming sessions on each of the 40 unmet needs; the total number of people subscribed to the wave and wavelets jumps to over 400. A total of 125 product alternatives are surfaced, mapped to the unmet needs. The team members self-select online into technical feasibility, strategic fit and profitability assessment teams, and each of the 125 product alternatives is scored on all three criteria. Finally, 22 of these ideas are green-lighted by the company for pilot testing, 35 are put on hold for further assessment the folowing year, and the remainder are 'set free'; anyone who has participated in the wave is allowed to pursue these ideas privately, and eight spin-off teams self-create to pursue some of these ideas. 5. Pilot testing Engineering reviews the designs and, after some back and forth on technical feasibility, comes up with some prototypes, which are market tested. Based on this, management gives a "go" to two new products. Engineering has been involved in the conversations since phase 2, and soon 22 prototypes are available. Marketing has also been involved since phase 2, and they coodinate market tests, drawing on additional testing that various team members agrees to do. The testing is much broader and more comprehensive than was possible under the old system, and it is iterative: prospective purchasers, many of them part of the wave, provide useful 'tweaks' to the prototypes which are then re-tested. All of the testing is coordinated through the wave itself. Fifteen new products are approved; the other 7 prototyped ideas are added to the 35 "on hold" for reassessment the following year. 6. Sourcing supply Purchasing puts out RFPs to prospective suppliers and selects winning bids. Some of the actual production will be done in-house; the rest it is decided will be outsourced. Many suppliers and prospective outsourcers have been part of the wave since early in the process, so the RFP process is dramatically streamlined and done as part of the wave itself. 7. Production The in-house production is planned for. Equipment is purchased or retooled. Production staff are hired and trained. The products are manufactured and inventoried. Production has also been part of the wave since early in the process, and were instrumental in the decision on which products to make in-house and which to outsource. The hiring and training of new staff is coordinated as part of the wave itself. The products are manufactured and inventoried. 8. Logistics Logistics arranges distribution to and warehousing with wholesalers and retailers. Logistics, and key distributors, wholesale and retail customers have been part of the wave since early in the process. They have already been discussing logistics, distribution and approximate order sizes in their own wavelets attached to the wave, so formal contracts can be fast-tracked. 9. Communication Advertising and other communications go out about the new products. Prospective customers have already been virally marketing the 15 new products, and have fed back responses and ideas to the marketing and communications groups, right on the wave. The formal advertising and communications programs capitalize on this. 10. Measurement and evaluation A budget is established for each new product's expected unit sales, revenues, variable and fixed costs, profits and ROI, and compared against actual results. Customer satisfaction surveys are carried out. Returns and repairs are monitored. This phase is unchanged by the introduction of GWave; see process at left. 11. Customer affinity program The company has not traditionally had a customer affinity program. Customers develop and subscribe to GWaves around each of the company's products. They use them to share information, to rate and rave or complain about the products, to surface ideas for product improvement, and to develop 'wraparound' products and services (for example, product add-ons, extended servicing, get-togethers of more rabid customers). The company monitors and participates in these waves but doesn't 'own' them. Now let's look at a 'greening our community' project, for a municipality of say 100,000 people, again the old way and the new way: Project Phase 2009 Process 2011 Process 1. Selecting project team Project director hand-picks team of municipal employees. The team does an RFP for an external consultant to advise on the project. Invitation is sent to initial list by GWave, passed on to others. Team members volunteer and are approved by director. Team includes employees at all levels, citizens, suppliers and other stakeholders, a total of over 300 people, mostly volunteers. No external consultant is used. 2. Needs assessment No needs assessment is done. The self-selecting team members interview others through GWave voice, IM and other tools using open-ended questions and 'what ifs'. A total of 40 'greening the community' project categories are identified, along with over 600 project ideas, some unique and some borrowed from other communities. This entire archive is captured and embedded in the GWave. 'Wavelets' for each of the 40 project categories are established. 3. Conducting research The consultant-employee team does online research to see what other municipalities of similar size have done.  This research has already been done as part of the phase 2 teamwork. 4. Innovating solutions A project outline is developed. An invitation is sent to local environmental groups and other known interested people to participate in a day-long workshop to review the project outline. Based on this, a program is developed and budget approval is sought. The project is scaled back to the approved budget; it involves public education, some changes to municipal purchasing policies, and funding of several new 'green' NPOs. Environmental groups and local suppliers have been involved in the conversations on each of the 40 project categories from the outset. With their assistance, self-selecting project team members coordinate both online and real-space brainstorming sessions on each of the 40 project categories; the total number of people subscribed to the wave and wavelets jumps to over 1,000. The team members collaborate on the wave to identify value-for-money assessment criteria for project ideas, and each of the 600+ project ideas is costed and scored on these criteria.  5. Pilot testing No pilot testing is done. The group collectively nominates a Project Group Leader for each of the 40 project categories, and under these Leaders a 'catalogue' of project ideas is produced, in decreasing order of value-for-money 'score'. Volunteer projects with passing 'scores' and no cost to the municipality are early-launched. The municipality provides a grant to the team to be allocated, by team consensus, for pilot projects that have exceptionally high value-for-money scores but significant costs or risks. Based on the available total project budget and available volunteer effort, a line is drawn on each of the 40 project category 'catalogues' above which projects are approved, and below which they are deferred for future years' consideration. 6. Sourcing supply Purchasing puts out RFPs to prospective suppliers of public education, and prospective NPO grant recipients, and selects winning bids. All project work from this point will be done by the outsiders with successful proposals. The 'green' changes to municipal purchasing policy are implemented. Many prospective suppliers have been part of the wave since early in the process, so the RFP process for all non-volunteer elements of the approved projects is dramatically streamlined and done as part of the wave itself. 7. Production The suppliers produce and deliver the public education and grant activities. Volunteers and successful bidding suppliers produce and deliver the products and services for projects in all 40 categories. 8. Logistics Not applicable. Not applicable. 9. Communication Promotional brochures, press releases and other communications go out about the new programs. Team members have already been virally marketing the program and its projects throughout the municipality, and have fed back responses and ideas to the municipality's communications staff, right on the wave. The program brochures, press releases and other communications capitalize on this.  10. Measurement and evaluation Program costs are monitored against budget. Taxpayer awareness surveys on the new program are carried out.  This phase is unchanged by the introduction of GWave; see process at left. 11. Customer affinity program Not applicable. Citizens participating in the program develop and subscribe to GWaves around each of the 40 program categories. They use them to share information, to rate and rave or complain about the program, to surface ideas for program improvement, and to develop and promote both volunteer and private-sector 'wraparound' products and services (for example, green products for household use). The municipality monitors and participates in these waves but doesn't 'own' them. The bottom line is that, through a mechanism such as GWave, instead of the communications and conversations about a new project being widely dispersed and unconnected, the entire set of conversations on a project can be captured and disseminated as a single wave, allowing far more participation, self-organization, information and idea exchange and assessment, project coordination, and collaboration to occur, involving a much broader set of interested, creative and knowledgeable people. GWave could be the springboard to Peer Production -- the co-creation and co-development of new products and services by suppliers, customers and others, in a way that will be more responsive to needs, more creative, more customized, better informed and better coodinated than was possible when the participants were separated by organizational boundaries. GWave could prove to be so robust that the conversation actually becomes the process and, except for the parts made of atoms, the product and service too. In business and in public organizations, that would change everything. Category: Communication Technology 11:34:50 PM  trackback []  comment []

	Monday, August 17, 2009

Smart Phones: What Comes Next A few years ago I made a pitch to one of the large cellphone manufacturers to create a smart phone that could, to some extent, become a 'buddy' -- it could remind you of things, monitor things for you, and by interacting with the 'buddies' of other phone users introduce you to people with whom you shared certain affinities. The cellphone company thought it was too wild, and couldn't see the 'business model' (how they could make money from it), so it never went anywhere. Since then, new technologies have made some of what was then impossible commonplace, and presented some new possibilities. So here is a story of what our cellphones might, if their manufacturers aren't too obsessed with profit and legal risk, soon do for you (you can find early demos of all of these technologies online -- I'm not inventing any of this): Karen props her phone on the table in front of her. It uses a combination of voice recognition and lip-reading technology (through its camera) to listen to and respond to her instructions. She reviews her Waves (new and open multimedia conversations) which are projected in large easy-to-read size onto the table, wall, or even holographically into mid-air. She answers or participates in most of them through dictation and voice-recognition instructions, editing them through use of a virtual keyboard, pointer and touch-screen that are part of the phone's projection display; her phone recognizes and translates her hand-movements through the camera. She also takes a look at her Subscribed Content, which includes blogs, wikis, updates to friends' and colleagues' personal home pages and tweets. Most of these are already embedded in Waves, and she comments on some of these and 'subscribes' friends to other Waves she thinks they might be interested in. She also looks at the active Waves that have formed around her own blog articles, and adds to these conversations. She changes her Conversation Status to Available for selected friends and work colleagues, and opens some new Waves, simultaneously carrying on several IM, voice, and video conversations; the people she is speaking with, and the documents and other objects she is sharing with them, are projector displayed. Some of her closest friends she has on Continuous Virtual Presence Status -- they can hear her, and see both what is in her camera image and what she is looking at on her projected display, any time they choose to, and vice versa (a small photo of them appears on her display whenever they are 'with' her). She calls up and plays a full-size projected Virtual Piano, practicing a new song she has writen for a free concert her band is putting on this weekend. She is notified that Ben, a work colleague from Finland, is currently in her town; their GPS proximity-detection software, their scheduling software and their affinity software (which allows you to list people you would like to meet, if and when they are willing and able), have worked together to set up a meeting at a nearby coffee shop in 30 minutes. Karen's phone asks her to confirm both her availability and her order, which will be waiting at her reserved table when she arrives. As she walks to the meeting, she is told about additional special offerings on the menu that coincide with her profile of food and beverage preferences, and she changes her order by voice instruction. Her menu is added to her daily calorie and nutrition counter, which tells her how her consumption fits with recommended daily allowances. The calories expended on the walk are also automatically registered and logged to her exercise program. She also reviews some 'auto-tweets' sent to her by her appliances (an updated grocery list), her home monitoring system (lights left on, windows closed), her plants (some of them need fertilizer) and her cat RonRon (photos taken by his collarcam every 15 minutes, and a view from his current location in the laundry basket). After several similarly-scheduled and coordinated meetings, she goes for a drink with her friend Rayah. They both decide to set their affinity software to Open, and they're discreetly shown photos and shared interests of other people nearby who have also set their status to Open. They agree that a foursome of business travelers from Chile would be interesting to meet, and signal their willingness through their phones. Their invitation is accepted and they are directed to a table at the other end of the bar they're in. The six hit it off well, and Karen and her friend show the visitors around town and invite them for dinner. Karen and one of the visitors begin a romantic relationship. Back at home, Karen's exercise regime is planned and monitored by software on her phone and sensors connected wirelessly to it. She also uses a biofeedback application to help her with her meditation practice and to manage her stress levels. As she uses her rowing machine, her phone projects holographic images of the Thames synced to the speed of her rowing motions. When Karen's away from home, she uses easy-to-pack resistance bands to replace the resistance of the rowing machine, so she can do these same exercises anywhere. The next day, her phone's CarShare program tells her that it's her turn to drive, and suggests the optimal route for her to pick up her three passengers for the morning drive. Her affinity software also tells her what interests she has in common with these strangers, so they have much to talk about. The speed detectors in phones in other cars along her route, and the overhead cameras of the department of transport, automatically feed information to her GPS, advising her of the best route to take. Her account is automatically credited with 'gas money' from her passengers. During a learning seminar that day, she voice- and video-links in several other people unable to attend in person, and the backchannel discussions she has with other participants are relayed to the seminar leaders, who improvise the program to respond to comments from all participants. The backchannel also leads to an impromptu follow-up meeting with several other far-flung participants Karen has never met, who, she discovers, share an interest in one specific aspect of the seminar subject-matter. That impromptu meeting turns out to be more valuable than the initial seminar. After the meeting, Karen accedes to her scheduling software's suggestion that she go grocery shopping. She negotiates the list with the shopping software, which uses economic order quantity algorithms to minimize both running out of items and the number of shopping trips she needs to make. This software also tells her which stores close to her have most or all of what she needs, and the total price. Once she's chosen a store, and even while she's shopping, sensors on the store's merchandise and elsewhere suggest additional or alternative purchases, and give her social responsibility, ecological and unit price data and comparatives on all the products on her list. Her proximity software tells her a friend is in the store, and they chat for awhile and agree to a later meeting. She also picks up items on the list of her elderly neighbour, and has a visit with her when she drops them off. That weekend, Karen participates in a city-wide bike rally and scavenger hunt for a local charity. Her enrollment, selection of team-mates, sponsors and donations for the charity, and play-by-play event instructions are all coordinated through open source software on her phone. A few themes to this coming-soon technology: It's mostly open source, collaboratively developed, free software. It's designed to improve users' social interaction, work effectiveness and time management, not to sell products. And it's developed by millions of people with the time and passion to develop, and essentially give away, extraordinary and innovative software, because it costs almost nothing except time to develop. This is integral to the emerging Gift Economy. Many more people have cellphones than laptops. As desktops have given way to laptops and now even smaller notepad computers, the obvious destination is the cellphone. Technology to do away with the physical keyboard and monitor are already here, so it's only a matter of time. If you want to know what's possible in business and social applications, look to the gaming applications, which are always two steps ahead. The camera-based apps described above were developed first for the Wii and other gaming platforms. Acceptance of these tools will always be a function of (a) ease of use (intuitive), (b) trust (the user has control, not the vendor), and (c) comfort (every new tool no matter how sexy will take a generation to become ubiquitous, because you're only really comfortable with what you've grown up with). The variable pricing model in place in most of the world for cellphone usage (including here in Canada) is an enormous barrier to the realization of these technologies. Many kids now are rationing and finding cheap workarounds to be able to afford usurous cellphone costs for both voice and data. We need to force carriers to move to a reasonably-priced, flat-rate-everywhere rate for cellphone charges. Thanks to Mushin: my conversation with him the other day was the inspiration for this exercise in imagining possibilities. I know some of you have wondered how someone who sees our civilization poised for collapse in this century can be so enamoured of this relatively frivolous technology. Since it's a subject I've been thinking about a lot lately (another of our knowing/feeling/doing disconnects), I'll have more to say about this in an upcoming post. Category: Social Networking 12:25:52 AM  trackback []  comment []

	Thursday, June 25, 2009

Google Wave: The Wikification of Conversation At a meeting of Canadian IT leaders today, I was charged with explaining Google Wave to them. The objective was for them to appreciate how GWave will change the way people in business communicate. I've viewed the videos and some online explanations of the product, which is due for public release in the fall. But none of these really gives the end-user a sense of what GWave is, or does. So I decided to tell a story instead. Here's the story I told them: One of our tasks is to provide guidance on how the transition of Canadian companies to IFRS (the new global accounting standards) will affect IT departments, and specifically how financial and reporting systems will have to change to accommodate these new standards. We've prepared an online training program (a webcast), a recorded interview with some IT experts who have implemented IFRS in Europe (a podcast), and an article in our association magazine. These three resources have been posted to our website, but we're struggling to get the intended IT audience to visit the site, because they're not aware of it. Marketing is, alas, not our strong suit. Suppose we had done all of this in 2010 instead of 2009. In 2010 we will have access to Google Wave, a new tool that integrates the functionality of e-mail, IM, wikis, blogs, Twitter, and other social networking tools. Here's what we would do instead of our 'IFRS for IT' web page, and what might happen as a result: We set up a 'wave' (a container for a conversation) entitled 'IFRS for IT'.  We post a text summary of the webcast, podcast and article to the wave. We embed the webcast, podcast and article (not just links to them) below the text summaries. One of the audience members of the webcast and podcast, who has put these two recordings through a voice recognition software tool, posts a text transcription of them underneath the embedded casts. The built-in Google Wave semantic spell-checker auto-corrects spelling and homonym ("there" vs. "their") errors. We use the built-in Google Wave translation tool to simultaneously post a French language translation of the transcriptions.  The twelve of us (the 'core group') involved in the project each independently "subscribe" people and groups we think might be interested to the wave. They receive the entire 'conversation' to date (the content and messages in the above steps). They can, if they wish, 'rewind' it and see each step as it was added in turn. Several of the invitees post IMs right in the text of the articles and transcriptions -- comments, clarifications, suggestions, and questions. The entire wave is a wiki -- people have full 'author' privileges to make changes (which are ascribed to them, and which can be reversed or amended, wikipedia-style, by a member of the core group if necessary). Other invitees, and core group members, join in the conversation, adding replies to the questions and to the suggestions. A whole new section of the article, dealing with specific IFRS IT issues for the banking industry, is contributed by one invitee, who invites other bank IT executives to contribute to this 'wavelet'. One banker embeds a YouTube video in the wavelet, a transcription for it is added, and several discussions about it ensue. One invitee solicits 'best practices' in transitioning IT departments to IFRS, and posts a 'form' (essentially a database) for replies, using the built-in Google Wave form generator. Within days, fifty practices have been posted to the database. Some people begin and reply to conversations about some of the specific practices in the database. Someone starts a Twitter tag called #IFRSIT and, using the Twave widget of Google Wave, embeds a real-time feed of tweets containing this tag into the wave. One of the bankers wants a conference call on IFRS IT implications for that industry. He posts a form soliciting participants for the call. Several people enrol, the call is scheduled and held, and a recording and transcription of it are immediately posted to the banking industry wavelet. Some remarkable things have happened here. There is no marketing involved. People invite people who invite others, and all are immediately included and engaged in the conversation. They can subscribe to the whole wave or just wavelets. They can have sidebar conversations, with full discretion over whether they are public or private. There is a complete, organized transcription of the entire 'conversation'. The conversation is collectively managed and collectively edited and formatted to suit the needs of the self-selecting participants, and it's easy to follow the threads. Updates and notifications occur in real time, and several people can be changing any part of the wave at the same time. With Google Voice (also new from Google), voice conversations can be recorded and transcribed and fed into the wave as well. Inventing the story above (based on the features described in the Google Wave publicity materials) led me to an Aha! moment: Google Wave is the wikification of conversation You read it here first. I predict this will be the tagline of this new tool, and that GWave will render e-mail largely obsolete. And why would you send an IM or a tweet when it's just as easy to start a wave, and capture and archive the entire multimedia 'conversation', and when waves can be linked together (a tsunami?) Here's another story, this one about (perhaps) the future of this blog: It's May 2010, and I've just agreed to do a conference presentation on Transitioning to a Steady-State Economy and what it means for producers and consumers.  I go for a walk in the forest, with my iPhone and sketch pad in hand. I take some video of the forest, with the voice track of my preliminary thoughts on both the subject of my presentation (what I will say) and the format (I want to make it interactive, conversational). I stop to rest, and sketch out some graphics I'd like to show, and take a camera shot of them. I also retrieve some useful graphics and links from the Web. I set up a Wave entitled 'Mindful Wandering - Thoughts on a Seminar on the Steady-State Economy'. It contains the video of the forest (just because it's beautiful), a GWave-produced, auto-corrected transcription of my spoken thoughts, my sketches, and the graphics and links I've retrieved from the Web. I post the Wave to my blog (this is how I do all my blogging these days). My readers edit, comment on, provide suggestions to, add to, and ask questions about, the transcription of my conference outline, key messages, and graphics. This is interactive -- I'm online the whole time, replying immediately by text or recorded voice, and all the discussions get added to the Wave. Someone contributes a video by Herman Daly, and someone else attaches extensive, highlighted extracts from one of Richard Douthwaite's online e-books. I casually mention I'd love to be able to talk with these two ecological economists. Someone who knows Herman Daly arranges an introduction and time for a phone conversation. I come up with and post the questions I'd like to ask him. Readers suggest additional questions and refinements. I edit them into a final question list. We have the conversation, and it's recorded and transcribed, and posted to the Wave. Now I'm ready to finalize the presentation content. I create a mindmap of the presentation, and link it to various parts of the Wave. Then I reorganize and clean up the Wave to mirror the mindmap. All of the changes in the above steps show up immediately on my blog, since by now blog 'posts' have been replaced by blog 'waves'. I 'perform' (using my webcam) my presentation, and produce a simultaneous transcription of my talk. I post it, in pieces, to the Wave, so that it's sync'd to the graphics. Now anyone who can't attend the presentation can see/hear it all, and those who prefer the text over the spoken version can opt for that instead, or in addition. I muse with my readers about the format for the presentation. Should participants be expected to watch/read the Wave version of the presentation in its entirety before the conference, so that we can spend the whole session just talking and answering questions? Should I just 'play' the presentation, in sections, on the big conference screen, and then entertain questions and conversations during the breaks between sections? Should I 're-enact' the presentation, live, at the conference, a kind of lip-sync'd version so people get to look at me and not just the screen?  There's lots of discussion, but the conclusion is that, since it's a live conference and since the audience can't be expected to view the Wave in advance, I'll have to 're-enact' what's already on the Wave. I feel like Vanilla Ice but that's what I do, and thanks to all the input from my readers, it's a big hit. The live conference session is recorded, but the only part of the live session that actually makes it into the Wave is a transcript of the Q&A.  We all wonder how long it will be before such conference sessions are replaced entirely by 'live Waves', where 'pre-recorded' wavelets are posted in real time on a 'conference Wave Site', with real-time questions submitted by the virtual 'attendees' queued and answered in real time at designated points in the 'presentation' (or answered after the session if there are more questions than can be answered in the time allotted). We conclude that, precluding $200 a barrel oil, this will not happen soon, because the real value of these conferences, as has always been the case, is the networking that occurs in the corridors between and around the actual presentations. If you're sufficiently familiar with Google Wave, I'd love your thoughts on how fanciful the above story is -- it sounds as if GWave should be able to deliver all this functionality, but perhaps my expectations are too high. On the way home from the meeting I listened to a great David Weinberger podcast from TVO, dating back to February. It just reinforced my sense that GWave, by adding context to conversations, will revolutionize the way we communicate. Highlights from David's presentation: We worry too much about the 'echo chamber' danger of the Internet. There is no evidence that we ever sought out people with conflicting views before the Internet came along, nor that we change our minds once we've made them up. Conversation is essential to how we self-identify. Machines and digital computers may be useful metaphors for how our DNA and brains work, but they are not how our DNA and brains work. The Internet has altered long-held views that knowledge is orderly, order-able, the same as 'content', more than mere 'opinion' or 'belief', or that any bit of knowledge fits in one best 'place' (under a specific 'topic' in a taxonomy or in a specific location). "Philosophy is not a topic". It's easier and preferable to filter stuff on the way out (user discretion) than on the way in (provider discretion). "Expertise doesn't scale." Mailing lists (the wisdom and conversation of a group) are inherently smarter than experts. Broadcasting, politics and advertising all oversimplify (dumb down) complex subjects to "maximize information ROI". Conversations and blogs add back the complexity, and in so doing add context and meaning. Our modern perception that we (can) live inside our heads is "psychotic metaphysics". "Knowledge is never done....We never get anything right, and then we die....[so] transparency is the new objectivity." Knowledge by itself, without context, is worthless. Its value is as a means to understanding. Category: Communication Technology 10:21:16 PM  trackback []  comment []

	Friday, June 19, 2009

The Psychology of Twitter: Doubly Addictive OK, let me start by saying I'm a Twitter user and fan. But something about it disturbs me. Like the near-defunct Usenet, the now-collapsing MySpace, and the soon to collapse under its own weight Facebook, Twitter doesn't make sense. For that reason, I predict it will soon suffer the same fate, replaced by tools that will do all the same good things, and which do make sense.   For those unfamiliar with Twitter (and users who haven't really thought about it), here is what Twitter is in a nutshell: Twitter is an instant messaging tool where the recipients of the messages are determined by the recipients, not by the sender. HOW TWITTER WORKS So you sign up, and send a bunch of IMs (instant messages -- short electronic messages that are delivered immediately and pop up on the recipients' laptops or phones) into cyberspace, into the void. Just like a newbie blogger, no one reads what you write, at first. Eventually some people will 'find' you and subscribe to your messages ('tweets'), and if they like them, they'll rebroadcast them ('re-tweet') to the people who subscribe to their tweets. Some of those second-hand readers will like what you say and subscribe to your tweets. When you subscribe to others' tweets, some of them, out of curiosity or a sense of reciprocity, may subscribe back to yours. You can post your Twitter name on your blog, and on your Facebook page, and send it out to your friends to get them to subscribe. This way, you build an audience. Just as there are 'A-list' bloggers with thousands of readers, there are 'A-list' tweeters who have audiences in the tens of thousands. And just as there are organizational and ghostwritten celebrity blogs, there are organizational and ghost-written tweeters, trying, mostly futilely, to market their product or information using this new medium. Unsurprisingly, there are bloggers who simply 'tweet' links to their latest blog posts. Tweets are supposed to be conversational (more than half of them are replies to previous tweets, identified using the @ sign before the original tweeter's username), so most of these lazy 'broadcasting' machinations are considered bad 'twitterquette', and generally fail. (Businesses, spammers and people trying to sell stuff through Twitter, please take the hint and stop). The catch with this reverse-IM tool is that the maximum length of a tweet is 140 characters, including the characters needed to acknowledge the original sender(s) in a re-tweet. You can extend this somewhat by linking to something longer by putting its URL in your tweet, or linking to a photo or video or song with its URL, and if the URL is long you can use any of the URL-shortening services to save precious characters. But there is no effective way to link tweets together to make a longer one. Brevity is everything. If you can't say it in 140 characters, it doesn't belong on Twitter. WHAT'S WRONG WITH TWITTER What you end up with, mostly, is a lot of cryptic messages you don't understand. In the process of squeezing your message to 140 characters, you will generally squeeze almost all of the meaning out of it. For example, when I've read the rapid-fire tweets of people tweeting from conferences, one highlight sentence or quote at a time, I've found it impossible to fathom most of what the tweeter found remarkable, or even what s/he meant. There is simply no context to provide meaning, so most of what you read is meaningless. What's worse, when most of the tweets of people you've subscribed to are replies to (or retweets from) people you are not subscribed to, it is almost impossible (and rarely worth the effort) to chase down the original thread to understand the context for the reply. In fact Twitter is in something of a war with users, since they have tried to reduce volume by suppressing these replies, so you only see replies to you, and to people who both the replier and you subscribe to. Users have developed ways around this, of course, and the war continues. Currently I 'follow' (subscribe to the tweets of) about 100 people, close to the Twitter median, who between them produce about 10 tweets an hour. I probably find time to read about 1/4 of the tweets they send. On top of this, I try to read any replies to my own tweets (those that have @davepollard in the message are displayed for me on a separate Twitter tab), and I read any direct messages sent specifically and only to me (traditional IMs, displayed on yet another separate tab). I have about 700 'followers'. The protocol for IM replies has generally carried over to tweets: Unlike e-mails, which you are generally expected to reply to, it is perfectly acceptable not to acknowledge or reply to IMs, and the same applies to tweets. This is one reason why I like IMs and Twitter more than e-mail. Based on some research I did the other day, I would estimate that, per year, for 240 hours' time investment, I scan about 36,000 tweets (most of them unintelligable) and in so doing discover about 200 interesting or memorable thoughts or ideas, identify a third of the content of my Links of the Week blog posts, have perhaps 20 useful follow-up one-on-one conversations and maybe make two new real friends. If I spent that 240 hours in other social activities, would the yield be higher or lower? WHAT TWITTER SHOULD BE Twitter has been important in emergency relief and grassroots organizing, and the reason for this is simple: It is currently the most globally ubiquitous real-time text communication tool. But the tool we should have is an IM tool that allows you to send real-time messages either to people on your IM/e-mail contact list, or to people who subscribe to your IMs, or both. This would be a simple add-on to GTalk or other IM tools, and it would render Twitter obsolete because it would have all Twitter's functionality, and more, in an existing ubiquitous tool. Tweets you receive would simply appear alongside your other incoming IMs, and you'd likewise be able to send tweets the same way you send IMs. In fact, Twitter originally did have an IM interface for GTalk like the one depicted above, but Twitter (perhaps fearing that IM tool developers would soon co-opt and obsolesce Twitter's functionality) disabled that interface some time ago. Such a send-publish-and/or-subscribe IM tool would also have great value within medium-to-large organizations, and could substantially replace internal e-mail. It appears that Google Wave will incorporate it, but expect to see IM and Twitter-type reverse-IM tools integrated within the next few months. It just makes sense. THE PSYCHOLOGY OF TWITTER What is it that makes people sign up for, and spend time with, Twitter? I think there are two reasons: Twitter is addictive to news junkies: The people who go through withdrawal or feel guilty if they don't read the morning paper cover-to-cover every day. The ones who look at every incoming e-mail immediately, even during conversations, meetings, or while driving. The ones who have more information in their RSS feeds than any human could possibly hope to absorb. The ones who are hooked on all-news stations with live coverage of the latest crisis, and watch as nothing happens for hours, taking in all the inane, meaningless and unactionable nearby-rooftop reports. For them (OK, us) Twitter is like crack -- live instant updates from real people right there, at the earthquake site, or at the ZXZZ technology conference. People are looking for attention, appreciation, affirmation, connection, and recognition. In short, we're looking for love. Twitter lets us get it (or feel like we're getting it) quickly, safely, and anonymously. This is addictive self-gratification. Having hundreds or thousands of people 'following' us is consoling when our self-esteem is low. Getting people we don't know to reply to us affirmatively is consoling when we're lonely. With text, with all the wisdom of the Internet (and other tweeters) to draw upon and quote, we can sound very smart, very together. All it takes is a willingness to churn out a lot of short messages and read through mountains of similarly cryptic messages from people we follow, looking for a few to comment on, and we can delude ourselves into believing we're appreciated, we're connected, we're engaging in meaningful conversation, we're expanding our networks, we're recognized, and people are paying attention to us.  As Dermot Casey has pointed out, we've been through all this before, with Usenet, twenty years ago. Tens of thousands of Usenet forums were inundated with millions of short messages, some of them fired off in such rapid succession that they were close to real-time, and the only substantive difference between Usenet and Twitter is that instead of subscribing to a person you subscribed to a group about a particular topic (perhaps Noam Chomsky, or nude celebrity photos, or how to commit suicide painlessly). Your posts were supposed to be 'on-topic', but as long as you marked the article 'OT' (for 'off-topic') it was OK, and what happened is that people formed clique communities where the people in the group, and their relationships, were more important than the ostensible topic. What happened to Usenet, and many other online forums that played around with social networking in those Web 1.0 days? Mostly, people realized that they weren't building real relationships, real friendships, that the information they were exchanging was ephemeral, and that the online relationships they thought they had built were more imagined, idealized, than real. This same phenomenon is evident in Second Life, where text is preferred over voice for communication because it's easier to sustain the illusion of an idealized, reciprocal, perfect relationship. With online tools like this, we're clever, we're witty, we're knowledgeable, we're articulate, we look good and sound good. We're always on. Totally addictive. We are inundated with mainstream media that feed a dumbed-down populace with propaganda and pap. It is not surprising then, that a medium like Twitter, with its immediate, unrehearsed, uncontrolled, authentic messages would have enormous appeal, and feed our addiction for information at the same time. Likewise, we live in a fragmented, stressful, isolating world, where despite the crowded cities most of us live in we find it difficult to make true connections, to build deep and enduring relationships, to be appreciated and get attention for who we really are and what we do. So we shouldn't be surprised, or ashamed to admit, that real-time, social networking tools like Twitter can fill an emotional void in our lives, a craving for connection. Is this harmless? For most people it probably is. We all have our little addictions, whether it be chocolate or sudoku. Recreation is good for us, and forty minutes a day Twittered away is pretty benign, I'd guess. It depends on what you'd do with that forty minutes a day (or more), if you weren't tweeting. I think what we will see, over time, is that our longing for authentic, one-on-one connection, and for context, will win out, and wean us off tools like Twitter in favour of richer and more personal ones. And the technology, with bandwidth and memory becoming almost unlimited and free, will enable us to approximate genuine physical meeting and rich face-to-face conversation more and more. There are a few tools out already that hint at what this might look like. The challenge is not in making the conversation real; it is in finding the people with whom to engage in conversation. This is the real magic of Twitter, and of other 'tools of discovery' like blogs: The onus to search for someone of like mind is moved from the searcher to the audience. The people you're looking for find you, based on your simple advertisements, in Twitter, blogs and similar media, that say, simply: Hey, world, this is me! Anyone want to connect? Category: Communications Technologies 9:56:13 PM  trackback []  comment []

© Copyright 2009 Dave Pollard. Last update: 12/21/09; 5:35:59 PM.