Keeping up with social media is a real challenge these days. However, one theme seems constant whenever you read blogs about social media, especially among marketers and so-called optimizers who target, target, target to drive, drive, drive customers to their client’s social media asset, i.e. video, blog, community, etc. You would think advocates of social media are Rowdy, Gil, Jed, or one of the other actors on Rawhide.
Howard Rheingold provides an interesting video podcast of an interview with Mark Elliott regarding the use of wikis in city planning, particularly in Melbourne. The Melbourne wiki uses the tagline, “the city plan that anyone can edit.” Mark indicates there were 500 registered users and 7,000 visitors to futuremelbourne.
I’m not convinced by Mark’s concept of stigmergy, analogizing patterns of insect behavior — specifically ants — to the activity of participants in a wiki. However, his overall point about the benefits of using wikis for collaboration between public officials and the community in civic projects, such as the New Zealand police act wiki, is persuasive.
Screencasts are effective ways to share ideas, images, concepts, experiences, and a range of information for a variety of purposes including eLearning, collaborative problem solving, or just fun. I just ran across a new technique for doing screencasts called a Flowgram. Eric Schonfeld over at TechCrunch describes it as,
…a full-screen player with what appears to be a screencast with a voiceover. Except that you can control the pages by scrolling up and down, watching any videos that might be on the page, or clicking on the live links (which takes you out of the Flowgram to that Website, but if you hit the back button it picks up where it left off). You can also add comments and share the Flowgram via a widget…It’s an interactive screencast, a way to synthesize the Web by pulling different pieces together The voiceover acts as the glue. It can be used for slide shows, travel guides, tutorials, sales pitches, or just to explain something to a friend.
I’ve signed up for the private beta access program so I can build a few Flowgrams of my own to get a better sense of how this tool compares to applications like Captivate or Camtasia. After briefly interacting with several of the Flowgrams available it looks quite promising. I like the ability to scroll pages as well as play videos embedded in pages presented in the Flowgram. I’m not sure why the developers decided to navigate out of the Flowgram when you click on a link that takes you to a page outside the Flowgram, rather than opening a window to view it, but when you click the back arrow the flow of the Flowgram seems to pick back up where you left it. Take a look at Flowgram for an overview.
Share this post…
Do you know who is on your team? It seems like an easy question for people who work in large corporations to answer. Reviewing Socialtext People recently led me to remember an interesting study I read a few years ago that reported rather surprising findings with significance for Enterprise 2.0, and to the lead-in question above. The study, largely ignored in the social networking literature, pointed to a clear limitation to collaboration in national and global corporations that organize teams geographically distributed.
Mark Mortensen and Pamela Hinds published a chapter titled, “Fuzzy Teams: Disagreement in Distributed and Collocated Teams”, in an edited collection called Distributed Work way back in 2002. The book itself contains an interesting range of studies on the challenges involved in organizing work across members of geographically distributed teams. However, it seems to me that Fuzzy Teams offers a key insight into the way Enterprise 2.0 applications, especially wikis, help to meet challenges in organizing distributed work that are often overlooked. Read the rest of this entry »
As a member of the boomer generation, a recent post by Stewart Mader on the use of Enterprise 2.0 at Wachovia caught my attention because it relates to a range of ongoing discussions on the relationship of age and innovative uses of technology in supporting collaboration.
Stewart points approvingly to a recent InformationWeek article on Wachovia’s use of wikis, blogs, and social networking to develop mutual mentoring between younger workers and senior staffers. Wachovia is assigning younger staffers to mentor senior staffers about the benefits of using collaborative networks. However, Stewart goes on to qualify the point of such mentoring with the following insight:
We often talk about how the millennial generation has an advanced grasp of these social and collaborative tools, but just half of the story in my opinion. I see enterprise 2.0 tools not as the exclusive domain of youth, but as a better connector for multiple generations, so that wisdom, tacit knowledge, and business know-how from the experienced can be shared with younger workers.
The point is bolstered by recent research, though with a couple of crucial caveats. Read the rest of this entry »
Wikis are largely about creating, organizing, and sharing knowledge. Most people think of textual and static graphic information created, organized, and maintained by groups of people when they consider what makes up a wiki. The integration of visualization tools is one of the more interesting developments in wikis recently though. As an example, the Thinkbase tool provides an ability to visually navigate and explore Freebase, an open, shared database of the world’s knowledge. The Thinkbase Blog is a good resource for learning about Thinkbase.
I know, I know, you are probably saying “Can’t he talk about anything but seamful and seamless design?” Well, I’ll get off that topic soon. Yet, in the meantime, here are a couple of examples of how a seamless interface to the user of a device is a seam for control by someone else. One basic point of those arguing for seamful design is that the user of the device, rather than the developer, is the agent whose control over the device needs maximizing by designers. Those who contend the goal of a seamless interface is a well-intentioned effort to relieve those using ubiquitous mobile devices from information overload often fail to mention up front that all connected devices provide seams of control. You might say that proponents of seamful design are the Libertarians of experience design, contending that control over the agency of any device belongs with the person who uses it, especially if they own it. Read the rest of this entry »
Part 1 promised that Part 2 would discuss Greenfield’s Everyware. However, before we get to that discussion, a few considerations on Moreville’s Ambient Findability are needed. The discussion of Moreville’s book will make clear the contributions offered in Everyware.
Greenfield and Moreville express skepticism about the ability of artificial intelligence to solve basic problems related to ambient findability and Everyware, what Greenfield terms ambient informatics. As more and more ordinary devices are available for people to engage as they go about routine activities, the sheer challenge of finding the right device among those available to support an activity promises to develop into a significant hurdle. Both authors recognize the challenge. Yet, Greenfield and Moreville both fail to discuss straightforwardly the challenges faced by attempts to manage relationships between connected devices. Read the rest of this entry »