Introducing impi! - Pierre Bienvenüe

May 28, 2016 · · Posted by Greg Lloyd

ImageI'm happy to introduce Pierre Bienvenüe, founder of impi Business Improvement Solutions Pty, a South African business improvement firm and TeamPage solution partner since 2012. Pierre has great experience in helping mid-size companies organize and run effective quality improvement programmes. impi! works with clients as partners from concept definition, initial rollout, through improvement of the quality program itself. Pierre has worked with Traction Software and clients to develop templates, plug-in extensions, and a methodology for using TeamPage to support the impi! business improvement model, with solid results to report. This post is an introduction. You'll hear more from Pierre as an expert guest blogger on this page, in Traction Software's TeamPage customer forums (free registration), and across the web.

Pierre Bienvenüe writes: Since 2012, the trigger to develop impi! was primarily the realisation that mid-size companies couldn’t afford quality improvement programmes à la TRACC, 20-Keys, Mission Directed Workteam or BMGI offering. Furthermore, they didn’t want an improvement programme but needed a business management system (BMS). Something that would outlive the consultant… (btw they didn't want training either, but coaching.)

Additionally, for a few years now we have experienced the convergence of Quality Assurance and Continuous Improvement. The latter becoming the enabler of the former. Since July 2015, I've had the privilege to contribute to the ISO 9001:2015 implementation at one of my clients (my official guinea pig!) under the guidance of one of the contributors to the new version of the standard. impi! has proven itself to be a solid and flexible platform to work through the implementation and manage the required documentation. As a result, the current impi! solutions are supportive of the new standard.

Why choosing mid-size companies? Their systems are usually less mature than that of large corporations and therefore, the implementation of an IT system underpinning the BMS wouldn’t usually clash with legacy systems. Also, most importantly, top management in mid-size organisations are more likely to get their hands dirty coaching the teams (changing the nappies) rather than the consultant-nanny who too often ends up raising the kids by implementing the programme bottom-up (which always fails in my experience).

A few concepts to build a business management system

impi! is applying the Lean tools and techniques other programmes offer (and probably not as well due to my limited experience and resources to develop the content). However, there are a few concepts, possibly original, that I’d like to share with you:

1. Integration of document management and improvement, blurring the lines between creativity and discipline, short term operation and long term systemic improvement.

The question here is how to ensure that improvement results in standardisation and standardisation in sustainability. There is always a tension between moving fast in improving and taking time to properly document, train and even audit.

Another tension exists between the daily operation (immediate) and its systemic improvement (essential). Here, a footnote on the Toyota Way led me to Paul Adler's article: “Building better bureaucracies” (see also attachment) on enabling vs coercive structures. And gave me hope that discipline and creativity should coexist in the workplace.

My response to the two challenges is:

  1. A dynamic business model, the Core Cycle, summarised by Drucker definition of management: “the essence of management is to make knowledge productive”. This model helps me to have an integrated view on how a business operates and therefore develop interlocking solutions to build its BMS. I attach a presentation of the Core Cycle, a subset of the foundation course I train my clients with;
  2. A technology (social media for companies: TeamPage) as an enabler of the Core Cycle that provides an integrated work environment, flexibility, ease of use and at the same time provides structure and visibility. With the technology we can have knowledge workers and even supervisors to collaborate, share, task, project manage, create and manage documents, etc.

I experimented and now understand that the technology - social media for companies (Enterprise 2.0) - and the philosophy - the Toyota half-way (see attachment) - share many principles: collaboration, transparency, accountability, emergence (pattern of improvement: pushing the knowledge threshold by doing).

2. Management needs to become a routine, implementing a routine is a project, starts at the top, everyone is responsible for improving the organisation. entrench the routine of change before planning to roll out at operational level. Rather than starting an improvement programme - typically with business goal alignment, we first need to build the structure for improvement.

I found that a two-weekly cycle of project review sets up a pace for the company and puts the right pressure on both top management and project leaders. I borrowed that idea from a 6-sigma project management method.

Everyone with a computer runs an improvement project (initially) related to their processes. The project leader gets some face time weekly (20 to 60 minutes) with a sponsor (the process owner = top management). Every two weeks, project leaders stand up and give an account of progress before top management using TeamPage. This is show time. Coaching and learning naturally happens. Con artists are exposed. We get to eat together. We celebrate project closure. The improvement champion (internal or external) can use that time for short training time at the point of need (e.g. what the hell is the Toyota Kata? What is a Pareto analysis, how and when to use it?). The forum is also used to get the teams to contribute to the Long Range Planning process.

Then implementation of any system is pushed through that improvement process. It is logged and managed as a project e.g. establishing standard meetings, rolling out KPIs, ISO 9001 implementation, 5S and of course improvement of business and operational processes. So we guarantee alignment to strategic objectives and make the workload of project leaders obvious.

3. Mirror the social media spaces to the actual Mini Business Units (MBUs). Harmonious mix of electronic and manual visual management

We create spaces for the systemic, strategic and selected operational mini-business units. The more the team uses the platform for its daily operation for communicating and tasking, the easier it becomes to use it for project management and documenting: it is the same platform. A bonus feature is that email traffic diminishes. Visual management (e.g. KPI tracking) is still displayed on the walls, yet in some cases is duplicated electronically. Tasking and minute taking is captured live by the team members in the relevant MBUs. Knowledge can also be created in the context of daily activities with threaded discussions. The discussions are usually informal but they are searchable and can be tasked.

4. Use the BMS to provide knowledge

Sharing of knowledge is woven into the BMS. Firstly, in the central repository of standard documentation (Best Operating Practice - BOP), secondly in the project templates themselves (e.g. DMAIC, Business Process Improvement), thirdly in the MBU spaces as described in Para 3:

  1. All impi! solutions are built on TeamPage on a wiki space and are standard documents. Every solution starts with a Policy (the why) and a Standard Operating Procedure (the how). The SOP is the hub that links all the other documents (the spokes). The templates used for these documents are the same that the client can use for their own controlled documentation in their own wiki space called “Knowledge Central”. Two outputs of every improvement projects are a) an operational improvement and b) documentation in Knowledge Central. The project templates used to run improvement projects comprise standard articles that will naturally become elements of the BOP (e.g. SIPOC, business process maps). When the project leader reaches the Control or Adjust part of the project, large chunks of the documentation would have been written. Using the capability of TeamPage simplifies the linking and tagging of documents. The organisation steadily builds its very own Wikipedia, and it’s ISO 9001 compliant. The risk of deadwood documentation is reduced: team members create their own documentation, hyperlinking contextualises the documentation and tagging and search capability ease retrieval of information.
  2. Several templates are available for improvement projects (e.g. PDCA, DMAIC). With each project milestones are associated standard articles e.g. project charter, project checklist, Fishbone diagram, business process “AS IS". To each milestone there are also associated tasks. In each task is a tutorial on its own with tips and links to glossary terms, One Point Lessons (e.g. How to use a risk assessment matrix) or external reference in the public domain, e.g. Wikipedia, Lean Institute.

Finally, here is a one page summary of impi! and the synopsis of one of the three solutions that Traction and I have released thus far and are currently being used at clients.


Voilà - I hope there is enough meat here to stimulate a conversation or two.

Since I have only developed impi! thus far with my clients and for my clients, I haven't started a public website. It will be up this year. Immediately though, I will value the comments and interactions @Pierre on Traction Software's TeamPage server (free registration) or email In the meantime, gazing a last time at the horizon of this South African part of the Indian Ocean, I'm aiming down to the engine room, pondering how I am to navigate this blue ocean.

Chris Nuzum Hyperkult XXV Video | Tripping Up Memory Lane

May 15, 2016 · · Posted by Greg Lloyd

ImageWatch this video of Chris Nuzum's Tripping Up Memory Lane talk at Hyperkult 2015, University of Lüneburg, 10 July 2015. Traction Software CTO and co-founder Chris Nuzum reviews hypertext history, his experience as a hypertext practitioner, and the core principles of Traction TeamPage.

Live video Christopher Nuzum: Tripping up Memory Lane Hyperkult XXV
Adobe Flash required for desktop Chrome or Internet Explorer 10 and earlier.


"Thoughtvectors in Concept Space badge" by @iamTalkyTina my posts |


Tripping Up Memory Lane - Chris Nuzum's written notes for his Hyperkult XXV talk.

Traction Roots - Doug Engelbart - About Doug Engelbart's Journal and Traction.

Original Traction Product Proposal - Hypertext roots and evolution of Traction TeamPage.

Doug Engelbart | 85th Birthday Jan 30, 2010 - "Doug Engelbart sat under a twenty-two-foot-high video screen, "dealing lightning with both hands." At least that's the way it seemed to Chuck Thacker, a young Xerox PARC computer designer who was later shown a video of the demonstration that changed the course of the computer world."

Thought Vectors - Ted Nelson: Art not Technology - "To give up on human understanding is to give up hope, what we call in English 'a counsel of despair.' I think there is hope for much better and more powerful software designs that will give ordinary people the power over computers that they have always wanted - power with complete understanding. But that requires inspired software design, which I believe is art and not technology."

The Work Graph Model: TeamPage style - The social dance of getting things done, dealing with exceptions, and staying aware of what’s going on around you

Introducing the TeamPage iOS App

May 13, 2016 · · Posted by Christopher Nuzum

I was delighted to find that our TeamPage iOS companion app was published on the App Store this morning. We've been enjoying the app for the past few months, and are excited finally to be able to share it with you.

A Simple, Useful Start

We've often thought about what we wanted in a mobile TeamPage app. Our ambition set a pretty high bar.

The app that we released today is not the app we thought we needed to build.

It's the app that we were tired of living without.

It has a simple objective: make it easy to stay in the loop when you're living your life away from your desk. So you can dash off a quick response while waiting in line for a coffee; read and respond to last night's posts on the train; or add an incoming request to your worklist before you turn off the light.

Two Views, for Two Ways of Dealing with Information


TeamPage provides dozens of ways to slice and present information: feeds and dashboards scoped to spaces, projects, and milestones; task lists; section tables; tag change and history views, cross-references and audit trails.

Desktop TeamPage, that is.

We boiled the mobile app down to two views: Notifications and Discussions.

Notifications are:

  • Low volume, focused on what you care about and what you need to know.
  • Great for responding to @mentions, seeing tasks assigned to you, following discussions you've participated in, and tracking activity on projects you own, spaces you subscribe to, and people you follow.
  • Perfect for individual contributors, engineers, and people who prefer to work with headphones on, since it keeps the level of distraction to a minimum.

Discussions are:

  • For when you want to, or need to, scan everything that's going on.
  • Perfect for analysts, support staff, and managers who need to scan for activity of interest and either jump into the conversation or follow up in detail later.

Personally, if it's been a while since I checked in, I review my notifications first, and then scan through discussions.

The list view showing notifications and discussions uses a new unread tracking capability built into TeamPage and synchronized with the iOS application to give you a snippet of the next unread message in the thread, while showing you the avatar of the person who posted it.

The discussions and notifications views are ordered based on how recently the thread was active, so you only need to scan down the list until you've reached an item you've seen before to know that you're all caught up. The yellow highlight on unread items also helps with this, making it very easy to stay on top of what's new.

A New Detail View

The Desktop version of TeamPage uses nesting to visualize replies in context, which works very well for getting the big picture and for threads you haven't read.

proteus view

In the app, to facilitate catching up on the latest additions, we organize the replies chronologically, and use the unread tracking to scroll you down to the next unread reply.

iOS app detail view

We also make it easy to swipe left and right or use left and right arrows to go to the next or previous thread in the list, which makes it very easy to catch up on activity using only one hand.

Two Actions, to Put Your Mind at Rest ⋮

When it comes down to it, when something comes to your attention on your mobile device, you either can deal with it then and there, or you can't.

iOS context menu

If you just need to answer a question, you can use the Reply via Email action to type or dictate a quick reply.

If you need to come back to it later, you can add it to your Worklist, where it will show up on top when you get back to your desk.

And if you need access to the full TeamPage web interface, e.g. to assign a task to someone, you can open a browser to the current discussion by switching from the preview tab to the WWW tab.

toggle iOS vs web view

Finally, you can use the Share Sheet to share a post's URL with other iOS apps.

iOS Share Sheet

That's It

For starters, anyway. We've focused on making it fast, functional, and friendly, while laying a foundation for future features. Behind the scenes, there's a new REST API on the server side; you can learn more about that in my next post, Behind the Scenes of the iOS TeamPage App. We'll be extending that API in concert with new features for iOS and other clients.

What's Next?

We welcome your feedback, ideas, and, inevitably, bug reports. We know our 1.0 isn't perfect, and it certainly isn't complete, but we find it indispensable, and hope you will too.

Depending on how you use TeamPage, you'll probably have a different opinion about what should come next. If you use it for ISO 9000 compliance or Quality Management, you might want to be able to compose new Quality Issues with photos right from the phone (today you can email them in). If you're a Competitive Intelligence professional, you might want access to Advanced Search. If you're a project manager, you might want to edit your project's tasks, or your team members' worklists.

Please send questions and feedback to, or post in the TeamPage Forum.

Note: The TeamPage app requires a TeamPage server version 6.1.14 or later. If you're a hosted customer, you're ready to go. If you have an on-premise TeamPage server, you'll need to upgrade before you enjoy the iOS app with your TeamPage server.

If you're interested in how we built the app, stay tuned for my next post, Behind the Scenes of the iOS TeamPage App.

Daily Report 日報 = Observable Work: Takashi Okutsu

March 29, 2016 · · Posted by Greg Lloyd

ImageTakashi Okutsu of Traction Software's Japanese Business Office recently posted an update to his free Daily Report TeamPage plugin. Takashi writes: "In some Japanese companies, it is common to look back what an employee did in the day, write a summary, and submit it to his/her boss. This is called "日報" (daily report or daily journal) and it's a way of sharing information between employees and bosses in the hierarchy. If you are interested in the ways of business in Japanese companies, you may find this blog post interesting." This example of Observable Work is very simple to understand and use. Quality Management and other TeamPage solutions follow the same pattern.


Takashi's free plug-in adds a Daily Report form to post and edit daily reports, along with a Daily Reports tab that includes a feed view, summary table, calendar view, and optional ranking. In addition to making it simple for employees to post a daily report, each report can be discussed, emailed, searched, and used like any other TeamPage article. For example, a visit to a customer which includes a suggestion or identifies a problem can be tagged with a follow-up task pinned to the original report and person who reported it, easily tracked from start to finish.

Like other TeamPage plug-in extensions Takashi's Daily Report is packaged as a single file that can be uploaded and installed with one click. Plug-in extensions add or override TeamPage capabilities, add new tabs, views and new setup pages to configure the appearance and behavior of the plug-in. TeamPage extensions include localized resources so the same plug-in can support many different languages - Japanese and English in this example.


See Takashi's Daily Report Form post for screenshots and examples. For a free TeamPage Forum and support account click here.


Shaka, When the Walls Fell

November 22, 2015 · · Posted by Greg Lloyd


In Shaka When The Walls Fell (The Atlantic, June 18, 2014) Ian Bogost poses a challenge based on Darmok, a 1991 Star Trek New Generation episode. Star Trek's Universal Translator knows how to translate the aliens words, but it's completely useless at telling Picard what the Tamarians mean. If that's how Children of Tama communicate, how could they ever have become a starfaring civilization?

"... after hailing the alien ship upon arrival, contact with Children of Tama proves more difficult than Picard imagined:

DATHON, the Tamarian captain: Rai and Jiri at Lungha. Rai of Lowani. Lowani under two moons. Jiri of Umbaya. Umbaya of crossed roads. At Lungha. Lungha, her sky gray.

(no response from Enterprise, looks at First Officer in frustration)

(slowly, deliberately) Rai and Jiri. At Lungha.

In the Star Trek universe, a “universal translator” automatically interprets between any alien language instantly and fluently. Unlike today’s machine translation methods, the universal translator requires no previous experience with another language in order to make sense of it. Such is the case with Tamarian, at least on the surface, as the Enterprise crew is able to comprehend the basic syntax and semantics of Tamarian utterances. “The Tamarian seems to be stating the proper names of individuals and locations,” offers Data, stating the obvious. But Picard quickly sums up the problem, “Yes, but what does it all mean?”

Picard calls the Tamarian's communication model metaphor, Troy calls it image, but according to Bogost's analysis they're both wrong:

"If we pretend that “Shaka, when the walls fell” is a signifier, then its signified is not the fictional mythological character Shaka, nor the myth that contains whatever calamity caused the walls to fall, but the logic by which the situation itself came about. Tamarian language isn’t really language at all, but machinery."

Read Bogost's essay for a fascinating dive into what Bogost calls “procedural rhetoric”—the use of computational processes to depict worldly processes.

I was struck by a simpler point: If the Tamarian's communicate using shared references, this implies:

1) A shared corpus of events known by every member of the Tamarian civilization;

2) A shared means of economically denoting a particular significant event in that corpus, with little likelihood of ambiguity or error;

3) A biological, technological, or technologically augmented biological means for every Tamarian to choose the appropriate event to communicate the desired interpretation (or logic in Bogost's analysis).

This seems like a tall order, but consider that most of us now live in a civilization that assumes that no factual question need go unanswered for more than a few minutes, after poking or talking at pocket sized supercomputer screens meshed with an associatively addressable, world spanning corpus that's glued together by annoying commercials, a few giant companies, and unicorn dreams of VCs.

What Tamarian's need (or have) is a culture spanning version of Doug Engelbart's Journal, a shared, addressable record of Tamarian history and its logic. I'll toss in Vannevar Bush's Memex too, for corpus spanning associative trails, if only we knew how to build the Memex's code book.

Doug on the screen in San Francisco. Dealing lightning.


In Shaka When The Walls Fell (The Atlantic, June 18, 2014) Ian Bogost. "In one fascinating episode, Star Trek: The Next Generation traced the limits of human communication as we know it—and suggested a new, truer way of talking about the universe."

And here's what Enterprise 2.0 looked like in 1968 | Dealing lightning with both hands... "Doug Engelbart sat under a twenty-two-foot-high video screen, "dealing lightning with both hands." At least that's the way it seemed to Chuck Thacker, a young Xerox PARC computer designer who was later shown a video of the demonstration that changed the course of the computer world." from John Markoff's What the Dormouse Said.

Thought Vectors - Vannevar Bush and Dark Matter Vannevar Bush's 1945 concept of trailblazing, across the dark matter of the Internet.

The Work Graph Model: TeamPage style Addressable work. ... A work graph consists of the units of work (tasks, ideas, clients, goals, agenda items); information about that work (relevant conversations, files, status, metadata); how it all fits together; and then the people involved with the work (who’s responsible for what? which people need to be kept in the loop?)

Original Traction Product Proposal

August 24, 2015 · · Posted by Greg Lloyd

I hope you'll enjoy reading the original Traction Product Proposal, dated October 1997. Many early Traction concepts carried over directly to the Teampage product first commercially released in July 2002, but we've also learned a lot since then - as you might hope! The quotes still make me smile. The Proposal and Annotated References may be helpful to students interested in the history and evolution of hypertext.

Motivated by Chris Nuzum's recent Tripping Up Memory Lane talk at HyperKult 2015, and Takashi's Design Concepts followup, I'm happy to continue the Traction history theme. I've removed the Confidential markings from the Proposal, and released it under the Creative Commons Attribution-Non-Commercial license (CC BY-NC 4.0), so you're welcome to read and use it for non-commercial purposes with attribution. Please link directly to this blog post.

Traction Software folk may make occasional blog posts referencing the Traction History project on this blog or on Twitter. Please follow @TractionTeam on Twitter, and feel free to message me as @roundtrip if you have questions.

The scribbled picture above from about the same time was my visualization of the Traction goal: To link and use anything that would cross a business person's desk using the Web as a platform, rather limiting hypertext to content stuffed inside silos like Lotus Notes.


When we introduced Teampage in 2002, the word "blog" was often dogmatically defined as the unedited voice of a person. It was a tough slog to introduce a chronological stream of content created by a group of people rather than a single individual. The concept of an activity stream or Slack channel - a group of people talking in a shared space or channel - better captures what Teampage does.

Teampage extends the concept of an activity stream or channel to include:

  1. Editable entries with a full audit trail, including wiki history
  2. An extensible family of entry types (task, status, ...) and relationships (comment, ...)
  3. Dashboard and other views that collect, organize, and show entries in context
  4. A unified permission model that makes it simple to roll up entries across spaces and navigate or search by topic, context, author, or other criteria, see The Work Graph Model: TeamPage style

Clay Shirky got the concept in his 2003 review: Traction: Weblogs grow up in Social Software: A New Generation of Tools, Release 1.0 Vol 21, No. 5 (pdf). So did Jon Udell in his 2002 InfoWorld review: Getting Traction Traction's enterprise Weblog system gets a grip on corporate KM.

"Somewhere around your 30th responses to a response to a response in Notes, you start to wonder where all this group discussion leads. Somewhere around the fifth time a document marches by with yet more groupware annotations and digital yellow stickies attached, you wonder if it is really all that wise to have all of that group editing taking place. After all, isn’t the purpose of a group to tap the greater intellect represented by all those fine thingies in the group and, once tapped, move quickly to a better decision? Shouldn’t the purpose of groupware be to build more intelligence rather than more features into the product?

While it’s useful to share documents, hold ad hoc discussions and post groupwide projects, the essence of groupware may be the ability to manage a business outcome by divining a group's thought process."

Eric Lundquist, The Next Big Thing in Groupware PC Week 1 July 1996.
Team Problem Solving from Traction Product Proposal Oct 1997 

The core concept was granted US Patent 7,593,954.

The original business case for Teampage cited project work as the most important use. We've learned that it's valuable give people a straightforward way to link action tracking, messaging, and collaborative content creation. By creating and tracking tasks that can be directly attached to Teampage or external content, it's easy to see and stay on top of what's happening for you, by person, by channel, or in context of a specific Teampage project.

We learned how to model permissions to extend work across many internal as well as external groups such as the clients of a consulting firm, or the suppliers and customers of a manufacturer. The Teampage model of multiple permissioned spaces was added soon after the 1997 proposal. You can focus on any space (like a channel) as well as search and navigate across all spaces and entries you have permission to see.

By adding individual and group permissions to a space with an ACL model, internal and external groups share the same Teampage server while seeing and participating in just the set of projects and activities that are appropriate for every individual. Comment, task, and tags can cross spaces - so it's simple for internal team members to have a more private discussion linked to a specific paragraph of page or question posted by an external customer. Streams, discussions, notifications, digests, navigation, and search all obey the permissions defined by business rules enforced at the core level.

Email and Teampage has an interesting history. The 1997 proposal describes Traction as an alternative to broadcast email, but cites email as an important source for information to be be recorded and shared. An emailed Digest was one of the first features added to TeamPage based a beta customer's request. The Digest includes title links and content snippets gathered from the stream of events posted since the previous Digest was emailed. The content of each Digest is clipped to conform to what that person is permitted to see.

The Digest remains a popular features of Teampage, later augmented by email notifications with auto threaded email replies: your reply to a Teampage email notification is posted as a comment by you, linked at the right point in the discussion thread - requested by major consulting firm. I agree with Alan Lepofsky's point that email is one of many channels for messsages: we should flip our perspective to the stream of messages rather than the channel used to deliver each message, see Takashi's Eat your spinach post.

This combination of capabilities is particularly valuable for projects that intertwingle collaborative writing, team communication, and action tracking such as: quality management, product development, product support, consulting, and competitive intelligence. See The Work Graph Model: TeamPage style and Teampage Solutions.

A note on links: Although some of the links in the proposal still work, many point to sites which have been moved, including Doug Engelbart references which have moved from to In most cases a bit of creative Googling will find the referenced page in a different location. If people are interested, I'll publish an editable version of the Annotation References section that can be used to share updated locations. Please message @roundtrip on Twitter if you're interested and willing to pitch in to tracking down current references. Sigh.


"Thoughtvectors in Concept Space badge" by @iamTalkyTina my posts |


Tripping Up Memory Lane - Hyperkult 2015: Hypertext lessons learned talk by Traction Software CTO and Co-founder Chris Nuzum

Teampage hypertext journal: Design concepts, by Takashi Okutsu Director of Traction Software's Japanese Business Office

Traction Roots - Doug Engelbart - About Doug Engelbart's Journal and Traction.

Enterprise 2.0 - Letting hypertext out of its box - "I believe that the radical departure is the Web as the context of work: the universal medium, universal library, universal marketplace, and universal platform for personal as well as enterprise communication... In every previous generation hypertext system, the ability to read, search, link and communicate came with a terrible price: it might work well, but only if you were willing to put everything you wanted to work with into some sealed box, and convince everyone you wanted to work with to use the same box. From the earliest days of Vannevar Bush's Memex, the vision was universal, but the implementation was a siloed."

Intertwingled Work - Working and scaling like the Web. "... in the past, conversations could only be intertwingled across paper memos, faxes, written reports and email. Until the advent of the Web it wasn't possible to intertwingle conversations, networks, analysis and work in near-real time and global scale. Now that's trivial and essentially free with basic Web access."

The Work Graph Model: TeamPage style - The social dance of getting things done, dealing with exceptions, and staying aware of what’s going on around you

Teampage hypertext journal: Design concepts, by Takashi Okutsu

August 7, 2015 · · Posted by Greg Lloyd

Takashi Okutsu of Traction Software's Japanese Business Office wrote a blog post, Teampage hypertext journal: Design concepts. Starting from Chris Nuzum's Tripping Up Memory Lane presentation, Takashi explains how TeamPage's append-only journal models editable content, links, and relationships − while maintaining a full audit trail. See this Google English translation.

Teampage's model was inspired by the work of Doug Engelbart, who in 1975 wrote:

Our Journal system was conceived by this author in about 1966. I wanted an underlying operational process, for use by individuals and groups, that would help bring order into the time stream of the Augmented Knowledge workers. The term "journal" emerged early in the conceptualization process for two reasons:

  1. I felt it important in many dynamic operations to keep a log (sometimes termed a "journal") that chronicles events by means of a series of unchangeable entries (for instance, to log significant events while evolving a Plan, shaping up a project, trouble-shooting a large operation. or monitoring on-going operations). These entries would be preserved in original form, serving as the grist for later integration into more organized treatments.
  2. I also wanted something that would serve essentially the same recorded-dialogue purpose as I perceived a professional journal (plus library) to do.

Compcon 75 Digest, Sep 1975 pp 173-178, Douglas C. Engelbart THE NLS JOURNAL SYSTEM see the full paper, courtesy of the Doug Engelbart Institute.

Working from Chris's presentation notes (pdf), Takashi explains how to Teampage builds on Engelbart's model to support editable, stable two-way links, relationships, and content.

Takashi uses an animation cel analogy to illustrate how the effect of multiple entries in a TeamPage journal can be superimposed to show the effect edits at any point in time. For more detail, see Teampage's US Patent 7,593,954.


Tripping Up Memory Lane Traction Software co-founder and CTO Chris Nuzum talk on hypertext lessons learned, Hyperkult 2015 conference, Lüneburg Germany, 10 July 2015

Traction Roots - Doug Engelbart About Doug Engelbart's Journal

The Work Graph Model: TeamPage style Understand how TeamPage connects people and their work

Tripping Up Memory Lane

July 16, 2015 · · Posted by Christopher Nuzum

Last week I gave a talk at the Hyperkult 2015 conference. It was an honor to present there, especially since it was the 25th and final time the conference was held. This was my proposal for the talk:

Sometimes it seems like collaborative software projects are designed in an ahistorical vacuum. Like all our ideas are new. Maybe that’s because so much software is designed by young people fresh out of computer science programs heavy in programming and data structures, but often paying little more obeisance to the history of software than to acknowledge that once people programmed on punch cards, however that worked.

In 1996, after celebrating the 50th Anniversary of As We May Think at the Massachusetts Institute of Technology, and inspired by a long, encouraging talk with Doug Engelbart, I co-founded Traction Software (originally Twisted Systems, Inc.) and set out to design a memex-inspired literary machine for the augmentation of collective intelligence. In this talk, I’d like to demonstrate how the Traction Hypertext Journaling Engine underlying Traction Software’s TeamPage product borrows from and builds on insights and ideas from Vannevar Bush, Doug Engelbart, and Ted Nelson. I’ll also talk a bit about what ideas we’ve abandoned and why, and end with some thoughts on ideas that I think haven’t yet had their day.

I'd never given a talk in Germany before, but since the German word Vorlesung means "reading", I thought I had better be prepared with something I could read, even though that's not how I'm used to presenting.

For anyone interested, I've posted the script I prepared for the talk: Tripping Up Memory Lane Script.pdf (14.2MB). The PDF also includes high-resolution versions of the images I used in my slides.

I hope you'll enjoy.

Update: See the University of Lüneburg's video of this talk. Adobe Flash required for Chrome and Internet Explorer 10 and older.

Eat your spinach: Email is good for you, but it could taste a lot better

July 3, 2015 · · Posted by Greg Lloyd

Takashi Okutsu of Traction Software's Japanese Business Office says that email is like spinach. It may be necessary for a healthy business, but not everyone likes spinach. He says that it's not reasonable to think that Social Network Software replaces email. It's better to look at how SNS extends and complements email. Takashi's July 3, 2015 blog post explains how, see this rough Google English translation.

Takashi often works with customers who depend on email for external and internal communication. In his blog post he uses several examples:


It's simple to email content into Teampage. The article or comment is automatically logged with the correct Teampage account based on the incoming email address. It's also simple to CC: email to Teampage when you want others to see an outgoing email to a customer or other person you are working with.

People can receive an email notifications when an article they are interested in is posted to Teampage. You can choose to receive notifications based on: comments added to articles or spaces you watch; comments added to articles you wrote or commented on; articles with a tag you watch; articles that mention you.

When you receive an email notification, you can reply to the email to automatically add a comment to the threaded discussion. Only the content you write is added to the thread, not a copy of the entire email thread.


But too many email notifications can be overwhelming. Teampage also provides an automatic email digest that summarizes articles and actions of interest, customized for the preferences (and access permissions) of each Teampage user.

You can use email notifications for your highest priority interests, and use the email digest to catch up on everything else. By default the digest is emailed once a day, but each person can choose to get a digest for a longer period (once a week), or several times a day.

Takashi concludes (in Google translation): "I think you have done already the spinach by e-mail. Why not been investigated in-house social us to support it. Just add a little plus of 'CC in TeamPage', you can get a big plus."


Understanding Spinach Update: Takashi writes that the Japanese word ホウレンソウ (HORENSO) has a literal English translation "spinach", but it is used to refer to a Japanese practice that aligns members understanding and synchronizes actions. Thanks to Takashi and Google Translate, I've learned that: 1) Japanese people have useful terms for communication practices that don't have an English language equivalent. We should adopt them; 2) Teampage is very good for ホウレンソウ !

"HORENSO is a way of information sharing by way of aligning members' understandings and synchronizing actions about changing circumstances that happen in and out of an organization." from NNA post. See also definition of HOKOKU.


Constellation Research Analyst VP Alan Leoposky aka @alepo frequently debunks claims that "email is dead" (or should be), pointing out: 1) Email is universal. No introduction or specialized software required; 2) Email is a firmly established habit. Habits are hard to change, and often shouldn't; 3) Email enables every person to filter, organize and prioritize what they see; 4) Email is one of many channels for messsages: we should flip our perspective to the stream of messages rather than the channel used to deliver each message. I agree.

Dec 2014 | TeamPage @ Mentions Bring any TeamPage item to someone's attention, bring them into the followup conversation

July 2014 | TeamPage Notifications Introducing inline notifications

The Work Graph Model: TeamPage style Understand how TeamPage connects people and their work

My Part Wor ks

May 22, 2015 · · Posted by Greg Lloyd

ImageAbout 50 years ago, Andy van Dam joined the Brown University faculty with the world's second PhD in Computer Science (earned at the University of Pennsylvania). Today many of Andy’s friends, faculty, students and former students are celebrating his 50 years at Brown with Stone Age, Iron Age and Machine Age panels. [ June 9, 2015 update: See event video: Celebrate with Andy: 50 Years of Computer Science at Brown University ]

I’m part of the Stone Age cohort. In 1968 Andy and his Swarthmore colleague Ted Nelson gave a medicine show pitch to convince skeptical undergrads to sign up for an an insanely demanding one year, four course sequence then called Applied Math 101/102 and 103/104. I bit.

Starting with a tiny, two person department - and as a matter of principle - Andy recruited undergraduates as teaching and research assistants, a tradition that continues to this day. In an essay on the history of the Brown CS UTA [Undergraduate Teaching Assistant] program Andy said:

“Offering teaching and research assistant opportunities to undergrads,” he says, “was even more unusual, indeed was viewed with everything from skepticism to outright hostility. Hardly anyone said, ‘What a fantastic idea!’ Everyone was used to four years of preparation as an undergraduate, then n years of graduate work before you could contribute to a science. But we’re different. CS was and is young, experimental, and open for undergrads to contribute. And undergraduate participation in research in all fields has become commonplace, especially in the last decade.

In 1965, a single, intense full-year course could cover much of the breadth, if not the depth, of the systems-oriented portion of the discipline, not including theory, AI, numerical analysis, and a few other topics. Andy insisted that students couldn’t learn to be good programmers by solving small “toy” problems; they had to write significantly-sized programs, each taking multiple weeks.

Not just checking for the right answer but giving useful feedback on structure, style, and efficiency required careful reading and one-on-one help with concepts and debugging. In a class with forty students, it was impossible for one graduate TA and a professor to provide this level of attention, no matter how little sleep they were getting, so van Dam asked for help from students who had taken a prior programming course. In that first cohort, he remembers Bill Adcock; Dan Bergeron, who also subsequently got his PhD with Andy and became Chairman of the CS Department at UNH and went with him and a group of six other of Andy’s students for his first sabbatical in 1971 at the University of Nijmegen in Andy’s country of origin; and Dennis Ruggles, among others.

“The undergraduate teaching assistants,” Andy explains, “though they were initially called graders, didn’t just grade programs -- they not only provided one-on-one help to students but also became active participants in course design and in subsequent years read research papers and brought new ideas into the curriculum. In fact, they did everything graduate TAs did, becoming producers and not just consumers of education. We kept modifying the course as we went along, but the one constant was the highly-appreciated UTA system.

Few people appreciate it more than Ed Lazowska ‘72, who will lead the first (“Stone Age”) panel for Celebrate With Andy. He says, “I’m a faculty member precisely because of the UTA program. I went to grad school because Andy told me to. In some way, everything I do professionally today is due to him.

To provide feedback for the course, students wrote detailed, multi-page evaluations, something that was almost unheard of in 1965. As Bob Munck recalls, “Also after every class, the graders would sit around on the floor of Andy's office (later my office) and critique the lecture and him. I'd never seen anything like it.

On his commute home from work, Andy would listen to tape recordings of his lectures, filling the empty minutes with self-critiques: “Boy, was that a clumsy explanation! Get rid of the ‘um’s and the ‘you know’s.” Presentation skills are still something that van Dam is keenly interested in. “Today’s equivalent of ‘you know’ is ‘like’, which I try to stamp out in all students who work with me. I’ve given up on ‘awesome’.

An interesting aspect of the UTA program is that the system has essentially never been challenged by students due to the built-in checks and balances. “By having rotating TAs and detailed rubrics,” Andy says, “you create fairness. It’s a system that’s at least as fair as having a single faculty member grading. Besides, a single faculty member, even assisted by a few graduate TAs, can’t begin to read that many programs at the required level of detail, and students recognize that. Part of the checks and balances is that faculty members are responsible for assigning the final grades, and I personally review all borderline grades, hoping to find evidence for promotion to the next grade bin.

Originally something made up as they went along, the UTA program matured over a period of decades. Iteration and gradual regularization brought cross-course norms and standards that are used today by almost all Brown CS courses. “In my opinion,” says Andy, “We have the most systemic TA program, and there’s a well-defined appeal system in place to address any grading errors.

You can read about Andy’s honors and achievements on his Wikipedia page, and Professor Shriram Krishnamurthi's answer to Why is professor Andy Van Dam (Andy) so cool? Here are two short stories from me.

After Dinner

Photo of Andy on WBGH Boston’s After Dinner show, broadcast live at 7:30PM Monday October 20, 1969.

After Dinner featured Andy van Dam, Chris Braun, Bev Hodgson (then Brown Daily Herald editor), Al Basile and myself talking about hypertext for 30 minutes on a stage set that was supposed to look like a professor’s living room, right next to Julia Child’s WGBH TV kitchen. Andy is pointing to photo of Chris Braun at the IBM 2250 Hypertext Editing System (HES) console.

AvD writes: You might mention that the topic wasn’t just hypertext per se, but the use of hypertext for non-linear narratives, esp. hypertext fiction as a new literary form (Montreal Expo (68) had just shown an audience-influenced branching movie, Burroughs’ Naked Lunch and Nabokov’s Pale Fire had been published, and experimentation was in the air. I’m sitting in the audience at the YURT inauguration symposium, listening to organizer John Cayley talk about “Cave Writing” and related spatial (immersive) hypertext projects that he and his students craft.

My Part Wor Ks

Brown Computer Science circa 1969. Original edition.

The story as I recall: Most people chose an individual final project for AM 101/102. However, a few folk chose the two person assembler project.

A grader did an in person review with a two person team, noting a problem. One team member replied: “My part works, but he keeps passing me garbage.

It became a team programming mantra.

The first part was made into a button, with Wor ks spelling. The second part was the AvD equivalent of a secret handshake. Until now.


"Thoughtvectors in Concept Space badge" by @iamTalkyTina my posts |



Andries van Dam - Wikipedia page

Celebrate With Andy: 50 Years Of CS At Brown - May 2015. An essay celebrating "the three golden anniversaries for the Brown CS family: fifty years of the UTA program, undergraduate involvement in research, and Andy van Dam at Brown."

Why is professor Andy Van Dam (Andy) so cool? - Quora, Jan 2015. I agree with Brown CS professor Shriram Krishnamurthi.

Pastepost - One more AvD story. The first public document from the first Hypertext Editing System was a press release announcing its own creation.

As We May Work - Andy van Dam - Tokyo 2008

The MIT/Brown Vannevar Bush Symposium - Celebrating the 50th anniversary of Bush's As We May Think. Organized and MC'd by Andy van Dam

Hypertext Editing System - Wikipedia page. Photo by Greg Lloyd.

Enterprise 2.0 - Are we there yet?

November 21, 2014 · · Posted by Greg Lloyd

ImageAndrew McAfee writes Nov 20, 2014: "Facebook’s recent announcement that it’s readying a version of its social software for workplaces got me thinking about Enterprise 2.0, a topic I used to think a great deal about. Five years ago I published a book with that title, arguing that enterprise social software platforms would be valuable tools for businesses...

Why did it take so long? I can think of a few reasons. It’s hard to get the tools right — useful and simple software is viciously hard to make. Old habits die hard, and old managers die (or at least leave the workforce) slowly. The influx of ever-more Millennials has almost certainly helped, since they consider email antediluvian and traditional collaboration software a bad joke.

Whatever the causes, I’m happy to see evidence that appropriate digital technologies are finally appearing to help with the less structured, less formal work of the enterprise. It’s about time.

What do you think? Is Enterprise 2.0 finally here? If so, why now? Leave a comment, please, and let us know."

Andrew – As we’ve discussed in the past, I don’t believe there’s a specific ‘Are we there yet?’ for Enterprise 2.0.

The lessons I learned from your excellent book and research are still relevant today. Enterprise 2.0 technology enables but does not guarantee organizational change. Some organizational change is invented and purposeful, some is serendipitous and emergent.

The effect of new technology on an enterprise is too often like picking up and shaking a sleepy beehive.

We’ve come a long way towards the vision that software and devices used inside a company will become more like software, Web services and mobile devices people use at home. Enterprise software and services need to meet the same expectations for clarity, any time / any where access, and easy of use that people expect at home, which shakes markets as well as assumptions. Tracking the relationship of Apple IBM from Nov 2009 through Nov 2014 (and their market cap) is an instructive example.

As Peter Drucker taught, organizations need to adapt and innovate to make use of these capabilities, which opens the door to new technology, capabilities, and markets for enterprise software and services at every layer of the stack. Which opens the door to new organizational challenges and opportunities…

I’m not surprised that this takes time - and like Bill Buxton’s analysis in his Long Nose of Innovation article from 2008.

I’ll also keep my faith in Peter Drucker and Doug Engelbart as the twin patron Saints of Enterprise 2.0. As I said in Nov 2009, you have your own sub-numinous stake in the game!



Enterprise 2.0, Finally? Andrew McAfee, Nov 20, 2014 (This blog post was originally posted as a comment)

Enterprise 2.0: New Collaborative Tools for Your Organization's Toughest Challenges Andrew McAfee, Harvard Business Review Press, Nov 2009

The Long Nose of Innovation Bill Buxton, Bloomberg Business Week, Jan 8, 2008

Enterprise 2.0 Schism Greg Lloyd, Nov 9, 2009

Ada Lovelace Day | Emmy Noether, Mathematician

October 14, 2014 · · Posted by Greg Lloyd

Ada Lovelace Day celebratesImage the contributions of women in science and technology, follow @FindingAda for news and events. This year I've chosen to write about mathematician Amalie "Emmy" Noether. At the time of her death in April 1935, she was described by Pavel Alexandrov, Albert Einstein, Herman Weyl, Norbert Weiner and others as the most important woman in the history of mathematics. Noether’s First Theorem is a fundamental tool of modern physics and the calculus of variations: every symmetry corresponds to a conservation law. "It was her work in the theory of invariants which led to formulations for several concepts of Einstein's general theory of relativity." [J J O'Connor and E F Robertson, 1997]. Of her later work, Nathan Jacobson said: "The development of abstract algebra, which is one of the most distinctive innovations of twentieth century mathematics, is largely due to her – in published papers, in lectures, and in personal influence on her contemporaries." Einstein wrote Noether's obituary in the New York Times, May 5, 1935:

"Within the past few days a distinguished mathematician, Professor Emmy Noether, formerly connected with the University of Göttingen and for the past two years at Bryn Mawr College, died in her fifty-third year. In the judgment of the most competent living mathematicians, Fräulein Noether was the most significant creative mathematical genius thus far produced since the higher education of women began. In the realm of algebra, in which the most gifted mathematicians have been busy for centuries, she discovered methods which have proved of enormous importance in the development of the present-day younger generation of mathematicians. Pure mathematics is, in its way, the poetry of logical ideas. One seeks the most general ideas of operation which will bring together in simple, logical and unified form the largest possible circle of formal relationships. In this effort toward logical beauty spiritual formulas are discovered necessary for the deeper penetration into the laws of nature.

Born in a Jewish family distinguished for the love of learning, Emmy Noether, who, in spite of the efforts of the great Göttingen mathematician, Hilbert, never reached the academic standing due her in her own country, none the less surrounded herself with a group of students and investigators at Göttingen, who have already become distinguished as teachers and investigators. Her unselfish, significant work over a period of many years was rewarded by the new rulers of Germany with a dismissal, which cost her the means of maintaining her simple life and the opportunity to carry on her mathematical studies. Farsighted friends of science in this country were fortunately able to make such arrangements at Bryn Mawr College and at Princeton that she found in America up to the day of her death not only colleagues who esteemed her friendship but grateful pupils whose enthusiasm made her last years the happiest and perhaps the most fruitful of her entire career."

Princeton University, May 1, 1935

In The Most Important Mathematician You've Never Heard Of Dr Dave Goldberg summarized Fräulein Noether’s life, her academic struggles - championed by Göttingen mathematicians David Hilbert and Felix Klein - and contributions to the foundations of modern physics.

"Hilbert and Noether skirted the rules by listing Hilbert as a course instructor and then having Noether as the perennial guest lecturer, though this didn't extend to getting Noether any sort of paycheck. It wasn't until 1922 that the Prussian Minister for Science, Art and Public Education gave her any sort of official title or pay at all, and even then only a pittance. As Hilbert described it in his memorial address for Emmy Noether:

When I was called permanently to Göttingen in 1930, I earnestly tried to obtain from the Ministerium a better position for her, because I was ashamed to occupy such a preferred position beside her whom I knew to be my superior as a mathematician in many respects. I did not succeed. . . . Tradition, prejudice, external considerations, weighted the balance against her scientific merits and scientific greatness, by that time denied by no one.

In all events, bringing her to Göttingen turned out to be an incredibly good idea. Almost immediately upon her arrival, Noether derived what's become known as Noether's 1st Theorem and by 1918 had cleaned it up enough for public consumption. And this is where we pick up the physics part of the story."

Fräulein Noether’s name and contributions to mathematics will live forever, despite the obstacles she had to overcome as a mathematical genius of the first rank - who happened to be a woman.

No woman should require the endorsement of mathematical legends like Hilbert, Klein, Einstein, Weyl, and Weiner to pursue and excel in the mathematical, scientific, or other career they love. We need every Fräulein Noether born in whatever place or circumstance, and need to support and encourage all who are inspired by her work and example.

Update See Marie Curie [ and Emmy Noether ] cartoon by xkcd "You don't become great by trying to be great. You become great by wanting to do something, and then doing it so hard that you become great in the process. So don't try to be the next me, Noether, or Meitner. Just remember that if you want to do this stuff, you're not alone." via @ValdisKrebs

More Finding Ada Blog Posts

Ada icon by Sidney Padua From the Thrilling Adventures of Babbage & Lovelace for your iPad (free). Enjoy Babbage and Lovelace adventures, backstory and more on Sydney Padua's 2D Goggles Web page.

Named Data Networking - Boffin Alert

September 8, 2014 · · Posted by Greg Lloyd

ImageOn Sep 4, 2014 the Named Data Networking project announced a new consortium to carry the concepts of Named Data Networking (NDN) forward in the commercial world. If this doesn't sound exciting, try The Register's take: DEATH TO TCP/IP cry Cisco, Intel, US gov and boffins galore. What if you could use the internet to access content securely and efficiently, where anything you want is identified by name rather than by its internet address? The NDN concept is technically sweet, gaining traction, and is wonderfully explained and motivated in a video by its principle inventor and instigator Van Jacobson. Read on for the video, a few quotes, reference links, and a few thoughts on what NDN could mean for the Internet of Things, Apple, Google and work on the Web. Short version: Bring popcorn.

For a short non-technical introduction, see Wade Roush's Sep 2012 piece on Van Jacobson and Content Centric Networking The Next Internet? Inside PARC’s Vision of Content Centric Networking. Background: Jacobson's work on CCN begot the NDN project, where he is now a Principle Investigator. A few quotes from Roush's story:

The fundamental idea behind Content Centric Networking is that to retrieve a piece of data, you should only have to care about what you want, not where it’s stored. Rather than transmitting a request for a specific file on a specific server, a CCN-based browser or device would simply broadcast its interest in that file, and the nearest machine with an authentic copy would respond. File names in a CCN world look superficially similar to URLs (for example, /…) but the data in a name is used to establish the file’s authenticity and provenance, not to indicate location.

It’s easy to see how much sense this makes compared to the current client-server model. Say I’m using my Apple TV box to browse my Flickr photo collection on my big-screen TV. To get each photo, the Apple TV has to connect to Flickr, which is hosted on some remote data center owned by Yahoo—it could be in Utah or North Carolina, for all I know. The request has to travel from the Apple TV over my Wi-Fi network, into Comcast’s servers, then across the Internet core, and finally to Yahoo. Then the photos, which amount to several megabytes each, have to travel all the way back through the network to my TV.

But the photos on Flickr are just copies of the originals, which are stored on my camera and on my laptop, about 15 feet away from my TV. It would be much smarter and more economical if the Apple TV could simply ask for each photo by name—that is, if it could broadcast its interest in the photo to the network. My laptop could respond, and I could keep browsing without the requests or the data ever leaving my apartment. (In Jacobson’s scheme, file names can include encrypted sections that bar users without the proper keys from retrieving them, meaning that security and rights management are built into the address system from the start.)

“The simplest explanation is that you replace the concept of the IP address as the defining entity in the network with the name of the content,” says Lunt. “Now all the talk in the network is about ‘Have you seen this content?’ and ‘Who needs this content?’ as opposed to ‘What is the routing path to particular terminus in the network?’ It’s a simple idea, but it makes a lot of things possible...

“One of the things that’s intriguing about not having to go to the source is that you could start to think about implementing applications differently,” Lunt says. “You could build apps that don’t have any notion of a server at all. So you could have Twitter without Twitter or Facebook without Facebook—that is, without having to have a major investment in hosting content, because the network is caching it all over the place.

Such architectures might give users more control over privacy and security of their data, and let them share their own data across devices without having to go through proprietary services like Apple’s iCloud, PARC executives say.

“What Apple is trying to do with iCloud is to say: You shouldn’t have to care which device you got an app on, or which device you took a photo on, whether it was your iPad or iPhone or MacBook Air. You just want your content to be on the other devices when you want it,” says Steve Hoover, CEO of PARC. “That validates our vision. But the way they are solving that puts more load on the network than it needs to, and it requires consumer lock-in. So Apple may be a user of this [CCN] technology one day, because it will make it easier. On the other hand, they could also hate it, because it will make it a lot easier for other people to provide that capability of getting the content whenever you want.

In my option, one of the technically sweetest characteristics of NCN is its relationship to current TCP/IP and networking protocols (quotes from NDN Architecture: Motivation and Details):

Like IP, NDN is a “universal overlay”: NDN can run over anything, including IP, and anything can run over NDN, including IP. IP infrastructure services that have taken decades to evolve, such as DNS naming conventions and namespace administration or inter-domain routing policies and conventions, can be readily used by NDN. Indeed, because NDN’s hierarchically structured names are semantically compatible with IP’s hierarchically structured addresses, the core IP routing protocols, BGP, IS-IS and OSPF, can be used as-is to deploy NDN in parallel with and over IP. Thus NDN’s advantages in content distribution, application-friendly communication, robust security, and mobility support can be realized incrementally and relatively painlessly...

Communication in NDN is driven by the receiving end, i.e., the data consumer. To receive data, a consumer sends out an Interest packet, which carries a name that identifies the desired data (see Figure 2). A router remembers the interface from which the request comes in, and then forwards the Interest packet by looking up the name in its Forwarding Information Base (FIB), which is populated by a name-based routing protocol. Once the Interest reaches a node that has the requested data, a Data packet is sent back, which carries both the name and the content of the data, together with a signature by the producer’s key (Figure 2). This Data packet follows in reverse the path taken by the Interest to get back to the consumer. Note that neither Interest nor Data packets carry any host or interface addresses (such as IP addresses); Interest packets are routed towards data producers based on the names carried in the Interest packets, and Data packets are returned based on the state information set up by the Interests at each router hop (Figure 3).

The router stores in a Pending Interest Table (PIT) all the Interests waiting for returning Data packets. When multiple Interests for the same data are received from downstream, only the first one is sent upstream towards the data source. Each PIT entry contains the name of the Interest and a set of interfaces from which the Interests for the same name have been received. When a Data packet arrives, the router finds the matching PIT entry and forwards the data to all the interfaces listed in the PIT entry. The router then removes the corresponding PIT entry, and caches the Data in the Content Store. Because an NDN Data packet is meaningful independent of where it comes from or where it may be forwarded to, the router can cache it to satisfy future requests. Because one Data satisfies one Interest across each hop, an NDN network achieves hop-by-hop flow balance...


NDN design assumes hierarchically structured names, e.g., a video produced by PARC may have the name/parc/videos/WidgetA.mpg, where ‘/’ indicates a boundary between name components (it is not part of the name). This hierarchical structure is useful for applications to represent relationships between pieces of data. For example, segment 3 of version 1 of the video might be named /parc/videos/WidgetA.mpg/1/3. The hierarchy also enables routing to scale. While it may be theoretically possible to route on flat names (see ROFL), it is the hierarchical structure of IP addresses that enables aggregation, which is essential in scaling today’s routing system. Common structures necessary to allow programs to operate over NDN names can be achieved by conventions agreed between data producers and consumers, e.g., name conventions indicating versioning and segmentation.

Name conventions are specific to applications but opaque to the network, i.e., routers do not know the meaning of a name (although they see the boundaries between components in a name). This allows each application to choose the naming scheme that fits its needs and allows the naming schemes to evolve independently from the network.

I haven't quoted from short sections on Data Centric Security, Routing and Forwarding, Intelligent Data Plane, Caching, or Intellectual Property Approach and open source. You should read NDN Motivation & Details, then much more from if either your head exploded, or you are jumping up and down in your seat with questions and objections.

Much of this is QED Marketing - I told you how it works, not what it means for you. Here are a few thoughts:

1) Secure efficient transport of content crossing many boundaries is a hard problem, getting harder as the number of people, things, and places on the Web grow, and as people look for a seamless and trusted way to deal with things they care about at home and at work. For example, how could Apple (or Google) leverage NDN to deliver on an internet of your things? How might players other than the giants leverage NDN to compete?

2) NDN offers the possibility of doing a lot of the hard work at the network level, which is a win if it offers a economic benefit to those who pay for the fabric of the internet, and opportunities to invent and grow scalable businesses more effectively. For example, what could change if Amazon offered NDN as an Amazon Web Service?

3) NDN might offer an appropriate secure, flexible framework for connecting people to content at work. Businesses use siloed applications for for transactional data for good reasons: they are simpler to build, (potentially) more secure, and (potentially) more flexible than old style monolithic business applications if they become sources of content linked together at a higher level of an application stack. NDN might be a great protocol to build flexible, secure, extensible business applications connecting people to the content they want - and are allowed to use.

With respect to the network issues, I'm a fan, not an expert, but the NDN proposal seems to share many of the (relatively) simple, scalable, decentralized characteristics that fueled the growth of the Web and evolution of TCP/IP. NDN seems to be most attractive for big content, particularly where multicast style delivery and caching can delivery big bandwidth and responsiveness improvements, but it looks like a lot of thought has gone into efficient localized delivery. Likewise, management of a very large, frequently changing name space is a challenge, which also seems to have gotten a lot of intelligent attention.

With Cisco and Huawei on board as founding industrial partners of the NDN Consortium, you can bet that a lot of caching routers can be sold, and NDN routing technology will take the fast track if there's economic payback for NDN, which will drive better payback, faster adoption, etc.

The good thing is the program has advanced to the stage where many of these questions can answered by experiment - we shall see.

Will the NDN Consortium take off? Will Google, Apple and Microsoft jump in? Or will NDN join the queue of technically sweet solutions that never really get off the ground? I'm optimistic that NDN has the right technical characteristics and pedigree, with smart experienced people leading the charge. With the Internet of Things and secure content distribution efficiencies as economic drivers, I hope we'll all benefit from NDN's content delivery model as the next stage of the Web's evolution. If you're not in the battle, bring popcorn and watch - it should be a good show.


Named Data Networking Architecture: Motivation & Details The best short technical overview I've found of the objectives and approach of the Named Data Networking project. Read the overview to get quick idea of how content is named, the NDN security and caching model, how NDN works over (or under) TCP, scaling issues, and more.

A New Way to Look at Networking - Van Jacobson's Aug 2006 Google Tech talk on TCP and Content Centric Networking (CCN). CCN is the title of Jacobson's Xerox PARC project, which became "the single biggest internal project at PARC." CCN led to the formation of the Named Data Networking project as a National Science Foundation funded Future Internet Architecture program in Sep 2010. Jacobson is currently a Principle Investigator of the NDN project. See Van Jacobson speaks on Content Centric Networking for a longer (three hour) and slightly earlier version of Jacobson's CCN talk presented as a Future Internet short course, including slides.

Reinventing the Web II (Aug 2014) The Web won vs "better" models by turning permanence into a decentralized economic decision. Why isn't the Web a reliable and useful long term store for the links and content people independently create? What can we do to fix that? Who benefits from creating spaces with stable, permanently addressable content? Who pays? What incentives can make Web scale permanent, stable content with reliable bidirectional links and other goodies as common and useful as Web search over the entire flakey, decentralized and wildly successful Web? NDN is the sweetest and most credible global technical approach I've seen.

Continuity and Intertwingled Work (Jun 2014) A level above an Internet of Things: seamless experience across devices for you, your family, your health and trusted service providers, at home and at work.

Intertwingled Work (Jul 2010) No one Web service or collection of Web servers contain everything people need, but we get along using search and creative services that link content across wildly different sources. The same principal applies when you want to link and work across wildly diverse siloed systems of record and transactional databases.

Thought Vectors - Ted Nelson: Art not Technology (Jul 2014) Ted Nelson should be smiling - but I won't hazard a guess. From what I see, everything in NDN seems compatible if not influenced by the Docuverse, Tumbler, and fine grain content addressable network architecture that Nelson described in detail in his 1987 book Literary Machines. I believe NDN provides secure, scalable, fine grain, and upwards compatible networking that could connect the front end and back end Xanadu architecture that Nelson describes in Literary Machines. I'll follow up on this with a separate Boffin alert.

Linked, Open, Heterogeneous

August 31, 2014 · · Posted by Greg Lloyd

Image Art, Data, and Business Duane Degler of Design For Context posted slides from his 5 April 2014 Museums and the Web talk, Design Meets Data (Linked, Open, Heterogeneous). Degler addresses what he calls the LAM (Libraries, Archives, Museums) Digital Information Ecosystem. I believe the same principles apply when businesses connect internal teams, external customers, external suppliers, and partners of all sorts as part of their Business Information Ecosystem. Read Degler's summary and slides, below:

"The tide of available information continues to rise. The opportunities that come from open access, linked data, sharing resources with other institutions, and standards-based data are enticing - and perhaps overwhelming?

Emerging design approaches help you find ways to make the most of your opportunities for new types of interactions and engagement with Information Objects. They focus on:

- Exploration, serendipity, use: Rich, relevant design requires an intimate understanding of information and the way people interact with it. It's more than attractive styling - although that's important. It's about people engaging in ways that stimulate the intellect and the experience. People need to find information, use it, relate other information to it, and share it for decades to come.

- Scalability, persistence, authority: Rich, relevant design also takes the long view. Understanding that the integrity of the information matters. This is increasingly important as we move toward more linked, open, and born digital cultural information.

Your institution becomes a gateway to an ecosystem of artistic imagery, scholarly insights, history, perspectives, and related objects. Other people will use your information to create new interpretations and works, which then build on what you hold. Curating information may be perceived as a burden (to be made easier!), yet it is a significant opportunity to reinforce the value and authority of institutions that enhance the information ecosystem."


Dark Matter by Michael Peter Edson 19 May 2014. "The dark matter of the Internet is open, social, peer-to-peer and read/write—and it’s the future of museums" an important essay on the opportunity and mission for museums and cultural institutions: "We’re so accustomed to the scale of attention that we get from visitation to bricks-and-mortar buildings that it’s difficult to understand how big the Internet is—and how much attention, curiosity, and creativity a couple of billion people can have."

Thought Vectors - Vannevar Bush and Dark Matter (2014) Inspired by Michael Edson's essay. Just as Bush suggested in July 1945, I believe there's a need for people to act as explorers, guides, and trail blazers over knowledge they know and love. You can experience that personal knowledge and passion on a tour, at a talk, or in a conversation on a bus, at a party - anywhere you meet someone who loves one of these institutions. I think it's particularly valuable to have trail blazers who are also skilled professionals personally represent and communicate the values, knowledge, and heritage of their museum, just as a great reference librarian becomes a library's ambassador.

Reinventing the Web II (2014) Why isn't the Web a reliable and useful long term store for the links and content people independently create? What can we do to fix that? Who benefits from creating spaces with stable, permanently addressable content? Who pays? What incentives can make Web scale permanent, stable content with reliable bidirectional links and other goodies as common and useful as Web search over the entire flakey, decentralized and wildly successful Web?

Intertwingled Work (2010) No one Web service or collection of Web servers contain everything people need, but we get along using search and creative services that link content across wildly different sources. The same principal applies when you want to link and work across wildly diverse siloed systems of record and transactional databases.

Hello! Greetings from Takashi Okutsu

July 10, 2014 · · Posted by Takashi Okutsu

TakashiHi everyone. I am delighted to introduce myself to you as a member of the Traction Software Team. As some of you know, my name is Takashi Okutsu, and I am the director of Traction Software's Japan Business Office, located in Yokohama.

I have worked for Applied Knowledge in Japan as technical support staff, and have a long association with TeamPage since 2007. During this job, I helped many customers to improve their business with TeamPage and got lots of experience.

I am very happy to keep supporting these customers, introducing our products to new clients, and consulting with all TeamPage customers based on my experience. I believe our product TeamPage is a flexible and adaptable tool and service for many customers and business areas, and hope you like it.

If you should need additional information regarding me or Japan Business Office, or if you need any help regarding TeamPage, please do not hesitate to contact me. You can email to I am looking forward to talk with you.

皆様、こんにちは。私は、奥津岳と申します。横浜にある Traction Software の日本支店(トラクション・ソフトウェア・インク)の代表を務めています。

TeamPage には 2007 年から長く関わっています。前職では、株式会社アプライドナレッジにて技術サポート スタッフとして、TeamPage を通じて多くのお客様の業務改善のお手伝いをさせていただき、たくさんの経験を積むことができました。今年からはトラクション・ソフトウェア・インク代表として、お客様へのサポート、製品の紹介、経験に基づいたコンサルティングなどご提供しております。

私たちの製品 TeamPage は、とても柔軟性があり、様々な業務に適用できる製品/サービスであると自負しています。多くの方々に気に入っていただけることを願います。

トラクション・ソフトウェア・インクや製品/サービスにご興味がございましたら、お気軽に私のメールアドレス までお問い合わせください。皆様からのご連絡をお待ちしております。

Thought Vectors - Ted Nelson: Art not Technology

July 5, 2014 · · Posted by Greg Lloyd

ImageThe technoid vision, as expressed by various pundits of electronic media, seems to be this: tomorrow's world will be terribly complex, but we won't have to understand it. Fluttering though halestorms of granular information, ignorant like butterflies, we will be guided by smell, or Agents, or leprechauns, to this or that pretty picture, or media object, or factoid. If we have a Question, it will be possible to ask it in English. Little men and bunny rabbits will talk to us from the computer screen, making us feel more comfortable about our delirious ignorance as we flutter through this completely trustworthy technological paradise about which we know less and less.

To give up on human understanding is to give up hope, what we call in English "a counsel of despair." I think there is hope for much better and more powerful software designs that will give ordinary people the power over computers that they have always wanted - power with complete understanding. But that requires inspired software design, which I believe is art and not technology.

I believe the technoid vision does not comprehend what is humanly desired, humanly needed, and humanly possible. Especially the need and possiblity of human understanding. So excuse me from the butterfly crowd; I hope you will come with me to where understanding may be found.

Ted Nelson
The Future of Information
ASCII Corporation, Japan 1997
Image courtesy of Computer History Museum

This quote from Ted Nelson's 1997 book makes a point similar to Nelson's closing point in his July 2014 interview with Gardner Campbell as well as statements in his 2011 Possiplex autobiography, and 1975 Computer Lib / Dream Machines. Nelson sees computer technology as a medium for creative expression, not an end in itself, or a cheap replacement for human creativity. He cites film directors among his primary inspirations and heros, noting that his personal ephipany came in the early 1960's when he learned that it was possible to connect computers to screens. Nelson invented the terms hypertext and hypermedia to describe the new capabilities that he envisioned. During his 2014 interview Nelson cited the example of Orson Wells. For Ted Nelson, what you see on a computer screen and interact with should be the result of human creative intelligence applied through the use of new engines of expression over an endlessly evolving intertwingled corpus of literature. Using Nelson's cinema analogy, history put him in a position where he would have to invent the motion picture camera to achive his goals, but I believe his motivation was to become the seminal director and intellectual father of the new media which are his earliest and most influential inventions.


"Thoughtvectors in Concept Space badge" by @iamTalkyTina my posts |


Intertwingled, The Festschrift-- Ebook celebrating Ted Nelson Day at Chapman University, 2014 (Springer-Verlag) (via @TheTedNelson, 12 Jul 2015) A free Springer ebook edited by Douglas R. Dechow and Daniele C. Struppa. Chapters by Alan Kay, Brewster Kahle, Belinda Barnet, Ken Knowlton, Dame Wendy Hall, and others. Closing chapter What Box? by Ted Nelson. I highly recommend this book.

Living The Dreams: A Conversation With Ted Nelson Published on Jul 5, 2014. Dr. Ted Nelson speaks with Dr. Gardner Campbell about research, fantics, computer liberation, and the ongoing struggle between schooling and learning. A conversation undertaken in support of "Living The Dreams: Digital Investigation and Unfettered Minds," a digital engagement pilot of Virginia Commonwealth University's UNIV 200, Inquiry and the Craft of Argument.

Ted Nelson talk - Possiplex book launch From Welcome to Possiplex : An Autobiography of Ted Nelson party at the Internet Archive on Oct 8, 2010.

Possiplex: Movies, Intellect, Creative Control, My Computer Life and the Fight for Civilization, an autobiography of Ted Nelson, Mindful Press, Feb 2011.

Triangulation 164 - Conversation with Ted Nelson Leo Laporte's July 2014 conversation with Ted Nelson, broadcast Aug 18, 2014 on On hypertext, Xanadu - and being a media guy. "To me, all media are alike. You think about what are the effects you want - and you think about what are the technicalities it will take to give you those effects. So when I took a computer course in graduate school, I thought 'Holy smoke, you can put interactive screens on them'... Interactive screens were instantly obvious to me."

Computer Lib / Dream Machines A brief description of Ted Nelson's 1974 book. Ordering information for an authorized 2014 replica reprint, which I highly recommend.

Ladies and gentlemen, the age of prestidigitative presentation and publishing is about to begin. Palpitating presentations, screen-scribbled, will dance to your desire, making manifest the many mysteries of winding wisdom. But if we are to rehumanize an increasingly brutal and disagreeable world, we must step up our efforts. And we must hurry. Hurry. Step right up.

Theodor H. Nelson, “Barnum-Tronics.
Swarthmore College Alumni Bulletin, Dec 1970, 12-15
Quoted from Dream Machines, 1975
See New Media Reader Computer Lib / Dream Machines excerpt

Video Archive MIT / Brown Vannevar Bush Symposium: A Celebration of Vannevar Bush's 1945 Vision, An Examination of What Has Been Accomplished, and What Remains to Be Done. Oct 12-13 1995, MIT. Talks and panel discussion with Doug Engelbart, Ted Nelson, Andy van Dam, Tim Berners-Lee, Alan Kay and others. See also ACM Interactions summary (free access), transcript of day 1 and day 2 panels.

Meet Takashi Okutsu: Director, Traction Software Japanese Business Office

July 2, 2014 · · Posted by Greg Lloyd

ImageTakashi has been a TeamPage wizard since 2007, and now directs Traction Software's Japanese Business Office. Takashi provides exceptional sales, consulting, and support to TeamPage customers in Japan. He is a valued member of the Traction Software global team, and a frequent contributor to the TeamPage Customer Support Forum including development and discussion of TeamPage SDK plug-ins and examples. We invite Japanese visitors to explore for TeamPage information and a free trial. You are also welcome to join the TeamPage Japan Customer Support Forum to talk with Takashi and Japanese TeamPage customers.

Please follow Takashi on Twitter as TSIJPBO for Japanese TeamPage news from トラクション ソフトウェア (Traction Software Branch Office), Yokohama, Japan.

You can also follow Takashi's Buna Tree Melopan Twitter account to learn about walking in the Tanzawa mountain area of Kanagawa Prefecture, computer topics, and Japanese cooking, including camping meals Takashi has made with his Traction Software Swiss Army knife.


Thought Vectors - What Motivated Doug Engelbart

June 23, 2014 · · Posted by Greg Lloyd

ImageBy "augmenting human intellect" we mean increasing the capability of a man to approach a complex problem situation, to gain comprehension to suit his particular needs, and to derive solutions to problems. Increased capability in this respect is taken to mean a mixture of the following: more-rapid comprehension, better comprehension, the possibility of gaining a useful degree of comprehension in a situation that previously was too complex, speedier solutions, better solutions, and the possibility of finding solutions to problems that before seemed insoluble. And by "complex situations" we include the professional problems of diplomats, executives, social scientists, life scientists, physical scientists, attorneys, designers--whether the problem situation exists for twenty minutes or twenty years. We do not speak of isolated clever tricks that help in particular situations. We refer to a way of life in an integrated domain where hunches, cut-and-try, intangibles, and the human "feel for a situation" usefully co-exist with powerful concepts, streamlined terminology and notation, sophisticated methods, and high-powered electronic aids. 1a1

Man's population and gross product are increasing at a considerable rate, but the complexity of his problems grows still faster, and the urgency with which solutions must be found becomes steadily greater in response to the increased rate of activity and the increasingly global nature of that activity. Augmenting man's intellect, in the sense defined above, would warrant full pursuit by an enlightened society if there could be shown a reasonable approach and some plausible benefits. 1a2

Doug Engelbart Augmenting Human Intellect: A Conceptual Framework. SRI Summary Report AFOSR-3223, October 1962

This week's Thought Vectors in Concept Space assignment is a blog post based on a nugget from the works of Doug Engelbart. I like this quote because Doug talks clearly about what motivates his research; what motivated his life's work.

To me, it's interesting to note that Doug wrote his report in 1962 just as NASA was launching Project Apollo, and not long after President John F. Kennedy announced his challenge to land on the Moon. Project Apollo was arguably the most challenging engineering project of the 20th century, designing and testing families of new engineering systems as well as new classes of hardware. But Project Apollo was more than an engineering project; it was a grand challenge that motivated NASA to do its best and engaged most of the world as spectators in a high stakes, highly visible race to the Moon.

Doug's vision was also an engineering vision, designing and testing new human/computer systems as well as new classes of software. The paragraphs, links, paragraph-grain addresses, relationships, viewspecs and visualizations of Augment/NLS made Doug's thought vectors as real as they could possibly be, recording, linking and animating thoughts in a way that could never be done with paper plans and records. But like Project Apollo, Doug's vision was more than an engineering project; it was and is a grand challenge, to find better ways to enable people to solve critical problems, part of a trail on augmentation started by Vannevar Bush that will never end.


"Thoughtvectors in Concept Space badge" by @iamTalkyTina my posts |


Doug Engelbart | 85th Birthday Jan 30, 2010 - Blog post celebrating Doug Engelbart's 85th birthday, includes quotes and links to resources. One of the quotes from Engelbart's talk at the Brown/MIT Vannevar Bush Symposium became the tag line for this VCU course. The Doug Engelbart Institute was was conceived by Doug Engelbart to further his lifelong career goal of boosting our ability to better address complex, urgent problems. It contains an excellent history, archive of papers, photos and other published resources as well as links to Doug's current projects.

Video Archive MIT / Brown Vannevar Bush Symposium: A Celebration of Vannevar Bush's 1945 Vision, An Examination of What Has Been Accomplished, and What Remains to Be Done. Oct 12-13 1995, MIT. Talks and panel discussion with Doug Engelbart, Ted Nelson, Andy van Dam, Tim Berners-Lee, Alan Kay and others. See also ACM Interactions summary (free access), transcript of day 1 and day 2 panels.

Augmenting Human Intellect: A Conceptual Framework. by Douglas C. Engelbart, October 1962 (SRI AUGMENT, 3906) A work Doug referred to as the bible of his research agenda, it also outlines the motive for his work: enabling groups of people to respond to the increasingly complex and urgent problems of humanity. If you want to read Doug's original works, start here.

Reinventing the Web II

June 16, 2014 · · Posted by Greg Lloyd

ImageUpdated 29 May 2015 Why isn't the Web a reliable and useful long term store for the links and content people independently create? What can we do to fix that? Who benefits from creating spaces with stable, permanently addressable content? Who pays? What incentives can make Web scale permanent, stable content with reliable bidirectional links and other goodies as common and useful as Web search over the entire flakey, decentralized and wildly successful Web? A Twitter conversation.

How the Web was Won

I believe Tim Berners-Lee's original HTTP and HTML protocols succeeded beyond his original vision of a globally scalable, loosely coupled network of Web pages that anyone could edit. The fact that his original protocols were simple, decentralized, and free for anyone to use were essential to success in a world of competing proprietary Internet publishing and commerce "standards" from Microsoft and others. But in my opinion, the Web won by turning permanence and stability into a decentralized economic decision.

Berners-Lee's original W3C protocols appeared at the right time to open clear field opportunities for distributed publishing, marketing, sales and advertising that fueled the Web's growth and evolution. Recapping the argument from my first Reinventing the Web post:

The idea that any sensible person would rely on a global hypertext system where links on one computer pointed at locations on another computer which would break whenever the remote computer was unilaterally moved, renamed, taken off line or abandoned seemed absurd.

The idea that you would have no way to know what incoming links would break when editing or refactoring content seemed just as bad.

The Word Wide Web protocols looked like they would work for relatively small cooperative groups like CERN who could keep things from breaking by having shared goals, and using peer pressure plus out of band communication to keep distributed content alive.

Actually that intuition was pretty good, because the World Wide Web took off in a direction based on other incentives compatible with those assumptions - and grew like crazy because unlike alternatives, it was was simple, massively scalable, cheap and eliminated the need for centralized control.

1) The Web became a distributed publishing medium, not the fabric for distributed editing and collaboration that Tim Berners-Lee and others envisioned. People and Web publishing engines like Amazon created content and kept it online while it had economic value, historical value (funded by organizations), or personal value. Content hosting became cheap enough for individuals or tiny groups. Advertising supported content became "free".

2) Search engines spanned the simple Web. Keeping content addressable now gained value since incoming links not only allowed people to bookmark and search engines to index what you had to publish (or sell), but the incoming links gained economic value through page rank. This provided even greater motivation to edit without breaking links, and to keep content online while it retained some economic, organizational or personal value.

3) People and organizations learned how to converse and collaborate over the Web by making it easy to create addressable content others could link to. The simple blog model let people just add content and have it automatically organized by time. The Wiki model required more thought and work to name, organize and garden content, but also creates stable, addressable islands of pages based on principals that reward cooperative behavior.

4) Search engines, syndication and notification engines built over the Web's simple, scalable protocols connected the Web in ways that I don't think anyone really anticipated - and work as independent and competing distributed systems, making rapid innovation possible.

Tim Berners-Lee made an inspired set of tradeoffs. Almost every concept of value on the Web: search engines, browsers, notification is built over his simple, open, highly scalable architecture.

I believe it's possible to provide what TBL calls "reasonable boundaries" for sharing sensitive personal or organizational data without breaking basic W3C addressable content protocols that makes linking and Web scale search valuable. That should be the goal for social and business software, not siloed gardens with Web proof walls.

Building a better Web over the Web we have

Telephone companies used to call their simplest and cheapest legacy service POTS (Plain Old Telephone Service). I believe it's possible to build a richer and more stable Web over POWS (Plain Old Web Services) without necessarily starting from scratch.

One answer to "who benefits?" and "who pays?" are the businesses who benefit from a richer and more stable Web connecting the systems they use to get work done. Stable fine-grain links and bi-directional relationships connecting systems of record and systems of engagement open the door to business systems that are more flexible, effective, simple to develop, and pleasant to use - more like the public Web than traditional line of business systems.

Museums, libraries, and archives such as Brewster Kahle's Internet Archive, the Library of Congress and others have a mission to collect and curate our cultural heritage and knowledge. The Internet Archive shows how little it costs to collect and index an archive of the content of the visible Web.

Commercial publisher monetize their archive, but have weaker economic incentives to maintain stable links to content outside their own domain.

Commerce sites and providers of consumer-focused Web services may have the greatest economic incentive for deep linking with stable references and relationships spanning devices you own, your home, your health and healthcare providers, your car, your family - and your work, see Continuity and Intertwingled Work.

If I'm right, there are economic incentives for Web content creators to make their work more linkable, visible and useable using straightforward, decentralized, and non-proprietary upwards compatible extensions of Plain Old Web Services.

I believe that indices spanning permalinked locations as well as incoming and outgoing permalink references to content in "stable islands in the storm tossed sea" can be created and maintained in near real time at Web scale, preserving the integrity of links to archival content distributed across the Web.

For example, any domain could publish an index to its permalinked content. Other domains implementing the same protocol could make incoming references to that content by permalink. This is a simple decentralized protocol, no more magical than the published external references that a link editor or dynamic linking system uses to resolve references connecting independently compiled modules of code.

Domains that agree to implement the same protocol, and use permalink (URI) references for content in other compatible domains then have a more stable, decentralized model for permanent links. If domains also publish their own permalink outgoing references (external as well as internal), a Web level service could build and maintain reliable inverted indices of bi-directional internal and domain spanning links. The federation of such domains could be spidered by any number of independently developed services, creating a more stable and useful Web as a decentralized service without breaking the simple Web protocols that every browser and other Web service relies on.

I don't know who has suggested this before; it seems obvious, and is a straw man not a solution. I'm using it to argue that we can and should invent ways to improve the capabilities of the Web using the same simple, decentralized philosophy that made the Web wildly successful versus "better" hypertext systems.

See Michael Peter Edson's Dark Matter essay and my Thought Vectors - Vannevar Bush and Dark Matter response.


Reinventing the Web (2009) Ted Nelson, Tim Berners-Lee and the evolution of the Web. Ted Nelson wants two-way links, stable transclusion, micropayments. Tim Berners-Lee wants a new Web with open, linked data. I believe that most of what they want can be delivered using the current flakey, decentralized and wildly successful Web as the delivery medium for richer, more stable, more permanent internal models, as stable federations of islands in a storm-tossed sea.

The Internet's Original Sin by Ethan Zuckerman, The Atlantic, Aug 14, 2014. Ethan confesses his role - invention of the pop-up Ad - stating "It’s obvious now that what we did was a fiasco, so let me remind you that what we wanted to do was something brave and noble." He makes a convincing case that the apple in the Web's garden is Investor storytime "... when someone pays you to tell them how rich they’ll get when you finally put ads on your site." A darkly comic but heartfelt essay on the past and future economy of the Web: "It's not too late to ditch the ad-based business model and build a better web"

Intertwingled Work (2010) No one Web service or collection of Web servers contain everything people need, but we get along using search and creative services that link content across wildly different sources. The same principal applies when you want to link and work across wildly diverse siloed systems of record and transactional databases.

Dark Matter: The dark matter of the Internet is open, social, peer-to-peer and read/write—and it’s the future of museums by Michael Peter Edson on May 19, 2014.

Continuity and Intertwingled Work (2014) A level above an Internet of Things: seamless experience across devices for you, your family, your health and trusted service providers, at home and at work.

Reinventing the Web III (2014) followup Twitter conversation with @zeynep, @jeffsonstein, @kevinmarks, and @roundtrip.

The Web of Alexandria (2015) by Bret Victor "We, as a species, are currently putting together a universal repository of knowledge and ideas, unprecedented in scope and scale. Which information-handling technology should we model it on? The one that's worked for 4 billion years and is responsible for our existence? Or the one that's led to the greatest intellectual tragedies in history?"

And Victor's followup post "Whenever the ephemerality of the web is mentioned, two opposing responses tend to surface. Some people see the web as a conversational medium, and consider ephemerality to be a virtue. And some people see the web as a publication medium, and want to build a "permanent web" where nothing can ever disappear. Neither position is mine. If anything, I see the web as a bad medium, at least partly because it invites exactly that conflict, with disastrous effects on both sides."

Update 13 Jul 2014 Added new section headings, added the inline recap and economic benefit examples, added a link to a Jul 2014 Reinventing the Web III Twitter conversation on the same topic.

Update 23 Aug 2014 Added link and brief note on Ethan Zuckerman's fine essay on advertising as the Internet's Original Sin.

Update 29 May 2015 Added links to Web of Alexandria and followup by Bret Victor on why the Web is a bad medium.

Thought Vectors - Vannevar Bush and Dark Matter

June 13, 2014 · · Posted by Greg Lloyd

ImageOn Jun 9 2014 Virginia Commonwealth University launched a new course, UNIV 200: Inquiry and the Craft of Argument with the tagline Thought Vectors in Concept Space. The eight week course includes readings from Vannevar Bush, J.C.R. Licklider, Doug Engelbart, Ted Nelson, Alan Kay, and Adele Goldberg. Assignments include blog posts and an invitation to participate on Twitter using the #thoughtvectors hashtag. The course has six sections taught at VCU, and an open section for the rest of the internet, which happily includes me! This week's assignment is a blog post based on a nugget that participants select from Vannevar Bush's 1945 essay As We May Think. Here's mine:

Wholly new forms of encyclopedias will appear, ready made with a mesh of associative trails running through them, ready to be dropped into the memex and there amplified. The lawyer has at his touch the associated opinions and decisions of his whole experience, and of the experience of friends and authorities. The patent attorney has on call the millions of issued patents, with familiar trails to every point of his client’s interest. The physician, puzzled by a patient’s reactions, strikes the trail established in studying an earlier similar case, and runs rapidly through analogous case histories, with side references to the classics for the pertinent anatomy and histology. The chemist, struggling with the synthesis of an organic compound, has all the chemical literature before him in his laboratory, with trails following the analogies of compounds, and side trails to their physical and chemical behavior.

The historian, with a vast chronological account of a people, parallels it with a skip trail which stops only on the salient items, and can follow at any time contemporary trails which lead him all over civilization at a particular epoch. There is a new profession of trail blazers, those who find delight in the task of establishing useful trails through the enormous mass of the common record. The inheritance from the master becomes, not only his additions to the world's record, but for his disciples the entire scaffolding by which they were erected.

This quote is part of a longer section in Bush's essay describing his concept of the Memex, a desktop machine imagined as an extension of 1940's microfilm and vacuum tube technology.

This quote stuck me while reading Michael Peter Edson's essay Dark Matter published on in May 2014.

Edson's essay begins "The dark matter of the Internet is open, social, peer-to-peer and read/write—and it’s the future of museums" explaining:

I am talking about museums, libraries, and archives—heritage, culture, knowledge, and memory institutions—and there is really nothing like them on the face of the earth. And whether we’ve realized it or not, my colleagues and I who work with technology in these institutions have been participating in an extraordinary project — the building of a planetary scale knowledge sharing network for the benefit of everyone on earth.

He writes:

Despite the best efforts of some of our most visionary and talented colleagues, we’ve been building, investing, and focusing on only a small part of what the Internet can do to help us accomplish our missions.

90% of the universe is made of dark matter—hard to see, but so forceful that it seems to move every star, planet, and galaxy in the cosmos.

And 90% of the Internet is made up of dark matter too—hard for institutions to see, but so forceful that it seems to move humanity itself.

And it’s not necessarily that the glass of museum, library, and archive technology projects is half empty, as opposed to half full; it’s the fact that the glass of the Internet and the dark matter of open, social, read/write cultural engagement is so much bigger than museums, libraries, and archives are accustomed to seeing and thinking about. And the glass keeps growing at exponential speed, whether we fill it with good work or wait in committee meetings for the water to pour itself…

Edson concludes that museums, libraries, and archives "can play a huge role in the story of how Earth’s 7 billion citizens will lead their lives, make and participate in their culture, learn, share, invent, create, cry, laugh, and do in the future" by going back to Tim Berners-Lee's original vision of the Web, where every person can be a writer as well as a reader.

Cultural Web sites, blogs, Google, Facebook, Twitter and are part of the solution, but Edison's challenge goes beyond that.

I believe there are three parts to his challenge:

The role of trail blazer: Just as Bush suggested in July 1945, I believe there's a need for people to act as explorers, guides, and trail blazers over knowledge they know and love. You can experience that personal knowledge and passion on a tour, at a talk, or in a conversation on a bus, at a party - anywhere you meet someone who loves one of these institutions. I think it's particularly valuable to have trail blazers who are also skilled professionals personally represent and communicate the values, knowledge, and heritage of their museum, just as a great reference librarian becomes a library's ambassador.

The medium: Museums have long had lectures, journals, and newsletters. Most cultural institutions now have web sites, blogs, and Twitter or Facebook accounts, which can be really interesting depending on who does the writing and response. In Dark Matter Edson goes well beyond the comfort zone of most museums into the world of video blogging, Reddit, Pinterest, Tumbler and more. Of the video blogging brothers who created 1,000 plus videos on the YouTube Vlogbrothers channel, Edson writes:

It is evident from watching 30 seconds of any of their videos that they are nerds, and they proudly describe themselves as such. If you announced to your museum director or boss that you intended to hire Hank and John Green to make a series of charming and nerdy videos about literature, art, global warming, politics, travel, music, or any of the other things that Hank and John make videos about you would be thrown out of whatever office you were sitting in and probably be asked to find another job.

The mission: A little less than a year before the end of World War II, President Franklin D. Roosevelt wrote a letter to Vannevar Bush, asking Bush how to turn the "unique experiment of team-work and cooperation in coordinating scientific research and in applying existing scientific knowledge" during WWII to the peaceful pursuit of scientific knowledge after the end of the war. President Roosevelt concluded: "New frontiers of the mind are before us, and if they are pioneered with the same vision, boldness, and drive with which we have waged this war we can create a fuller and more fruitful employment and a fuller and more fruitful life." Bush responded to then President Harry S. Truman in July 1945, the same month As We May Think was published in The Atlantic Monthly. Bush's report, titled Science the Endless Frontier, lead to the creation of the National Science Foundation.

The Dark Matter mission is different, but it calls on museums and other cultural institutions to rethink how they bring together the heritage they preserve and the broader society they serve. I believe that the skills and passion of trail blazers can help connect the people and the common record of their culture by creating trails that can be seen and built upon now and by future generations. Anyone can now create a trail, and museums should become the richest and most welcoming sources for trail creation. Museums can help by opening up access as well as by creating and curating trails - across all media - as part of their core mission, a unique experiment in team-work and cooperation.

See Dark Matter and Trailblazers - @mpedson and Vannevar Bush for more quotes from Michael Peter Edson's essay, quotes from As We May Think, and President Roosevelt's wartime letter to Vannevar Bush.

Update Oct 30, 2014 See Michael Peter Edson's Internet Librarian International 14 keynote slides, Dark Matter 

Update Jan 21, 2015: See The Museum of the Future Is Here by Robinson Myer, The Atlantic, Jan 20, 2015. A thoughtful redesign of the Smithsonian's Cooper Hewett museum adds a stable URL for every object in its collection, as well as an API for accessing related content.

What the API means, for someone who will never visit the museum, is that every object , every designer , every nation , every era , even every color has a stable URL on the Internet. No other museum does this with the same seriousness as the Cooper Hewitt. If you want to talk about Van Gogh’s Starry Night online, you have to link to the Wikipedia page . Wikipedia is the best permanent identifier of Starry Night-ness on the web. But if you want to talk about an Eames Chair, you can link to the Cooper Hewitt’s page for it ...

“When we re-open, the building will be the single largest consumer of the API,” said Chan.

In other words, the museum made a piece of infrastructure for the public. But the museum will benefit in the long term, because the infrastructure will permit them to plan for the near future.

And the museum will also be, of course, the single largest beneficiary of outsider improvements to the API. It already talks to other APIs on the web. Ray Eames’s page , for instance, encourages users to tag their Instagrams and Flickr photos with a certain code. When they do, Cooper Hewitt’s API will automatically sniff it out and link that image back to its own person file for Eames. Thus, the Cooper Hewitt’s online presence grows even richer.


"Thoughtvectors in Concept Space badge" by @iamTalkyTina my posts |


As We May Think - Vannevar Bush, Atlantic Monthly, July 1, 1945

Reinventing the Web - Blog post on the creation and evolution of the Web and thoughts on making the Web a more writerly medium based on Berners-Lee's original intent and the vision of Ted Nelson.

Doug Engelbart's copy of As We May Think - with Doug's 1962 notes scribbled in the margins - Blog post also includes links to the Oct 1995 Brown/MIT Vannevar Bush Symposium on the 50th anniversary of As We May Think, with videos of talks and panel sessions.

Doug Engelbart | 85th Birthday Jan 30, 2010 - Blog post celebrating Doug Engelbart's 85th birthday, includes quotes and links to resources. One of the quotes from Engelbart's talk at the Brown/MIT Vannevar Bush Symposium became the tag line for this VCU course:

Doug Engelbart: ... So, moving your way around those thought vectors in concept space - I'd forgotten about that

Alan Kay: You said that, right?

Doug Engelbart: I must have, its so good. [laughter] Its to externalize your thoughts in the concept structures that are meaningful outside and moving around flexibly and manipulating them and viewing them. Its a new way to operate on a new kind of externalized medium. So, to keep doing it in a model of the old media is just a hangup that someplace we're going to break that perspective and shift and then the idea of high performance and the idea of high performance teams who've learned to coordinate, to get that ball down the field together in all kinds of operations.

Continuity and Intertwingled Work

June 12, 2014 · · Posted by Greg Lloyd

ImageAt Apple's WWDC 2014 on 2 Jun 2014, Apple demonstrated how to build a great user experience spanning a your iPhone, iPad, and Mac. Apple calls this OS level capability Continuity. It enables you to continue what you're doing across devices and applications by securely encapsulating your identity and the context of your action as an object. From picking up a draft email message started on an iPhone and continuing work with that draft on your Mac, to answering an incoming iPhone call on your Mac, I believe this opens the door for a level of seamless experience that everyone will want for personal use, their family, and at work.

Here’s why. I believe Apple aims to connect:

  • Your actions, across the devices you use
  • Your family (Family Sharing);
  • Your home (HomeKit);
  • Your health and healthcare providers (HealthKit);
  • Your car (CarPlay) See what Apple is offering via auto OEMs;
  • Your work (by extension I'll call this WorkKit) If Apple wanted to play in the enterprise software space. [Apple does want to play, see IBM/Apple Update below - grl]

Regardless of Apple’s intention as a platform for business applications, if Apple succeeds in the personal space, I believe this vision of continuity sets a benchmark for user experience at work, and will kick off a new level of competition to win the attention of enterprise developers and IT departments, working top down rather than bottom up.

1) Apple is using SDK extensions to bridge access to other Apps and OS services. My understanding of the SDK extensions introduced at WWDC 2014 is that personal information and context flows across Apps and iOS services based on extension of the App sandboxing that has kept iOS relatively malware free and consistent. This is critical if you believe that Apple’s strategic goal is to become the trusted, secure home for a fabric of personal information that includes a record of your actions in context. The fabric links you, your devices, your family, your health information, and other things you own or use including your home, car, and what you use at work. The record of actions in context makes it possible to learn, use, and reason about the verbs (actions) and nouns (things) you use every day, including the context in which you use them. It's what I believe is needed to make an Internet of Things usable.

2) Google, Yahoo and others gather correlate, analyze and use personal identity metadata including your location, search history, browsing history to monetize for their own purposes or to sell to others. I believe Apple is trying to build a counter story on security using identity and services encapsulated in devices you own. [Confirmed. See 17 Sep 2014 A message from Tim Cook about Apple’s commitment to your privacy and links below - grl] In addition to continuity, examples include OS8 MAC address randomization for WiFi localization privacy and hardware partitioned storage of iOS fingerprint data.

3) Folk who dislike the Apple’s walled garden and curated applications sometimes fail to acknowledge that many people value a safer, more consistent, curated, and delightfully designed user experience to a toolkit.

4) I want my personal information and keys to access health, home, car, family information stored in a walled garden in a device I own, with gated access looking in for Apps I authorize, and delegated freedom to search, link and use anything I have rights to looking out. Apple appears to be developing its stack top down, starting from a vision of a seamless user experience that just works, giving developers the extensions they need to innovate and prosper.

5) I believe Apple’s principles of continuity and identity are also what businesses need for a safe, secure, consistent, delightful, and productive user experience for people at work, see Intertwingled Work and Work Graph Model: TeamPage Style.

Update 12 Aug 2014

IBM's 15 July 2014 partnership announcement with Apple caught many analysts by surprise. To me, it makes perfect sense as a path to broaden Apple's market. Over the past several years Apple's iOS security, provisioning, and deployment investments removed barriers and eliminated friction for Enterprise customers bowing to Apple as the inevitable Bring Your Own Device of choice. IBM's position as a trusted supplier and developer for Enterprise customers complements Apple's position and focus as your lifestyle hub - for healthcare, home, family, car, and work - and the Internet of Things. I see Google as Apple's only potential competitor. Look for interesting times.

Tbits: Putting IBM MobileFirst in (Apple’s Enterprise) Context Andrew Laurence writes: "Since the iPhone, Apple has developed a subtle enterprise strategy, so subtle that many pundits miss it. Instead of pursuing business sales directly, Apple has quietly worked to remove barriers that might impede usage of its products, including in enterprises. This approach enables Apple to pursue design and user experience while also making its devices more useful to business and fitting enterprise concerns better..."

"Although commonly known as a “computer company,” IBM is really a software and services company, focused on developing and supporting applications for customers. And not only applications, but whole solutions, which requires combining development, hardware, software, management, and more. When a company hires IBM, they also sign on to purchase software licenses; for IBM to supply, manage, and service hardware through its lifecycle; and to purchase support for it all through the life of the contract. The service contract includes not only development of the application if necessary, but also ongoing support and management services: provisioning and deployment, as well as integration of the application and hardware into a cohesive whole to provide a coherent solution..."

For IBM’s customers, the MobileFirst endeavor represents just such an opportunity. Their applications can be developed and deployed on Apple’s popular iOS platform, drawing on IBM’s deep well of enterprise development experience and letting IBM bask in Apple’s reflected glory. I imagine that IBM will get special pricing for Apple products sold through MobileFirst; I also suspect these devices will be provisioned through Apple’s Streamlined Enrollment and tightly managed (via mobile device management policies) through IBM’s Endpoint Manager and MaaS360 products, with software procurement managed through Apple’s Volume Purchase Program."

How IBM could help Apple win one of the biggest markets of all Ryan Faas writes in CITEworld: "Apple's partnership with IBM may deliver more value to Apple than just expanding the iPad's penetration in the business world. Although the partnership will certainly focus on creating business apps, the focus on creating industry-specific apps may boost Apple's fortunes in one of the fields that it is actively seeking to disrupt -- health care."

Update 23 Aug 2014

Apple HealthKit and VRM. A thoughtful essay by Doc Searles. Doc methodically examines Apple's HealthKit from the perspective of Vendor Relationship Management (VRM) principles, goals, and tool requirements - all relating to customers ability to define and manage their own relationship with vendors, rather than vice versa. He finds that HealthKit's principles appear to be an encouraging match, quoting this blog post on "security using identity and services encapsulated in devices you own".

On points 3) and 4) of this blog post, Doc says:

"As a guy who favors free software and open source, I agree to the extent that I think the best we can get at this stage is a company with the heft of an Apple stepping and doing some Right Things. If we’re lucky, we’ll get what Brian Behlendorf calls “minimum viable centralization.” And maximum personal empowerment. Eventually."

Doc see one big unanswered question:

In all cases the unanswered question is whether or not your health data is locked inside Apple’s Health app. Apple says no: “With HealthKit, developers can make their apps even more useful by allowing them to access your health data, too. And you choose what you want shared. For example, you can allow the data from your blood pressure app to be automatically shared with your doctor. Or allow your nutrition app to tell your fitness apps how many calories you consume each day. When your health and fitness apps work together, they become more powerful. And you might, too.

Update 18 Sep 2014

We're Building Privacy Into Everything You Use Every Day Apple on privacy. The moment you begin using an Apple product or service, strong privacy measures are already at work protecting your information. We build extensive safeguards into our apps and the operating systems they run on. Apple examples include: iCloud; Safari; Maps, Siri and Dictation; Mail; Apps and the App Store; Pay; Health; HomeKit; Spotlight Suggestions; Randomized Wi-Fi Addresses; Security by Design]

A message from Tim Cook about Apple’s commitment to your privacy Quotes:

At Apple, your trust means everything to us. That’s why we respect your privacy and protect it with strong encryption, plus strict policies that govern how all data is handled...

Security and privacy are fundamental to the design of all our hardware, software, and services, including iCloud and new services like Apple Pay. And we continue to make improvements. Two-step verification, which we encourage all our customers to use, in addition to protecting your Apple ID account information, now also protects all of the data you store and keep up to date with iCloud...

A few years ago, users of Internet services began to realize that when an online service is free, you’re not the customer. You’re the product. But at Apple, we believe a great customer experience shouldn’t come at the expense of your privacy.

Our business model is very straightforward: We sell great products. We don’t build a profile based on your email content or web browsing habits to sell to advertisers. We don’t “monetize” the information you store on your iPhone or in iCloud. And we don’t read your email or your messages to get information to market to you. Our software and services are designed to make our devices better. Plain and simple.

One very small part of our business does serve advertisers, and that’s iAd. We built an advertising network because some app developers depend on that business model, and we want to support them as well as a free iTunes Radio service. iAd sticks to the same privacy policy that applies to every other Apple product. It doesn’t get data from Health and HomeKit, Maps, Siri, iMessage, your call history, or any iCloud service like Contacts or Mail, and you can always just opt out altogether.


Apple's WWDC 2014 Continuity Demo: Identity, Security, User Experience - Storified clipping of the Twitter conversation with @dhinchcliffe @DylanTWilliam and @haydn1701 that motivated this post.

Internet of Everything - Four Questions (with Tweets) - Ron Miller moderated a 20 Jun 2014 Twitter conversation on The Internet of Everything. Ron defined IoE: "For context think of the Internet of Everything as the Internet of Things plus people, process and data." A few Tweets from me specifically related to the topic of this post:

"When I walk into a room, every device and system should know who I am, what I'm interested in, what I can do."

"Not just "May I refill your coffee?" from the coffee pot, but "whoops looks like widget supplier will be late" on ERP wall."

“Device/owner delegates authority to trusted service to securely collect data and act on things on behalf of owner” vs

"Assumes HQ is safe and challenges device in field to prove to what level it and its owner can be trusted"

Software design is taught in the wrong department. Interactive software is a branch of cinema - Ted Nelson, April 2001

Intertwingled Work (2010) No one Web service or collection of Web servers contain everything people need, but we get along using search and creative services that link content across wildly different sources. The same principle applies when you want to link and work across wildly diverse siloed systems of record and transactional databases.

The Work Graph Model: TeamPage style ... the units of work (tasks, ideas, clients, goals, agenda items); information about that work (relevant conversations, files, status, metadata); how it all fits together; and then the people involved with the work (who’s responsible for what? which people need to be kept in the loop?)

A new TeamPage logo, and a new look at Traction

June 9, 2014 · · Posted by Greg Lloyd

ImageYou'll be seeing the new TeamPage logo here, on Twitter, Facebook, across the Web, and next to TeamPage sites shown in your browser's tabs; I hope you like the it! I also hope you like the the new look at Our customers believe TeamPage is ideal for work that combines collaboration and action tracking, including quality management, human resources, project work, intelligence analysis, knowledge management, and compliance. We want to tell this story simply and clearly, and we'll continue to improve this site just as we continually improve TeamPage. Please contact us for insights into how customers use TeamPage to get work done, along with a free trial.

Where Collaboration Meets Chess

April 4, 2014 · · Posted by Jordan Frank

In 12 Habits of Highly Collaborative Organizations, @Jacob Morgan draws awesome parallels between collaboration strategy and chess strategy:

Chess is virtually an infinite game yet somehow we have grand-masters who are always at the top. How do they succeed in this infinite game? They identify patterns and look for identifiable scenarios. This same approach is applicable for collaboration.

Jacob outlines 12 strategies for successful collaboration. They're numbered but there's no specific order here -- the key is to assimilate these strategies and match them to any as a means to develop the right mix of approaches that will turn a grass roots effort into a collaborative productivity engine for your organization.


These strategies are vital when you seek improvement opportunities with social process engineering. To tackle this grand problem, I like to look first at one working group's key artifacts - whether they are process documents, issues to track, or any other material that passes over your desk regularly - then I start at "6. Integrate into the flow of work" and develop an approach that is supported by the other 11 principles outlined by Jacob.

Thinking like a chess master enables you to make a first tactical move, but do so within a framework that sets you up for success further down the line when use cases are added and new stakeholders must be convinced.

An Infinite Number of Cats on Keyboards: Ted Nelson & Computer Lib at Homebrew Computer Club Reunion

November 16, 2013 · · Posted by Greg Lloyd

Order a perfect reprint of the original version of Computer Lib / Dream Machines directly from Ted Nelson, autographed if you wish. Highly recommended.


Ted Nelson's original 1974 edition of Computer Lib / Dream Machines was tour de force on hypertext, personal computers, and more. It was printed tabloid size, with Ted's hand drawn diagrams, neatly scribbled annotations, pasteup text and graphics in a style that has to be seen to be appreciated: think Whole Earth Catalog for computer geeks, film buffs, authors, philosophers, cartoonists, carnival barkers, and children of all ages.

In 1987 Microsoft Press did a good deed by reprinting the book, but chose a standard trade paperback layout which lost much of the charm.

The 1974 edition printed by Hugo's Book Service in Chicago has two front covers (one for Computer Lib and one for Dream Machines). Both books share the same binding, and you flip to read in either order. An original edition sells for over $250 when you can find a copy.

Read a fine essay and authorized sample from Computer Lib / Dream Machines as well as other classics at New Media Reader Excerpts, by Noah Wardrip-Fruin and Nick Montfort (Editors), MIT Press 2003.

In Nov 2013 Ted announced that you can order a perfect reprint directly from him for $100 including US postage ($108 for California residents).

See Mark Graybill's blog post on meeting Ted at the Homebrew Computer Club Reunion, 11 Nov 2013.

Here's the back of the Computer Lib flyer including payment address, terms, and email ordering address:


Ted Nelson speaks at the HomeBrew Computer Club Reunion, 11 Nov 2013 (YouTube video)

Update: On April 24, 2014 Chapman University hosted INTERTWINGLED: The Work and Influence of Ted Nelson. The conference "examined and honored the work and influence of this computer visionary and re-imagined its meaning for the future". Speakers include: Belinda Barnet, Dame Wendy Hall, Alan Kay, Ken Knowlton, Jaron Lanier, and Noah Wardrip-Fruin. Concluding remarks by Ted Nelson. See conference session videos.

Update: Intertwingled, The Festschrift-- Ebook celebrating Ted Nelson Day at Chapman University, 2014 (Springer-Verlag) (via @TheTedNelson, 12 Jul 2015) A free Springer ebook edited by Douglas R. Dechow and Daniele C. Struppa. Chapters by Alan Kay, Brewster Kahle, Belinda Barnet, Ken Knowlton, Dame Wendy Hall, and others. Closing chapter What Box? by Ted Nelson. I highly recommend this book.

Ada Lovelace Day | Marissa Ann Mayer, Software Engineer, Product Manager, and Executive

October 15, 2013 · · Posted by Greg Lloyd

Ada Lovelace Day celebratesImage the contributions of women in science and technology, follow @FindingAda for news and events. This year I've chosen to write about Marissa Ann Mayer Software Engineer, Product Manager, and Executive, currently President and CEO of Yahoo! Over her career Ms Mayer earned exceptional recognition for Computer Science teaching (while working for her Stanford degrees), software engineering, design, product management, and her executive skills. Ms Mayer joined Google as employee number twenty in 2009 and played an instrumental role leading Google Search for over 10 years.

In 2013 Ms Mayer ranked 31 in the Forbes Magazine list of the World's 100 Most Powerful Women, and the first woman listed as number one on the Fortune Magazine's annual list of the top 40 business stars under 40 years old.

Quoting from her Yahoo! biography: "During her 13 years at Google, Marissa held numerous positions, including engineer, designer, product manager, and executive, and launched more than 100 well-known features and products. She played an instrumental role in Google search, leading the product management effort for more than 10 years, a period during which Google Search grew from a few hundred thousand to well over a billion searches per day. Marissa led the development of some of Google's most successful services including image, book and product search, toolbar, and iGoogle, and defined such pivotal products as Google News and Gmail. She is listed as an inventor on several patents in artificial intelligence and interface design.

Prior to joining Google, Marissa worked at the UBS research lab in Zurich, Switzerland and at SRI International in Menlo Park, California. She graduated with honors from Stanford University with a B.S. in Symbolic Systems and a M.S. in Computer Science. For both degrees, she specialized in artificial intelligence. While at Stanford, she taught computer programming to more than 3000 students and received the Centennial Teaching and Forsythe Awards for her contributions to undergraduate education. In 2008, the Illinois Institute of Technology awarded her an honorary doctorate of engineering."

"Companies with the best talent win." Marissa Mayer, CEO Yahoo!

Ada icon by Sidney Padua Download the Thrilling Adventures of Babbage & Lovelace for your iPad (free). Enjoy their adventures, backstory and more on author Sydney Padua's 2D Goggles Web page.

Previous years

Ada Lovelace Day | Sunita Williams, Astronaut and Captain U.S. Navy 2012

Ada Lovelace Day | Betts Wald, US Naval Research Lab 2011

Ada Lovelace Day | Fran Allen, IBM Fellow and A.M. Turing Award Winner 2010

Ada Lovelace Day | Professor Lee S. Sproull, Stern School, NYU 2009

The Work Graph Model: TeamPage style

October 11, 2013 · · Posted by Greg Lloyd

ImageJustin Rosenstein wrote an excellent option piece for Wired, The Way We Work Is Soul-Sucking, But Social Networks Are Not the Fix. Justin begins: "With Twitter’s recent IPO filing, the most popular graph dominating conversation is the “interest graph.” Before that, it was the “social graph,” courtesy of Facebook. But we’re now seeing the emergence of a third important graph: the work graph." The work graph term is new - and useful - but I believe the model dates back to Lotus Notes and even Doug Engelbart. In this blog post I'll review Justin's definition and use it to describe Traction TeamPage's work graph model. I'll also show how TeamPage leverages its work graph model to meet challenges of information overload, work with external as well as internal teams, and work that needs to span siloed systems of record.

Work graph defined

"...A work graph consists of the units of work (tasks, ideas, clients, goals, agenda items); information about that work (relevant conversations, files, status, metadata); how it all fits together; and then the people involved with the work (who’s responsible for what? which people need to be kept in the loop?).

The upshot of the latter data structure is having all the information we need when we need it. Where the enterprise social graph requires blasting a whole team with messages like “Hey, has anyone started working on this yet?”, we can just query the work graph and efficiently find out exactly who’s working on that task and how much progress they’ve made. Where the enterprise social graph model depends on serendipity, the work graph model routes information with purpose: towards driving projects to conclusions." Justin Rosenstein, Wired 9 Oct 2013

Just so!

TeamPage's work graph

TeamPage watches what you do, and automatically maintains two-way links and relationships as you edit, keeping an accurate version history of everything so you can easily see what changed, when, and who did what.

TeamPage's work graph automatically connects articles, comments, status messages, tasks, milestones, projects, links, shared references, and relationships stored in TeamPage to the TeamPage profile of the person who created, edited or tagged the work, along with a time stamp for the action.


This concept of a work graph is helpful in describing what TeamPage automatically creates and maintains as you work.

But what counts is how TeamPage uses its work graph model to cut clutter, make it much easier to work with people anywhere inside or outside your organization, and make files and records already in IT systems easily accessible to get work done.

The same work graph information is organized and presented two different ways: by person, or by unit of work. This enables TeamPage to show activity feeds, dashboards and calendars of people, linked to the work they created or edited, as well as activity feeds, dashboards, and calendars for specific tasks, projects, and spaces where many people work together.

Dealing with information overload - use the work graph to add context to de-clutter activity streams, navigation and search

You can start by creating a new task directly attached to any paragraph in a TeamPage article. TeamPage links the task and paragraph to make it simple to see what the task is about, in the context of the original meeting notes, spec, or question that kicked off the followup action. You don't need to explain much to define the task, because the task has a direct link to the original source - in context - making it much easier for anyone to come up to speed. Or just click the New Task button to create an independent task.

No more fumbling through your own email, hoping that the person you're working with can find their own copy of the right email or file, or wasting time sending copies to people who just realized they don't have the right stuff. Send a link to any TeamPage task or other item by email or your favorite messaging system when you want to talk about a complicated item during a phone call or video chat.

You can collect a set of tasks to manage as a named Project, and use name Milestone to specify common Start or End dates for related tasks.

You can focus on any specific project or collaboration space and see its dashboard and activity stream without irrelevant noise and clutter. You can also zoom out to a birds eye view which shows a dashboard, activity stream, or calendar view spanning everything you have permission to read. Or click any person's profile to see a dashboard, activity stream, or calendar view focused their work units and actions (clipped to what you're allowed to read).

You can shift your focus whenever you want. You can also watch any article, task, project, or other unit of work and get an automatic email or inline notification when it changes or is commented on. Click on the link in the message to zoom back to that context, or simply reply to the email notification to add a comment in the right place. Or subscribe to TeamPage's email digest for an automatically generated daily summary of activity with links you can click through to read more or reply.


Working with external and internal teams - use permission rules to clip what the work graph lets you see

TeamPage's work graph model includes permissioned access that automatically clips content to show just those work items, relationships, and search results each person is allowed to read.

This makes it simple to use TeamPage for work that can cross boundaries, linking customers, suppliers, partners and internal teams with different permissions to different business activities on the same TeamPage server.

TeamPages' work graph model allows you to put a private comment (or task) in a more private space where it's only visible to a smaller group. For example, an internal team discussion on a customer's question.

Typically each external client has a private space (like separate clients of a law firm), and internal team members have a birds eye view across all clients and most or all internal spaces. TeamPage makes it simple to set up granular access rules for spaces based on individual names, Active Directory, LDAP, or TeamPage group membership.

There's one TeamPage work graph connecting all internal, external, public and private content. Permission based filtering of TeamPage's work graph happens automatically and efficiently at a very deep level whenever activity stream, dashboard, comment thread, or search results are shown to any person. This technology is covered by Traction Software's US Patent 7,593,954.

With TeamPage you don't have to stand up multiple systems and juggle posts, conversations, and tasks across multiple social software silos to work with customers, clients, partners or internal teams working on different activities with different permissions.

Extending the work graph to content on the public Web, Intranet pages, and siloed systems of record.

TeamPage's Social Enterprise Web enables you to share, tag, task or comment on any page your browser can see on the public Web or on your private intranet. Just install TeamPage's Web browser plug-in extension for modern browsers including Internet Explorer, Chrome, Firefox, and Safari.

The Social Enterprise Web also lets you add a TeamPage share button (like Facebook or Google+ share buttons) or comment box (like Disqus) to any public or intranet Web page your organization controls. Comments are stored in TeamPage , and link back to the external Web page, which is treated as part of the TeamPage work graph.

As a bonus, the content of a page linked to TeamPage with the browser plug-in, share button, or comment box is automatically indexed for TeamPage search and drill down navigation.

The Social Enterprise Web makes pages on the public Web or your organization's intranet simple to see, share, find and connect to TeamPage tasks. A task or question on an internal purchase order page can tracked and used part of TeamPage's work graph without complicated or expensive custom integration.

For example, add a TeamPage comment box to an Purchase order page in a Web based ERP system by adding a JavaScript snippet, and see something like this:


TeamPage's Attivio Plus option enables you to extend the TeamPage work graph to content stored in your organization's SharePoint, Documentum, File server or SQL Database applications.

You can then search, share, task, tag or comment on any work item in these external systems, making live external transactions part of your TeamPage work graph, including integrated TeamPage and external content analysis, search and navigation.

The Attivio Plus option scales to handle very large external content stores using Attivio's world-class AIE technology along with a simple deployment model and licensing that's both flexible and affordable.

Contextual Computing At Work:

"In the world of work, I believe it's incredibly valuable to capture and connect the natural objects of your attention and interest, including tasks, projects, work product, relevant discussion, related references even if you're standing in for Siri or Google Now.

When Mr. Dithers shouts: "Bumstead! Where are we on the Acme Account?", the most timely, frequently discussed and contextually relevant version of Dagwood's Acme tasks, projects and work should pop up near the top of the result list, along with the cloud of tags and people who have touched or talked about tasks, projects and other related to the Acme account and its associated activity streams.

The important requirement is making tasks, projects, pages, discussions and other work products first class sharable, named objects that can be connected to each other and what you're working on, discussed, tagged, tasked, and navigated as well as found using search. Being able to talk about tasks and projects relating to Acme captures one important part of your interest and behavior graph (activity stream), and links these items to the names and behavior of other people working with or discussing the same objects.

The objects and connections made in the context of work are more reliable than connections that need to be inferred from your behavior - and they're available now, including the ability to connect tasks, projects, pages and discussion in TeamPage and files, discussion, email and SQL databases in your external systems of record. They record valuable context for Siri and Google Now when used at work - but there's no reason to wait to get started."

TeamPage examples

How to make your ISO Auditor Smile; And Make Your Professional Life Much Easier Use TeamPage to create, edit, view work instructions from concept to shop floor, tracking every part qualification and compliance issue and notifying everyone when a significant change has occurred so they can read about and adopt the new procedure on their own. Result: a happy and productive team, and a smiling ISO auditor.

Zoom in to focus, zoom out for awareness, bubble up items in the flow of work TeamPage shows dashboard, activity stream, and calendar views of any project, task, milestone when you want to focus on a specific action, or zoom out to get a dashboard that shows a birds eye view of all business activity (based on what each person has permission to read). You can also click to any person's TeamPage profile and see a dashboard, activity stream, or calendar view of all of that person's actions (based on what each person has permission to read).

The Future of Work Platforms: Like Jazz When you watch a skilled team in action, it's like watching a great jazz group - there are themes, there is structure, and there are limits, but a team shines in individual excellence combined with coordination, improvisation, innovation, handling exceptions, and seemingly effortless awareness of where others are and where they're headed. The TeamPage action tracking model focuses on making it simple for individuals and teams to plan and coordinate the daily, weekly and monthly activities that drive effective teamwork, with task that can be pinned directly to any paragraph of a TeamPage article or comment.

Extending the fabric of work, or How to Be Emergent A question found in a customer email stored in Exchange, an issue with a new drug application filed in Documentum, a fact in a legacy document stored in SharePoint or a File server S: drive, a record in an SQL database can all be discovered, discussed, tagged, and tasked for follow-up action in TeamPage without converting or importing data from its original source. Systems of record look and act like they are part of the same permission-aware TeamPage fabric used for collaboration, communication, and action tracking in the flow of daily work.

Intertwingled Work Observable work can (and should) crossing silos and systems. Business context makes observable work easy to find and use. Functionally specialized transactional systems in an organization will likely remain silos of structured information - but market forces will drive vendors to make their content addressable using simple Web standards and services - with consistent authentication and visibility based on context dependent business rules.

Three primary knowledge domains: intelligence, dialog records, and knowledge products Want to talk about work graphs? Here's how Doug Engelbart dreamed up and build the first hypertext system to link work units and people with the NLS/Augment software, starting in 1968 (no typo). See Remembering Doug Engelbart, 30 January 1925 - 2 July 2013

Original Traction Product Proposal Original proposal from October 1997, including Traction business case and references, released under Creative Commons license.



Dec 2015 | Quality Management, Signature Requirements - Adds Feedback, Non-Conformance, and Corrective Action forms and dashboards to TeamPage's standard support for authoring, sharing and tracking updates to quality and compliance documentation.

Oct 2015 | Personal Worklists, Quick Forms - Track and share what you plan to work on. It's easy to add, rearrange, organize, checkoff and share items on your personal worklist.

July 2015 | TeamPage Live Task Lists - Shared task lists keep everyone in synch on order of execution for tasks as well as planned start and end dates.

May 2015 | TeamPage Bookmarks, interactive filters, and Japanese search improvement - Focus on what interests you; return to any filtered or standard view with one click.

March 2015 | TeamPage 6.1 Burn-up charts, interactive tables, SDK extensions - Track progress and summarize activity in context.

Dec 2014 | TeamPage @ Mentions - Bring an article, comment, status post or other object to someone's attention by typing their name.

July 2014 | TeamPage Notifications - Inline and email notifications. Watch what interests you, reply inline or by email.

How to make your ISO Auditor Smile; And Make Your Professional Life Much Easier

August 27, 2013 · · Posted by Greg Lloyd

ImageJordan had a conversation with a TeamPage customer in Sweden who agreed to document and publish a TeamPage case study, but the ISO auditor story is too good to wait. The customer is small precision machined products manufacturer. They initially supplied prototypes to the Swedish defense industry, but now focus on precision products for heavy vehicle manufacturers.

The company is ISO/TS 16 949 certified for Quality Management, ISO 14 001 certified for Environmental Management, and rightly proud of their reputation for producing high quality products and close cooperation with their customers. They use TeamPage for their Advanced Product Quality Planning (APQP) process and Product Part Approval Process (PPAP). When the conversation took place, they had moved 90% of their procedures and shop floor work instructions from Microsoft Word to TeamPage. This gave everyone in the company live access to TeamPage procedures, for quick reading, search, moderated editing, ECO, and issue tracking from concept to shop floor.

Then the ISO auditor paid a visit:

"We had an audit last week and because we have incorporated about 90% of our procedures in TeamPage and also having the output from them in TeamPage our auditor was freakin' ecstatic. I demoed the 'Add' button for sections and a template article and I see his jaw drop. Pretty funny to see, these guys are very seldom impressed.

We also use TeamPage for work instructions read/used mainly by 40 machine operators. We also post news about new work instructions and change information on updated ones.

Earlier the same day the auditor came to see us we received a customer complaint. That is serious stuff in our line of business. I wrote an 'Quality Alert' in TeamPage (based on a template) and in this particular Quality Alert there were a few things that the operator needed to do and inspect so that we are again able to supply parts within customer specifications.

The auditor picked-up on this immediately when he arrived. I showed him the procedure written in TeamPage, the Quality Alert in TeamPage and the updated work instructions in TeamPage. He said “Good, but have you talked to the operators?” and I said “No, I don't need to. I would have but I have been to busy preparing for this audit”. He walked directly to the machining area and started interrogating operators. I was grinning, he looked surprised. It was amazing. All operators knew exactly what they were supposed to be doing, the information distribution and the Quality Alert simply worked. It always works.

  • Thank you Traction Software for making my professional life so much easier."

You're very welcome!

The quotes are from our Quality Manager contact (used with permission), writing in that company's space on Traction Software's TeamPage server. A company space is used to work with Traction Software folk privately, versus posts made to one of the Forum spaces shared by all TeamPage customers, friends, and Traction Software employees.

See TeamPage Solutions: Quality Management


Decagon Devices: Plans, Products, Projects, Procedures and ISO 9001 Quality Management

Athens Group - Traction TeamPage for Quality Management, Training and Knowledge Base

The Future of Work Platforms: Like Jazz

Enterprise 2.0 Schism

Remembering Doug Engelbart, 30 January 1925 - 2 July 2013

July 4, 2013 · · Posted by Greg Lloyd

ImageI was very sad to learn that Doug Engelbart died quietly at home on 2 July 2013. Doug had a long life as a true visionary engineer, inventor, and pioneer of technology we use every day, and technology where we're just starting to catch up to Doug and his SRI team in 1968. Unlike many pioneers, Doug had a quiet, friendly, and unassuming nature combined with deep knowledge, iron will, and a determination to pursue his vision. His vision was to aid humanity in solving complex, difficult and supremely important problems; Doug's goals were noble and selfless. The sense of dealing with an Old Testament prophet - a kindly Moses - is perhaps the greatest loss I and countless others who have met and been inspired by Doug feel today. I've written frequently about Doug in the past, and I'll continue to do so. Here are a few remembrances and resources that seem appropriate. I'll update this list over the next several days. Farewell Doug and my sincere condolences to his family and many friends.

“Someone once called me ‘just a dreamer’. That offended me, the ‘just’ part; being a real dreamer is hard work. It really gets hard when you start believing in your dreams.” — Doug Engelbart, Dreaming of the Future, Byte, September 1995.

Press and public valediction

DOUGLAS C. ENGELBART, 1925-2013 Computer Visionary Who Invented the Mouse John Markoff, New York Times, 3 July 2013. "It was his great insight that progress in science and engineering could be greatly accelerated if researchers, working in small groups, shared computing power. He called the approach “bootstrapping” and believed it would raise what he called their “collective I.Q.”"

In Memoriam: Douglas Engelbart, Maestro of the Mouse and So Much More Harry McCracken, Time, 3 July 2013. "Engelbart was able to see things that most people couldn’t, and make them real. But he was also a passionate believer in what he called Collective IQ — the ability of teams to do things that lone guns cannot.

Computing pioneer and GUI inventor Doug Engelbart dies at 88 Dylan Tweeny,, 3 July 2013. "Although Engelbart is often referred to as the inventor of the mouse, that’s a bit like saying Henry Ford was the inventor of the steering wheel. The mouse was a clever invention, but it was merely one component of a larger vision of how computers could increase human intelligence, or what Engelbart called our collective IQ."

Doug Engelbart, visionary Robert X. Cringley, I Cringley, 3 July 2013. "To most people who recognize his name Doug Engelbart was the inventor of the computer mouse but he was much, much more than that. In addition to the mouse and the accompanying chord keyboard, Doug invented computer time sharing, network computing, graphical computing, the graphical user interface and (with apologies to Ted Nelson) hypertext links. And he invented all these things — if by inventing we mean envisioning how they would work and work together to create the computing environments we know today — while driving to work one day in 1950."

Chris Nuzum's fine valediction for Doug: "RIP Doug Engelbart, and thank you. For taking the time to walk a few miles after dinner in 1995 with a young admirer, for your urgent encouragement to do something about my ideas, for your generosity with your time in providing feedback and encouragement, and for the lifetime of work your poured yourself into with boundless enthusiasm and determination. Your inspiration lives on." See photo

Douglas Engelbart's Unfinished Revolution Howard Rheingold, MIT Technology Review 23 July 2013. "To Engelbart, computers, interfaces, and networks were means to a more important end—amplifying human intelligence to help us survive in the world we’ve created. He listed the end results of boosting what he called “collective IQ” in a 1962 paper, Augmenting Human Intellect. They included “more-rapid comprehension … better solutions, and the possibility of finding solutions to problems that before seemed insoluble.” If you want to understand where today’s information technologies came from, and where they might go, the paper still makes good reading."

Engelbart's First, Second and Third Order Problems. Jonathan Stray's 4 July 2013 Twitter valediction, a Storify collection with some links expanded. "First order is doing. Second is improving the doing. Third is improving the improving."

If you truly want to understand NLS, you have to forget today. Brett Victor wrote A few words on Doug Engelbart 3 July 2013 in honor of Doug Engelbart life and passing. A few very well chosen words. A Storify collection with a few links expanded and quoted.

"The least important question you can ask about Engelbart is, "What did he build?" By asking that question, you put yourself in a position to admire him, to stand in awe of his achievements, to worship him as a hero.

But worship isn't useful to anyone. Not you, not him. The most important question you can ask about Engelbart is, "What world was he trying to create?" By asking that question, you put yourself in a position to create that world yourself."

Doug Engelbart Resources The Doug Engelbart Institute was was conceived by Doug Engelbart to further his lifelong career goal of boosting our ability to better address complex, urgent problems. It contains an excellent history, archive of papers, photos and other published resources as well as links to Doug's current projects.

Douglas Engelbart Interviewed by John Markoff of the New York Times Outracing the Fire: 50 Years and Counting of Technology and Change Computer History Museum oral history interview, March 26, 2002.

Doug Engelbart Video Archive: 1968 Demo - FJCC Conference Presentation Reel Dec 9, 1968 Internet Archive, the so called Mother of All Demos. See also From Pranksters to PCs chapter about Engelbart's 1968 FJCC demo from John Markoff's book What the Dormouse Said: How the 60s Counterculture Shaped the Personal Computer Industry, authorized excerpt.

Video Archive MIT / Brown Vannevar Bush Symposium: A Celebration of Vannevar Bush's 1945 Vision, An Examination of What Has Been Accomplished, and What Remains to Be Done. Oct 12-13 1995, MIT. Talks and panel discussion with Doug Engelbart, Ted Nelson, Andy van Dam, Tim Berners-Lee, Alan Kay and others. See also ACM Interactions summary (free access), transcript of day 1 and day 2 panels.

Augmenting Human Intellect: A Conceptual Framework. by Douglas C. Engelbart, October 1962 (SRI AUGMENT, 3906) A work Doug referred to as the bible of his research agenda, it also outlines the motive for his work: enabling groups of people to respond to the increasingly complex and urgent problems of humanity. If you want to read Doug's original works, start here:

By "augmenting human intellect" we mean increasing the capability of a man to approach a complex problem situation, to gain comprehension to suit his particular needs, and to derive solutions to problems. Increased capability in this respect is taken to mean a mixture of the following: more-rapid comprehension, better comprehension, the possibility of gaining a useful degree of comprehension in a situation that previously was too complex, speedier solutions, better solutions, and the possibility of finding solutions to problems that before seemed insoluble. And by "complex situations" we include the professional problems of diplomats, executives, social scientists, life scientists, physical scientists, attorneys, designers--whether the problem situation exists for twenty minutes or twenty years. We do not speak of isolated clever tricks that help in particular situations. We refer to a way of life in an integrated domain where hunches, cut-and-try, intangibles, and the human "feel for a situation" usefully co-exist with powerful concepts, streamlined terminology and notation, sophisticated methods, and high-powered electronic aids. 1a1

Man's population and gross product are increasing at a considerable rate, but the complexity of his problems grows still faster, and the urgency with which solutions must be found becomes steadily greater in response to the increased rate of activity and the increasingly global nature of that activity. Augmenting man's intellect, in the sense defined above, would warrant full pursuit by an enlightened society if there could be shown a reasonable approach and some plausible benefits. 1a2

Traction Software Blog posts

Tricycles vs. Training Wheels Jon Udell writes: "Easy-to-use computer systems, as we conventionally understand them, are not what Engelbart had in mind. You might be surprised to learn that he regards today’s one-size-fits-all GUI as a tragic outcome. That paradigm, he said in a talk at Accelerating Change 2004, has crippled our effort to augment human capability." Doug's discussion with Alan Kay at the 50th Anniversary of As We May Think (including links).

Traction Roots - Doug Engelbart Elements of Doug's work that directly inspired Traction TeamPage, what we do, and how we work. A personal rememberance.

Flip Test 1971 | Email versus Journal Doug Engelbart's Journal versus email - an alternate history.

And here's what Enterprise 2.0 looked like in 1968 | Dealing lightning with both hands... The 1968 Mother of All Demos and John Markoff's What the Dormouse Said

Enterprise 2.0 Schism Doug Engelbart and Peter Drucker are the two patron saints of Enterprise 2.0. And why.

Doug Engelbart | 85th Birthday Jan 30, 2010 Doug Engelbart's mission, goals and accomplishments, including a dialog with Alan Kay at the 50th Anniversary of As We May Think symposium.

Doug Engelbart's copy of As We May Think - with Doug's 1962 notes scribbled in the margins From the Doug Engelbart digital archive (see links). Original donated to the Computer History Museum.

Happy Birthday Doug Engelbart! Video highlights from Doug's talk and panels at the 50th Anniversary of As We May Think symposium, Oct 1995. Videos of Doug's talks including his famous Dec 1968 Mother of All Demos are now part of the Doug Engelbart Digital Archive maintained and managed by The Internet Archive

Pharma and Biotech Risk Management

June 17, 2013 · · Posted by Jordan Frank

Risks are the leading cause of costly delays in the process of bringing a biotech product to market. Risk management in the product development process all too often means one person juggling a list of risks in a spreadsheet. It's hard to edit, but even harder to open a discussion on an existing risk when someone has a question, sees a problem, or wants to add a new risk. Traction Software partner Rosemary Vu used TeamPage's Section Table widget and extended TeamPage's Article to create a Risk form. For more on TeamPage Section Tables, see Q: How do I link to an Excel file? A: Why Would you Do That?

Here's an example of a Section Table of Risks, including risk type, module, hazard, cause, severity, likelihood of occurrence, and other attributes.


Unlike a spreadsheet, you can easily expand and comment on any entry in the table. Click the Add button to add a new Risk to the table and raise the Risk form. Rosemary created the Risk form as a specialized extension of a TeamPage article, inheriting all standard TeamPage comment, task, tag, edit history, search and activity feed capabilities, while adding editable attributes as pulldown choices or fill in the blank field. Like other TeamPage extensions the Risk form is packaged as a plug-in to make extension installation, sharing, and maintenance very simple. Rosemary created the Risk form on her own with no IT help or programing experience by incrementally modifying a free plug-in example from Traction Software's SDK Forum Library.

Here's an editable view of the third Risk:


The TeamPage Risk form has fields, pulldowns and a free text description that makes it very easy to enter and edit. Risk values are formatted in a way that makes them easy to read when a Risk is shown as single Teampage article (below) as well as when a Risk is referenced in a Risk table.


Using TeamPage to manage Risks makes it easy for anyone to submit a risk, update a risk, and comment on the issues associated with it. TeamPage's extensible and customizable architecture makes it possible for a power user with no programing expertise to extend Teampage, and easily share that extension with other TeamPage customers. Rather than relying on just one person to manage all risk information in a spreadsheet, the whole team gets involved and plays a part in identifying and resolving risks. Accountability is raised and communication is much more efficient. TeamPage's easy extensibility makes risk management in biotech and other similar tasks in other domains clearer, easier, faster, and more effective.

Working Across Boundaries

June 16, 2013 · · Posted by Greg Lloyd

ImageIn his Jun 2, 2013 blog post, Chess Media analyst and author Jacob Morgan asks: How Open is Too Open? He asks "Would you be comfortable working in an all glass building where people can see everything you do and every move you make?" Jacob outlines the benefits of transparency: "Keep everyone on the same page; Build trust and fostering better relationships; Allow employees (and customers) to contribute ideas and value when they see the opportunity to do so." Jacob recognizes that a balance needs to be struck, but not being transparent enough may do more harm than good. He ask: "How open is too open?" I agree with the benefits Jacob outlines, and believe the answer to Jacob's question depends on the answer to a critical question: "Transparency for what purpose?" I'll start the ball rolling in with this post, including some real-life customer examples.

For example, if you work for a consulting (or law) firm, your clients have a strong, natural expectation that their work with the firm will be kept private from other clients, even if client work is more broadly shared internally among members of the firm. Some work within the firm may be more closely held for good reason - ranging from employee health records to Board meeting minutes. I believe it's a mistake to limit collaboration to work that must be visible by all members of the firm. I also believe it's extremely valuable to work with external clients, suppliers, and partners as well internal teams, within and across necessary and natural boundaries. The question I'd like to discuss is: "How do you balance transparency, boundaries, and the need to work across boundaries?"

Jacob recognizes that a balance needs to be struck, and uses an analogy that compares a glass building vesus "a regular building that just doesn't have locked doors."

"I do believe that organizations need to be much more open and transparent but there’s a balance that needs to be struck here. There’s a big difference between showing everything to everyone vs making things open to people should they want to see it. To use an analogy it’s the difference between constructing a glass building vs constructing a regular building that just doesn’t have locked doors." - How Open is Too Open?

I'd say "very few locked doors, where needed to get work done, particularly with external stakeholders."

In an early Three Places for People blog post, I use a similar analogy:

"Great architects of physical places know that people bring expectations and norms about the kind of behavior that's appropriate and enjoyable to any physical space. Architects are skillful in designing spaces to match their clients desires and expectations by providing cues that are easy to perceive and appropriate for the intended purpose, but a lot of the norms of the same physical space become clear only from social context.

If you walk into a conference room with a group of people you don't know talking quietly around a table - and someone closes the door behind you - you'll likely speak and act differently than if you walk into the same room with people you know laughing, eating and drinking. If you walk into a theater you'll probably seat yourself quietly in the audience rather than striding onto the stage (see the Re-Placing Space reference).

What fascinates me about social software is how we're learning to create places with perceived affordances - features and user models - that seem natural for different purposes and intentions. I use Facebook, Traction Software's TeamPage server, and Twitter as three separate places: my neighborhood, my workplace, and the public commons I like to use." - Three Places for People

One Traction TeamPage customer matches the consulting firm / client example precisely. The firm is near the top of the list of 100 global firms in their market. They use separate TeamPage spaces for each client, but allow members of the consulting firm to work across all client spaces. Members of the firm use TeamPage's project, task, milestone or client space dashboards to focus, and can also step back to a bird's eye view across all activity that they are permitted to see, organized by Space or by Person (with activity stream, project, task and milestone tabs on each individual's Profile). See Action Tracking, Project and Case Management in TeamPage

Another Traction TeamPage customer provides services to customers worldwide, with over 5,000 employees operating in over 150 locations and 75 countries. The firm uses TeamPage to get new clients onboard; author and share client and location specific procedures; track and communicate status including response to weather conditions and other forces that require changes to planned procedures. Shared access to procedures, notifications, and changes build strong business relationships that are a competitive advantage for the firm. Tens of thousands of complicated procedures need to be constantly changed and reviewed in near real time by both the firm and clients. The shared procedures are the core operating plan for the firm and the basis for everything the client values and pays for. TeamPage dashboards, notification, action tracking and search provide simple, reliable and secure access for each client, while allowing members of the firm to maintain global awareness, diving into any project, task, or space to quickly resolve an issue or come up to speed, see Deep Search.

In summary, I believe there's no reason to settle for a collaboration and action tracking solution that only handles internal collaboration, or assumes that everything happens in a building with glass walls and no doors. Real business value and sustainable competitive advantage often depends on working easily within and across boundaries that need to be in place to do business.


The Work Graph Model: TeamPage style - Working with internal and external teams

Borders, Spaces, and Places - Walks through specific examples of boundaries and boundary crossing activity

Explaining Twitter - One of Three Places for People - About the social architecture of three places: 1) a public commons (like Twitter); 2) a place for friends and family (like Facebook); 3) a place where you work (for me, Traction Software's TeamPage server).

Intertwingled Work - Working across siloed systems and boundaries set up to meet business purposes - like the consulting firm client example.

A Circle is not a Space - How Google+ circles make it possible to share individual conversations with a list of circles each individual controls (later extended to groups) versus sharing work within one or more spaces. Some distinctions are important to understand when you want to handle collaboration for a business or other purpose over an extended period of time.

Open Cafe: E2.0 Implementation and Adoption

May 29, 2013 · · Posted by Jordan Frank

@JeffMerrell posed a series of questions for his Master's Program in Learning & Organizational Change. I'll offer my own experience as it pertains to each of his question areas.

Question Area: Implementation of new social technology platforms

When stepping into E2.0, there's a temptation to go enterprise wide while also wanting to meet a specific need and show success. Invariably, it's easier to define a specific need for a small group and get adoption there at the "local" level. In my own experience and with customers, the same pattern is generally evident: Shooting for instant enterprise adoption is OK for short-lived processes like an idea jam while long lasting adoption with sustained return occurs when a small group identifies a "process" need and organizes around that.

I think the sweet spot occurs when a particular group's collaboration can benefit an entire organization. Over at Athens Group, there was a need for a focused group to put together process and training information which was valuable on an on-going basis to all their consultants. I've also seen this pattern with competitive intelligence use cases.

Question Area: Adoption of new social technology (by individual users)

Jeff asks what tells you when you've hit a tipping point. For sure that's when a super-user says "my customer's stats just passed my own!" That happened recently at site of a consulting company using TeamPage for their customer requirements and project implementation tasking.

Motivating adoption is always tricky, no matter how good the tool. But organizing spaces around a space dashboard clearly identifies what's important is critical. Then folks can understand where the value is found, and how to play along.

I talk about this in Emergineering which focuses on meeting the freedom required by collaboration with a simple structure that encourages it.

As for incentives, they're questionable since motivation is better when it comes from within. See Blog2031: Problem and Process rather than Incentives for E2.0 Tools

Question Area: Formal and informal community management

We all wish communities would manage themselves. One problem with communities is they aren't necessarily directed towards a particular goal. In a sense, communities are optional. So, the key is to figure out how it can sustain itself.

One of my earliest customers was a pharmaceutical division of a Fortune 100. They pushed they had a competitive intelligence need which was a terrific basis for building communities by market area.

There were 25 individuals which were easily identified as being involved in sharing and developing competitive and market intelligence with another easily identified set of managers. We were able to setup spaces by market area. Information was posted to the market area communities rather than through individual emails. The result was a vibrant pattern of communication which not only increased efficiency, but created greater awareness across the division and even showed some instant gains as a wider set of people could validate and amplify the key intelligence, e.g. a case of a competitor working on a new drug which a scientist was able to indicate would fail based on their own internal experiments.

In this case, the community managed itself by running user group meetings on a regular basis to check their progress and improve the quality of their information gathering based on surveys and reactions of key management and sales constituents. They also wrapped their management objectives around participation.

Question Area: Measuring activity, outcomes and value in social technology platforms

Activity and value can be attacked through efficiency, adoption and any number of other metrics. They aren't always obvious, and the outcomes aren't always predictable when you get started.

At one Pharmaceutical firm, it was evident the system was providing value when usage metrics increased after roll-out and leveled out to a consistent pattern. At that point, it was clear from behavior that it was delivering value and had hardened as an organization process. See page 10 of the PDF attached to Blog119: Thierry Barsalou, IPSEN CIO, Speaks at Gilbane Conference on Content Management.

At Alcoa Fastening Systems, a Deloitte study highlights a 62% reduction in time spent on compliance activities. There's a case where compliance was converted from a chore to something that just happens along the course of getting work done!

Question Area: Knowledge sharing to learn as well as to perform

I think the term knowledge development hits the mark closer than knowledge sharing. Knowledge development happens in the course of documenting processes, policies, and FAQs. This is a Wiki type approach where you develop and refine knowledge over time. This is the case in the Athens Group study mentioned above. Some customers have even received ISO certification for their process of managing process and training documentation. Having these core information assets makes leverage easier to achieve when questions are asked and current procedures are challenged by new opportunities for improvement.

Contextual Computing At Work

May 28, 2013 · · Posted by Greg Lloyd

ImageIn Co.Design May 24, 2013 Peter Morrison of Jump Associates writes The Future of Technology isn't Mobile, it's Contextual. He says that the way we respond to the world around is based on situational awareness. "The way we respond to the world around us is so seamless that it’s almost unconscious. Our senses pull in a multitude of information, contrast it to past experience and personality traits, and present us with a set of options for how to act or react. Then, it selects and acts upon the preferred path. This process--our fundamental ability to interpret and act on the situations in which we find ourselves--has barely evolved since we were sublingual primates living on the Veldt.

Here’s the rub: Our senses aren’t attuned to modern life. A lot of the data needed to make good decisions are unreliable or nonexistent. And that’s a problem.

In the coming years, there will be a shift toward what is now known as contextual computing, defined in large part by Georgia Tech researchers Anind Dey and Gregory Abowd about a decade ago. Always-present computers, able to sense the objective and subjective aspects of a given situation, will augment our ability to perceive and act in the moment based on where we are, who we’re with, and our past experiences. These are our sixth, seventh, and eighth senses."

Peter argues that we need four graphs to make contextual computing work:

  • The Social Graph - how you connect to other people and how they are connected to one another, including the nature and emotional relevance of those connections.
  • Your personal graph contains (gulp) all of your beliefs - data relating to a your deepest held beliefs, core values, and personality.
  • The Interest graph - what you like - is about curiosity
  • Your behavior graph - sensors that record what you actually do versus what you claim you do

I agree that one great value of Peter's contextual computing is to make agents like Apple's Siri or Google Now much more effective in answering questions, making recommendations, and delivering what you want based on how you express it in your own words or gestures, taking into account your current situation, recent requests and interests. But this augments a more fundamental capability: human content navigation, including but not limited to search.

In the world of work, I believe it's incredibly valuable to capture and connect the natural objects of your attention and interest, including tasks, projects, work product, relevant discussion, related references even if you're standing in for Siri or Google Now.

When Mr. Dithers shouts: "Bumstead! Where are we on the Acme Account?", the most timely, frequently discussed and contextually relevant version of Dagwood's Acme tasks, projects and work should pop up near the top of Dagwood's result list, along with the cloud of tags and people who have touched or talked about tasks, projects and other related to the Acme account and its associated activity streams.

The important requirement is making tasks, projects, pages, discussions and other work products first class sharable, named objects that can be connected to each other and what you're working on, discussed, tagged, tasked, and navigated as well as found using search. Being able to talk about tasks and projects relating to Acme captures one important part of your interest and behavior graph (activity stream), and links these items to the names and behavior of other people working with or discussing the same objects.

The objects and connections made in the context of work are more reliable than connections that need to be inferred from your behavior - and they're available now, including the ability to connect tasks, projects, pages and discussion in TeamPage and files, discussion, email and SQL databases in your external systems of record. They record valuable context for Siri and Google Now when used at work - but there's no reason to wait to get started.


Zoom in to focus, zoom out for awareness, bubble up items in the flow of work

Intertwingled Work

Enterprise 2.0 and Observable Work

Traction TeamPage: Connected Work

TeamPage Action Tracking with Tasks, Milestones, and Projects

Join us at E2 Boston 2013 - Traction Software is Social and Collaboration Track Sponsor

May 17, 2013 · · Posted by Jordan Frank

ImageHow well you work with your colleagues, online and off, will make the difference when trying to win the next deal, design the next product or craft the next winning strategy. Consider how important people are to process and how social collaboration (versus some pre-ordained workflow) is the barrier to or the enabler of successful outcomes. We see immense value when people document their knowledge, streamline their communication and track actions to completion in TeamPage. We hope you can join us to see TeamPage and learn from the leading analysts and practitioners at E2 Boston June 17 through 19.

Traction Software is a track sponsor this year for the Social and Collaboration Track. The sessions range from Going Beyond the Activity Stream to the Rise of the Connected Workplace and Evaluating Emerging Technologies for the Enterprise.

Please visit the E2 Social and Collaboration Track site to learn more and register for this upcoming event. There are other tracks on Big Data, Cloud, Mobility, UX, and People, Process and Engagement. That's a lot to learn in a few short days!

Register with discount code CMTRACTION to earn $200 off Full Event Passes, $100 off Conference registration, or a FREE Keynote + Expo Pass.

Lost Roots of Project Management: Think Agile that Scales

April 25, 2013 · · Posted by Greg Lloyd

The Manhattan Project, Atlas, and Polaris projects are cited as roots for traditional phased stage-gate Project Management, but didn't use that model. New high innovation projects shouldn't either; think agile that scales. Read this fascinating 2009 paper by Sylvain Lenfle and Christoph Loch of INSEAD, cited on Twitter by Glen B. Alleman who calls it "breathtaking".

Launch of an Atlas B intercontinental ballistic missile - Wikipedia USAF photo

Lost Roots : How Project Management Settled on the Phased Approach (and compromised its ability to lead change in modern enterprises) 
Sylvain Lenfle and Christoph Loch, 2009/59/TOM
INSTEAD Research Working Paper

Quoting from Introduction:

“Modern” Project Management is often said to have begun with the Manhattan Project (to develop the nuclear bomb in the 1940s), and PM techniques to have been developed during the ballistic missile projects (Atlas and Polaris) in the 1950s. The Manhattan Project “certainly displayed the principles of organization, planning and direction that typify the modern,management of projects.” “The Manhattan Project exhibited the principles of organization, planning, and direction that influenced the development of standard practices for managing projects.

This characterization of the roots of PM represents a certain irony – the Manhattan Project did not even remotely correspond to the “standard practice” associated with PM today, and both the Manhattan and the first ballistic missile projects fundamentally violated the phased project life cycle: both applied a combination of trial-and-error and parallel-trials approaches in order to “stretch the envelope”, that is, to achieve outcomes considered impossible at the outset.

However, the Project-Management discipline has now so deeply committed itself to a control-oriented phased approach that the thought of using trial-and-error makes professional managers feel ill at ease. In our seminars, experienced project managers react with distaste to the violation of sound principles of phased control when they are told the real story of the Manhattan Project (or other ambitious and uncertain projects). The discipline seems to have lost its roots of enabling “push the envelope” initiatives, de facto focusing on controllable run-of- the-mill projects instead.

How could this happen? And does it matter? In this paper we describe how the discipline lost its roots and we argue that it matters a great deal: it has prevented the project management discipline from taking center stage in the increasingly important efforts of organizations to carry out strategic changes and innovation.


Update Feb 6, 2016: See Glen B. Alleman's Herding Cats blog post, Agile at Scale - A Reading List (Update 9)

The Future of Work Platforms: Like Jazz - The social dance of getting things done, dealing with exceptions, and staying aware of what’s going on around you

Intertwingled Work - Working and scaling like the Web

Big Data, Meet Long Data, Meet Blog Data

April 2, 2013 · · Posted by Jordan Frank

Big Data Meet Long Data by Jeff Bertolucci - @jbertolucci - column appears this week in InformationWeek to reminds us that "Long Data" or historical data is vital for analysis and comprehension of trends that span years.

Bertolucci's article links to a Wired article from January 2013 titled Stop Hyping Big Data and Start Paying Attention to ‘Long Data’ where the author, Samuel Arbesman - @arbesman - says "Big data puts slices of knowledge in context. But to really understand the big picture, we need to place a phenomenon in its longer, more historical context."

Bringing this home to a company's context, Bertolucci quotes Benjamin Bruce (Pitney Bowes - Marketing Director) as saying "Big data is more about taking a slice in time across many different channels" and that "long data involves looking at information on a much longer timescale. Ignoring customer data and records that go back decades can limit a company's ability to connect with its customers."

Taking a long-data trip back to May 2008 brings us to a quote from Now Everything is Fragmented by Dave Snowden - @snowded - in KMWorld where he said:

"Over the last decade as I have worked on homeland security, we have had the chance to run some experiments that show that raw field intelligence has more utility over longer periods of time than intelligence reports written at a specific time and place. In other experiments, we have demonstrated that narrative assessment of a battlefield picks up more weak signals (those things that after the event you wished you had paid attention to) than analytical structured thinking."

He continues with explanation: "we live in a world subject to constant change, and it’s better to blend fragments at the time of need than attempt to anticipate all needs." Amen.

So when you leave data on the chopping block after completing an analysis, you are denying the next person an opportunity to go back to the raw data and run their own analysis, possibly for the same or different purposes.

I'll assert that what's needed is the thin slicing in big data concepts combined with the long data trends that allow for understanding change and gathering some picture of the future.

Bringing this back to "blog" data - thats where we can capture the vital narrative that Snowden says carries the weak signals. The blog data helps to annotate the context where big data lives.

Blog data in a TeamPage demo also offers a simple and easy example to explain the importance of thin slicing over long trends. Here is a tag cloud from one of my demo servers. It's set to All Time. The tags tell a story, of sorts. Interpret it as you may.


Now, when we use a date selector control, we can see it tells a very different story in 2012 vs. 2011.

Date Selector: Year 2010 Date Selector: Year 2011
Image Image

In the example, you can see the company's attention has shifted from competitors like Nike and Vibram in 2010 to competitors like Merrell in 2011. It also looks like they've done less work with Policy work in 2011 and have shifted away from HUMINT (human intelligence collection).

This sort of tag cloud view offers a pretty blunt view across a whole server or a particular space at a time. Greater precision is often required. Another way to slice the content is with our premium search which is powered by Attivio's Active Intelligence Engine. You can search for any set of words and get a tag cloud for the search, then even slice that into a time period or by any other facet or set of tags.


In this search interface, Attivio also helps us extract and display tag cloud style views of any facet, including keywords, spaces, content authors, and more. From the keywords facet, you can quickly see there are 5 hits on Marathon Training and Injury Prevention.

This brings us to Small Data. Once we can thin slice small, relevant, data, we can quickly assess what topics are prominent even before digging in to read the source content or more quickly understand trends.

A thick slice across all time isn't adequate to explain a course of events - a long view with thin slices and supporting narrative is vital. With all this, you might take a long music trip back to the 80s and You May ask Yourself How Did I Get Here? ...and actually come to a good answer!!

Or, if you want to consider more thought provoking ideas about tags, other meta data and the role of time, please click over to my Tag Mush presentation linked at the bottom of Ontologies & Tagsonomies at Taxonomy Boot Camp to read more about the Information T.


This Information T model talks directly to the importance of Long Data, Big Data and context from Blog Data.

Problem and Process rather than Incentives for E2.0 Tools

February 15, 2013 · · Posted by Jordan Frank

Over on Quora, Ben Lopatin @bennylope has a best-answer to a question on the best ways to incentivize people to use E2.0 knowledge management and collaboration. He starts by shunning external incentives (as I do in Need for Incentives, and other Innovation Myths) and works through a few key principles which I've seen work time and time again:

  • Focus on the problem for which the tools are to be employed. Most people don't care about enterprise wikis, they care about being able to do their jobs,
  • Provide people with a working demonstration of an existing business process.
  • Actively help people figure out how their processes, tasks, etc, can be accomplished with the new tools
  • Get people up the ladder using the new tools... if you want to achieve pan-organization adoption you need leadership to show that they're using it, too
  • Be careful about overestimating how easy the tools are for everyone. And not just the interfaces, but changes in underlying concepts.

I wish I had an Blog1326: Emergineering! badge to put on this answer because it captures the essence of understanding the problem and underlying process, figuring out how to address it in a way that enhances productivity, and finally getting the organization around the new approach. That's just what's needed for folks to figure out how to turn "social software" into "social productivity software" and really start using these tools for more than very basic and fleeting conversation.

I'd also hand out the badge to Catherine Shinners @catshinners for amplifying the benefits of social process transformation.

In her notes from the E2.0 Innovate conference, she wrote:

There are specific benefits of a social business process:

  • immediacy - better access to the information
  • serendipity - enabling discovery of new information
  • transparency - supporting honest and ethical behavior through openness

A business process does not become social simply because it's in a social network. Hughes called out the different types of social business processes

  • unstructured processes – the opened ended “hey I've got a question does anyone know the answer” or easy invitational “why don't we?” kind of interactions
  • semi-structured – direct queries to engage a constituency or cohort in a group conversation or comment about artifacts i.e., “please review or provide feedback”
  • structured – business process workflow kinds of structure “approve my expenses - request time off”

Beyond simple productivity gains of moving process from email and the water cooler to E2.0 platforms, or flexibility achieved by moving them from structured but hard to manage custom systems, this outline offers a clear sense for why a social platform is not only more ethical, its more effective because its observable and encourages team participation.

PLM Gets Social, Untangles Ball of Confusion

November 27, 2012 · · Posted by Jordan Frank

Stan Przybylinski - @smprezbo - of CIM Data advised an audience at Social PLM 2012 on inevitable social side of product lifecycle management. In the talk (video on YouTube here), he identifies companies including Traction Software (Minute 9:06) whose platforms are being used by product teams for everything from building requirements, to managing risks and simply discussing product issues.

I particularly liked his slide on "How Things Actually Get Done - Can You Say Ball of Confusion?"


The essence of this is that traditional PLM offerings capture some but not all work in progress and don't support the communication loops around project communication or problem solving. Social platforms are filling the gap, and in many cases are actually supporting the whole PLM cycle.

TeamPage Action Tracking can help firms manage informal tasks, track issues or risks, and manage entire projects. TeamPage is also used to manage documentation or work-in-progress and discuss anything that's happening.

E-Mail: an On-Ramp for Enterprise Social Media

November 20, 2012 · · Posted by Jordan Frank

Bill Ives, @billives, points to Nathan Eddy's eWeek column titled Businesses Still Reliant on Email as Social Media Use Grows. The column reminds us that Email is still the dominant go-to application of choice and that's not changing any time soon. Rather than run away from email habits, social software in the enterprise has to embrace it. Back in 2004, I gave a presentation at the INBOX conference advocating for the use of Email as an on-ramp for collaboration and an off-ramp for notification.


Dennis McDonald, @ddmcd, in a comment, concurred in a comment and pointed to his post on Social Media Engagement Tips where he said "Email operates as an extended user interface for many applications."

In TeamPage, we've steadily enhanced support for email as an extended user interface with hooks for Publishing from email including the ability to post new articles, status posts, and tasks. You can also setup notifications on any kind of addition or change. Changes can include edits, tag changes, and assignee changes (for tasks). There's also iCal links to permission filtered server, space, project and personal calendars. You can also reply to comment on notifications, so that you don't have to shift your user experience from your email client or smart phone when a notification needing your immediate response is needed.

TeamPage SAAS / Cloud Hosting Helps Bring Customers Closer, Improves Support

November 7, 2012 · · Posted by Jordan Frank

ImageAs we've put more attention to our cloud hosting (see Traction Software and Traction Software Japan) with free trials and an increasing hosted customer base, I'm seeing first hand how the customer relationship can become much closer, more interactive and more informed. In the last 24 hours, I was able to quickly help:

- a Global Logistics customer find a set of attachments which were removed when a page was edited 8 days ago.

- an IT / Management consulting customer determine the best way to setup a subcommittee dashboard where they can track issues, manage tasks, conduct discussion and share meeting agendas / outcomes.

This was possible to do asynchronously and quickly around our busy schedules because of a mutual bond of trust (so they allow me into their systems) and because their software is not buried behind a firewall.

Most customers still deploy software behind their firewall for a variety of good reasons. In those cases, we use web conferencing and issue tracking in TeamPage customer support spaces. This still works great, but I'm definitely seeing many cases where the cloud option opens up new opportunities for better support and better value for TeamPage software.

Carving a Path to Productive Knowledge Management: How?

October 24, 2012 · · Posted by Jordan Frank

I gave the following presentation at the first ever meeting of the Boston Chapter of the Knowledge Management Association today. As this was a first meeting, I thought I'd raise the issue that "managing knowledge" is about as daunting a task as "herding cats."

After we pick apart components of knowledge and understanding how context is critical to understanding it, I offered a two step process to bring an organization to towards a KM and collaboration strategy that starts with asking How? and relies on Emergineering to work knowledge management and context into daily social processes on platforms like TeamPage.

JSB on Capturing Context not Just Content

October 17, 2012 · · Posted by Jordan Frank

In John Seeley Brown's KMWorld Keynote (live streamed 17 Oct 2012 at, he makes an important point about how knowledge has no boundaries. @johnseelybrown #KM12


He goes on to say that the way to manage knowledge in today's age is about capturing context along with content. That's the driving point around Traction TeamPage: Connected Work. It's the reason to build wiki style knowledge bases, integrated with blogs, discussion and tasking.

He goes on to talk about the futility of building profiles and managing inventories of skills by bringing up a case at SAP where the average time to ask and get an answer to a question is 17 minutes. He highlights another case at MITRE where social bookmarking exposes the knowledge and interest areas of each of the employees, while they work.


That's why we built the Social Enterprise Web module, to make social bookmarking easy and to enable discussion and tagging right into the context of enterprise systems.

In JSB's words - this helps meet a goal he states as the need "to build social and intellectual capital" by capturing the output of emergent processes.

He calls sharing in this way as intimate legitimate peripheral participation. PIt's a way to be intimate within working groups, but allow for social listening at scale.

Another terrific example he raises is how to cope when an ERP calls out an exception condition. A social process has to take over.


Employees have to raise, discuss and resolve the issue. Exception handling is a key issue brought up by his work at Deloitte. A system process issue becomes a social process issue to be handled and resolved. Knowledge about the decision is brought together, from content, context and active problem solving.

That's connected work, and why it matters. That's why connecting context with content is relevant and why we could "inherently want to share."

Ada Lovelace Day | Sunita Williams, Astronaut and Captain U.S. Navy

October 16, 2012 · · Posted by Greg Lloyd

ImageAda Lovelace Day celebrates the contributions of women in science and technology. This year I've chosen to write about Suni Williams, NASA Astronaut and US Navy Captain currently commanding Expedition 33 on the International Space Station. I hope young women reading about Ada Lovelace Day now are encouraged by her example to pursue their dreams where ever they may lead - here on Earth or as the first Earthling to set foot on Mars.

Captain Williams graduated from the U.S. Naval Academy in 1987 with a B.S. Degree in physical science and was designated a US Naval Aviator in 1989. She served as a helicopter combat support officer and officer in charge of a H-46 detachment for Hurricane Andrew Relief Operations before being selected for NASA's Astronaut Training program in 1998. She served as crew for on International Space Station Expedition 14, setting new records for female astronauts in space (195 days) and spacewalk EVAs.

On July 14 2012 Captain Williams launched from Baikonur Cosmodrome to join ISS Expedition 32 as Flight Engineer and Expedition 33 as Commander. On Aug 6, 2012 she and Flight Engineer Aki Hoshide completed a pair of spacewalks totaling more than fourteen hours to install a balky Main Bus Switching Unit, bringing her total EVA time for six spacewalks to over 44 hours. She is a member of the Society of Experimental Test Pilots and the Society of Flight Test Engineers. Read Captain Williams' Why Did I Become an Astronaut interview for her personal story. Follow @Astro_Suni on Twitter.


Ada icon by Sidney Padua: I strongly recommend that you download the thrilling adventures of Babbage & Lovelace for your iPad (free), and enjoy more of their adventures on author Sydney Padua's 2D Goggles Web page.

Previous years

Ada Lovelace Day | Betts Wald, US Naval Research Lab 2011

Ada Lovelace Day | Fran Allen, IBM Fellow and A.M. Turing Award Winner 2010

Ada Lovelace Day | Professor Lee S. Sproull, Stern School, NYU 2009

Creating GWT Date / Time Pickers That Work in Any Time Zone

September 6, 2012 · · Posted by Andy Keller

We're working on new features for the next release of TeamPage that allow people to create events on a calendar. For the edit event dialog, we needed date and time pickers that allow people across different time zones to edit the dates and times of events. We ended up creating new GWT controls and adding them to our open source gwt-traction library .

Edit Event Dialog

It seems easy enough to implement using our own secret sauce of HTML/XML/SDL, some GWT, and a bit of CSS to make it look nice. I had almost everything working in an hour or so. Most of the fields use widgets provided by GWT or controls we've already written ourselves. I saved the Start Date and End Date fields for last.


I've used a bunch of different calendar applications and looked around the web for inspiration. Could there be a time control that I could just use? I found a lot of people with similar questions and a few decent solutions. I found this question on Stack Overflow. Eventually I decided that I was on my own. Not a big deal. I've written widgets before and we like to share them with the GWT community, so everyone wins.

I'd need two fields: a date input and a time input that together specify a time, independent of timezone. On the server we store them as the number of milliseconds since January 1, 1970, 00:00:00 GMT, the same value used by the Java Date object.


There's a nice date picker control that is part of GWT called a DateBox.


However, we noticed that it doesn't handle time zones very well, so we created the UTCDateBox. It makes it so that whatever Date you choose, you get a Long value as midnight in UTC of the date selected. The GWT DateBox control returns Date values and they are different values depending on the TimeZone in which you select the date. In the places we choose dates, we want a date independent of timezone.

For example, New Years Day is always Jan 1st even though it's still Dec 31st in the US when people start celebrating it in Japan. So using the UTCDateBox, if I'm in JST (Japan) and choose Jan 1st 2013, that will be the same as choosing Jan 1st 2013 in EST (US Eastern). They'll both have the same selected value (midnight Jan 1st 2013 UTC), independent of the time zone in which they were selected. We're happy with this solution for Dates and have been using it for years.

Time however, cannot be specified independent of TimeZone. I can't just say let's meet at 2pm on Dec 2nd and expect people around the world to show up at the right time. A time like 2pm is only meaningful in an associated TimeZone.

Since 2003, TeamPage has allowed users to create and edit articles, comments, files, tasks, etc. in their own TimeZone and Locale. It can be a little tricky to make sure everything is properly parsed and formatted, but we're used to the issues involved. It's important to keep the data that you store in a normalized format that you can query and sort.


Here's the UTCTimeBox that I decided to build. It's a TextBox with some special parsing that allows time to be entered in the user's preferred time format or other common formats. It's pretty lenient about parsing, so 6 is 6:00 AM, 6p is 6:00 PM, 645pm is 6:45 PM, etc. When you click the box, you get a drop-down list of a possible times in 30 minute intervals, formatted in your Locale.


Even though we have two separate controls for date and time, we still store a single Long value on the server side as milliseconds since January 1, 1970, 00:00:00 GMT. Ideally, we'd just have a single composite widget with these two controls implementing HasValue<Long>. setValue would split the value into separate date and time values and set the value of each controls, getValue would combine them, and this would all work in the user's preferred TimeZone which might be different than the server or browser TimeZone.

I spent a while on this until I realized that there just isn't enough information about TimeZones available to JavaScript. Other people have reported the same problem. I hate wasting time implementing things that can't work.

Since we can't properly split a single Long value into date and time parts in the browser, we'll have to do it on the server. I decided that the UTCTimeBox would just edit a value of milliseconds since midnight, independent of time zone (e.g. 12am is 0, 12pm is 12*60*60*1000).

When a user submits the form, the server, which knows the user's time zone, creates the corresponding Date value. When we edit the form, the server will split the values into appropriate values for the user's time zone. Nice and symmetric and the client code is much simpler. We made the server-side processing code available here.

Now we can edit events and the value is properly stored on the server.


The final piece is creating some interaction between the start and end dates to make it easier to create and maintain proper ranges. When you move the start date forward, the end date should move forward, maintaining a fixed duration. When you move the end date, the duration should adjust unless you move it before the start date. In that case it should move the start date back and maintain duration. It's the kind of interaction that you don't really notice but appreciate. This behavior is implemented by the UTCDateTimeRangeController.

HTML5 date/time inputs for iOS

HTML5 has new inputs for date, time, month, datetime, and more. iOS has particularly nice controls for selecting dates and times. Using deferred binding in GWT, we created a separate HTML5 implementation of the UTCDateBox and UTCTimeBox widgets. Currently we only present these to versions of Safari that support the "datetime" input (which is currently only iOS). While Opera supports these inputs, we think our text based controls work better than their dedicated date and time inputs.


As a developer using the UTCDateBox and UTCTimeBox, you don't need to do anything special to use the HTML5 versions in iOS. They will be presented automatically and use the same Long values described above instead of the standard HTML5 values.

Remembering Neil Armstrong...

August 26, 2012 · · Posted by Greg Lloyd

Image"I am, and ever will be, a white-socks, pocket-protector, nerdy engineer -- born under the second law of thermodynamics, steeped in the steam tables, in love with free-body diagrams, transformed by Laplace, and propelled by compressible flow." - Neil Armstrong, The Engineered Century. I was sad to hear about the death of Neil Armstrong on 25 August 2012. I'll always remember meeting Armstrong at an event for high school science students in the spring of 1966. He'll be remembered forever as the first person to set foot on the Moon on 29 July 1969. He coolly navigated the lunar lander to the surface despite computer alarms, avoiding rocks at the planned site, and landing with gauges showing about 20 seconds of fuel left. But that wasn't his only close call as an astronaut. In March 1966 Armstrong and David Scott successfully returned Gemini VIII to earth after a runaway thruster spun the Gemini and attached Agena target vehicle to a roll rate of about 300 degrees per second, making chances of recovery "very remote".

Armstrong and Scott were scheduled for a brief question and answer session at the Pennsylvania state science museum auditorium in Harrisburg - squeezed between astronaut meet and greet events for the Governor and state legislators a few blocks away. A handful of high school students and their science teachers from local schools were invited to the event on short notice. I was lucky to be selected by my high school physics teacher, who knew I was a space nut - before geek came into general use. There were a few hundred students, teachers, and a small number of reporters and photographers in the auditorium for the afternoon event.

A state official welcomed Armstrong and Scott, invited them to tell us about the Gemini VII mission, and cautioned that they'd only have a few minutes for questions before they had to move on to the next event. Armstrong and Scott thanked everyone for showing up on short notice, made a few brief remarks on the mission, and opened the floor for questions.

All hands went up. A local science teacher was the first person recognized - not Mr. Sault my physics teacher. He asked how they as astronauts would justify the time and treasure that the US spent on the space program. His question was a long, slow, philosophical speech. All the kids groaned and mumbled. Armstrong diplomatically summarized NASA's mission and suggested that although as a citizen he enthusiastically supported NASA's mission, astronauts executed policy, but didn't make it.

The next question went to the pudgy kid with glasses and camera jumping up and down in the tenth row - me. Maybe it seemed like a safe bet. Before the talk I reviewed everything I could read and remember about the mission and had my question prepared. Most of us in the room remembered when the spin began at about 4pm the afternoon of the 19 March 1966 launch since the launch and significant events like the Agena docking were covered on live TV, and of course we watched. So: 1) What in your training and experience enabled you to diagnose and recover so quickly? 2) How far along was the mission debrief and investigation? 3) Could you share any insights on the thruster issue and changes to avoid similar problems?

I got a smile and a nod from Neil. Armstrong and Scott ran out the short time remaining on the clock with a crisp summary and discussion on the thruster problem, test pilot skills, and new training procedures, which they enjoyed as much as we did. When Armstrong and Aldrin ran into issues on Apollo descent and landing I felt confident it would work out.

On Saturday 25 Aug his family posted: "Neil was our loving husband, father, grandfather, brother and friend. Neil Armstrong was also a reluctant American hero who always believed he was just doing his job."

They continue:

“While we mourn the loss of a very good man, we also celebrate his remarkable life and hope that it serves as an example to young people around the world to work hard to make their dreams come true, to be willing to explore and push the limits, and to selflessly serve a cause greater than themselves.

“For those who may ask what they can do to honor Neil, we have a simple request. Honor his example of service, accomplishment and modesty, and the next time you walk outside on a clear night and see the moon smiling down at you, think of Neil Armstrong and give him a wink.” - The family of Neil A. Armstrong, 25 Aug 2012

I hope this sky isn't cloudy, since I plan to spend some time looking at the moon. And winking.

A few links and references on the life and times of Neil Armstrong, including several that aren't so common. I strongly recommend his NASA Oral History project interview.

The Engineered Century - Neil Armstrong, National Academy of Engineering, Spring 2000, The Bridge, National Academy of Engineering. Edited version of remarks to the National Press Club, 20 Feb 2000

Neil A. Armstrong (1930 - 2012) - From the family of Neil Armstrong

Neil Armstrong | 1930 - 2012: Made 'Giant Leap' as First Man to Step on Moon - John Noble Witford's New York Times obituary, 25 Aug 2012

Gemini VIII Mission Summary - NASA Apollo Lunar Surface Journal

Apollo XI Mission Summary - NASA Apollo Lunar Surface Journal

Lunar Landing Guidance Equations - Part of the source code for the Lunar Module's (LM) Apollo Guidance Computer (AGC), for Apollo 11. From the Virtual AGC and AGS emulation project

Oral History Transcript Neil A. Armstrong, NASA Johnson Space Center Oral History Project. Interview by Dr. Stephen E. Ambrose and Dr. Douglas Brinkley, Houston, Texas - 19 Sep 2001 (pdf 106pp)

Catalog of NASA Oral History Collections - NASA Headquarters and Field Centers

Monitoring and Leveraging Social Media Chatter, on the Internet and in the Enterprise

July 19, 2012 · · Posted by Jordan Frank

In the Pharma Chatter session at the SLA 2012 (Special Librarians Association) conference, I had the opportunity to talk about gathering and managing intelligence from social media. I was joined by Craig McHenry (Pfizer), Lisa Orgren (Septagon Research Group), and Heather Bjella (Aurora WDC)

On the internet front, I focused on traps to avoid when monitoring and leveraging social media on the internet. Enterprise social media, by contrast, can be use case focused and highly valuable for intelligence, topic area communities, project teams and knowledge management.

After highlighting a set of use cases where my customers have found success, I outlined one specific case where a team and their limited community of <100 managers and executives have proven their leverage with over 84,000 reads and an average of 35 reads per page posted in a year. This demonstrates the continued value to be reaped from wiki style documentation and blog style communication in the enterprise. Please enjoy the slides:

Anti-Social Software

July 17, 2012 · · Posted by Greg Lloyd

ImageIt's common to read about corporate culture as a big barrier to successful adoption and use of social software in business. It's easy to understand people's reluctance to change and adopt a new way of working. There are many good reasons to be wary of the promised benefits of change if you don't have relevant direct experience ("I've used this and it works"), clear examples, trust in your organization, and trust in your leadership. Books like Jacob Morgan's new The Collaborative Organization offer great practical guidance, examples, and answers to important questions. However, most social business advice makes a common and good-natured assumption that your organization is healthy - or at least has good intentions - but is just hard to convince. That's not always true.

The culture of some organizations ranges from ineffectual to poisonous, and it's difficult to turn such organizations around. I believe social software can be an amplifier of behavior - bad or good. A list of patterns of behavior to avoid comes from an interesting source: the January 1944 Office of Strategic Services (OSS) Simple Sabotage Field Manual No. 3 (declassified in 2008). I tip my hat to Michael Cooney for his July 13 2012 Network World story: CIA: Five particularly timeless tips from the Simple Sabotage Field Manual which includes Michael's own selection of quotes and a link to the newly released manual.

The purpose of the manual was to educate people in World War II occupied countries on techniques for simple sabotage, performed by ordinary citizens with no special training or equipment. In addition to physical sabotage, the manual offers suggestions on General Interference with Organizations and Production which should be read as an anti-pattern for Enterprise 2.0 behavior and methods.

Simple Sabotage Field Manual

OSS Field Manual No. 3
17 Jan 1944


a. The purpose of this paper is to characterize simple sabotage, to outline its possible effects, and to present suggestions for inciting and executing it.

b. Sabotage varies from highly technical coup de main acts that require detailed planning and the use of specially trained operatives, to innumerable simple acts which the ordinary individual citizen-saboteur can perform. This paper is primarily concerned with the latter type. Simple sabotage does not require specially prepared tools or equipment; it is executed by an ordinary citizen who may or may not act individually and without the necessity for active connection with an organized group; and it is carried out in such a way as to involve a minimum danger of injury, detection, and reprisal.

c. Where destruction is involved, the weapons of the citizen-saboteur are salt, nails, candles, pebbles, thread, or any other materials he might normally be expected to possess as a householder or as a worker in his particular occupation. His arsenal is the kitchen shelf, the trash pile, his own usual kit of tools and supplies. The targets of his sabotage are usually objects to which he has normal and inconspicuous access in everyday life.

d. A second type of simple sabotage requires no destructive tools whatsoever and produces physical damage, if any, by highly indirect means. It is based on universal opportunities to make faulty decisions, to adopt a non-cooperative attitude, and to induce others to follow suit. Making a faulty decision may be simply a matter of placing tools in one spot instead of another. A non-cooperative attitude may involve nothing more than creating an unpleasant situation among one's fellow workers, engaging in bickerings, or displaying surliness and stupidity.


11. General Interference with Organizations and Production

(a) Organizations and Conferences

(1) Insist on doing everything through "channels." Never permit short-cuts to be taken in order to expedite decisions.

(2) Make "speeches." Talk as frequently as possible and at great length. Illustrate your "points" by long anecdotes and accounts of personal experiences. Never hesitate to make a few appropriate "patriotic" comments.

(3) When possible, refer all matters to committees, for "further study and consideration." Attempt to make the committees as large as possible - never less than five.

(4) Bring up irrelevant issues as frequently as possible.

(5) Haggle over precise wordings of communications, minutes, resolutions.

(6) Refer back to matters decided upon at the last meeting and attempt to re-open the question of the advisability of that decision.

(7) Advocate "caution." Be "reasonable" and urge your fellow-conferees to be "reasonable" and avoid haste which might result in embarrassments or difficulties later on.

(8) Be worried about the propriety of any decision - raise the question of whether such action as is contemplated lies within the jurisdiction of the group or whether it might conflict with the policy of some higher echelon.

(b) Managers and Supervisors

(1) Demand written orders.

(2) "Misunderstand" orders. Ask endless questions or engage in long correspondence about such orders. Quibble over them when you can.

(3) Do everything possible to delay the delivery of orders. Even though parts of an order may be ready beforehand, don't deliver it until it is completely ready.

(4) Don't order new working materials until your current stocks have been virtually exhausted, so that the slightest delay in filling your order will mean a shutdown.

(5) Order high-quality materials which are hard to get. If you don't get them argue about it. Warn that inferior materials will mean inferior work.

(6) In making work assignments, always sign out the unimportant jobs first. See that the important jobs are assigned to inefficient workers of poor machines.

(7) Insist on perfect work in relatively unimportant products; send back for refinishing those which have the least fiaw. Approve other defective parts whose fiaws are not visible to the naked eye.

(8) Make mistakes in routing so that parts and materials will be sent to the wrong place in the plant.

(9) When training new workers, give incomplete or misleading instructions.

(10) To lower morale and with it, production, be pleasant to inefficient workers; give them undeserved promotions. Discriminate against efficient workers; complain unjustly about their work.

(11) Hold conferences when there is more critical work to be done.

(12) Multiply paper work in plausible ways. Start duplicate files.

(13) Multiply the procedures and clearances involved in issuing instructions, pay checks, and so on. See that three people have to approve everything where one would do.

(14) Apply all regulations to the last letter.

(c) Office Workers

(1) Make mistakes in quantities of material when you are copying orders. Confuse similar names. Use wrong addresses.

(2) Prolong correspondence with government bureaus.

(3) Misfile essential documents.

(4) In making carbon copies, make one too few, so that an extra copying job will have to be done.

(5) Tell important callers the boss is busy or talking on another telephone.

(6) Hold up mail until the next collection.

(7) Spread disturbing rumors that sound like inside dope.

(d) Employees

(1) Work slowly. Think out ways to increase the number of movements necessary on your job: use a light hammer instead of a heavy one, try to make a small wrench do when a big one is necessary, use little force where considerable force is needed, and so on.

(2) Contrive as many interruptions to your work as you can: when changing the material on which you are working, as you would on a lath or punch, take needless time to do it. If you are cutting, shaping or doing other measured work, measure dimensions twice as often as you need to. When you go to the lavatory, spend a longer time there than is necessary. Forget tools so that you will have to go back after them.

(3) Even it you understand the language, pretend not to understand instructions in a foreign tongue.

(4) Pretend that instructions are hard to understand, and ask to have them repeated more than once. Or pretend that you are particularly anxious to do your work, and pester the foreman with unnecessary questions.

(5) Do your work poorly and blame it on bad tools, machinery, or equipment. Complain that these things are preventing you from doing your job right.

(6) Never pass on your skill and experience to a new or less skillful worker.

(7) Snarl up administration in every possible way. Fill out forms illegibly so, that they will have to be done over; make mistakes or omit requested information in forms.

(8) If possible, join or help organize a group for presenting employee problems to the management. See that the procedures adopted are as inconvenient as possible for the management, involving the presence of a large number of employees at each presentation, entailing more than one meeting for each grievance, bringing up problems which are largely imaginary, and so on.

(9) Misroute materials.

(10) Mix good parts with unusable scrap and rejected parts.

12. General Devices for Lowering Morale and Creating Confusion

(a) Give lengthy and incomprehensible explanations when questioned.

(b) Report imaginary spies or danger to the Gestapo or police.

(c) Act stupid.

(d) Be as irritable and quarrelsome as possible without getting yourself into trouble.

(e) Misunderstand all sorts of regulations concerning such matters as rationing, transportation, traffic regulations.

(f) Complain against ersatz materials.

(g) In public treat axis nationals or quislings coldly.

(h) Stop all conversation when axis nationals or quislings enter a cafe.

(i) Cry and sob hysterically at every occasion, especially when confronted by government clerks.

(j) Boycott all movies, entertainments, concerts, newspapers which are in any way connected with the quisling authorities.

(k) Do not cooperate in salvage schemes.

Strategic Services Field Manual No. 3

17 January 1944
OSS William J. Donovan Director
Declassified 2 April 2008
Download the full manual (.pdf) from the unclassified news archive.

"All of this has led me to believe that something is terribly wrong with e-mail. What’s more, I don’t believe it can be fixed."

July 11, 2012 · · Posted by Greg Lloyd

Image"All of this has led me to believe that something is terribly wrong with e-mail. What’s more, I don’t believe it can be fixed," writes New York Times columnist Nick Bilton - not pictured on right - in his July 8, 2012 Bits column, Disruptions: Life's Too Short for So Much Email. He's cranky just because he received 6,000 emails this month, not including spam and daily deals. Nick says: "With all those messages, I have no desire to respond to even a fraction of them. I can just picture my tombstone: Here lies Nick Bilton, who responded to thousands of e-mails a month. May he rest in peace."

Nick continues: "Last year, Royal Pingdom, which monitors Internet usage, said that in 2010, 107 trillion e-mails were sent. A report this year from the Radicati Group, a market research firm, found that in 2011, there were 3.1 billion active e-mail accounts in the world. The report noted that, on average, corporate employees sent and received 105 e-mails a day. Sure, some of those e-mails are important. But 105 a day?" Please read his entire column for a lively piece of Nick's mind on the subject.

Email is OK for incoming introductions and disposible notifications, but when you try to use email for collaboration, multiple To: addresses turn it into something like the stateroom scene in the Marx Brothers A Night at the Opera.

Add the Cc: line and give up all hope! In 2008 Google engineer Kevin Marks referred to email as a "strange legacy idea" for the younger generation. I call it tragicomically inept for collaboration.

In 2003 Clay Shirky said: "All enterprises have more knowledge in their employees as a group than any one person, even (especially?) the CEO. The worst case is where one person has a problem and another knows a solution, but neither knows the other – or that the other knows. Despite e-mail’s advantages for communication, it falls down as a close collaboration tool on complex projects: E-mail makes it hard to keep everything related to a particular project in one place; e-mailed attachments can lead to version-control nightmares; and it’s almost impossible to get the Cc:line right. If the Cc:line is too broad, it creates “occupational spam” – messages from co-workers that don’t matter to everyone addressed. If the Cc:line is too narrow, the activity becomes opaque to management or partners."

From my 2008 blog post Email isn't dead - It's only sleeping

See Clay Shirky, Social Software: A New Generation of Tools by Clay Shirky, Release 1.0 Vol 21, No. 5, 20 May 2003 (pdf)

Caroline McCarthy, The future of Web apps will see the death of e-mail,, Feb 29, 2008

Modern social software is now being widely adopted as an alterative to email collaboration, based on a pattern that Doug Engelbart recognized long ago, see Flip Test 1971 | Email versus Journal.

May I suggest Traction TeamPage?

Why links matter - for your business as well as the public Web

July 7, 2012 · · Posted by Greg Lloyd

Image Mathew Ingram recently wrote Why links matter: Linking is the lifeblood of the web. He makes a strong case for the value of open linking - giving credit to original sources - as an ethical imperative. He also points out the collective benefit, quoting Om Malik:

"Links were and are the currency of the collaborative web, that started with blogs and since then has spread to everything from Twitter to Facebook to Tumblr. Links are the essence of the new remix culture. It is how you show that you respect someone’s work and efforts. It is also indicative that you are part of a community."

Despite the success of Facebook and mobile apps that attempt to maximize value from walled gardens (where your attention is the product being sold), I remain optimistic that the Web and behavior that rewards linking will continue to win.

And I believe that the same open link and search model will win for work and serendipitous discovery in the realm of Enterprise 2.0 (or Social Business if you prefer).

See Intertwingled Work, my two cents on why links matter in E2.0 - from 2010.

Why we're here. TeamPage at Enterprise 2.0 Boston 2012

June 18, 2012 · · Posted by Greg Lloyd

ImageIf you're attending E20 Boston 2012, please drop by Traction Software's booth 418 to say hi and learn what Traction TeamPage can do. If you're interested in social task management, integrating systems of record and systems of engagement - or just using social software in the context of work, talk the folk at Traction Software who know how to help you succeed. That's where we started and that's our enduring goal.

TeamPage in the Cloud Jordan and I can answer questions about TeamPage's new Cloud options, starting at less than $2.50 per user per month for 25 user accounts - or see for yourself.

You can see TeamPage improvements introduced over the past year, including:

New streamlined Proteus interface makes summary awareness, status, task tracking, and coordinated activity fast and easy.

Unified search in the header makes looking up people, spaces, tasks or projects quick and easy. You see suggested matches based on name, email address and other content as you type, with a Show All choice if you want to browse more. Unified search also matches names and descriptions of all preferences and setup controls and takes you to the right spot in all setup and administration views.

Autosave and "finish later" saves your work in progress if you want to take a break - or if you accidentally click away from or close a browser window!

iPad and mobile access Monitor the pulse of your organization, stay informed, and work securely from the beach or mountains with your iPad, iPhone, or Android tablet. "I'd rather be sailing" isn't an mutually exclusive choice any more - ask Chris!

If you're early in line Tuesday or Wednesday, you can also pick up free, signed, pre-release copy of Jacob Morgan's excellent new book The Collaborative Organization.

If you're too late to pick up a free copy, you can still pick up a bookmark as a reminder of what Enterprise 2.0 is about - at least for me:


See Enterprise 2.0 Schism

The Future of Work Platforms: Like Jazz

Extending the fabric of work, or How to Be Emergent

20 June 2005 | Supernova | Why Can't a Business Work More Like the Web?

Traction Roots - Doug Engelbart

The Collaborative Organization - Free signed copy, Traction Software Booth 418 E2.0 Boston 2012

June 13, 2012 · · Posted by Greg Lloyd

ImageI've read an advance copy of Jacob Morgan's upcoming book, The Collaborative Organization: A Strategic Guide to Solving Your Internal Business Challenges Using Emerging Social and Collaborative Tools. I'm very happy that we decided to give Enterprise 2.0 Boston folk a chance to meet Jacob and get their own free, signed copy at Traction Software Booth 418 next week. Jacob says: "The purpose of this book is to act as a guide for executives, decision makers, and those involved with collaborative initiatives at their organizations". I believe he hits the mark with a book of lasting value, as do reviewers including Vivek Kundra, former Chief Information Officer of the United States; Erik Brynjolf, MIT Center for Digital Business Director, and others.

Jacob organizes his book into three parts: The Opening, The Middle Game, and The End Game. The Opening chapters talk to people in organizations who are just getting started with their initiatives. It covers business drivers, case studies, evaluating risk, and getting the right people involved. The Middle Game chapters cover topics including defining goals to match your business, developing a strategy, vendor evaluation, dealing with resistance, rolling out a platform, and developing governance. The End Game chapters talk about strategies for sustaining and maintaining these initiatives in the long term, including a bonus chapter on Enterprise 2.0 with Andrew McAfee.

Jacob's book is based on his own analysis and research, including interviews, case studies and survey responses from 234 individuals around the world, working for companies ranging from 1,000 to over 100,000 employees, with responsibilities ranging from mid-level to C-level executives. The Collaborative Organization is vendor neutral, involving actual practitioners who are implementing collaborative tools and strategies for their organizations - not vendors or consultants.

Each chapter includes analysis, examples and a well-written Summary and Action items section, with actionable advice that you'll turn to often. Chapters include case studies, examples and results drawn from practitioner experience, not hand-wavy fluff.

It's a handbook you'll have on your desk for the next few years. I particularly like:

  • Chapter 2 - The First Step to Recovery is Admitting You have a Problem on business drivers and problems (20 pages)
  • Chapter 7 - The Adaptive Emergent Collaboration Framework practical advice on choosing and adapting approaches to match your business goals and culture (27 pages)
  • Chapter 8 - Resistance is Futile on barriers to success (13 pages)
  • Chapter 12 - Measures of Success, practical advice on measuring soft benefits, hard benefits, and defining business value (19 pages)

Traction Software is the only source for full hardbound copies before the book's official ship date in July 2012! Show up in person at Traction Software's booth 418 during E20 Boston 2012 Showcase Exhibit hours. Follow @TractionTeam on Twitter for times when Jacob will be available for signing and to talk with him about business challenges using emerging social and collaborative tools.

Free copies are limited. I'll post rules for an online Enterprise 2.0 Twitter quiz you can use to put yourself first in line for a copy. You must show up in person to claim a book, but the Twitter quiz should be fun too!

Update: See E2.0 Boston 2012 Twitter Pop-Quiz for rules and quiz highlights.

Update: Thanks to the @e2conf staff and everyone who dropped by booth 418 to talk, and pick up a free copy of Jacob's book. After you read it, please post a review on Amazon to let others know what you think. Here's my Amazon review.

Also, after visiting us at Booth 418, don’t miss Robert Morison (@rfmorison), author of Analytics at Work: Smarter Decisions, Better Results at Talent Analytics Booth 232.

See 19-20 Jun 2012 | Traction Software Enterprise 2.0 Boston

The Future of Work Platforms: Like Jazz

Extending the fabric of work, or How to Be Emergent

Laser focused E2.0, without the risk? Get Traction!

May 10, 2012 · · Posted by Jordan Frank

I really like how Kashya Kompella from the Real Story Group offered a great dose of context for his E2.0 Marketplace Analysis Q2 2012: "Slightly modifying what the ancient Greeks said, you cannot dip your finger twice in the same (activity) stream." Simply said, there is not a lot of room for risk when an enterprise makes an attempt at an E2.0 effort, whether they are trying to build knowledge in a wiki, approach project management from a perspective managers actually like, or wrap up the whole effort with blogs, discussion, and a social networking layer on top.

In his 4D chart below, Kompella grades market players based on vendor business and product risk. Unlike most quadrant analyses, this is a case where being high upper right is not good.


By way of example, perhaps he grades Newsgator as low vendor and high product risk because they've been around a long time (vendor stability) but their product focus has changed entirely three times (from RSS client to RSS Server to Social layer on SharePoint).

The Vendor and Product risk appears general as the color of the circle also demonstrates an area of risk based on the vendor's focus on the E2.0 market. Oracle is the lowest rated on product risk, but they are colored white to indicate a very low focus on E2.0. So, perhaps Oracle is a good choice for your next database, but don't hold your breath if you are counting on them for your E2.0 platform.

Traction Software and our product Traction TeamPage show up low and to the left (low product and vendor risk) in a cluster with Microsoft and Oracle. However, we also show a Black circle (compared to White for Oracle and Purple for Microsoft) demonstrating laser focus on the Enterprise 2.0 market - as has been our focus since our founding and long track record.

Of course, none of this matters if the platform isn't any good. This chart doesn't say much about the product itself except for its focus and the rate at which its being overhauled, which can be a sign of innovation (good) but it also may warn of a sloppy underlying platform or poor vision as new capabilities are added. Traction TeamPage was built from the start as a journaling and editing system - which laid ground for every E2.0 "feature phase" starting with Blogs and then leading to Wiki, MicroBlogging, Discussion, Social Bookmarking, RSS, Project Management and User Profiles / Social Networking.

To gauge quality, there are ample analysts who've weighed in on that matter, showing TeamPage has a stable platform upon which we've been able to innovate successfully over the last decade. Here are a few recent indicators:

  • contributor Haydn Shaughnessey says: "Traction, for my money, is the best conceived collaboration suite for companies that have a technical development requirement." He cites Traction Software as an example of a business that successfully competes with large companies like IBM by retaining: "... close attention to client needs, a personal desire to explore changes in the work environment, and a desire to see those reflected in the platform."
  • The 9th Annual MIT Sloan CIO Symposium has announced Traction Software as one of ten finalists for the 2012 Innovation Showcase as its Traction TeamPage product represents a cutting edge B2B solution that combines the strong value and innovation to enterprise IT.
  • CTOLabs adds Traction Software to its companies of note list, "firms we believe enterprise technologists should track":
  • Jacob Morgan from Chess Media Group says: I’ve seen the Traction product a few times now I have to say that I really like it and not just for small and medium size businesses. Traction offers an amazing search integration feature which many large vendors can’t even come close to replicating."

So, if you want a platform that rocks and remains cutting edge in the E2.0 marketplace, all without introducing vendor and product risk, Get Traction! And do it risk free as we just introduced new hosting options and the opportunity to try it free for 30 days, then pay monthly. Check it out.

"Probably the coolest vendor pricing page I've seen for any collaboration vendor" ~ Jacob Morgan

April 19, 2012 · · Posted by Greg Lloyd

Thanks to Jacob Morgan, Chess Media Group for his Tweet this afternoon while we were chatting on the phone. Last October Jacob reviewed Traction TeamPage in his Emergent Collaboration Vendor series, and liked what he saw, including TeamPage pricing. He said: "I had the pricing explained to me so I understand it but I think it would be helpful if they made it easier to understand for all site visitors because it really does make sense." We agree on both points! In updating the Buy page, Chris Nuzum used Apple Store product configuration pages as benchmarks for clarity and ease of use.

We followed Jacob's price comparison model, providing interactive feedback on per user per month pricing as well as an annual roll-up and clear option pricing. Cloud-hosted TeamPage is featured front and center - with hosted TeamPage free for your first month, at $1.87 per person per month for 100 people. All TeamPage products include integrated action tracking for project and case management that works like jazz, not something out of 1984.

Pricing options includes cloud-hosted Attivio premium search and Social Enterprise Web, choices of workgroup or full TeamPage configurations, flexible pricing based on the number of named accounts, and easy upgrades when you want them. Cloud-hosted TeamPage is great for small to mid-size organizations who want to punch well above their weight without hiring or adding IT staff.


I'd change Jacob's probably the coolest and say the coolest, no doubt! Thanks Chris! Go to the Buy page and see for yourself.

A Focus on Individual Users

April 4, 2012 · · Posted by Jordan Frank

With Dartmouth President Jim Kim's recent nomination to the World Bank, I pulled out my copy of Mountains beyond Mountains to find the Kim quote that I found most inspiring for my day to day work.

From page 294:

"And," he says, "another secret: a reluctance to do scut work is why a lot of my peers don't stick with this kind of work." In public health projects in difficult locales, theory often outruns practice. Individual patients get forgotten, and what seems like a small problem gets ignored, until it grows large, like MDR. "If you focus on individual patients," Jim Kim says, "you can't get sloppy."

Sure, guiding customers on their social software use cases (one of many things I do in a day) seems somewhat insignificant compared to eradicating Tuberculosis in Haiti (one of Jim Kim's missions when founding Partner's in Health with Paul Farmer) though we do have the occasional case such as the Borlaug Global Rust Initiative where software is being used to combat a plant disease which, unabated, would cause a great deal of starvation.

Nonetheless, there is useful wisdom in the focus on the individual patient which, in my case, is the software user, their business need and corresponding use case. A very current example is a customer we are working with this week in an effort to make TeamPage meet some very particular project management reporting needs. We've provided Q&A support over the course of a few months, but not until we took the a "journey to the sick" (a practice of Kim's PIH partner Paul Farmer, where he takes routine hikes to patients in hard to reach towns) did we understand the process fully enough to prescribe an approach and technical solution.

While most folks get up and running perfectly well TeamPage, there are various that could do things better. This was one of those cases where the customer did OK for months but wanted to improve their use case prior to an all out replacement of a custom built project management system.

Another case was an energy company that tracked issues with Wiki pages because that was the first thing they tried. It worked for years so they didn't even consider using Tasks for each issue - an immediate recommendation we made when we finally saw what they were up to.

All too often, RFPs and their corresponding software requirements roll up a set of user needs into a list of features that you check off to qualify. But underneath all those checks are some very specific processes and quirks that a feature list alone will never support.

You can't just solve a software problem in the abstract any better than you can solve a health problem without seeing the patient, their living conditions and even the political environment in which they live. It's crucial to take the long journey to visit (by foot or by web meeting, of course) the user to see the content, examine legacy systems and understand the skills and challenges facing people involved.

Jim Kim did great things for Dartmouth and I wish him luck in getting the position at the World Bank. For anyone that doubts his credentials, I suggest a read of the World Bank's strategic themes- most of which refer to basic clean water, nutrition and infectious disease issues which devastate the poor countries that the Bank is trying to assist. These are the issues Kim faced very directly at PIH.

What's the Point ?

February 15, 2012 · · Posted by Greg Lloyd

From Nora Ephron speaking at Brown University, President's Lecture series, "Adventures in Screenwriting" April 24, 1997. Paraphrased notes by Greg Lloyd: I took my first journalism course in high school. The fellow who taught it left after two years and opened a hardware store in LA. I think I was the only person he taught who went on to work as a journalist.

We learned the basics of story writing - who, what, when, where - and then learned how to write a lede. One day, the teacher wrote something like this on the board:

Mr. Charles Fenwick, principal of the Broadmoor High School, and his staff will attend the regional educator's conference in Wilmington on Thursday April 25th. Dr. Raymond White, state Secretary of Education, will keynote the conference, which will also feature an address by Dr. Marsha Newman, High School teacher of the year.

He said, "Write the lede." We sat at our desks and wrote, Dr. White to keynote educator's conference, Fenwick to lead teachers on trip to Wilmington and so on.

We turned them in. The teacher looked them over and said "No. What's the point?

"Your lede is, No School Thursday"

At that instant, I thought "What's the point? What a wonderful question!"

Feb 15, 2012 Reading John E. McIntyre's excellent blog post The Things Editors Do reminded of a point that tickled me in Nora Ephon's talk. Her story seems particularly apt in the age of Twitter, activity streams, and social software.

Happily I had a record of my notes posted in Traction Software's TeamPage server automatically carried forward from pre-release version of TeamPage, and still as easily findable and quotable as my latest post. - grl

"If what you write does not relate to the point, it may be good, but it will likely end up on the cutting room floor." ~ Nora Ephron, Adventures in Screenwriting, April 24, 1997.

Happy Birthday Doug Engelbart!

January 30, 2012 · · Posted by Greg Lloyd

ImageHappy Birthday Doug! A perfect gentle knight of technology as well as a pioneer and great inventor. Doug Engelbart's 87th birthday - today - is a fine day to watch the video of Doug's talk "The Strategic Pursuit of Collective IQ" embedded below. And a great day to (re) read Doug's "Augmenting Human Intellect: A Conceptual Framework" 1962, see My favorite Doug quotes and links, see Doug Engelbart | 85th Birthday Jan 30, 2010 from two years ago.

Update Remembering Doug Engelbart, 30 January 1925 - 2 July 2013

[from] "The Strategic Pursuit of Collective IQ" - Doug Engelbart's presentation at the The Brown/MIT Vannevar Bush Symposium in 1995, celebrating the 50th anniversary of Bush's groundbreaking article "As We May Think". Introduced by host and long-time friend Andy van Dam, Doug recounts his discovery of Vannevar's work, briefly describes the unfolding of his own work and what's next using hisBootstrap "Paradigm Map", and shares his wish that, had he only known that Vannevar was still alive in 1968, he would have sent him the film of his 1968 demo. See Doug's Abstract and Bio for this talk. Presentation: 50 minutes; Q&A 10 minutes.

See the Video Archives - Bush Symposium page at the Doug Engelbart Institute website for links to all 11 sessions of this Symposium.

This movie is part of the collection: Doug Engelbart Video Archives

Don't take my word for it - Byrne and Koplowitz on SharePoint

November 29, 2011 · · Posted by Jordan Frank

At the Enterprise 2.0conference two weeks ago, Tony Byrne (President, the Real Story Group) and Rob Koplowitz (VP and Principal Analyst, Forrester Research) were joined for the SharePoint Analyst Panel. David Carr's Information Week column Does SharePoint Have Future As A Social Platform frames the debate as lopsided with a simple conclusion: No.

IT Managers across the globe are deploying SharePoint in hopes that it will form the basis of their collaboration and social strategy, but SharePoint's ability to check off the feature lists (yes, it has a notion of profiles, pages, tagging, discussion, tasking) belies the actual outcome.

Koplowitz said: "it's a lot better portal than it is a social platform." (I am not convinced that this implies it's a good portal)

Byrne said: "They've built a decent platform for lightweight file-oriented collaboration... But SharePoint only provides two of the 10 or 11 key applications enterprises are looking for" in a social platform.

Byrne said: "the dirty little secret of SharePoint is that the vast majority of its usage is for very basic file sharing."

Koplowitz said: "If you're going to take on this beast--if you're going to take the buffalo down--you'd better be prepared to consume every part of it."

Not very promising.

An easy way to handle basic file sharing or even construct a basic portal may be an important part of an information strategy but isn't worth the true cost of SharePoint and doesn't merit the upside down 3 to 1 (by a conservative estimate) services to licensing cost ratio that any company should be ready to swallow if they want to tune and customize SharePoint to do more than what it's good at out of the box (some portal and lightweight file oriented collaboration activities). Following that path is expensive and led Thomas vander Wal to write SharePoint: Gateway Drug to Enterprise Social Tools.

If you don't have SharePoint, Koplowitz' fair warning is you better be ready to take the buffalo down. But the good news if you already have SharePoint is twofold:

1) It is OK at short term, small team oriented file collaboration and always will be.

2) You can break down the workspace and content type silo problem and make that locked up content more findable, social and valuable by adding TeamPage to the mix. For far less than it would cost to re-engineer "social" into SharePoint or even upgrade it to the 9s to run their FAST Search, you can unlock it's silos and socialize around it with TeamPage Attivio Plus Search and Social Enterprise Web.

Why stop with a social wrapper around or inside SharePoint. By making Connected Workpossible with TeamPage, you can also engage across all your other enterprise systems, content, and even the entire web.

Seamless integration can work like the Web | W3C Social Business Jam

November 9, 2011 · · Posted by Greg Lloyd

ImageI just joined the Nov 2011 W3C Social Business Jam and added a discussion topic: Seamless integration can work like the Web. I'm on deadline for Enterprise 2.0 next week in Santa Clara [ see you there ! ] but will try to steal time to jump in to a live IBM Jam while it's open (through Nov 10, 2011 8pm EST).

The description for Seamless Integration begins: Are there effective ways to combine legacy applications with new social technologies to help foster or encourage greater use in the company? If so, can it be done incrementally?

I propose:

... integration of social software (now "systems of engagement") and transactional systems where work gets done (now "systems of record"), using the same W3C protocols and layers over W3C protocols that make the public Web successful: Web-standard content delivery, links, and link-aware search."

The world inside a social business differs from the public Web in many significant ways: a) it's much smaller; b) it's very link-deprived compared to the public Web; c) there's a lot of redundant content (think of all of the copies of the same slide deck distributed in email); d) some highly valuable content isn't linkable at all (think legacy systems of record); e) finer-grain permissioned access rules are much more important when you want to open up the most of what the business does, and what people in the business know. On the plus side, social business activity adds valuable context.

This bring issues like consistent and reliable identity, consistent and reliable access controls (over W3C protocols), representation of context, and permission aware search to the top of the queue. I believe these issues can be addressed by system architecture and layering of services over base level W3C protocols, which may eventually lead to extension or additional layers of W3C protocols.

Then use Doug Engelbart's model linking Knowledge Product (systems of record), Dialog (systems of engagement), External Intelligence (email, public Web, other social businesses) as examples. And Traction TeamPage. Published in the Jam with with links of course!


See Seamless integration can work like the Web - in the W3C Social Business Jam.


Ada Lovelace Day | Betts Wald, US Naval Research Lab

October 8, 2011 · · Posted by Greg Lloyd

ImageAda Lovelace Day celebrates the contributions of women in science and technology. I've chosen to write about Betts Wald who was a branch chief in the Communications Science division of the US Naval Research Laboratory (NRL) when I first met her. I joined NRL in 1974 as my first real job - after serving in the US Army when I was drafted as a graduate student at Brown. It was a great experience. NRL was full of wildly talented, energetic and brilliant managers who knew how to get impossible things done in engineering and government, and taught that skill to their teams. Betts was one of the best: leading and inspiring her team, running interference, providing just enough technical guidance (i.e. to avoid permanent damage) while constantly encouraging and developing her team's talents. Women in science and technology should be encouraged to consider career paths as leaders as well as individual contributors: Betts is a great role model. Although I never heard Betts shout: "To the difference engine!", except for the pipe it would be in character. And I'm not certain about the pipe.

Ada icon by Sidney Padua: I strongly recommend that you download the thrilling adventures of Babbage & Lovelace for your iPad, and see author Sydney Padua's excellent 2D Goggles site.

What's the 2.0 of Enterprise 2.0? Or, How to Be Emergent?

September 4, 2011 · · Posted by Greg Lloyd

ImageHat tip to Professor +Andrew McAfee for pointing out Do Happier People Work Harder? my nomination for Required Reading of the Day (#RRD). Teresa Amabile, a professor at Harvard Business School, and Steven Kramer an independent researcher wrote a great New York Times Labor Day opinion column. They cite sobering results from a Gallup-Healthways poll of 1,000 adults every day since Jan 2008: "People of all ages, and across income levels, are unhappy with their supervisors, apathetic about their organizations and detached from what they do." They also suggest that the problem is manageable - by what I would define as great enterprises.

Over the past half-decade Amabile and Kramer researched micro-level causes behind this problem, collecting nearly 12,000 electronic diary entries from 238 professionals in seven different companies. The results support three important conclusions:

1) "... inner work life has a profound impact on workers’ creativity, productivity, commitment and collegiality... Conventional wisdom suggests that pressure enhances performance; our real-time data, however, shows that workers perform better when they are happily engaged in what they do."

2) "Gallup estimates the cost of America’s disengagement crisis at a staggering $300 billion in lost productivity annually. When people don’t care about their jobs or their employers, they don’t show up consistently, they produce less, or their work quality suffers."

3) Managers can help insure that people are happily engaged at work - I believe Peter Drucker would claim that's the primary responsibility of management. And doing so isn't expensive.

Amabile and Kramer say:

"Workers’ well-being depends, in large part, on managers’ ability and willingness to facilitate workers’ accomplishments — by removing obstacles, providing help and acknowledging strong effort. A clear pattern emerged when we analyzed the 64,000 specific workday events reported in the diaries: of all the events that engage people at work, the single most important — by far — is simply making progress in meaningful work..."

"Most managers don’t understand the negative consequences of this struggle. When we asked 669 managers from companies around the world to rank five employee motivators in terms of importance, they ranked “supporting progress” dead last. Fully 95 percent of these managers failed to recognize that progress in meaningful work is the primary motivator, well ahead of traditional incentives like raises and bonuses."

"This failure reflects a common experience inside organizations. Of the seven companies we studied, just one had managers who consistently supplied the catalysts — worker autonomy, sufficient resources and learning from problems — that enabled progress. Not coincidentally, that company was the only one to achieve a technological breakthrough in the months we studied it."

That's good news - but not really news. An enterprise that makes great use of the creative talents, enthusiasm and unique expertise of its people can gain a sustainable competitive advantage and be a great magnet for attracting and maintaining talent. Look at Apple among others.

Technology can't create a great enterprise, but it can open the door for innovation in how any enterprise operates - from micro to macro scale - including how it operates with external stakeholders, customers and suppliers. This opens the door to another form of strategic as well as operational advantage.

I've persistently said that the 2.0 of Enterprise 2.0 should refer to a conscious rethinking of how an enterprise can work more effectively and creatively, using Web technology to enable "action at a distance" and connections spanning barriers of space and time. Web technology is necessary but not sufficient for this kind of innovation at scale, although Doug Engelbart's work clearly called this shot decades before the Web.

I'm no sociologist, but Amabile and Kramer seem to support the view that socialization in the context of everyday work - rather than as a separate "social" duty while at work - may be best. I don't think people know how to "be emergent", but people are very good at discovering and developing unexpected relationships in a context where many values and norms are shared - at work.

Repeating points from Enterprise 2.0 Schism in 2009: 1) It's not just the technology; 2) It's not just the people; 3) An effective organization is a social invention that is created or shaped to serve extraordinary ends, and that may be the most valuable invention of all.

"The purpose of an organization is to enable ordinary humans beings to do extraordinary things." ~ Peter Drucker, Management: Tasks, Responsibilities, Practices (1974)

See Amabile and Kramer's New York Times column, and read their July 2011 book The Progress Principle (Forbes interview).

Do Happier People Work Harder? By Teresa Amabile and Steven Kramer New York Times Sunday Review, September 4, 2011

G+ discussion on +David McRaney's The Illusion of Asymmetric Insight and how emergent behavior is not all unicorns and rainbows. Think Lord of the Flies

Need for Incentives, and other Innovation Myths - The most powerful incentives are intrinsic, not "pay to share" games.

Enterprise 2.0 Schism - Why Doug Engelbart and Peter Drucker should be declared Patron Saints of E2.0

Peter Drucker and Enterprise 2.0 - Drucker Centenary Nov 2009

Doug Engelbart | 85th Birthday Jan 20, 2010

See G+ for original post and discussion

Enterprise photo courtesy US Navy. Strictly speaking CVN-65 is Enterprise 8.0 - the eighth US Navy ship to bear that name see

I don't know what a picture of an "Enterprise 2.0" might look like, and don't want to use any of the stock photos of smiling folk around a laptop that are about as convincing as socialist realism posters of smiling tractor factory workers. And all the good Star Trek Enterprise photos are Paramount's copyright.

Extending the fabric of work, or How to Be Emergent

August 24, 2011 · · Posted by Greg Lloyd

ImageI enjoyed reading Dion Hincliffe's Putting Social Business to Work and G+ discussion led by Luis Suarez on Laurie Buczek's The Big Failure of Enterprise 2.0 Social Business. I agree that top down - and isolated - Social Business parallels the faults of top down - and isolated - Knowledge Management. I like Laurie's analysis and recommendations, including her top level: "Make social tools part of the collaborative workflow." This is good for both social business and knowledge management. The question is: how to extend the fabric of work?

An edict from management or prayer from internal evangelist to "be social" is often translated: "how many hours a week?" and "instead of doing what?" A top down Knowledge Management edict: "share what you know" turns into a empty Friday afternoon exercise that's soon abandoned.

In both cases bottom-up capture of conversations, actions, responses to routine or exceptional issues, and human actions in context is a much better way to deliver what knowledge management and social business promise.

This includes free-form accidental discoveries and introductions to folk throughout the organization who aren't usually involved or aware of what others are doing. In my opinion, emergent and unpredictable value that advocates of Enterprise 2.0 promise is an outgrowth of making work more open, observable and discoverable. It's also critical to make work easier, more effective and more enjoyable. Build on that rather than adding overhead and waiting for people to jump into an activity they see as optional and divorced from their contribution to the success of their business.

Enterprise 2.0 systems like Traction TeamPage are really good at capturing conversation in context, tracking action and linking what people do or say to their profiles and vice versa. But it's difficult to make work done within siloed systems of record - document repositories, ERP, CRM - visible and actionable. Opening up siloed discussion in each system of record makes matters worse, not better.

Sharing activity streams across systems of record is one way to avoid the siloed discussion trap. But limiting visibility of work to activity streams opens a new problems: activity stream overload. If you think following hundreds or thousands of people on Twitter can be frustrating, wait until you hear what you get from raw streams from line of business applications. A stream of "What I had for lunch" tweets is thrilling compared to a stream of Documentum check-in notices and decontextualized status.

I believe that the best solution will include permission-aware search than spans activity streams and systems of record to make documents, individual email messages, SQL database records from CAD/CAE or other line of business systems actionable, social objects. What's important is the ability to connect people, records, conversation and action in the context of core business activities like product development, sales, support, and coordinated work with customers, suppliers and partners. This should include daily routine, exceptions, and new discoveries.

At E2.0 Boston, Traction Software announced and showed TeamPage and Attivio's Social Enterprise Web technology used to search, discuss, tag, task, and share live structured data or unstructured content in external systems of record including Microsoft SharePoint, EMC Documentum, Microsoft Exchange, File servers, SQL databases, intranets, and the public Web.


A question found in a customer email stored in Exchange, an issue with a new drug application filed in Documentum, a fact in a legacy document stored in SharePoint or a File server S: drive, a record in an SQL database can all be discovered, discussed, tagged, and tasked for follow-up action in TeamPage without converting or importing data from its original source. Systems of record look and act like they are part of the same permission-aware TeamPage fabric used for collaboration, communication, and action tracking in the flow of daily work.

Large companies have enormous IT teams promising enterprise-wide search and collaboration with roadmaps stretching years into the future and budgets of seven to ten figures or more. Traction TeamPage and Social Enterprise Web capabilities are packaged and priced to make deep, permission aware search and collaboration crossing many sources simple to deploy, manage, and use. This is a game changer for small to mid-size businesses who don't find complex, multilayered enterprise architectures manageable or affordable. This is also a great option for teams in large companies who want to get their work done now, working over existing systems of record.

You'll hear more about this soon [or contact us to learn more now]. Making systems of record look and act more like the Web - including scalable, permission aware search - extends the fabric of work in context for external and internal stakeholders.


On G+ see
Luis Suarez - 24 Aug 2011
Dion Hinchcliffe - 24 Aug 2011
Greg Lloyd - 24 Aug 2011

Lipstick on a Pig

August 5, 2011 · · Posted by Greg Lloyd

On Aug 5, 2011, Andrew McAfee opened a public discussion on Google+ by sharing How Apple (unintentionally) revolutionized corporate IT by Aaron Levie. McAfee commented "Story from CNNMoney about how Apple is unintentionally revolutionizing corporate IT. About time, too." and asked "Does anyone doubt that the Cloud + mobile + social + new devices is going to have a huge impact on corporate technology infrastructures and costs within the next 5-10 years?" Off to the races...

Greg Lloyd - This may also radically reduce the roll-out time for new corporate capabilities designed to use native Web infrastructure including HTML5, GWT and other technologies that deliver a user experience on par with the public Web.

The same applies to back end services and IT's ability to acquire, deploy, adapt and support back end services more rapidly and effectively.

Contrast aggressive internal awa external use of Web tech and architecture by IT versus the interlocking three, four, or five year update cycles using the MS stack (or others) and update cyles of IT systems that depend on and lag MS by years.

A very highly placed person in government told me: "Traditional IT architecture and practice almost guarantees that any new initiative will be late, grossly over budget, and obsolete before it is delivered."

Forcing change to a Web-like approach from front end mobile and user experience expectations can shift IT back to focus on timely response and business value rather than plumbing. And deliver systems people like to use.

Dan Camper - +Greg Lloyd I agree with you, so long as the problem (and solution!) domain remains within the "corporate capabilities designed to use native Web infrastructure."

There is sometimes a tendency for IT to force an inappropriate solution onto the customer merely to make IT's life easier. A web app implementation rather than a thin app (or even a custom app), for instance. Or vice-versa. This leads to a dissatisfied captive customer base, which of course doesn't help anyone in the long term.

An IT department would do well to treat its internal customers as if they where external, paying customers instead. To borrow some of Steve Jobs' phrasing: Delight those customers with extraordinary, amazing solutions. Yes, you have to pay to play, but the end result would be worth it.

Greg Lloyd - +Dan Camper I agree. "Lipstick on a pig" fits for a weak Web interface as one-for-one replacement for IE6 or similar vintage IT clients for systems of record. But even a weak Web interface can at provide mobile access, and steps around an obsolescent plumbing choice that Microsoft urges customers to abandon.

I believe that the 5-10 year shift in corporate technologies and infrastructure Andy envisions should and will move toward: 1) traditional, transactional "systems of record" - ERP, MRP, Accounting, CAD/CAE - remain as specialized silos and functional back-ends for enterprise systems; 2) minimalist secure (authenticating) Web-compliant interface to these systems of record (to create a thin or custom app as needed); 3) secure, permission-aware search spanning content of systems of record and "systems of engagement"; 4) minimalist but effective, easily adaptable and extensible Web interfaces provided by vendors of system of record (scaling down to mobile); 5) social software / Enterprise 2.0 technology and "systems of engagement" spanning and connecting human work, exception handling, innovation and "systems of record".

Issues of enterprise wide authentication, secure access, permission aware search spanning "systems of record" and "systems of engagement" at enterprise rather than public Web scale can and have been successfully addressed - at least in early stages. The architecture of enterprise IT will more or less resemble the architecture of the public Web - with adaptation and extension of provisions for authentication, permission-aware access, permission-aware search that go beyond the needs of the public Web (although Google and G+ seems to be heading in that direction too).

For thoughts on this shift in IT architecture, see:
July 2010 | Intertwingled Work - Observable work as an activity spanning systems of record

And a step in that direction (Note - I am President and co-founder of Traction Software)
June 2011 | Traction Social Enterprise Web - "Marrying Deep Search and Collaboration"

In this case (and others) it's putting our money where our mouth is, not vice versa.

These are quotes from a public GooglePlus discussion - feel free to join in. If you need a Google+ invitation, please email with the email address I should use to send the invitation.


Reinventing the Web on how we got here

Building pleasant and stable islands in a storm-tossed sea on extending the Web

A Circle is not a Space on GooglePlus experiments and notes

Note: The only iStock photo I could find with lipstick on pig used a piggy bank rather than a real porker. Seems to fit.

A Circle is not a Space

July 13, 2011 · · Posted by Greg Lloyd

ImageLike many people in the tech industry, I've been happily exploring and enjoying Google+ for the past week or so (thank you Susan Scrupski for the early invitation). I like the Google+ bar, polished integration with Google Profiles, Photos, and Video, as well as the new Huddle and Hangout capabilities. And I'm looking forward to Google+ integrated Search. Nov 20, 1985 update: Google's updated Community and Collection model finally gives Google+ something like a shared Spaces as well as email-like Circles. Keep reading for thoughts on why Circles never caught on. - grl

Google's Circle model was carefully designed, with a wonderfully polished interface for adding folk to Circles and creating new Circles. Google is encouraging active discussion, feedback and suggestions on how Google+ should evolve. That said, I've also followed more than a few Google+ discussions in which people get confused by what the current Circle model is versus what the word "Circle" means to them.

I think it's easiest to understand the Circle model by comparing it directly to email lists. This post illustrates that analogy, with my analysis of the Circle model's strengths and weaknesses, and how it might evolve.

My Google+ Foodie Circle Example

If I create a Circle named Foodies and include all my foodie friends, I can post restaurant photos and notes that can only be read by folk I've included in my Foodies circle, hidden from the public. They can comment on what I post, and their comments can be seen by others named in my Foodie circle.

This means:

1) You can't add yourself to my Foodies circle. I'm the only person who can add people to my own Circles.

2) When you look at my Profile, you don't know what Circles I may have added you to. You see either: a) I haven't added you to any Circle (I won't even see your Public posts in my Google+ stream), or b) You are in Greg's circles too. If you're in at least one of my Circles, I will see anything you post to Public or to one of your Circles that include me.

3) You don't know the names of any of the Circles I have created. For all you know, I may have Circles named Saints, Sinners, and Bozos as well as Foodies.

4) You don't know the names of those Circles of mine of which you're a member. You may be both a Saint and a Foodie.

5) You can't treat Foodies like a Twitter Hash tag. It's not the label of a topic that categorizes my posts in a way that is meaningful (or visible) to anyone but me. It's [currently] a set of people to whom I can choose to address a specific post.

So when I create a Foodies Circle, you can't follow or block posts I make to that Circle (a common request).

You don't even know that my Foodies circle exists unless I tell you about it. So you can't "follow just my Foodie posts" without Google+ allowing me to share at least some of my Circle definitions, and giving you the ability to follow just those posts rather than everything I publish.

And when I'm on my Google+ Streams Page, clicking Foodies doesn't show me posts I or others have made "about" food - it just shows me the list of all public or limited distribution posts made by people I put in my Foodies circle. Foodies is a set of people, not a topic or a shared Space.

It's also not [currently] possible for a group of friends to create a public Google+ Circle that people can follow, join, or leave on their own. As a variation on this theme, different types of public Circles might have open membership, moderated membership (to keep out the spambots), or membership by invitation only.

Adding public Circles would create a kind of shared Space model, where everyone who is a member of the same Space gets (at least) permission to see what other members of the same Space post. The globally known (or selectively shared) name of a Space like Foodies would then create a shared room or context for people to talk or work within, implicitly sharing access with other members. Traction TeamPage builds on and extends a Space model to provide permissions, tags, and context for business activities, see Borders, Places and Spaces.

The current Circle definition and possible extensions are pretty clear to folk who get deeply into sharing models (including yours truly). But details of the Circle model seem pretty complicated when you try to write them down, draw pictures, or explain them. Part of the problem is the power of the word Circle.

"Circle" is so powerful that I think a lot of people hear it as something acting more like a shared Space than how Google+ currently works: Circles act like email lists. Thanks to John Tropea for the Google+/Email analogy in his Google Plus : Closed group email collaboration done online of 8 Jul 2011.

A Google Circle is Like a Personal Email List

Google+'s Circle model provides a way for you to share specific conversations with a set of people who you select, who may choose to listen to what you say, and who can comment back to you and others who share the same conversation.

1) You address a Google+ post to a specific set of individuals or to a named Circle (email list) when you create a post. A Google+ Public post can potentially be read by anyone (cc: the World).

2) If people to whom your post is addressed decide to listen to you (they name you in at least one of their Circles), they'll see your post in their input stream. Otherwise they'll need to look at their Google+ Incoming stream to read posts addressed to them from you and other people they don't already "follow". Reading Google+ Incoming feels like reading a low-priority email folder vs reading your standard or Circle filtered stream.

The list of your Circles shown on your Google+ Stream page looks something like a list of incoming email folders. Actually it's a way to show incoming posts from people listed in that Circle: Click a Circle to see all of their Public posts and limited distribution posts addressed to you. As an input filter, Circles don't organize posts by topic (like an email folder), but by sets of people.

3) Commenting on a post is like replying to a specific email message. People who can see the original Post can see the additional comments. The current Google+ presentation becomes noisy when a famously popular person writes a post which attracts an endless stream of "me to" or spammy comments (see G+ comment stream discussion below).

4) You can't change the Circle to which a post is addressed. Like the email list of an outgoing message, the selected Circle or specific folk addressed by a post are fixed when you send it. However, unlike email you can retroactively edit members of the Circle to add or remove folk, as well retroactively edit your own post or comment.

5) When you Share a Google+ post from someone else, it's like you're sending a copy of the original post to a different set of people (the Circle you select), but without the original post's comments. This is analogous to forwarding an email to a different group after stripping out any embedded replies.

Each Shared copy then accumulates its own independent set of comments, visible to the people to whom the new Share was addressed, including resharing a private message to the general Public. Google quickly added an option that the original author can use to disable Sharing of specific posts, and a reminder that resharing of limited distribution posts can be a violation of confidence. But like an email message that's copied and forwarded many times, comments on Shared posts quickly become fragmented.

GMail, Wave, Buzz, Google+ Circles - Email messaging is the model

I believe GMail, Wave, Buzz, and the Circle model of Google+ all share DNA from Google's email culture and the GMail product:

... there are literally tens of thousands of special interest groups that can range in size from two to more than 1,000 members and cover topics from wine to hiking to quilting to Dungeons & Dragons. There are the Gleeglers (who sing a cappella); the Dooglers, who bring their dogs to work; the Snowglers (skiers); and the Skeptics (who question everything). There are groups for pilots, expectant moms and photographers, and a group for Googlers who like flea markets. There's even a group for former startup employees whose companies were bought by Google and who may struggle to navigate a company where they must be both entrepreneurs and employees.

Any employee can start a group -- in fact, employees are encouraged to, said Stacy Sullivan, Google's chief culture officer, a title bestowed by the founders. Most groups have an email "alias" on Google's vast intranet system, such as "" Google has more than 100,000 group aliases in its Intranet system, although not all groups are active.

For employees, the groups "have been kind of anchors and havens and think tanks -- to actually be able to build their own community, just for their own support and interactions, within the mass of all Google," Sullivan said. As Google has grown, "I think it's become much more important because when you're this big, you can lose sight of being connected to the mass around the world. So this is one way they can all pull together."

From At Google Groups are key to the company's culture
by Mike Swift, San Jose Mercury News, 23 Jun 2011

Google+ Circles avoids the Buzz assumption that your social network could be gathered and publicized by analyzing the your email contacts - an assumption that might have worked internally for Google, but which caused a firestorm of protest and legal action when Buzz launched. But the Buzz presentation model of a top level Post and its comment tree as the unit of conversation, floating to the top of your stream every now and then, carries over to Google+.

Google+ Circles provide a much more refined model of selective sharing. However, in my opinion the Circle sharing model works much better for Facebook style sharing of friends and neighbor conversations - a post by an individual and its comments - than it does for Twitter's fast paced global stream of conversation fragments which interleaves the equivalent of posts, comment (replies) in one stream that's easier to scan, particularly when a post may collect tens or hundreds of comments.

Twitter connects fragments by tags. Twitter also implements a socially refined retweet and reply permission model that works better than Google's for that purpose: in Twitter you only see replies if you are following both the person who posted and the person who makes the reply. This has signifiant value for conversation and signal to noise in a large public Commons. See "Option of Latest Posts Discussion" below.

A Circle is not a Space

For work, the current Google+ post and comment presentation can become noisy and unpredictable, repeatedly showing promoted posts based on recent comments from any source, and repeating Shares that fragment comment threads. A presentation choice that favors a top level post and comments, rather than a stream of post and comments (with link back to the conversation in context) is a presentation choice, not a fundamental limit.

More significantly, the current Google+ Circle model makes it difficult to see what's happening in the context of a business activity - tapping into a stream of posts, comments, replies, actions, and actions. For business activities, the stream of actions and conversation in a shared Space provide a natural framing context and natural boundary for permissioned access.

For example, a Space shared by members of law firm and Client A naturally frames and protects work and conversation in that context while also protecting it from disclosure to any other client. A shared Space, tag, and activity stream model is simpler to understand and use for work and conversation with groups that share a purpose and common expectation of privacy.


JP Rangaswami is currently experimenting with three different formats for three purposes:

Playing with formats. Twitter as short form frequent. google plus as longer form, one per speaker at TED. Blog as even longer, one per event) 12 Jul 2011 @Jobsworth

He's also experimenting with a Google+ Circle workaround to allow people to opt in to his conference liveblog posts. You post a comment back to him, he adds you to the Conferences circle he'll use for his liveblog posts. In this case, JP's intent is to allow folk to throttle down the volume of his liveblogging posts appearing in their stream, rather than make those posts private. See "Circles should be created by Publishers as well as Subscribers" discussion below.

The Google+ preview is just about a week old, and Google is actively asking for feedback and suggestions, which has led to lively discussions on how Circles might evolve. And when Google+ integrated search appears (soon), I expect it will be permission-aware, which will be a game changer. Enough balls are in the air to make me rethink for Commons, Neighborhood and Work players in Explaining Twitter - One of Three Places for People - stay tuned!

See links and Google+ discussion (gathered from G+ and all over)

JP Rangaswami, Google+, 12 Jul 2011 (Public)
I'm experimenting …

JP Rangaswami - I'm experimenting. Seeing if I can avoid making noise in people's streams by giving them subscriber-level choices on subsets of my stream. For the next few days I will be covering TEDGlobal, but the updates will only reach those who ask me for them. If you asked me, and you don't start receiving them in a short while, do let me know.

Yes I know the way I've done it is messy (creating a publisher circle and then manually adding people to that circle as they ask to be included) but I could not find s simpler way. Let us see.

John Tropea, Library Clips blog, 8 Jul 2011
Google Plus: Closed group email collaboration done online

Greg Lloyd, Google+, 6 Jul 2011 (people in my Circles only)
G+ comment streams on public posts by popular folk are problematicI can't Share this to Public without losing comments, but here's the main point:

Greg Lloyd - Interesting - and encouraging - to see improvements to adaptive boost of posts based on new comments. Today a 5 hour old +Sergey Brin scenic photo post ~ sticks in place as older post despite a continuous patter of "nice photo!" comments from folk I don't know or follow.

Not clear what the promised comment weighting stream boost adjustment was. Social / follow weighted, linguistic or other, but helps S/N for public posts by famous folk whose patter of friendly, log rolling or spam comments would never die. Google+ needs to fix this before it's gamed to spoil the Public commons.

Followed by:

About 30 minutes after post thanking Google for promised improvement in comment boost to reduce noise based on "non-relevant" comment, a 5 hour old +Sergey Brin photo popped to the top of my mobile and desktop stream with a recent "Cool Man!" comment. No intervening comments from folk I follow in those 30 minutes that I can see.

+Sergey Brin Still getting flooded with tortoise pictures and the like. More recent pyramid pictures are an improvement, but please keep pushing for improvement.

See "flooded by tortoise pictures" discussion

JP Rangaswami, Google+, 10 Jul 2011
In G+, Circles should be created by "publishers" as well as "subscribers"

JP Rangaswami - I guess I'm warped. What I really want is to break myself up, classify myself, into a series of circles: cloud, food, music, books, cricket, politics, hippieness, freedom, whatever. Then others who put me into their circles can choose to put bits of me or all of me. Publisher circles are like hashtags and channels. Subscriber circles are filters and balancers. That combination creates the best signal-to-noise ratios

Jeff Jarvis, Google+, 4 Jul 2011 (public)
... I still want the option of only the latest posts, regardless of comment tagging.

Greg Lloyd - I'd also welcome a pure chron option, with one click to take me to the full post and comments for context when I want it.

For promotion or pure chron, imo Twitter asymmetric reply clip is pretty effective. E.g. Twitter rule that mutes replies from your stream unless you follow both parties. Although I originally opposed the change, I've grown to like it.

Without a pure time ordered option (and jump to full thread) or a hard clip, promoting a post from famously popular person will always be problematic when thousands of "me too" comments pile on. That was my major beef with Buzz. I guess I need so see what Google+ does with rank.

... Jennifer Forman Orth - So, basically, no one's ever going to see this comment :-). How does this foster networking, especially for the Technorati who cultivate these large clusters of folks they do not know to follow them? If I figure no one's going to read what I say, what is the incentive to comment?

Greg Lloyd - Jennifer - A valid point, but IMO the recourse is social. With Twitter, Jeff or someone else may rt or "publicly" reply to you and a wider non-clipped audience by prefixing your handle with a character. This subtly raises the visibility of particularly good comment based on human judgment, polite recognition, and an invitation to a larger audience to read more of what you say.

Greg Lloyd - Taking this conversation as something close to a best case, about 50% of the comments are "I agree" or restate the original point. This from a group of bright and eager early adopters. When the number of Google+ folk increases by three or four orders of magnitude - not counting bots - the bounce will become ludicrously noisy, like Buzz. That's not conversation, that's Brownian motion. Selectively following a reasonably large number of diverse, curious and intelligent folk with a sense of humor is the only scalable filter I know that balances breadth vs S/N. I want to leverage their judgement to surface interesting discussion and as well as talent scouts for who else to follow

Sergey Brin, Google+, 4 Jul 2011 (Public)
… getting flooded by comments on [ five year old ] tortoise pictures

Sergey Brin - I think a lot of people are under the misimpression that I am posting photos of exotic places at a furious pace to Google+. Actually, I have had a bunch of albums public for some time on my picasaweb page. However, people only started to take note recently thanks to Google+ and when they comment on those photos they end up in the streams of people who have me in their circles.

We made some ranking changes recently that demote such comments if the commenter is not in your circles. Let me know if you are still getting flooded with tortoise pictures and the like.

Ross Mayfield, Slideshare, 5 July 2011
Visual Guide to Circles in Google+

Introducing Online Workplaces - Greg's notes on Larry Cannell's July 2011 Webinar

July 8, 2011 · · Posted by Greg Lloyd

ImageLarry Cannell, Research Director, Gartner Group presented great slides and hosted an excellent webinar on July 7, 2011 based on his research and experience. Free registration gives public access to a recording of the Webinar and a copy of Larry's slides - at least for a few days (after than please check Gartner Webinar Archives). Please register and learn! Larry will also be leading sessions at Gartner Catalyst Conference 2011 San Diego, July 26-29. Larry's framework is very crisply stated, general and useful. The 65 slides include very helpful diagrams, examples, scorecard decision aids, and more. These are just top level points from my notes.

An IT Vision for Social Software: Introducing Online Workplaces

The emergence of a new layer of online capabilities, one that sits between rigid business applications and the dynamic world of the information worker, has gone unnoticed for years. Some have started to call this a social layer, inspired by the rising popularity of social software. However, it is better described as an online work layer because not all activities within an enterprise are social in nature, but they all support how work is done. Enterprises need to develop their own tailored vision for how this online work layer (which includes the use of social software) improves their business, rather than relying on vendor product positioning.

This webinar will describe a vendor-neutral framework that helps IT describe, manage and evolve collaborative and workplace technologies to maximize the effectiveness of their enterprise’s information workers. ~ Larry Cannell, Research Director, Gartner

Introducing Online Workplaces
Larry Cannell, Research Director, Gartner @lcannell

Need to distinguish:
What (Business Objectives) vs How (Approach for accomplishing What)

What (business objective): Work
How: Unified communication, Email, conferencing, Productivity tools, Social Software, Workspaces, Content Management, Search

Defining a Work Layer

Enterprise Goals and Objectives -> Business Processes (PD, Mfg, Sales...) <-> Work Layer (Routine, Non-Routine) <-> People (individuals, teams, communities)

[ Very good slides distinguish needs and perspective as individual, as member of functional team, as participant in broad community and directed versus volitional participation ]

Online Workplace:

Organize/Manage Work (tasks, priorities, etc)
Facilitate Work Processes (ad-hoc, tacit)
Work as Individuals (attention management)
Work together (team, communities)
Capture and Reuse Intellectual Assets.

Online Workplace Relationships:

Business processes <- (tasks, priorities) -> Online Workplace <- (completing tasks, prioritizing work, planning, deciding) -> People
Human Capital (knowledge, experience, relationships) <- (discover, describe) - > Online Workplace
Structural Capital from Applications (CRM, ERP, PLM, SCM, etc) - (data) -> Online Workspace

Online Workplace Framework:

Individual environments, Group environments (Teams, Communities)
Business Applications, External Information

Group Environments - A spectrum of participation
directed - individual must participate to meet some joint objective or get certain kind of work done.
volitional - individual choses to participate or not, choses level of participation

Process (90% directed participation, 10% volitional participation)
Activity (50% directed, 50% volitional)
Community (30% directed, 70% volitional)
Network (10% directed, 90% volitional)


Position online workplaces as strategic assets
Take care of the individual worker
Expect to support multiple online workplaces
Develop new skills
Provide a roadmap
Demand what you need from your vendors

Online Workplace Framework and Traction TeamPage

Larry's framework is descriptive and intentionally vendor and technology neutral.

I believe Traction TeamPage is very well aligned and easy to explain in terms of Larry's framework. Expect me to make liberal use of his framework and terminology - with credit to Larry. Here's a start:

Traction Software Introduces Social Enterprise Web - The TeamPage workplace spans external Sharepoint, Documentum, Exchange, Email and other Systems of Record using TeamPage Attivio Plus, bookmarking and content badging. Unlike some analysts and vendors, I believe the future workplace will be search and content coupled (just like the public Web) rather than exclusively activity stream coupled.

I see activity streams as a great alerting mechanism to help maintain situational awareness with respect to human centered or software events spanning many systems. But event awareness is no replacement for unified, permission-aware search combined with link, tag, task and comment capabilities spanning systems of record. That's what TeamPage delivers, enabled by Attivio's Active Intelligence Engine™ (AIE) technology.

The Future of Work Platforms: Like Jazz - When you watch a skilled team in action, it's like watching a great jazz group - there are themes, there is structure, and there are limits, but a team shines in individual excellence combined with coordination, improvisation, innovation, handling exceptions, and seemingly effortless awareness of where others are and where they're headed.

Intertwingled Work - The record of collaborative and observable work needs to span multiple external and internal systems to provide a simple and coherent view of activities

Traction Roots - Doug Engelbart - A dynamically evolving knowledge base ... [consists] of three primary knowledge domains: intelligence, dialog records, and knowledge products (in this example, the design and support documents for a complex product). ~ Doug Engelbart


See also Enterprise 2.0 Schism - Why Peter Drucker and Doug Engelbart should be the patron saints of Enterprise 2.0. And what to do with social media gurus and sinners.

Doug Engelbart | 85th Birthday Jan 30, 2010 - Irresistible quotes and references.

The Debate Zone: Has the US passed peak productivity growth? | McKinsey & Company

May 23, 2011 · · Posted by Greg Lloyd

ImageSee the lively McKinsey & Company What Matters debate, Tyler Cowen: "Yes. The big gains in the 20th century resulted from transformative innovations that are much rarer today." versus Andrew McAfee and Erik Brynjolfsson: "No. We’ve only just begun to reap the productivity benefits of digital technology." Read the analysis, lively comments, and jump in! My two cents (also posted as What Matters comment): I agree with Andrew McAfee and Erik Brynjolfsson's analysis that digital technology - including but not limited to the Web, communications and computer technology - is a GPT that "leads to fundamental changes in the production process of those using the new invention." and whose impact on productivity will be felt over decades, not years.

In a narrower domain of technology, Bill Buxton refers to this as "The Long Nose of Innovation" (link below)

Buxton cites a 2003 report presented by Butler Lampson to the Computer Science and Telecommunications Board of the National Research Council in Washington which traced the history of a number of key technologies driving the telecommunications and information technology sectors.

"The report analyzed each technology (time-sharing, client/server computing, LANs, relational databases, VLSI design, etc.) from first inception to the point where it turned into a billion dollar industry. What was consistent among virtually all the results was how long each took to move from inception to ubiquity. Twenty years of jumping around from university labs to corporate labs to products was typical. And 30 years, as with the mouse and RISC processors, was not at all unusual (and remember, this is the "fast-paced world of computers," where it is "almost impossible" to keep up)."

Buxton concludes: "Any technology that is going to have significant impact over the next 10 years is already at least 10 years old. That doesn't imply that the 10-year-old technologies we might draw from are mature or that we understand their implications; rather, just the basic concept is known, or knowable to those who care to look."

I believe that the fundamental value of the GPT we call the Web is as part of an interlocking set of communication and information technology capabilities organizations *can* employ to reduce the friction of knowledge work across space and over time, as well as fundamentally shift channels of marketing, sales, and distribution.

Assimilation and productive use of these new capabilities requires organizational change and innovation as profound as the technology driven changes of the Industrial Revolution. Steam, railroads and electricity fundamentally changed the economics of production of material goods - as well as introducing new media like radio and new travel and leisure markets.

I would not be surprised to find that the long nose of Enterprise 2.0 innovation enabled by this GPT (with a tip of my hat to Prof McAfee) spans 30 to 50 years.

The Long Nose of Innovation
Bill Buxton, Business Week, Jan 2, 2008

Image[Bloomberg BusinessWeek image] Bill Buxton is Principal Scientist at Microsoft Research and the author of Sketching User Experiences: Getting the Design Right and the Right Design. Previously, he was a researcher at Xerox PARC, a professor at the University of Toronto, and Chief Scientist of Alias Research and SGI Inc.

Enterprise 2.0 Schism
Greg Lloyd, Traction Software Inc, Nov 9, 2009

Zoom in to focus, zoom out for awareness, bubble up items in the flow of work

May 9, 2011 · · Posted by Greg Lloyd

ImageThere's been a lot of Web and Twitter discussion about the value of activity streams to promote broad awareness versus the potential problem of showing too much information and having important signals get lost in the flow. I believe that the best solution is to allow people to selectively zoom into activity streams, status and discussions - clipped by space, project, person or milestone - to focus on any particular activity in context. To focus more precisely, click a watch button to get notification when anything is added, changed, or discussed in a context you want to monitor carefully.

Traction TeamPage Release 5.2 adds mini-dashboards to make it simple to see status, activity, tasks, discussions and related articles or documents focused on a particular project or milestone, complete with sparkline diagrams to see at a glace what's happening over time. Each project, space, and person has an activity stream, making it simple to focus on what you care about - and shift your focus easily.

See Action Tracking with Tasks, Milestones, and Projects videos

You can also zoom out a broader view of all spaces you have permission to read, or people you choose to follow. This makes it easy to dip into the flow and read, search, or navigate by person, tag, task or discussion thread.

You can flip to your own profile to review and use the stream of your own activities, tasks, and calendar across all spaces and projects you have permission to see.

Flip to the profile of any other team member by clicking their name to review their activities, tasks, and calendar, limited to just what you have permission to read.

You can flag a post, project, tag, or space and receive an automatic notification (by email or Jabber) when a comment is added, edit is made, a specific tag is added (e.g. urgent) or other actions happen in the context of activities you want to watch closely. If you receive a notification by email, you can reply to that email and your comment is automatically added to the right discussion.

Because Traction TeamPage spaces carry access permissions, internal teams, customers, suppliers and other external stakeholders can freely tag, task, link and discuss anything they discover - even make more private comments on more public content.

Activity streams, search results, comments, email digests, notifications, and even tag clouds are automatically clipped to keep private activities private, but make everything you're allowed to see visible in context.

When you see something that looks important you can tag, task or comment on the relevant item to raise its visibility as an opportunity, an answer to an important question, or an issue to be addressed.

A TeamPage project creates a shared context where work actually gets done - with specific deliverables; as an open ended activity with a stream of actions and milestones; or as customer or client case to be tracked and guided to a desirable outcome. In each case, TeamPage's integrated action tracking makes it easy to recognize, track and handle exceptions or opportunities in the natural flow of work.

A TeamPage customer quoted in the Feb 2011 Deloitte Social Software for Business Performance study said:

"With Traction Software I can post meeting notes and assign action items to individuals. Then, they can go into the tool and write comments to update the group on the status of their action items as well as post deliverables. It greatly increases transparency and streamlines communications."


Literate Business and Euan Semple

May 4, 2011 · · Posted by Greg Lloyd

ImageEuan Semple's Literate Business post of May 4, 2011 is well worth reading. In preparing to write his book, Euan noted "There's something wrong with the names we use for social web tools in business... whether Enterprise 2.0, Social business or whatever."

"It occurred to me that what is significant about the tools we are seeing creeping into the business world is not so much that they are social as that they are literary in nature. They require, at whatever level, people to observe the world around them, make sense of it, and convey that sense to others, mostly, through the written word. All three parts of this process are the essence of good literature and they are all relatively unfamiliar in the business world. Most people don't pay much attention to what is going on around them, they don't sit and think much about what it means, and they are very unlikely to take the time to sit down and write about it. This is what blogging or tweeting makes easier. It also makes it collective."

I like Literate Business a lot. One advantage vs Enterprise 2.0, Web 2.0: the prior state is "illiterate" - which carries a lot of truth.

Literate implies, but does not strictly require an audience. The audience expects that they can come up to speed at any time by reading what the author has written in the past, as well as literate (curated) commentary, discussion and analysis. The value of the curated content grows over time. Evaluation of past decisions and analysis can even be changed in light of future experience! You might get better at what worked, avoid what failed, and let everyone learn from experience!

Literate also says much for the value of recorded narrative or observable work versus a business environment where decisions are made and good or bad inferences are drawn in near-real-time, with nothing preserved but ill formed and inconsistently remembered recollections of those present in the little room or on the call.

The only thing missing is collaborative creation of literature, which is not that common. But if you set the words to music I guess you could call it Business Jazz!


The Future of Work Platforms: Like Jazz
Enterprise 2.0 and Observable Work
Enterprise 2.0 Schism

Water Cooler ROI Part II - Project Networks Improve Performance

April 22, 2011 · · Posted by Jordan Frank

ImageIn Water Cooler ROI - Putting Social Software to Productive Work I pointed to some terrific research that uncovered the extent to which project work relies on communication (in various mediums) and how digital networks actual enhance productivity (with a 7% increase in one case). More fuel for the fire comes from Why Project Networks Beat Project Teams, a study published in the MIT Sloan Management Review last month.

In a review of 177 teams at one organization, the researchers discovered that the teams demonstrating the highest performance consistently reached out via personal network to more non-core contributors for assistance and knowledge. "Finalists" which were the best performing teams involved an average of 4.5 non-core contributors per core team member, whereas non-Finalists only involved 2.5 non-core contributors per team member. All other key factors such as resources, core team membership churn, and project change orders were equivalent.

This was not a study of teams that use social software or not - but the implication is clear: performance should increase for teams that use a social communication and knowledge management medium capable of (a) consistently sharing information with identified non-core members and even (b) extending visibility of that medium to a wider ring of individuals outside the personal networks of the core team members.

Need for Incentives, and other Innovation Myths

April 11, 2011 · · Posted by Jordan Frank

In our own Customer Forum, Rolf Isaksen (click here for blog's main page) recently asked: "Why do we need incentives to share?" Some of the follow-on conversation converged on "we don't" with some good pointer to experience and research supporting that premise. Rather, focusing on intrinsic motivation rather than rewards can net greater benefit and long lasting E2.0 success.

Brian Tullis referred to the way in which conducting work activity in a visible E2.0 environment leads to motivation and ultimately high performance:

Activities -> Visibility -> Connections -> Purpose -> Motivation -> Engagement -> High Performance

This, and supporting research he points to by Adam Grant (which comes via Daniel Pink) are referenced in Brian's blog post "Whats the Vis." In simple terms - consider whether the motivation individuals harness by seeing the results of their work. Without "observable work" there is no way to connect one's own actions with the results (positive or negative) that they have on the organization. Sales systems may tell us who is closing business, issue management systems may tell us who closes the most customer support issues and how quickly, and observable work in collaborative social software systems may tell us who is contributing to the work process, idea flow, and problem discussion and resolution. By omission, social software systems can also tell us who is not involved.

Yes, there are all kinds of incentives built into a work process built on social software - but not the kind of "dollars for ideas" incentives that fail.

The Grant research concludes: "Three field experiments with fundraising callers and lifeguards suggest that mere exposure to task significance cues can enhance job performance by fostering a deeper understanding of the social impact and social value of one’s work." There are many ways to provide feedback about task significance in terms of sales results and customer satisfaction, but few so direct as the flow of communication when you engage in observable work patterns where you can gain a sense for your own ripple effect in an overall activity stream.

The 5 Myths of Innovation published in the December 2010 MIT Sloan Management Review by authors By Julian Birkinshaw, Cyril Bouquet and J.-L. Barsoux adds more fuel to the fire for intrinsic motivation. They identified the following 5 myths:

  1. The Eureka Moment
  2. Built it and They will Come
  3. Open Innovation is the Future
  4. Pay is Paramount
  5. Bottom-Up Innovation is Best (see our various thoughts on bottom-up approaches)

For the scope of this line of thinking on Incentives, the Pay is Paramount myth was especially revealing. The authors state:

Extrinsic rewards such as money are usually secondary, hygiene-type factors. The more powerful motivators are typically "social" factors, such as the recognition and status that is conferred on those who do well, and "personal" factors such as the intrinsic pleasure that some work affords." They add "psychology research that individuals view the offer of reward for an enjoyable task as an attempt to control their behavior, which hence undermines the intrinsic task interest and creative performance."

So, do we need incentives? Certainly not, at least if you an incentive is dollar and action/response based. Incentives are desperately needed in the form of systems where the "can-know" audience can observe the work done by individuals, where participation is appreciated in an outright way, and possible and actual outcomes are communicated to individuals during the course of work and after it's actual impact has occurred.

I won a ticket to Google I/O!

April 11, 2011 · · Posted by Andy Keller

We've been using the Google Web Toolkit (GWT) for about 2 years and have also gone to the past 2 years of Google I/O. It's been a fun and useful conference and there was no question we were going to go again this year.

I had been watching @googleio on Twitter and was ready to buy tickets when they were available. The day they went on sale I was traveling to Providence, RI to do a week of product design and strategic planning with the rest of the Traction team. While I was in the air, tickets for Google I/O sold out in 59 minutes.

A few weeks ago, Google announced Last Call for Google I/O, a series of developer challenges that would award 100 developers a ticket to Google I/O. One of those challenges involved creating a countdown timer using GWT and my submission was one of the 10 winners chosen.


See my countdown timer live

The implementation is simple but uses some novel techniques that only work in modern browsers.

Here are the pieces that make this countdown timer work:

Google Web Toolkit (GWT)

GWT compiles Java into JavaScript. I use it to create a timer that, every second, computes the time remaining for the countdown and adjusts the CSS class value for the digit elements. The markup is pretty simple and here's what you see if you inspect it the digits:


The first class on the digit lets the background color of the digits be styled independently. The second class corresponds to the value of the digit.

CSS3 Transitions

Instead of doing the animation in GWT, I wanted to use CSS3 Transitions to let the browser take care of the animation. CSS3 Transitions are incredibly simple and powerful. I use SASS and Compass to write all of my CSS and here's what that looks like:


+transition is a Compass mixin that creates all the CSS3 transition rules for browsers that support it and +replace-text will replace text with an image with a specified background position. If you inspect a digit, you can see the CSS that Compass generates and maybe appreciate why we love SASS and Compass. It's the GWT of CSS.


CSS3 Transitions are really simple. When the class on an element changes, instead of rendering the new styles immediately, the two transition rules say to animate the background-position change over 0.3s. This is why the digits appear to slide in as they change.

24-bit Transparency in PNG

The individual digits are rendered using the same single image, digits.png. The image has a white foreground and transparent numbers. This means that any background behind the image will show through. You'll notice that the numbers have nice rounded corners. They are anti-aliased which is possible because 24-bit PNGs have a full 8-bits (256 values) of transparency.

In the 4 hours I spent on this implementation, I think an hour was spent creating that image. I know emacs better than Photoshop and pasting into a layer mask is a non-obvious process.

The source code is available at if you'd like to explore it.

Hope to see you at Google I/O this year!

-Andy (@pulazzo)

Deloitte and Sampson: Focus on process, the "why" not the "what", for social software

March 22, 2011 · · Posted by Jordan Frank

I found a common thread on process centric adoption in the Deloitte Center for the Edge's Social Software for Business Performance report and Michael Sampson's User Adoption Strategies book. This advice is reflected in my post on Emergineering from last fall.

The Deloitte study focuses heavily on a Traction TeamPage deployment at Alcoa where the study highlights a 61% reduction in hours spent on compliance activities in IT project management. Separately, Alcoa reports substantial performance increases in terms of time savings of over 100 hours per week in an IT implementation that was completed in 7 rather than an expected 18 months. It also highlights Traction TeamPage customer Ensign-Bickford where a process around Tooling Requests that created an continuous feedback loop, reduced re-work and reduced overtime hours from 10 to 1 (or less) per week.

In their analysis, Deloitte says meaningful performance improvement is achievable:

The experiences of Alcoa and OSIsoft prove that social software can achieve meaningful improvements. How did they succeed where so many others did not? Both Alcoa and OSIsoft employed a simple tactic: they avoided focusing on adoption. Rather, they identified specific operational pain points in the business that social software could address. By focusing on something tangible, broadly relevant and widely acknowledged as a problem, they overcame initial skepticism.

Sampson's book is another great reference point on adoption. He takes special care to focus on second wave people.

What-why reversal. A first wave person is attracted to the "what" of the new collaboration technology, but may struggle to articulate the "why" -- the future oriented picture -- to other people. They may "get it" implicitly, but struggle to put it into words. A second wave person gets the "why" (if it's conveyed in terms of their work), but will need help with the "what." (Page 30)

Later on, Sampson uses my quote to lead off Chapter 9 - Making it Real:

The deployments I have seen succeed the fastest and become the most enduring are those that are built under the backdrop of a defined work process that is better conducted wiki or blog-style than in email, Notes, SharePoint or whatever the alternative. Patterns emerge within these deployments that change their nature and branch into new uses of the technology -- but leveraging the core process (or processes) is vital to gaining high participation and sustained user attention.

When you focus on the "why," people stop looking at the platform as a "blog" or "social" system but rather as a work-process system. They take it more seriously and part of their daily work, rather than a destination to only enjoy and engage in when they have a (very rare) free cycle. The patterns that take over become hardened and information infrastructure starts to take root. It's this infrastructure, whether its the history of issue / exception process focused discussions or documentation and later execution of compliance test plans, that creates a pattern on which new use cases can emerge, and enables a substantial Return on Information.

March 11 - Vannevar Bush's Birthday

March 11, 2011 · · Posted by Greg Lloyd

ImageThe Computer History Museum's This Day In History March 11 reminded me that today is the birthday of Vannevar Bush (born March 11, 1890), a distinguished educator, engineer, Vice President and Dean of MIT, and President of the Carnegie Institution. As World War II Director of the Office of Scientific Research and Development, Bush managed all US wartime research, reporting directly to President Franklin Delano Roosevelt. After the War he was instrumental in creation of the National Science Foundation based on a 1944 request from FDR. Bush is also known as the author of a famous July 1945 Atlantic Monthly essay As We May Think, where he described a possible "new relationship between the thinking man and the sum of our knowledge" including the Memex - a literary machine which inspired the invention of hypertext twenty years later - and indirectly lead to creation of the Web. See the video archive of the MIT / Brown Vannevar Bush Symposium on the 50th Anniversary of As We May Think for a great collection of talks by Doug Engelbart, Ted Nelson, Andy van Dam, Tim Berners-Lee, Alan Kay, and others inspired by Bush and and his work.


Visit the Computer History Museum in Mountain View California or on the Web.


The Future of Work Platforms: Like Jazz

February 16, 2011 · · Posted by Greg Lloyd

ImageYesterday I read GigaOM analyst and editor Haydn Shaughnessy's Future of Work Platforms report (registration required, free seven day trial available). I commented: Haydn -- A very thoughtful and useful analysis – a combination that’s all too rare! I’m particularly happy to see your thoughts on observable work (see the full report for Haydn's excellent analysis).

Ever since Jon Udell coined the term, it struck me as good way to talk about practical benefits and a business purpose for collaboration. In my opinion it helps by pealing back issues of privacy in context and activity streams, along with subtleties required to support the social dance of getting things done, dealing with exceptions, and staying aware of what’s going around you without getting swamped. This is much closer to jazz than the world of canned business transactions. It requires a level of attention to ease of use and user experience that’s just as important but in many ways more challenging to do well in a business context than for the public Web.

I also thank you for your careful analysis and kind words about Traction Software.

I've thought a lot about how to describe the relationship between Observable Work and the style of action tracking, coordination and agile project management used by TeamPage customers like Brian Tullis and Joe Crumpler, as well Traction Software folk. When you watch a skilled team in action, it's like watching a great jazz group - there are themes, there is structure, and there are limits, but a team shines in individual excellence combined with coordination, improvisation, innovation, handling exceptions, and seemingly effortless awareness of where others are and where they're headed.

Traction TeamPage 5.1 aims to support this performance model. Bill Ives captures the idea well: "The action tracking concept is not old school project management with Gantt charts and resource allocation. It is allowing employees to manage their work tasks and make this management transparent to those who need to know...This is the action tracking part of project management for the regular employee, not the program management office. It brings this activity into the enterprise 2.0 world as every task is treated as an object for comments, RSS, and made searchable to those with the proper permissions."

Every business activity involves some measure of action planning and tracking. People have lived with action tracking systems that range from a list on the back of an envelope, to getting things done style planning, to multilevel project plans for large and complex products like aircraft.

The TeamPage 5.1 action tracking model focuses on making it simple for individuals and teams to plan and coordinate the daily, weekly and monthly activities that drive effective teamwork. This level of coordination can quickly become too complex for the simplest systems, but too detailed – and close to real life – to be effectively modeled, tracked and managed in real time using software designed solely for top down project modeling and planning.

In my opinion, the big difference is action tracking built in to the natural flow of work. This makes daily life easier rather than more complicated.

  • Collect individual tasks into projects to make summaries easy to report up, and top down progress easy to track by project or by individual.
  • Tag any paragraph as a task and later dive down by person, task, project or milestone to make personal tracking and maintaining awareness much easier.
  • Click a name and link to a colleague's profile to see tasks, activity and status from their perspective.
  • Pop a quick question into a status window to make communication quick, effective and observable.
  • Add a comment to a task (status message, page, post or paragraph) to raise an issue or suggest a solution, to make exceptions much easier to recognize and handle.

All of this works with TeamPage's advanced search, notification, and a collaboration model that puts tasks, status, conversations and posts in a business context, organizing communication by space for those who have permission to read, while using spaces to protect all content in client, partner or internal spaces that require privacy.

Watch the video to see what I mean.

I've worked for the US Naval Research Lab managing parts of very big projects for the US Navy, and as a member of small startup teams. I believe that at the working level the same model supports effective teamwork where bottom up activities meet top down plans as the foundation of projects of any size.

We're seeing first results from TeamPage customers and Traction Software using TeamPage 5.1 integrated action tracking and the response has been great. Look for updates here, on Twitter, or join the TeamPage Forum and the live conversation - or to should I say jam? (to borrow a great term from IBM).


Applied Knowledge Co Ltd - Bringing Traction TeamPage 5.1 to Japan

January 21, 2011 · · Posted by Greg Lloyd

ImageOur long-time Japanese reseller partner Applied Knowledge Co Ltd has done a great job bringing Traction TeamPage to the Japanese market. They are an excellent sales and consulting partner for Japanese market customers. AKJ also has deep experience applying Enterprise 2.0 principles, the Traction TeamPage SDK, Japanese Language localization of the TeamPage interface, and Japanese advanced linguistics and faceted navigation capabilities of Traction's Attivio powered Advanced Search.

I'm proud and happy to point to AKJ's excellent Japanese Traction TeamPage Release 5.1 examples posted on I thank our friends at AKJ for bringing the full set of TeamPage 5.1 action tracking, integrated status, profiles, Attivio advanced search features and Proteus user interface to the Japanese market so quickly and professionally.

Here are few links to Japanese Traction TeamPage 5.1 examples and screenshots. You can use Google Translate or other tools to browse in English or other languages.

Traction TeamPage 5.1 Introduction (Japanese)

Status and following model of Traction TeamPage 5.1 (Japanese)

Using TeamPage status updates - mobile, laptop, desktop (Japanese)


Task and Action Tracking in TeamPage 5.1 (Japanese)

Traction's Attivio Powered TeamPage Advanced Search (Japanese)

See also 14 Dec 2010 | - プロジェクトの円滑な遂行をサポートする「TeamPage 5.1」 アプライドナレッジ、コラボレーションツールの新版を発表

Traction TeamPage 5.1: Social Software, Meet Project Management

December 2010 | Gilbane Conference - Portal vs. Enterprise Social Software Panel

January 18, 2011 · · Posted by Jordan Frank

Jordan Frank writes: At the Gilbane Conference last month I stood in for Greg Lloyd in the Portal or Enterprise Social Software: Which Collaboration Environment to Choose? panel with David Seuss (CEO, Northern Light) and Jay Batson (Co-Founder and VP, Acquia).

I started my talk off with emphasis by asking Why Does Enterprise Search Suck? Then I elaborated on why the social intranet, built on the basis of links and pages, can work with good search such as our TeamPage Attivio® Search Module to deliver an intranet that works. In cases, social software may be used for a given use case (e.g. project management) or it may serve as the backbone for the intranet as well.

The tail end of the talk offers examples of each case deployed at customer scenarios at Kuka Systems, Alcoa, Athens Group, Borlaug Global Rust Initiative, National Health Service and a Global Pharma.

The full set of slides is available here at SlideShare:

Doug Engelbart's copy of As We May Think - with Doug's 1962 notes scribbled in the margins

January 6, 2011 · · Posted by Greg Lloyd

The Doug Engelbart Foundation's 1995 Vannevar Bush Symposium video archive page includes a section on Bush's influence on Doug's work, including his copy of Bush's As We May Think with Doug's 1962 notes in the margins (pdf). Talk about deeply intertwingled living history. Per a note in the .pdf, the original hardcopy has apparently been donated to the Computer History Museum. Look for this paper when the Computer History Museum's Revolution - The First 2000 Years of Computing exhibit opens in Mountain View CA - and online on 13 Jan 2011.

Update Remembering Doug Engelbart, 30 January 1925 - 2 July 2013


Doug Engelbart | 85th Birthday Jan 30, 2010

Could I interest you in a Memex?

The Evolution of Personal Knowledge Management

Good Titles/Headlines are Good Practice

November 19, 2010 · · Posted by Jordan Frank

In my role as an emergineer, I talk a lot about best practices and how they can be leveraged in a given customer deployment. One practice that works in any sphere from email to social software and journalism is to write a good headline.

At the Traction User Group meeting in October, Jon Udell talked, in part, about Heds, Deks and Ledes (words used to mean Heads, Decks, and Leads but intentionally mis-spelled so they are not mistaken for content in a news room). He followed the conference, intentionally or not, with a blog post of the same title: Heds, Deks and Ledes.

Jon says: "We're all publishers now in one way or another. None of us can predict the contexts in which what we publish will be found. But if we're careful about writing heads, decks, and leads, we'll improve the odds that it will be found."

He talks through how this applies whether you are writing an email message or a blog post, then really brings it home in a Facebook example where when you post an event "Heds will always be visible to a scan or a search; decks and leads are active in far fewer contexts."

So, his recommendation for posting an event in Facebook is to pack the Hed of an event with the event title, location and date.

Email is a little more forgiving on Search, but when looking at email, we always start by scanning a list of titles (Heds). When scanning its crucial to understand, from a title, if a message is relevant to you and what dates it applies to (if its an event or deadline notice).

In a blog post or wiki page, similar rules apply. You also have to consider that search ranking may be influenced by word order, word proximity and exact matching (all factors in our Attivio Search Module). When writing a title for a wiki page you also have to consider the naming schema for the rest of the wiki. As a result, there may be advantages to being concise in the head, leaving the deck and lead to explain further.

The happy medium, as Jon indicate, depends on where you are publishing, how its viewed and how its searched.

TUG 2010 Newport | Thank you!

October 15, 2010 · · Posted by Greg Lloyd

ImageTUG 2010 Newport just wrapped up after four busy and enjoyable days. It's hard to express how grateful I am to the customers, partners, friends - and the Traction Software team - who made this such an enjoyable event. First I'd like to thank keynote speakers Jim McGee, Chris Nuzum, Jon Udell as well as customers, friends and partners whose thoughtful talks and enthusiasm made Wednesday's sessions so rewarding.

Jon Udell cheerfully and skillfully moderated Thursday morning's Observable Workshop in an unconference spirit when I asked for the benefit of his advice and experience with no advance notice - thank you Jon!

Thanks to Jordan Frank, Kellen Roach and everyone on Traction Software's exceptional team for making every training, product and developer session sing, and for their consistent dedication to make every customer happy and successful. Special thanks to Chris Nuzum, Andy Keller, Dave Shepperton, and Roger Fujii for the leadership, hard work, dedication and talent that brought TeamPage 5.0 to customers earlier this year, and for the awesome new task and project management capabilities they demonstrated at TUG which we'll announce at E2.0 Santa Clara this November.

For more, see

Fixing Enterprise Search

September 4, 2010 · · Posted by Greg Lloyd

ImageA few days ago the Enterprise 2.0 Blog published Venkatesh Rao's excellent post The Real Reasons Enterprise Search is Broken. When he hears ironic jokes comparing search on the public Web versus internal enterprise search, Venkatesh notes: "People move on because they seem to think that this is incompetence at work. Search is soo 1.0 right? It's been solved and we're just fumbling the execution, right?" He says: "I have reached a radical conclusion: broken search is the problem, but fixing search is not the solution. Search breaks behind the firewall for social, not technical reasons... Let's start with the blindingly obvious, and then draw some weird conclusions." I think they are perceptive conclusions based on sound analysis, and agree with most, but come at the problem from a different angle.

I strongly agree with Venkatesh's main conclusion: "The fundamental social and information flow assumptions of “search” need to be deconstructed and reconstructed for the enterprise. Local/silo search within single sites/assets is fine. Enterprise-wide search in its naive form is a terrible idea."

I agree that flat and dumb enterprise-wide search is broken for the reasons he points out. The principles that make relevance ranked search work well on the public Web fail miserably in the link-poor, (relatively) small scale, cc spammed, siloed and obscurely hidden environment behind the firewall in most companies.

I agree that "Web 1.0" technology can't address problems of redundant attachments, email hairballs, point-to-point back channel communication that's not even indexed, let alone officialese used to send timed and coded signals the clear! [ I think Venkatesh just outed enterprise steganography. Cool! ]

A few years ago I wrote a note based on similar customer disappointment with enterprise search versus what they saw on the public Web and came to conclusion that the Web 2.0 / Enterprise 2.0 layer over the Web 1.0 layer offers hope for technology-based improvement:

1) Make business context manifest for discovery and search: This means the ability to create spaces that frame natural business context.

A space defines a context for documents, blog posts, wiki pages, status, what we now call activity stream items and more. A space can also carry permission to see or use content within that space - or know that the space exists.

For example a space "Board of Directors" or "Medical Records" may have more restrictive access that a space "Engineering". Although there are good reasons for making spaces as transparent to as many people as possible, a client facing space in a law firm would need to have permission limited to that client and members of the firm - reliably excluding other clients.

Likewise a space in which private medical issues are analyzed and discussed would need to be more private than most other spaces, but provides a perfectly transparent named context for search, faceted navigation and discovery, tagging, activity stream aggregation, or automatic notification - for those with appropriate permission.

A space provides context and can carry permissions, both of which are important for discovery, tagging, navigation, search, and cross-boundary discussions spanning as many spaces as an individual has permission to see (see Borders, Spaces and Places).

2) Searching across business systems is not the major problem. Enterprise search engines such as Attivio do a great job searching across multiple enterprise business systems. An MRP system, Accounting system, CAD/CAE repository may be a "silo", but it's a silo with a well defined purpose that functions like a "bounding space" by providing context that an enterprise search engine can map and use.

For example, searching for a part number might return hits in MRP, Accounting, and CAD/CAE design databases. These different sources can be modeled as facets, which makes it pretty easy to choose from among MRP, Accounting or CAD/CAE hits when you enter a part number depending on content: Are your interested in manufacturing, accounting, or design related part information?

In my opinion, the real problem pops up when you have one, two or a myriad of generic Content Management Systems or email repositories that are used as general purpose buckets where data and documents are dumped:

  • Without a bit of context (think of the Ark at the end of Raiders of the Lost Ark)
  • Without hope of making stored content discoverable and linkable.
  • With redundant copies of email conversations and attachments scattered over tens, hundreds or thousands of email accounts and email servers

I don't know a technical solution that disentagles this mess once it has been created. The context was never recorded or was destroyed when it was stored.

Doing a content search for "Acme Briefing" and finding thousands of hits in redundant copies of different versions of the same .ppt attached to email that has been cc:'d and re:'d to death for months is very discouraging.

Intelligent indexing of context as well as content in an Enterprise 2.0 system such as Traction TeamPage solves the nasty problem of correlating messy human details that people rely on beyond the neatly ordered world of functionally siloed business systems. I realize "Neatly ordered" business systems is a relative. A part number is a lot less ambiguous than "a really big contract problem with important customer" when you're trying to discover something.

The answer to a messily human search for "what's the contract problem" is likely to be found in the Enterprise 2.0 record of work, conversation, tagging and tracking by finding either the answer or people who know the answer (and who are now a click away)

I believe that the transactions and content in functionally siloed business systems should be observable and addressable using standard Web protocols (with appropriate identity and security to allow transparent linking). It would also be best to avoid creating separate social silos that act as walled gardens embedded within each business system, see Intertwingled Work.

3) Make "who links to what and who talks to whom about what" indexable for search and discovery. Indexing author, date, space and other metadata as well as content associated with links and attachments adds valuable context for facet content navigation, discovery and search.

When Mr. Dithers shouts: "Bumstead! Where are we on the Acme Account?", the most timely, frequently discussed and contextually relevant version of Dagwood's slide set could pop closer to the top of the result list, along with the cloud of tags and people who have touched or talked about that account (see Why Enterprise Search Sucks).

4) Be clear what you mean by Enterprise Search. No technology or search engine will be able to find its way through the twisty maze of social relationships and pathological behavior that people can use to hide information that they want to keep private and off the record. The only exception is the technology proposed by Prof Germain Gervais in his Green Chameleon video.

What if you really want the inside scoop on what's happening with the Acme Account?

4a) Use the social network. Find someone in the know and ask them. Enterprise social networking can be a lifesaver when the big barrier is finding something which wants to be widely know in the company but is hidden by an infrastructure that sucks. If what you want to know is the unofficial word (often the truth), find people in the know who are part of a network of trust. If you're been in the military, you'd ask a trusted Sergent or Chief who's well connected in the NCO network.

4b) Hire a private detective. It take human intelligence and experience to find something that doesn't want to be widely known in the company (even if it should be widely known by policy). You could also become a whistle blower and get professional investigators on the case if the issue is really serious.

4c) Find a better place to work. If your just plain frustrated with an inability to find what you need to get your job done and feel happy about it, rise to a position of power and fix it, or find a job in an organization that's not so damaged.


For an example of how Traction TeamPage handles boundary aware navigation, tagging and search, see TeamPage Attivio® Search Module and Michael Sampson's Currents: "TeamPage - the One System to Rule It All".

Work you can see x Who you know = What you can do

August 24, 2010 · · Posted by Greg Lloyd

Work you can see x Who you know = What you can do
With thanks to Jessica Hagy
Who created her great This is what 2.0 means drawing on Aug 14, 2010.


Enterprise 2.0 and Observable Work

Intertwingled Work

The Future of Work Platforms: Like Jazz

29 July 2010 | Enterprise 2.0 and Observable Work: Brian Tullis and Joe Crumpler, Burton Group Catalyst 2010 Santa Diego

July 29, 2010 · · Posted by Greg Lloyd

Brian Tullis and Joe Crumpler did a lively talk on Enterprise 2.0 and Observable Work at the Burton Group Catalyst 2010 North America conference in San Diego. For those of us who couldn't be there in person, see their Abstract quoted below and the enthusiastic Twitter stream from 29 Jul 2010! I'll add a link to their speaker notes and slides when they become available. Update: Brian posted Enterprise 2.0 and Observable work slides and speaker notes. For slides see inline Slideshare below. Sounded like a super session!

Abstract: Most large organizations face huge challenges in staying aligned, knowing when and how to collaborate, and capturing knowledge for future use. Traction TeamPage has allowed a large virtual team at Alcoa Fastening Systems to implement principles of “Observable Work” – which for us means making visible and transparent the normally arcane processes of Information Technology management. Implementation of observable work practices has increased alignment, collaboration, and knowledge capture in the organization. Topics discussed include:

• What is Observable Work and why is it important?
• Overview of techniques used to manage the flow of information.
• Examination of a successful multi-country ERP project managed with these tools and techniques.
• Areas of improvement and where we go from here.

See also Enterprise 2.0 and Observable work slides and speaker notes
Brian's blog post Observable Work: The Taming of the Flow
Jim McGee's original blog post
Followup discussion and links on Jim's post

Observable Work session Twitter feed

Image movito @panklam's term "OpenWork" and the just-coined "Observable Work" are more focused & precise. #owork holds far greater potential than #e20. via Tweetie for Mac

Image PhilippBohn RT @gialyons Loving the concept of Observable Work. hashtag is #OWork #cat10 <-- me2 via CoTweet

Image movito RT @gialyons Break out of proprietary doc formats, and use addressable hypertext (URLs) ← it's the best way forward #cat10 #alcoa #owork via Tweetie for Mac

Image movito RT @MikeGotta Observable work: make status of work visible and avoid needless "status meetings" - status available to all that care #owork via Tweetie for Mac

Fredrik Mathesonmovito RT @MikeGotta Observable work principles applied to project freed up 30% labor due to reduced meetings #cat10 #owork #socbiz via Tweetie for Mac

Gia Lyons gialyons Really great content here at Burton Group Catalyst Conference, esp. in the Social Means Business track. #cat10 via Seesmic

Gia Lyons gialyons Hey @Greg2dot0, @joecrumpler just presented about how Alcoa saved 100 hours by using #socbiz for project status updates. #OWork #cat10 via Seesmic

Gia Lyons gialyons Loving the concept of Observable Work. hashtag is #OWork #cat10 via Seesmic

Andy Wang aewang “@scottylogan: @joecrumpler @briantullis great presentation on observable work #cat10 #OWork” totally agree via Twitter for iPhone

Gia Lyons gialyons Most excellent prezzy from @joecrumpler @briantullis at #Alcoa #cat10 via Seesmic

Scotty Logan scottylogan @joecrumpler @briantullis great presentation on observable work #cat10 #OWork via YoruFukurou

Mike Gotta MikeGotta RT @gialyons: Traditional daily status process: 4hrs, 3 times/wk w/10 ppl=loss of 120 hrs of project labor, new process saves 100 hrs #cat10 via TweetDeck

Catalyst Tweet catatweet RT @gialyons Traditional process took 4hrs, 3 times/wk w/10 ppl=loss of 120 hrs of project labor. New #socbiz process saves #cat10. WOW!!! via Twittelator in reply to gialyons

Michael Rollings mikerollings "observable work" - anybody that ever experienced "death by meetings" would appreciate this approach #cat10 via Echofon

Andy Wang aewang Awesome presentation by the Aloca guys on E2.0 and Observable Work #cat10 via Twitterrific

Gia Lyons gialyons Project mgr throws an "explosion of information hand grenade" via #socbiz for others who care. Like mgrs. #alcoa #cat10 via Seesmic

Michael Rollings mikerollings "Observable work" reduces project status meetings because issues and accomplishments are transparent to team members as they occur #cat10 via Echofon

Dustin Updyke dustinupdyke Can I take @JoeCrumpler to work on Monday to clear our path of pointless meetings? #cat10 via TweetDeck

Larry Cannell lcannell Observable work also enables better focused meetings (not just reduces them), more productive use of (expensive) F2F time #cat10 via TweetDeck

Gia Lyons gialyons Traditional daily status process took 4hrs, 3 times/wk w/10 ppl=loss of 120 hrs of project labor. New #socbiz process saves 100 hrs. #cat10 via Seesmic

Mike Gotta MikeGotta Observable work principals applied to project freed up 30% labor due to reduced meetings #cat10 via TweetDeck

Catalyst Tweet catatweet Status as you work. #cat10. Reduce meetings. 30% increase in actual work. The result of observable work is reduced need for meetings. via Twittelator

Gia Lyons gialyons Reduce meetings is a result of observable work using #socbiz software; got 30% more labor out of teams, too. #cat10 #alcoa via Seesmic

Scotty Logan scottylogan reducing number of meetings led to a 30% increase in actual work #cat10 via YoruFukurou

Catalyst Tweet catatweet Manage content streams, read, and remain aware. #cat10. A key objective of the observable work principle. via Twittelator

Jason Keath jakrose @gialyons amen #cat10 #alcoa via TweetDeck in reply to gialyons

Mike Gotta MikeGotta "Status as you work" ... whether status telegraphs positive or negative news - all visible, transparent - and "observable" #cat10 via TweetDeck

Catalyst Tweet catatweet Use #social technology to have LESS MEETINGS by leveraging the status reporting inherent in the technology. #cat10 via Twittelator

Michael Rollings mikerollings Principle: achieve status from observable work #cat10 words to live by via Echofon

Gia Lyons gialyons Heh. sitting next to a fellow former Certified Lotus Instructor (CLI) #cat10 #bleedyellowstilljustalittle via Seesmic

Andy Wang aewang RT @MikeGotta Observable work: make status of work visible and avoid needless "status meetings" - status available to all that care #cat10 via Twitterrific

Scotty Logan scottylogan terrifying slide of kid with circular saw! #cat10 via YoruFukurou

Eric Ziegler ericzigus funny pictures in #alcoa presentation #cat10 via Touiteur

Andy Wang aewang RT @MikeGotta Concept of "observable work" a new way to operate at Alcoa Fasteners #cat10 great concept via Twitterrific

Scotty Logan scottylogan Alcoa guys: Use addressable hypertext rather than (proprietary) documents #cat10 via YoruFukurou

Mike Gotta MikeGotta Alcoa took a project that normally takes up to 18 months in 7 months #cat10 (QAD implementation in China using Traction TeamPage) via TweetDeck

Gia Lyons gialyons "here's a piece of content, please comment, we'll change content based on what you say, let you know when it's changed." #cat10 #alcoa 41 minutes ago via Seesmic

Gia Lyons gialyons Break out of proprietary doc formats, and use addressable hypertext (URLs) #cat10 #alcoa via Seesmic

Mike Gotta MikeGotta Observable work: make status of work visible and avoid needless "status meetings" - status available to all that care #cat10 via TweetDeck

Dustin Updyke dustinupdyke Doing the work in an observable way eliminates the need for status metings #cat10 via TweetDeck

Catalyst Tweet catatweet Meetings suck! One outcome of observal work is that status is apparent to anyone that needs it #cat10 via Twittelator

Gia Lyons gialyons Do your work in an observable way (via #socbiz), and others will see it, make mental connections b/n theirs and yours. #cat10 #Alcoa via Seesmic

Scotty Logan scottylogan Alcoa don't like meetings - observable work reduces the need for meetings #cat10 via YoruFukurou

mikelor mikelor Make people realize that they are inside a ecosystem, encourage clickable and linkable content. #cat10 via TweetDeck

Gia Lyons gialyons People need to know how what they do is linked to what others do in the company #cat10 #alcoa via Seesmic

Bryant Duhon bduhon RT @gialyons: If you create a community of trust, they'll be comfy working together outside of hierarchy #cat10 via HootSuite

Catalyst Tweet catatweet Authority to update content - don't worry about it. The right thing will happen. #cat10 #OWork via Twittelator

Jamie Lewis jamiemlewis That's the goal. Glad to hear it's working. ;-) RT @JBrodkin: Great tech content at #cat10. Very little marketing BS. via TweetDeck

Gia Lyons gialyons Need to interject social in what you do, especially if you're in IT. #alcoa #cat10 via Seesmic

Mike Gotta MikeGotta Sign of an unhealthy culture is a mindset that thinks they "we" have to survive encounters with "them" (insiders vs. outsiders) #cat10 via TweetDeck

Catalyst Tweet catatweet Collaboration requires trust. The battle plan rarely survives contact with the enemy (users) ;-) #cat10 via Twittelator

Gia Lyons gialyons Being introverted IT guys, we love to close the doors and focus on transaction work. #cat10 #alcoa via Seesmic

Handslive handslive #cat10 HR needs to be aware of the impact of the changes they make. OMG yes. via Twitter for iPhone

Gia Lyons gialyons If you create a community of trust, they'll be comfy working together outside of hierarchy #cat10 via Seesmic

Gia Lyons gialyons Oh, this is shaping up to be a fun and informative preso. #Alcoa #cat10 via Seesmic

Nishant Kaushik NishantK IMO, if more business processes were structured like a game, more stuff would get done way more efficiently #cat10 via TweetDeck

Dustin Updyke dustinupdyke "the battle plan rarely survives first contact with the enemy" #cat10 via TweetDeck

Gia Lyons gialyons ... which leads to better performing team and company. #cat10 via Seesmic

Catalyst Tweet catatweet Why observable work is important. Common aps and processes, within a world of compliance and accountability - we can control work! #cat10 via Twittelator

Gia Lyons gialyons Alcoa hypothesis: Implementing observable work PRINICPLES through enabling TECH creates stronger connections w/customers & colleagues #cat10 via Seesmic

Gia Lyons gialyons Alcoa makes fasteners that go on large things. Like airliners, trucks, etc. #cat10 via Seesmic

Gia Lyons gialyons Alcoa is up now. #cat10 Brian Tullis, Joe Crumpler presenting via Seesmic

Catalyst Tweet catatweet Observable work principles in the realm of #social presented by Alcoa here at #cat10 via Twittelator

Mike Gotta MikeGotta Concept of "observable work" a new way to operate at Alcoa Fasteners #cat10 via TweetDeck

Eric Ziegler ericzigus standard disclaimer from #Alcoa about ideas are their personal ideas not of their companies #cat10 via TweetDeck

Image roundtrip "Enterprise 2.0 and Observable Work" @BrianTullis and @JoeCrumpler session @ #cat10 11:50am PDT #OWork #E20 via Osfoora for iPhone


Intertwingled Work

July 5, 2010 · · Posted by Greg Lloyd

Image Last week's post by Jim McGee Managing the visibility of knowledge work kicked off a nice conversation on Observable Work (using a term introduced by Jon Udell) including: my blog post expanding on a comment I wrote on Jim's post; Brian Tullis's Observable Work: The Taming of the Flow based on a comment Brian made on Jim's post, which he found from a Twitter update by @jmcgee retweeted by @roundtrip; a Twitter conversation using the hash tag #OWork (for "Observable Work"); John Tropea's comment back to Jim from a link in a comment I left on John's Ambient Awareness is the new normal post; Jim's Observable work - more on knowledge work visibility (#owork), linking back to Mary Abraham's TMI post and Jack Vinson's Invisible Work - spray paint needed post, both written in response to Jim's original post; followed by Jack Vinson's Explicit work (#owork) and Paula Thornton's Enterprise 2.0 Infrastructure for Synchronicity.

That's a bunch of links! But I include them for a reason. [ For anyone who finds the presence of inline links distracting, see Apology to the Easily Distracted, below. ]

This modest trail is not only observable - it's spread over about a dozen posts on eight unrelated blog servers using unrelated software, loosely coupled by conversations, links and hash tags observable in the Web commons known as Twitter. The only things that connect this trail are links, search, syndicated feeds and serendipity. In the words of Ted Nelson this is an intertwingled trail - although not very deeply intertwingled, and not that easy to follow.

That brings three points to mind:

1) The fact that "intertwingle" is an amusing word can obscure an important idea I believe Ted Nelson is a Casandra-like inventor blessed and cursed with a rapier wit and the ability to invent concepts and coin terms that stick deeply in peoples minds. Hypertext one of the terms Ted coined and concepts he invented - working independently from Doug Engelbart at about the same time - inspired by the work of Vannevar Bush.

One of Ted's mantras: "EVERYTHING IS DEEPLY INTERTWINGLED. In an important sense there are no "subjects" at all; there is only all knowledge, since the cross-connections among the myriad topics of this world simply cannot be divided up neatly." Ted Nelson, Computer Lib / Dream Machines, 1974

Although I think it's useful to believe in the existence of subjects, in the past, conversations could only be intertwingled across paper memos, faxes, written reports and email. Until the advent of the Web it wasn't possible to intertwingle conversations, networks, analysis and work in near-real time and global scale. Now that's trivial and essentially free with basic Web access.

2) The Web does what it's intended to do, so long as content is addressable and findable. The trail on observable work isn't stored in one specific place - but with a little effort it's possible to follow the flow and join the conversation.

The fact that blog posts and comments are created and served by different content server systems is irrelevant, so long as the content is addressable using basic Web standards. How the different servers store the addressed content internally is likewise irrelevant so long as they deliver the content using Web content standards.

The fact that you don't need a single common place to contain all trails is an advantage of the Web, not a disadvantage. It makes finding and linking harder, but creation and association infinitely easier than attempting to force the world into one "Observable Work" discussion area you create in one specific blog, wiki, forum, Wave or whatever.

The Web succeeds succeeds by making it possible for anyone anywhere to create a trail which others can find, follow and join using nothing more than their own Web browser, Web search layered over the basic Web, and a place like Twitter (one of many places where anyone can easily create visible, Web indexed trails).

The Web doesn't guarantee that you'll be aware of conversations on observable work going on in other trails unless you search or stumble upon a link which leads you connect the two. I don't follow discussions on LinkedIn, but might be alerted to something interesting there by someone I follow in a commons like Twitter where I do participate.

The fact that everything posted publicly on Web is potentially observable doesn't lead mean you have to deal with Too Much Information shoved in your face - or into your email box.

You choose who and what to follow, augmented by Web search and your ability to jump in and join or forget about and a trail at any time - although you might hold on to a link so it's easy to find the trail again if you change your mind.

3) Business context makes intertwingled work easier to create, discover and use. Unlike the public Web, work in a private or public organization has a purpose and context that can make intertwingled work easier to discover and talk about. Work and discussion in an organization generally take place in the context of broad business activities like sales, product development, research, finance or administration. Context in an enterprise can be represented as places where work and conversation takes place with reliable privacy aware search, tagging, linking, comments, status updates and activity streams.

I believe the important point is supporting business context - not business process in the sense of transactional workflow or automated systems. I believe that functionally specialized transactional systems in an organization will likely remain silos of structured information - but market forces will drive vendors to make their content addressable using simple Web standards and services - with consistent authentication and visibility based on context dependent business rules.

These functionally specialized systems will also signal their status using social computing standards that are now starting to take shape. This will push routine reporting and dealing with exceptions from transactional systems into the "social" places where people can stay informed, recognize issues and exceptions and decide what to do. In an ideal world, transactional systems would provide authenticated access to Web addressable content or analysis, signals based on routing activity or exceptions, Web sensible control interfaces - and not a much more. Most human access would be handled on the Web rather than transactional processing side. I believe the Web has become a valid, scalable and secure alternative to proprietary stacks for integrating most enterprise software at the user experience level.

Much of what a sociologist would call "social" behavior when talking about Enterprise 2.0 would naturally center on the sociology of work: how people communicate and interact with others while dealing with questions, issues, exceptions, suggestions and the messy stuff that routine transactional systems can't handle, along with interpersonal relationships that develop in a specific context or as member of an extended enterprise (including customers, suppliers, consultants and external as well as internal stakeholders).

On top of relationships based well established patterns of work and conversation - Andrew McAfee's strong ties - enterprise social software opens the door to discovering people and groups who most folk in a large organization would never meet face to face.

This offers the same opportunities for serendipitous discovery we see on the public Web, but with privacy in context which enables open discussion and shared goals and purpose that are part of what Peter Drucker calls the purpose of an organization: "The purpose of an organization is to enable ordinary humans beings to do extraordinary things."

Much of what's challenging about using "observable work" principles can be addressed by examples at top, middle and grassroots levels of an organization. What's needed is a willingness to tolerate and encourage observable work in the small under local control, and leadership to make it an enterprise norm.

As Paula Thornton says: "For as much as people want to make Enterprise 2.0 about technologies, then I’m willing to concede this: Enterprise 2.0 is the means by which to achieve Work 2.0 to deliver Business 2.0."

To be continued Jim, Brian, John, Mary, Jack, Paula, Mark, Gordon, Rawn, Jose, JP, Tom, Deb and the rest of the World - over to you. The best way to follow the evolution of the Observable Work trail is Twitter's #OWork tag. All of the participant's seem to use Twitter as a commons linking posts that either directly respond to the Observable Work conversation, or are related in some interesting way, such as Tom Peter's Strategy: Space Matters ("who sits next to whom in your office can make a huge difference"), JP Rangaswami's Musing about learning by doing, Deb Lavoy's Common Operating Picture - share facts, debate possibilities, John Tropea's link to Keith Swanson's excellent slide set, and John's soon-to-be-published post on Adaptive Case Management.

Unfortunately neither Twitter nor Google's hash tag search seems complete and reliable. So far as I can tell not all Tweets mentioning are found by either service. There's room for improvement on the public Web as well as the Enterprise 2.0 domain.

Apology to the Easily Distracted: Readers who find embedded links distracting don't have to click while reading the paragraph. I apologize if using the Web to source references that would be unimaginably difficult to provide in any other medium is a distraction. I believe it's not hard to exercise a little discipline when reading, then go back and click any links where you'd like to dive deeper based on your interests. I like to put a small number of See Also links at the bottom of posts where you can dive deeper if you choose.


The Work Graph Model: TeamPage style - "...A work graph consists of the units of work (tasks, ideas, clients, goals, agenda items); information about that work (relevant conversations, files, status, metadata); how it all fits together; and then the people involved with the work (who’s responsible for what? which people need to be kept in the loop?)"

Reinventing the Web - Ted Nelson, Tim Berners-Lee and the evolution of the Web. The Web rightly won versus "better" models by turning permanence into a decentralized economic decision.

Reinventing the Web II - Why isn't the Web a reliable and useful long term store for the links and content people independently create? What can we do to fix that? Who benefits from creating spaces with stable, permanently addressable content? Who pays? What incentives can make Web scale permanent, stable content with reliable bidirectional links and other goodies as common and useful as Web search over the entire flakey, decentralized and wildly successful Web?

The Future of Work Platforms: Like Jazz - The social dance of getting things done, dealing with exceptions, and staying aware of what’s going around you

Fixing Enterprise Search - Context and addressable content in functional line of business systems

Enterprise 2.0 - Letting hypertext out of its box - Hypertext and the Web

User Experience Standards for Social Computing in the Enterprise Notes for Mike Gotta E2.0 Boston 2010 panel

Enterprise 2.0 and Observable Work - A riff on themes from Jim McGee and Jon Udell

29 July 2010 | Enterprise 2.0 and Observable Work: Brian Tullis and Joe Crumpler, Burton Group Catalyst 2010 Santa Diego

Enterprise 2.0 and Observable Work

June 23, 2010 · · Posted by Greg Lloyd

I really like Jim McGee's Jun 23, 2010 blog post Managing the visibility of knowledge work. Jim makes the excellent point that "Invisibility is an accidental and little-recognized characteristic of digital knowledge work." and points back to his 2002 post Knowledge Work as Craft Work to reflect on what Jim calls a "dangerous tension between industrial frameworks and knowledge work as craft work". Early in his 2002 post McGee says:

"The Importance of visibility in craft work Almost by definition, the final product, process, and intermediate stages of craft work are visible. Consider your experiences at a glass blowing workshop or touring a silversmith's workshop. The journey from apprentice to master craftsman depends on the visibility of all aspects of craft work."

Jim continues with an exceptional analysis of what he calls "Knowledge work today as invisible craft":

"One unintended consequence of today's technology environment is to make the process of knowledge work less visible just when we need it to be more so. The end products of knowledge work are already highly refined abstractions; a financial analysis, project plan, consulting report, or article. Today, the evolution from germ of an idea through intermediate representations and false starts to finished product exists, if at all, as a series of morphing digital representations and ephemeral feedback interactions."

Please read the full post!

Two connections sprang to mind (and I didn't need a hyperlink to divert my attention - mea culpa):

1) Jon Udell's April 2009 talk at the April 2009 Open Education Conference. Udell says:

"In the pre-industrial era, education and work were: Observable, connected
In the post-industrial era, they are: Non-observable, disconnected"

Jon notes that only recently have work processes become network observable, and that this was rare in practice for all but software people. Jon speculates that software folk's norms of feedback, iterative refinement and testable outcomes seem aligned with principles of observable work - and they've become comfortable with networked technology after using the Internet for collaborative development of software and standards over many years.

2) Thomas Stewart in the Wealth of Knowledge (and my personal experience working on projects at the Naval Research Laboratory many years ago). Stewart says:

"A whale ship was my Yale College and my Harvard," said Herman Melville's Ishmael; when it came to learning my job, circulating correspondence was mine. Reading my superiors' letters opened a window into how they conducted business with the world outside; I aped things more experienced colleagues did, and saw how they handled tricky situations; I copied useful addresses into my Rolodex (another antique). I learned who knew what, and that made me better at asking for advice."

I don’t think the notion of visible work or observable work is new: mentoring, apprenticeship, and letting trusted folk watch, learn and use what they see on their own is how law, medicine and other professions were originally taught and refined as collaborative practices - and it's still so today. But as Jim McGee points out, we've lost some of the habits of observable work - to some degree intentionally, to some degree due to blinders added by the tools we've grown comfortable using:

"With e-mail, word processors, spreadsheets, and presentation tools, maintaining visibility of your knowledge work (at both the individual and workgroup level) requires mindful effort. An office full of papers and books provided clues about the knowledge work process; a laptop offers few such clues. A file directory listing is pretty thin in terms of useful knowledge sharing content. In an analog process, it’s easy to discern the history and flow of work. When an executive takes a set of paper slides and rearranges them on a conference room floor, a hidden and compelling story line may be revealed. You can see, and learn from, this fresh point of experience. That’s lost when the same process occurs at a laptop keyboard at 35,000 feet. The gain in personal productivity occurs at the expense of organizational learning."

I believe that Enterprise 2.0 principles open the door to making most work observable throughout an enterprise. There are important exceptions to protect the privacy of employee medical, financial and personnel records as well as Board and other discussions which require an exceptional degree of privacy until approved for release or for a longer term. I believe that Enterprise 2.0 collaboration principles apply equally to these more private domains within the enterprise as well as domains open to most employees. With appropriate attention to security and privacy in context, most collaborative work with external stakeholders including clients, customers, suppliers can also be made observable throughout the enterprise while simultaneously respecting privacy among clients, customers, suppliers, and all internal stakeholders.

Jim suggests that principles of observable work apply to the flow of work as well as the work product:

"The right starting point is to simply make the flow of work more visible. I suspect that this is one of the underlying attractions of social networking and micro-blogging. They promise to restore some visibility to digital team work that we lost in the first generation of tools."

I agree with Jim's suggestion. I also suggest that both the flow of work and the collaborative work product recognize privacy in context for authoring, linking, tagging, discussion, content navigation and search that seamlessly connects the worlds of flow and content. This makes it possible for almost everyone in an enterprise to be potentially aware of almost everything their organization is doing - and who knows what - to the benefit of each individual and to the enterprise as a whole.

I believe Traction TeamPage 5.0 is exceptionally well equipped to enable that vision - that's our explicit goal - but please see for yourself.

I believe that principles of open, observable work – like open book financial reporting to employees - is a simple and powerful principle that people at every level of an organization can become comfortable using. In my opinion, wider adoption of observable work principles can succeed with support and encouragement from true leaders at every level of an organization - as Peter Drucker defines that role: "A manager's task is to make the strengths of people effective and their weakness irrelevant--and that applies fully as much to the manager's boss as it applies to the manager's subordinates."


gwt-traction project on Google Code

June 22, 2010 · · Posted by Andy Keller

ImageWhile building our new GWT-based Proteus skin for Traction TeamPage 5.0, we created some widgets and utilities that we thought other developers would find useful. Most of these are pretty simple, but we hope they save other GWT developers some time. As we factor out code that can be shared with others, we'll add more to this gwt-traction Google community project.

As a TeamPage 5.0 user, you'll notice that this is just a tiny fragment of the functionality we built for Proteus. Most of the great widgets we built, like the PillBox and auto-expanding TextAreas, are dependent on other libraries and other sections of code that are more difficult to share. We'll be working to make more of this code available under the Apache 2.0 license.

The goal for the first release was to share some solutions to issues that most GWT developers encounter, regardless of the kind of application they might be building.

Learn more about gwt-traction at

Learn more about the Google Web Toolkit (GWT) at


June 18, 2010 · · Posted by Jordan Frank

ImageSince introducing the idea of Social Process Reengineering? earlier this week I've socialized it virtually and personally (at E2.0 Boston) with at least a dozen customers, bloggers, analysts and other leading thinkers.

Consensus on the concept was generally positive with a variety of feedback ranging from the matter that the "facebook" approach doesn't just work in the enterprise to the matter that the social, structural and business pain have to be taken into account for successful E2.0 efforts.

Two real gems came out of conversations with John Tropea and Nick Gall.

John pointed me to a recent post, Bridging the Enterprise Gap for a new level of literacy, where he references a similar June 4th post by Rex Lee titled Beyond Serendipity for Enterprise 2.0. Rex says we need:

a shift from emergence to social engineering. Social engineering, not in the IT security sense, or Machiavellian sense, but as a means to better focus and harness intellectual capital for specific business purposes.

Serendipitous is the timing of our respective thoughts on social engineering!! Of greater importance is the message of course. His emphasis on a solution points to the engagement factors which include Motivation, Opportunity and Capability. I'll concur that grasping and addressing these factors and then casting them in context of a use case and E2.0 platform structure for supporting the use case are of cardinal importance for those of us looking to maximize success of a use case and achieve the 10x results needed for success.

ImageSeparately, I got in touch with Nick Gall (an enterprise architecture and design thinker at Gartner) after watching Introducing Hybrid Thinking where he opened by saying "all too often we are doing architecture to people rather than architecture for people." He comes back to his foundational point in the conclusion of his talk by showing the T-Shirt pictured here. I think its a brilliant reminder that the goal of IT is for human productivity, with a balance of consideration of standards, rather than the other way around. This sounds like E2.0 (doing architecture for people) vs. E1.0 (doing architecture to people). I reached out to Nick figuring he would be keen on concepts of a Social Architect or Social Process Engineer who may lay foundations where emergent work could achieve best returns. Turns out he prefers the metaphor of a Farmer or Gardener, but the semantic debate will take me too far into the weeds.

At E2.0 he swung by for a tour of TeamPage 5.0 and, in discussion of Social Process Reeingeering, he came up with (and even told me I could claim) a modification: Social Process Emergineering.

I liked it. I called another design thinker, Paula Thornton, to chew on this further and we resolved that the term Emergineering is inherently social (emergent) and inherently considerate of process (engineering).

So, Emergineering it is. Lets run with it.

Welcome to Traction TeamPage 5.0!

June 15, 2010 · · Posted by Greg Lloyd

ImageOn Tuesday June 15, 2010 we'll introduce Traction TeamPage Release 5.0 to the world at the Enterprise 2.0 Conference in Boston. TeamPage Release 5.0's new generation Proteus interface technology is fast, simple, and looks great. TeamPage 5.0 leverages this technology to add extensible personal profile pages, Twitter style personal status, group live blog technology, slick and simple Feed summary and more as a natural part of Traction's award winning Enterprise 2.0 platform.

I believe Proteus lives up to the TUG 2009 Proteus mantra: Fast, Simple, Beautiful and hope you agree. I'd like to thank all of the members of the Traction Software Team for imagining, designing and bringing Proteus to life - particularly Andy Keller, Chris Nuzum, Dave Shepperton and Michael Angeles. I'd also like to thank the Traction TeamPage customers who worked closely with us in the conceptual design, mockup, wireframe and preview stages of Proteus, social networking, and project management extensions.

Please see Traction Traction TeamPage 5.0: Social Software for Work for a brief white paper on TeamPage 5.0 including a tour of these slides:

A release candidate for Traction TeamPage 5.0 is available today for download and installation by customers - including users of the free five user TeamPage configuration.

TeamPage 5.0 is also running on Traction Software’s corporate TeamPage server which provides free access (registration required). Register today to join the conversation and download a free copy of Traction TeamPage 5.0.

I hope you all enjoy using TeamPage 5.0 as much as everyone at Traction Software already does. Tell your friends!

Social Process Reengineering?

June 13, 2010 · · Posted by Jordan Frank

As much as I hesitate to introduce this term into social software lingo, I think it's exactly what Enterprises are doing with social software on the road to Enterprise 2.0 - striving for a fundamentally new way to work.

Considering various definitions of Business Process Reengineering (BPR), you can start to see what's in common:

"... the fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in critical contemporary measures of performance, such as cost, quality, service, and speed." Hammer and Champy (1993)

In reference to BPR, Davenport (1993) says that "Today firms must seek not fractional, but multiplicative levels of improvement – 10x rather than 10%."

We are in the same situation today - but trying to achieve those 10x gains with social systems rather than rigid business workflow systems. 10x, while lofty, has to be the goal to overcome the 9x Email problem discussed by Andrew McAfee (in reference to J. T. Gourville's "Why Consumers Don't Buy: The Psychology of New Product Adoption") and explored further by Greg Lloyd in Enterprise 2.0 - Letting Hypertext out of its Box.

Across whatever set of metrics, Social Software has to give adopters the perception that it's 10x better than the alternative.

Andrew McAfee recently posted an entry which ponders What's the Simplest Thing That Could Possibly Work? McAfee quotes an E2.0 Evangelist from a big tech company who complained:

"Progress is slower than I’d like. I don’t know why more people aren’t doing more. I think part of it is that we have a huge Intranet, and these tools can be hard to find. I think a lot of our people aren’t even sure they exist.

ImageMcAfee's proposed simple solution is to put a box in every intranet page that urges users to Search, Ask or Share - each with a simple text box for input. In the discussion, McAfee references his own rule to deploy "Tools that deliver something novel - that aren't trying to displace an incumbent - avoid the 9x effect."

I am all for the idea of thinking in simple terms, but the suggestion diverges from answering the challenge to deliver a 10x improvement. The suggestion left me wondering "10x over what?" The Search, Ask, Share idea is on target but an action so simple and attractive as Share is dead on arrival if even a few key stakeholders are 9xd in email.

I am on board with avoiding other incumbent tools (except email which is an open wound advertising the pain resulting from broken processes), but it's vital to realize that any time you move communication to an E2.0 system you are displacing a social process (however it manifests - at the water cooler, in meetings, in email) with a social technology process.

Taking a social process reengineering approach, I take a Druckerian vision which agrees with Greg Lloyd's stance in Enterprise 2.0 Schism:

I believe that although both technology and broad bottom-up participation are necessary to achieve the Drukerian vision, neither element alone is sufficient to achieve the noble end of re-engineering how ordinary people work together to achieve the ends of enterprises they choose to affiliate with.

Its the mix of social and technology that come together to enable, in Drucker's words, "ordinary people to do extraordinary things." But not every technology works and not every social group can simply pick up a tool and run.

If McAfee's E2.0 Evangelist from the tech company is so puzzled about why participation in his E2.0 pilot is not succeeding, he should start considering whether people, teams and departments know their Whats, Hows and Whys:

  • What process does the system support for my group, team, department, enterprise? What business pain does it alleviate?
  • How, mechanically speaking, do people operate the technology defined in What to achieve the result?
  • Why does the How create a perception of 10x ROI - Return On Information

For the last 8 years I've worked on social software with companies and organizations in every pocket of industry, multiple governments in the US and abroad, and non-profits. One of my favorite adoption stories runs counter to what many E2.0 evangelists would ever expect. The deployment was led by Peggy Walker, a grandmother of many at a very conservative, very large, very old mid-western firm. The initial group of adopters were age 40 to 60 - a far cry from the typical Facebook and MySpace generation which some would perceive as a pre-req for E2.0 adoption.

ImageWhat made this adoption story work, in days and weeks not years, was Peggy's six-sigma green belt which helped her focus one eye on process and one eye on leadership. She was a master of what Paula Thornton recently coined as B2.0: Orchestrated Improvisation. Peggy understood the piece parts of what her orchestra members do in their daily work life, understood the process context in which they worked, and, like a good conductor, was able to lead them, like any good conductor, to play together to the symphonic challenge of the day - which was sure to be ever changing but followed certain patterns and basic structures. Whether the technology was new-fangled or old didn't matter - the key was her ability to figure out What, How and Why. Then she could explain the new process (loosely described as a set of interleaved intelligence communities) and how people could use the technology to do their jobs better.

Social Process Reengineering is a far cry from Business Process Reengineering which may require fleets of consultants and man-years of programmers to arrive at rigid processes that improve the flow of goods through a supply chain.

Instead, SPR requires that we understand our social processes, find the underlying pain points, understand social artifacts, and figure out how to structure for emergence. Finally, the role of leader is not Evangelist, it's Conductor. The individuals who lead the deployment, who work with teams to pile-on use case after use case, need to coordinate their orchestra of workers to outcomes which are inevitably new and always extraordinary.

Converse to man-month BPR planning efforts, SPR can happen in minutes over morning coffee or in a Stewart Mader style afternoon Barn Raising. By way of example, I've talked to a dozen customers about replacing Excel based processes with a New Way to Work and many made the switch immediately.

In fact SPR's flexible and emergent outcomes offers the perfect balance needed by BPR which seeks rigid rules driven outcomes based on process optimization. BPR aims to produce workflow systems for predictable business problems whereas SPR, using social software as the supporting technology, is the agent that lets us plan for change, face competitive threats and leap onto market opportunities. While SPR and BPR seem like opposing concepts, one may just be the Yin to the other's Yang.

One of our customer stories takes me right to this point. At KUKA Systems, an IT team seeded their social software deployment by deploying a set of spaces where anyone at the firm could post issues pertaining to their enterprise systems. They took a social approach to discussing, tracking and executing on changes to these business critical process systems. This is a perfect example of a social process that, to McAfee's point, is one of the simplest things you can do and, meanwhile, has a meaningful and tangible 10x impact on the way issues are handled as well as on the productivity and performance of business systems. Maybe I've just reached the bigger picture point to which John Tropea was referring when he referred to the KUKA Systems customer story as the "Seminal enterprise 2.0 task-based/process soln."

Q: How do I link to an Excel file? A: Why Would you Do That?

June 11, 2010 · · Posted by Jordan Frank

I talked to two customers yesterday, both who came to me with some questions about attaching and linking to excel files. Easy enough, but before responding with a simple answer I challenged them: Why are you using Excel?

Pages vs. Rows, Tags vs. Columns

In both cases, we agreed on a better approach using page in Traction instead of rows in Excel, and a simple tagging strategy instead of columns in excel.

The first case was a customer at a state level Department of Health. Her Excel sheet had a simple list of 20 rows, each describing part of a work plan. There was very little sort criteria, except perhaps a way to scan and see which requirements are complete. She agreed that there was much more detail behind each row which could better describe it, and sharing status on it would mean continual running commentary that would redirect people to the file which they would have to open and then have to detect visually for changes.

The second case was a customer at a Big Pharma with a system for capturing as many as 3,000 journal abstracts at a time and dropping them into an excel sheet. The system applies some logic to the text to break out columns indicating whether certain drugs and certain categories were mentioned. Then a team of people comb through the sheet to prioritize and score each record. This brings up all kinds of work process issues along with the obvious squint session involved in trying to read abstract text jammed into cells.

In both cases, we quickly figured out a strategy for how to arrange the content in terms of Pages and Tags and how to use search to slice and dice the information to satisfy even the most begrudging team members. What brought the matter home in both cases, though, was giving them a tool which gives the article content the appearance of being in a table. This approach not only surfaces the tagging strategy and makes the process of change-over from excel easier, it is also a powerful way to view the articles and support the work process.

An Example - From Rows in Excel to Pages Instead

By way of illustration, here is an example of a product Feature displayed in its article / page view, then represented in a table which has sortable columns for priority, status and milestone.

Single Page View: Here you can see the article and its tags which include assignment of content type (Feature), status (To Do), priority (P2), and milestone (V2_1).


Section Table View: This view leverages the use of a Section in an article which operates as a filter over just the pages marked To Do AND (Feature OR Bug). You can see that the tags are broken out into columns which can actually be sorted. This offers an immediate sense of how the different kinds of tags work together to form a tagging strategy and help structure an emergent and agile workflow.


Section Table View with Page Expanded: The next issue is how you can actually interact with the table. As noted above, you can sort on the columns but what if you want to see more about an article, change status, change priority or add some commentary. The section table includes a (+) feature that lets you expand any page. This displays all its content and right click actions let you add comments, change tags or even edit the article.


A New Way to Work

As people make the transition from email, word and excel to page based communication in social software platforms like Traction TeamPage, there needs to be a fundamental reset on how we think about information and how to organize it.

I love this example because it offers a clear visualization of:

a) Why breaking big word documents into separate pages offers incredible advantages.

b) How page based workflows are achieved with a simple tagging strategy.

c) Why our concept of the types of structure you can create in Excel or database tools can be met and beat with pages, tags and meta data oriented around the pages.

This is one of many good examples of how social software can fundamentally alter the way we work for the better. Making this kind of transition, from DOC and XLS to Pages is not only fun, it makes a profound impact on productivity and communication.

The spy who came in from the code | O'Reilly Radar | Carmen Medina interview

May 4, 2010 · · Posted by Greg Lloyd

ImageSee The spy who came in from the code for James Turner's excellent O'Reilly Radar interview with Carmen Medina who recently retired from the CIA after 32 years after serving in roles including Deputy Director of Intelligence, and Director of the CIA's Center for the Study of Intelligence. Carmen was the keynote speaker at Traction Software's Oct 2009 Traction User Group meeting, speaking on Enterprise 2.0 and the Context of Work (see slides and video). She'll speak at the Gov 2.0 Expo on May 26, 2010 Washington DC on A Match made in Heaven: High Reliability-High Risk Organizations and the Power of Social Networks. Don't miss her talk, and follow @milouness on Twitter!

Return On Information

April 14, 2010 · · Posted by Jordan Frank

Rather than thinking about communication, collaboration and KM software in terms of Return on Investment, isn't the real goal to achieve Return On Information?

ROI (in the context of Return on Investment) comes up routinely on this blog and internet wide but I think considering the issue as one of return on information points to the real value sought.

When you think about return on investment, you think about how time is saved or resources are used better for monetary return. When there is not a direct line between action and revenue, as is often the case with knowledge activities, you work hard to identify marginal time savings through less face to face meetings or to quantify the value of insight and team work.

When thinking about return on information, you can consider tactical benefits:

- How easily can I conduct conversations?

- In what ways can we leverage pages in multiple contexts, rather than lose or simply stash and forget knowledge?

- In what ways can information be followed proactively or retrieved reactively?

- What different ways can pages be rendered into cross-sections which may be useful in a status or issue review?

- If the point of wiki is documentation, how can we view pages on a screen and output them to useful formats like email, word or PDF?

You can also consider strategic benefits:

- What benefits are found by opening up lines of communication from "need to know" to "can know" permission boundaries? These benefits may be expressed in terms of value found by connecting people faster or of value found by involving key people who can offer immeasurable value but may not be directly involved in a given team's communication swirl.

- In what ways does journaling raw information (meeting notes, call notes, ideas, issues) support future analysis and insight?

When I did a simple web search on return on information I found only a few relevant references, including one about enterprise search - which may enhance the ability to discover information but does not offer the tactical scenarios for further enrichment of it. While ROI hasn't been at the top of many RFPs I've received lately, I am hoping future RFPs will focus more on information leverage than typical questions about presence of certain features.

Ada Lovelace Day | Fran Allen, IBM Fellow and A.M. Turing Award Winner

March 23, 2010 · · Posted by Greg Lloyd

ImageFor the second annual Ada Lovelace Day, March 24, 2010 - celebrating women in science and technology - I've chosen to write about Frances E. Allen, IBM Fellow, Turing Award winner and pioneer in the theory and practice of optimizing compilers. I've never had the pleasure of meeting her in person, but I'll take the liberty of calling her Fran, as Dick Merwin and everyone I know called her in their Fran stories.

According to her Wikipedia biography, Fran Allen grew up on a farm in update New York. After earning BSc and MSc degrees in Mathematics she joined IBM in July 1957, deeply in debt and planning to stay only until her school loans were paid. She stayed for a 45-year IBM career that included pioneering research and development in computer languages and compilers, leading her to become the first female IBM Fellow in 1989. She retired from IBM in 2002, won the Augusta Ada Lovelace Award that year from the Association for Women in Computing, and the A.M. Turing Award for 2006 (aka computing's Nobel Prize. Fran used the $100,000 Turing prize, funded by Intel, to start a fund to teach girls in areas of the world where educational opportunities are slim.

I first learned about Fran's work from Dick Merwin, then my boss at the Safeguard System Office, and former Engineering Manager of the IBM Stretch / Harvest computer. Stretch (aka the IBM 7030) was an extraordinarily ambitious and influential project to build the world's fastest computer; it was that - although it fell short of its 'stretch' goal of 100x faster than the IBM 704.

Very early in her career Fran played a crucial role in creating computer languages and compiler optimization techniques for the NSA's HARVEST system (which used Stretch technology) which Fran described in a Nov 2000 interview:

From abstract: " In response to government requests, IBM Research designed a system for a very large data processing application, known as the HARVEST system, including Stretch, which was delivered to the National Security Agency in the early 1960s. The combined Stretch-HARVEST Project created a milieu for developing new technologies, new hardware architectures, and new software to meet the challenges of both systems. One of the guiding principles of the project was to make programming easier by the use of a compiler to generate code automatically from statements in the user's language.

Allen was a member of the ALPHA language design team which created a very high level language featuring, among other things, the ability to create new alphabets beyond the system defined alphabets (e.g. English, decimal, integer, binary) and treat complex, heterogeneous data in high-level statements. In addition to an overview of Stretch-HARVEST, the talk will describe some of the lesser known aspects of the project the people and institutions involved, the political climate, and the shared knowledge, views, and value systems which were part of this interesting project at an interesting time in the history of computing. "

Stretch HARVEST compiler lecture by Fran Allan | Film | Computer History Museum

And finally: "Allen, 74, thinks women were more prevalent when she started her career--in 1959, three of her four IBM co-managers were women--than they are today. The shortage of women in IT "is getting worse," she says." Fran Allen 2007 Information Week Interview.

Footnote: I tip my hat to IBM for its early leadership in fair, progressive employment and promotion policies that encouraged recruiting, recognition and promotion of highly qualified women, minorities and others who suffered from discrimination. It was was not only a morally right action, but also a business decision that brought exceptional talent to IBM to the lasting benefit of IBM stockholders.

Order shirts or mugs with the Ada Lovelace Day art (shown above) by Sidney Padua, author of The Thrilling Adventures of Lovelace and Babbage - a free Web comic you'll surely enjoy.

Via here's a great Ada Lovelace Day 2010 presentation by Andra Keary

Social Media Policy Almost = Blabbing Policy

March 18, 2010 · · Posted by Jordan Frank

After reading 10 Social Media Commandment for Employers, I was reminded of Blogging Policy = Blabbing Policy, a blog entry I wrote back in 2006 when the the "conversation" in the blog-o-sphere started to center on corporate blogging policies.

I don't care to debate the merit of each of the commandments, but do take issue with the concept at all. The fact that, in the past, there was consideration (by anyone) of corporate Blogging policies makes the point perfectly clear:

Companies don't need a FILL IN THE TREND HERE Policy, they need a Communications (Blabbing) Policy and a related Conduct Policy which governs employee behavior with respect to trade secrets of all forms and terms for legal and ethical conduct.

There is one facet of Social Media policy that could be worth special coverage in a communications policy. Specifically, certain employees who get involved on a business development level with potential partners could be a good target for your competitors' monitoring. If those employees, be they researchers, strategists, or CEOs are visibly connecting to a given set of like individuals from a potential partner's company, the likelihood of a potential partnership or business deal could be anticipated by your competitor.

So, if the formation of an incipient business to business relationship is covered by an NDA (or should otherwise be confidential), company employees ought to be careful about forming "following" or "link" type connections with individuals from the counter-party and, I believe, its perfectly in-bounds for a corporate "communication policy" to specify ground rules for "public gathering," rather than calling out social media specifically.

Garry Kasparov on Computer Chess and Enterprise 2.0

February 19, 2010 · · Posted by Greg Lloyd

Image Professor Andrew McAfee posted a very good business analysis of points made by Garry Kasparov in his Feb 11, 2010 New York Review of Books article on Diego Rasskin-Gutman's book Chess Metaphors: Artificial Intelligence and the Human Mind. Kasparov's summarized of his own thoughts as a Chess Grandmaster and world chess champion playing against - and losing to - IBM's Deep Blue chess computer. But the interesting part comes when Kasparov talks about a recent match open to grandmasters who were allowed to use computer chess programs of their choice to augment their own chess skills: "The surprise came at the conclusion of the event. The winner was revealed to be not a grandmaster with a state-of-the-art PC but a pair of amateur American chess players using three computers at the same time." McAfee quotes Kasparov and continues:

My favorite aspect of these 'freestyle' competitions was the specific type of human creativity that led to victory. Instead of pure chess genius, it was something much closer to business process design brilliance. The overall winner was a team that contained neither the best human players nor the biggest and fastest computers. Instead, it consisted of "a pair of amateur American chess players using three computers at the same time. Their skill at manipulating and "coaching" their computers to look very deeply into positions effectively counteracted the superior chess understanding of their grandmaster opponents and the greater computational power of other participants."

Kasparov was surprised at this outcome and I have to confess that I was as well, despite my deep conviction that a well-designed process is a potent weapon. I didn't think that smart process design — in this case, a process for determining the "best" chess move — could overcome both cognitive and computational deficits. But it did, even in this domain where brains and calculations would appear to be the only things that matter. As Kasparov writes of this amazing result, "Weak human + machine + better process was superior to a strong computer alone and, more remarkably, superior to a strong human + machine + inferior process." I think that's my new motto. - Andrew McAfee, Harvard Business Review, Feb 18, 2010

Read McAfee's Did Garry Kasparov Stumble Into a New Business Process Model for his excellent analysis and conclusions. I commented: Thanks for a great post on what it means to augment rather than automate business processes! Doug Engelbart devoted a lifetime of work to investigating how technology can augment the abilities people to address complex and challenging problems, including but not limited to business (see Engelbart links below).

The Kasparov quote also gets to what I believe is the heart of the Enterprise 2.0 value debate:

• ERP / MRP / BI and other enterprise IT systems deliver value based on optimizing flow of transactions, optimizing management of predictable processes, or providing analytic insight. ROI calculation for optimizing automated processes is straightforward - and managers are comfortable estimating the potential business value of better analytics.

• Enterprise 2.0 systems augment the ability of organizations to recognize and deal with opportunities, exceptions (and threats) which aren't predictable but have high enough value and occur frequently enough give companies who execute well a sustainable competitive advantage.

I believe the two points are connected. Expensive analytic and reporting systems are of little value if discoveries made can't be turned into actionable insights. Senior management should weigh how Enterprise 2.0 techniques can augment their people's ability deliver value using the expensive transactional and analytic IT systems that they already have or want to create.


Doug Engelbart | 85th Birthday Jan 30, 2010 Augmentation quotes and links

Enterprise 2.0 Schism Why I believe that Doug Engelbart and Peter Drucker are Patron Saints of E2.0

Augmenting Human Intellect: Remove the brick

ImageIn 1962 Doug Engelbart wrote the paper he calls his bible: AUGMENTING HUMAN INTELLECT: A Conceptual Framework. It is both a roadmap of his lifework - and a white paper presented to ARPA and other agencies for funding. In 1962 Doug could not cite examples for the use of computer systems to augment the creative and problem solving abilities of humans - he was in the process of inventing that - but he could perform a de-augmentation experiment which he used as a counter example. He tied a brick to a pencil and demonstrated that his handwriting became much slower and much less legible. My paraphrase of Doug's research objective: Remove the bricks that limit our ability to write, work and communicate effectively by providing computer systems that augment people's natural abilities to write, work and communicate.

Traction Roots - Doug Engelbart

Doug Engelbart | 85th Birthday Jan 30, 2010

January 30, 2010 · · Posted by Greg Lloyd

Image"DOUG Engelbart sat under a twenty-two-foot-high video screen, "dealing lightning with both hands." At least that's the way it seemed to Chuck Thacker, a young Xerox PARC computer designer who was later shown a video of the demonstration that changed the course of the computer world." from What the Dormouse Said, John Markoff.

Doug Engelbart has been recognized as a great figure in the history of technology with awards including the National Medal of Technology presented by President Bill Clinton for: "... creating the foundations of personal computing including continuous real-time interaction based on cathode-ray tube displays and the mouse, hypertext linking, text editing, on-line journals, shared-screen teleconferencing, and remote collaborative work."'

Doug is also noble figure. Doug's research has a moral purpose, reflecting the skills and attitude of a great engineer and humanitarian: If the world is faced with complex, intractable problems that challenge the ability of individuals and nations to solve, what can I do to help people fix what's broken?

Doug's research focuses on how computers can aid people's ability to think and work as groups as well as individuals - what Doug refers to as Augmentation rather than Automation. This involves understanding how problem solving groups actually behave - and how introducing new technology changes behavior and vice versa. This led me to nominate Doug along with Peter Drucker as a patron saint of Enterprise 2.0; the phrase is flip but the thought is serious. Please send 85th Birthday greetings to Doug today.

I'll let Doug speak for himself in the opening paragraphs of what he calls the bible of his research agenda, AUGMENTING HUMAN INTELLECT: A Conceptual Framework from Oct 1962:

By "augmenting human intellect" we mean increasing the capability of a man to approach a complex problem situation, to gain comprehension to suit his particular needs, and to derive solutions to problems. Increased capability in this respect is taken to mean a mixture of the following: more-rapid comprehension, better comprehension, the possibility of gaining a useful degree of comprehension in a situation that previously was too complex, speedier solutions, better solutions, and the possibility of finding solutions to problems that before seemed insoluble. And by "complex situations" we include the professional problems of diplomats, executives, social scientists, life scientists, physical scientists, attorneys, designers--whether the problem situation exists for twenty minutes or twenty years. We do not speak of isolated clever tricks that help in particular situations. We refer to a way of life in an integrated domain where hunches, cut-and-try, intangibles, and the human "feel for a situation" usefully co-exist with powerful concepts, streamlined terminology and notation, sophisticated methods, and high-powered electronic aids.1a1

Man's population and gross product are increasing at a considerable rate, but the complexity of his problems grows still faster, and the urgency with which solutions must be found becomes steadily greater in response to the increased rate of activity and the increasingly global nature of that activity. Augmenting man's intellect, in the sense defined above, would warrant full pursuit by an enlightened society if there could be shown a reasonable approach and some plausible benefits.1a2

This report covers the first phase of a program aimed at developing means to augment the human intellect. These "means" can include many things--all of which appear to be but extensions of means developed and used in the past to help man apply his native sensory, mental, and motor capabilities--and we consider the whole system of a human and his augmentation means as a proper field of search for practical possibilities. It is a very important system to our society, and like most systems its performance can best be improved by considering the whole as a set of interacting components rather than by considering the components in isolation. - AUGMENTING HUMAN INTELLECT: A Conceptual Framework, Douglas Engelbart October 1962

And notes from a conversation with Alan Kay - one of the two thousand people who attended Doug's Dec 1968 Demo, and went on to shape the world of technology as we know it.

Alan Kay At PARC one of the goals was to do NLS as a distributed system and all of the ALTOs had the five-finger keyboards as well as the mouse on them. We basically loved NLS and we'd done a few modifications which we thought even sped up. NLS part of the interaction scheme on it was, I believe, because the analog mouse there was some drift in it, so one of the things that they did was to say what kind of a thing you were pointing at, so you'd say move character or move word or move paragraph and so forth. It was kind of a procedure where you gave the command first and then bug bug and then command accept. We realized at Xerox PARC that you wanted to have a speedy scheme for interacting and we thought we could go even one better by selecting the objects, so you'd select something you'd do something to, give the command and then, in the case of move character you'd go select, move, select and it would it with fewer keystrokes.

Now, the abortion that happened after PARC was the misunderstanding of the user interface that we did for children, which was the overlapping window interface which we made as naive as absolutely we possibly could to the point of not having any work flow ideas in it and that was taken over uncritically out into the outside world. So we have many systems, like Lotus Notes and many mail systems that when you say replay it comes up with a window over the very thing you were reading as though there weren't any connection between these things. So this is an abortion to me, but its basically part of the whole feel. Whereas our notion was that you start the kids off on this fairly simple, naive thing and then there would be an actual progression where you would get up to this several commands a second kind of thing that you could do with NLS. If you have ever seen anybody use NLS it is really marvelous cause you're kindof flying along through the stuff several commands a second and there's a complete different sense of what it means to interact than you have today. I characterize what we have today as a wonderful bike with training wheels on that nobody knows they are on so nobody is trying to take them off. I just feel like we're way way behind where we could have been if it weren't for the way commercialization turned out.

Doug Engelbart Well, strangely enough, I feel the same. It's part of the thing of the easy to learn and natural to use thing that became sort of a god to follow and the marketplace is driving it and its successful and you could market on that basis, but some of the diagrams pictures that I didn't quite get to the other day was how do you ever migrate from a tricycle to a bicycle because a bicycle is very unnatural and very hard to learn compared to a tricycle, and yet in society it has superseded all the tricycles for people over five years old. So the whole idea of high-performance knowledge work is yet to come up and be in the domain. Its still the orientation of automating what you used to do instead of moving to a whole new domain in which you are going to obviously going to learn quite a few new skills. And so you make analogies of suppose you wanted to move up to the ski slopes and be mobile on skis. Well, just visiting them for an afternoon is not going to do it. So, I'd love to have photographs of skateboards and skis and windsurfing and all of that to show you what people can really if they have a new way supplied by technology to be mobile in a different environment. None of that could be done if people insisted that it was an easy-to-learn thing.

So, moving your way around those thought vectors in concept space - I'd forgotten about that

Alan Kay You said that, right?

Doug Engelbart I must have, its so good. [laughter] Its to externalize your thoughts in the concept structures that are meaningful outside and moving around flexibly and manipulating them and viewing them. Its a new way to operate on a new kind of externalized medium. So, to keep doing it in a model of the old media is just a hangup that someplace we're going to break that perspective and shift and then the idea of high performance and the idea of high performance teams who've learned to coordinate, to get that ball down the field together in all kinds of operations. I feel like the real breakthrough for us getting someplace is going to be when we say 'All right, lets put together high-performance, knowledge-work teams and lets pick the roles they're going to play within our organizations in some way in such even though they operate very differently from their peers out in the rest of the organization they can interact with them and support them very effectively. So there are roles like that that would be very effective and everyone else can sortof see because they're interacting with these guys what they can do. And suppose it does take 200 hours of specialized training - that's less than boot camp.

One of those boxes on that paradigm map about deployment was really coming down and showing you that special purpose teams are one kind of thing in the way that they can propagate and very different from moving a group of people who have an existing set of staff and processes and methods and skills and equipment and trying to move them all together. It's practically an impossible task to do that in any significantly large step without having casualties. They just aren't all equipped to mobile in that space. So, there's a lot to go with that and it all stems from looking at today and saying 'why do we accept that?' That's the modern thing, its almost a religion. In any other company I'd be afraid to bring that out. Maybe I'll have to run from you too... from Notes from the Panels The Brown / MIT Vannevar Bush Symposium, October 1995

Update Remembering Doug Engelbart, 30 January 1925 - 2 July 2013

Doug Engelbart Resources The Doug Engelbart Institute was was conceived by Doug Engelbart to further his lifelong career goal of boosting our ability to better address complex, urgent problems. It contains an excellent history, archive of papers, photos and other published resources as well as links to Doug's current projects.

Douglas Engelbart Interviewed by John Markoff of the New York Times Outracing the Fire: 50 Years and Counting of Technology and Change Computer History Museum oral history interview, March 26, 2002.

Doug Engelbart Video Archive: 1968 Demo - FJCC Conference Presentation Reel Dec 9, 1968 Internet Archive, the so called Mother of All Demos. See also From Pranksters to PCs chapter about Engelbart's 1968 FJCC demo from John Markoff's book What the Dormouse Said: How the 60s Counterculture Shaped the Personal Computer Industry, authorized excerpt.

Video Archive MIT / Brown Vannevar Bush Symposium: A Celebration of Vannevar Bush's 1945 Vision, An Examination of What Has Been Accomplished, and What Remains to Be Done. Oct 12-13 1995, MIT. Talks and panel discussion with Doug Engelbart, Ted Nelson, Andy van Dam, Tim Berners-Lee, Alan Kay and others. See also ACM Interactions summary (free access), transcript of day 1 and day 2 panels.

Doug Engelbart's copy of Vannevar Bush's 1945 As We May Think, with Doug's 1962 notes scribbled in the margins.

Tuesday Dec 9, 2008 | Forty years after the Mother of All Demos Engelbart's demonstration of the Augment shared screen hypertext and video system developed by a team at SRI under Doug's leadership. Links to videos, interviews and other resources

AUGMENTING HUMAN INTELLECT: A Conceptual Framework By Douglas C. Engelbart October 1962 (SRI AUGMENT, 3906)

And yes, Doug also invented the mouse, and used it in his 1968 demo. But introducing Doug as the inventor of the mouse is like introducing Leonardo da Vinci as a guy who knew how to make good paint brushes.


Facebook: A Carnival Midway not a Neighborhood?

December 17, 2009 · · Posted by Greg Lloyd

ImageOliver Marks wrote a very good post: Facebook: The Legal Rumblings Start Dec 17, 2009, on the Facebook's potential legal exposure due to its controversial changes to member privacy capabilities and settings. My comment: Oliver -- Very good followup on Facebook's awkward (to put it mildly) changes to selective privacy capabilities which were a large part of their differentiation vs Friendster and MySpace.

With over 70 million folk apparently hooked on "social" games like Farmville, targeted ads that seem to belong on late night TV, and incredibly lame attempts to nag folk get their friends to use Facebook more (giving "viral" a new and flu like meaning), I see Facebook becoming a downscale carnival midway more than a neighborhood. They certainly have a right to do that.

Originally I thought the equally lame and manipulative privacy changes would just contribute to the downmarket feel of the place.

But as you point out - EU privacy laws may land them in legal entanglements too.

Facebook is becoming a bad example rather than a good example for use of social software in the enterprise - or anywhere for that matter. Look out below!

My point is that Facebook has every legal right to attempt to develop, market and monetize a site with whatever privacy and promotional rules it wants - and let customers vote with their feet. But changing rules of an established site by eliminating privacy related permissions can run into legal trouble as well as losing trust that makes people comfortable continuing to use the site.

Facebook seems to be floundering and flailing into the greedy vision of "a closed Internet with ads" that has been the graveyard of AOL, Friendster and others, see the Onion Video Internet Archaeologists Find Ruins of 'Friendster' Civilization. Even worse - Facebook ads, apps and promotions are increasingly loud, spammy and sometimes offensive. Google does a pretty good job of mixing advertising that's not too obtrusive with their services - and the certainly makes money. Facebook should learn from Google.

I believe that the popularity of social sites on the public Web and the value of internally and externally facing Enterprise 2.0 collaboration comes from a skilled combination of affordances that make spaces more or less inviting and suitable to some intended purpose. Great architects of physical places know that people bring expectations and norms about the kind of behavior that's appropriate and enjoyable to any physical space - and that's a lesson that public Web and Enterprise 2.0 designers need to learn and use.


The Social Facebook Fiasco Oliver Marks, Dec 15, 2009. Analysis. "...the effect of these Facebook fiascos are a confused business audience, some of whom would like to see an ‘enterprise Facebook’ in their corporate environment…if they could get a handle on Facebook’s ever mutating terms of service."

Facebook's Privacy Move Violates Contract with Users Kaliya Hamlin, Dec 15, 2009. Guest RWW post reviews the changing "social contract" offered by Facebook - and points to Second Quarter 2010 planned availability of Facebook's Social Graph API as the motive for the privacy change.

Privacy groups file complaint with FTC over Facebook settings Larry Dignan, Dec 17, 2009. A very concise summary of Facebook's Dec 2009 revision to privacy settings offered to members.

Explaining Twitter - One of Three Places for People I decided to describe Twitter as one of three distinct places on the Web where I socialize every day: the public commons. The others two are my neighborhood (Facebook) and my workplace (the 300+ spaces on Traction Software's TeamPage server). Compares and contrasts patterns of connections and the social architecture at work and in public places.

Ask an Engineer: What do you think of the Facebook Terms of Service Flap? Analyzes the Feb 2009 Facebook terms of service revision flap based on the difficulty in defining privacy policy based on two different and irreconcilable sets of expectation on what should happen to data previously shared by applications if a member subsequently revokes permission to share.

Clarity Amid the Hype What's different about enterprise Twitter? Most of this carries forward to consideration of What's different about enterprise Facebook?

Borders, Spaces, and Places How to model permissions and borders to enable collaboration where there's a natural expectation of privacy crossing many spaces - for example a law firms simultaneous collaboration with each its clients as well as internal groups. Permissions and borders need to be simple, scaleable and secure to work for internal and externally facing E2.0 collaboration.

How big a deal is Enterprise 2.0? What do you mean by "Big"?

November 22, 2009 · · Posted by Greg Lloyd

I'm flattered that Professor Andrew McAfee cites Enterprise 2.0 Schism in his Nov 20, 2009 blog post Enterprise 2.0 is Not THAT Big a Deal, kicking off a neat discussion on serious points behind my tongue in cheek analysis. McAfee agrees that Enterprise 2.0 is a big deal - but "... I don't see E2.0's tools, approaches, and philosophies making obsolete managers, hierarchies, org charts and formal cross functional business processes". There's no need to use a 2.0 version for the Enterprise, but:

I yield to almost no one in my belief about the power and utility of ESSPs [ Emergent Social Software Platforms ], but I just don’t think they’re going to transform the structure or purpose of the enterprise. As I wrote earlier, I don’t see E2.0’s tools, approaches, and philosophies making obsolete managers, hierarchies, org charts, and formal cross functional business processes...

I want to be clear: Lloyd’s post is fantastic: grounded and very thoughtful. He’s not in the enterprise-as-slime-mold camp. And I definitely agree with him that Enterprise 2.0 is a big deal. So what’s the right way to describe its impact?

Here’s my take: ESSPs will have about as big an impact on the informal processes of the organization as large-scale commercial enterprise systems (ERP, CRM, Supply Chain, etc.) have had on the formal processes.

This is not a conservative statement. Enterprise systems have been a huge deal for organizations. They’ve turned reengineering from a whiteboard exercise into an unignorable reality for many, many companies. And Drucker was right when he said that “Reengineering is new, and it has to be done.” - Andrew McAfee Nov 20, 2009

I happily replied:

Andy -- Thank you for the kind words as well as the thoughtful analysis. I agree strongly with your take that the impact on the informal processes will be as large as the impact of large scale commercial enterprise systems on formal processes.

I differ a little by including daily working communication, awareness and alerting (the way people work - not workflow or transactional communication) along with the ESSPs as having a large impact on the informal processes of organizations.

It's an interesting - Peter Drucker style - question to see how this plays out over time see my Drucker Centenary post which really should have been titled: "What questions would Peter Drucker Ask about Enterprise 2.0?"

On the 2.0 question: I always took the "2.0" of Web 2.0 as a tongue in cheek observation that the way people use the web and their expectations have shifted dramatically even though there is no "version" you can associate with the emergent phenomena we call the Web. "Who rolled the version?" on the Web is a funny and enlightening question.

I wouldn't expect organizations to use "2.0" as much more that a rallying cry, koan or plain old kick in the pants to take a look around and see what's changed. That's useful too.

Euan Semple commented:

Great post Andrew. I think what is happening IS a big deal but have been wary of labelling it Enterprise 2.0 as this makes it too easy to make it "other" and ignore it or assimilate it - bit like what happened to KM. I don't think our current methods of organisation are inevitable and I don't think we have even begun to see the effect of networked ways of thinking on how we relate to the world. This is why when asked recently how long I thought it would be before the full impact of what is happening works itself into organisational life I said fifty years.

I replied:

I agree with your 50 years - if you start the clock running with Doug Engelbart in 1968!

More seriously - for a major shift in enterprise use of technology I believe 10 years (from early adopter to common use) is closer : From "We have a Web Page" in 1993 to Web Commerce Bubble of 2001; Rare use of inter-enterprise email 1988 to universal by 1998; "Enterprise 2.0" in the broad sense 2006 to 2016. Pretty close to Engelbart + 50 years!

The evolution of the Web itself is an great example of an emergent phenomena. It started from TBL's very austere protocols and concepts though unpredictable and intertwingled rounds of innovation in how the Web was used the tech layered over it (search engines+), see Reinventing the Web for my view as early Web skeptic.

I believe the motivation for changing informal processes of organizations will come from a combination of: 1) people's expectations on how things can and should work from their direct experience with the public Web (as well as internal examples); 2) a measure of strategic thinking about how patterns of work and management can change based on new technology and expectations - in the spirit of Drucker and Engelbart.

Very few individuals in an enterprise are experts in ERP / MRP / Supply Chain Management etc so the feedback and demand cycles that drive human factor improvement and evolution of these systems are very weak. I have very few constructive comments on improving my payroll system and only whine about its eccentricities and complexity.

However everyone is a social animal and brings that experience to work every day. That's the "social" in social software that will drive evolution and adoption of new enterprise technology - with the public Web as a practical benchmark.

Euan replies:

I'm sticking to 50 years from now! I was thinking of the impact on how we structure organisations rather than just common adoption of technologies. Still think that will take a long time.

If I'm wrong I hope I'm around to settle the bet in fifty years!


Tuesday Dec 9, 2008 | Forty years after the Mother of All Demos
And here's what Enterprise 2.0 looked like in 1968 | Dealing lightning with both hands...

Peter Drucker and Enterprise 2.0 | Drucker Centenary

November 19, 2009 · · Posted by Greg Lloyd

ImageEarlier this week Oliver Marks wrote an excellent post on his Collaboration 2.0 Blog: 'The Purpose of a Business is to Create a Customer' - Peter Drucker Centenary. Oliver celebrates the Nov 19, 2009 Centenary of Peter Drucker's birth with two of his favorite Drucker bumper sticker quotes: " ‘Knowledge has to be improved, challenged, and increased constantly, or it vanishes‘ and ‘There is an enormous number of managers who have retired on the job‘, which somehow seem to fit together very well." then uses these quotes as context to discuss the disturbing findings of the 2009 Shift Index report and followup analysis by John Hagel, John Seely Brown and Lang Davidson of the Deloitte Center for Edge Innovation. Please read Oliver's full post - you'll like it. Oliver was also used kind words to build on my earlier Enterprise 2.0 Schism post. Here's a slightly extended version of the comment I posted in reply, along with my two favorite Drucker bumper sticker quotes and several links to celebrate Drucker's birth and life.

Thank you for the kind words and for pointing out the HBR Drucker Centenary issue. My "Enterprise 2.0 Schism" post was fun to write - with tongue firmly in cheek - as you note. But it also expresses some serious beliefs.

For me the key Drucker quote is: "The purpose of an organization is to enable ordinary human beings to do extraordinary things."

The scale shift that ubiquitous Web tech enables as well as bottom up participation in E2.0 initiatives are both necessary - but neither are sufficient to distinguish "Enterprise 2.0" from the Web we see and use every day outside work. I believe the difference lies in the shared purpose which drives people to create or join an enterprise and work together over time, along with the need to manage use of scarce resources to a shared end.

By definition an enterprise is a purposeful undertaking that generally requires many hands, expertise and capital that aren't easy for a non-purposeful group to gain and apply over time. This make the "social ecology" of an enterprise different from other groups.

In saying "2.0 modifies how the Enterprise works, not the technology," I take the rhetorical position that the technology which underlies E2.0 - specifically the ubiquitous Web as a platform - is a necessary enabler which provides the first chance to practically apply many of the principals of open work, distributed work and effective collaboration over time that Drucker and Engelbart have advocated for the past fifty years.

I believe that emergent phenomena which Prof Andrew McAfee includes as a core part of his definition of Enterprise 2.0 are significant and different in kind and structure from anything seen before in any enterprise - based on the speed, scale, simplicity and ubiquity of the technology combined with expectations and experience grounded in the public Web. Speculating on how management could embrace but not squash these phenomena to "create more customers" is a good Druckerian question.

But I also believe that the most likely path to large scale adoption and use of this enabling technology will come from small to mid size groups within an organization who intentionally use it to improve their own ability to get work done - rather than in direct pursuit of emergent benefits. They can (and by mandate should) open the direct and indirect record of their work to others who then may become better aware of what their enterprise plans to do, is doing or has done - and who knows what. I really like Jon Udell's term for this principal: Observable Work.

I believe this bottom up and pragmatic adoption model parallels lessons learned from bottom up Knowledge Management versus the failure of top down KM, and lessons learned from the history of the simple, practical Web itself versus failed dreams of more sophisticated universal hypertextuality.

The benefits that are new in kind are emergent, but the path to broad adoption and acceptance will be based on mutual consent, compelling benefits to those who do the work, leadership, and experimentation in activities that have a clear business purpose - designing, building, selling, maintaining products, providing services to clients, customers and partners.

It's presumptuous to guess what Peter Drucker would say about the relationship between the technology, techniques and phenomena we call Enterprise 2.0 and its potential to change the patterns of work and management of an enterprise.

But I believe it's fair to ask: "What sort of hard questions might Peter Drucker ask?" David Rendall (of the UK's National Health Service, Orkney) tossed a nice Druckerian question to Carmen Medina during the followup discussion to her Enterprise 2.0 and the Context of Work keynote at TUG 2009 last month:

#tug2009 Question for Carmen: how do those collaborative networks balance with clear lines of responsibility e.g. in healthcare? from TweetDeck @davidrendall

For example, the decision on course of treatment for a particular patient is yes or no and may be life and death. You want many people to be able to contribute to that decision - including the patient - but ultimately someone has to accept responsibility for that outcome. In all enterprises decisions between mutually exclusive courses of action need to be made - up to and including "bet the company" decisions.

See the video (time 68:20) for David's question. Then follow Carmen's response and a fascinating discussion that includes FAA experience in understanding and mandating training on cockpit resource management to make air crews aware of how to communicate effectively in high stress situations. Planes have literally flown into mountains when a junior officer was not willing or able to alert a senior pilot to a critical issue while the senior pilot was dealing with the same or an unrelated emergency.

Drucker would hold management ultimately responsibility for the course of action and outcome. But how to make best use of the experience and judgement of a distributed, experienced and self-directed organization is not a simple question, particularly in a crisis such as the mortgage credit crisis (or South Sea Bubble) where madness rather than wisdom of crowds is part of the problem. In my opinion Drucker was often at his best when expressing and defending contrarian opinions that he considered morally right as well as intellectually correct. See Schumpeter and Keynes which Drucker wrote on the Keynes Centenary.

Drucker makes the point that innovation in how an enterprise (profit or non-profit) works - how it provides motivation, support, leadership and resources to its members to "Create a Customer" - is as important as innovation in whatever else an enterprise delivers.

I hope we'll see more good work (like John Hagel & John Seely Brown's The Only Sustainable Edge) that focuses on E2.0 style business innovation based on Drucker's understanding of what drives success.

PS - My second Peter Drucker bumper sticker quote for the day: "A manager's task is to make the strengths of people effective and their weakness irrelevant--and that applies fully as much to the manager's boss as it applies to the manager's subordinates."

Peter Drucker Centennial

'The Purpose of a Business is to Create a Customer' - Peter Drucker Centenary Oliver Marks, Nov 16, 2009

Entreprise 2.0 : Les promesses du management moderne enfin tenues ? Cecil Dijoux, Nov 11, 2009

Drucker Centennial Week Celebration ( - The Drucker Institute, Claremont Graduate University

The Drucker Centennial ( - The Drucker Institute
[ Drucker photo credit ]

The Drucker Centennial - Harvard Business Review, Nov 2009

Books and articles by Peter Drucker

Management: Tasks, Responsibilities, Practices - Peter Drucker (Paperback edition 1993)

The Essential Drucker: The Best of Sixty Years of Peter Drucker's Essential Writings on Management (Collins Business Essentials) (Paperback 2008)

The Theory of Business - Peter Drucker, HBR Sep-Oct 1994 ($)

Schumpeter And Keynes - Peter Drucker, Forbes May 1983 (cover story) A superb essay comparing the two greatest economists of the 20th century, written in the centenary of Keynes birth. A Drucker classic on the relationship between economics and innovation.


Enterprise 2.0 Schism

CIA and the NHS: Common features of “high risk, high reliability” organisations - David Rendall, A Web that Works, Nov 3, 2009

Carmen Medina: Enterprise 2.0 and the Context of Work | TUG 2009 Keynote

As We May Work - Andy van Dam

Mind, heart and hands: Lifelong learning and teaching in the digital age - Jon Udell on what he memorably calls the principal of Observable Work April 2009

Reinventing the Web

Enterprise 2.0 - Letting hypertext out of its box

Traction Roots - Doug Engelbart

Enterprise 2.0 Schism

November 9, 2009 · · Posted by Greg Lloyd

Image I have to confess that I've enjoyed watching recent rounds of Enterprise 2.0 discussion and mud wrestling. The fact that so many people enjoy debating definitions, values, doctrinal principals - even the existence of Enterprise 2.0 - makes me think that E2.0 might best be framed as a religious debate. With that in mind, I'd like to introduce a new and exciting element: schism.

I hereby declare myself an Enterprise 2.0 Strict Druckerian. I believe that "2.0" should be considered a modifier of Enterprise rather than an allusion to mere Web 2.0 technology - which is what an Enterprise 2.0 Strict Solutionist would have you believe.

I further declare: No, it is not "all about the people" - which is what an Enterprise 2.0 Strict Proletarian would have you believe. Without the enabling technology of the Web, plus search engines and other affordances based on Sir Tim Berners-Lee's innovation, the Strict Proletarian would find it difficult to fit the inhabitants of McAfee's inner, middle and outer rings into the same room, get them to participate in the same conference call, or exhibit their "emergent" behaviors using typewriters, copy machines, faxes and email. Speed, scale and connection patterns matter and the technology that spans these barriers is neither trivial nor insignificant to the phenomena Strict Proletarians value.

I believe that although both technology and broad bottom-up participation are necessary to achieve the Drukerian vision, neither element alone is sufficient to achieve the noble end of re-engineering how ordinary people work together to achieve the ends of enterprises they choose to affiliate with.

As Peter Drucker said: "The purpose of an organization is to enable ordinary human beings to do extraordinary things." Management: Tasks, Responsibilities, Practices Chapter 28, The Spirit of Performance, p. 361 (1974)

I nominate Peter Drucker and Douglas Engelbart as Patron Saints of Enterprise 2.0 (Strict Druckerian). If you don't know who either of these gentlemen are, I suggest you click their Wikipedia links for two pretty good short biographies.

Peter Drucker constantly advised businesses to give employees direct control over their own work and environment, with teams of "knowledge workers" responsible for work toward goals stated as broad business objectives rather than prescriptive plans. Drucker stated that management could only achieve sustainable profits by treating people as an enterprise's most valued resources, not as costs. In later years he described his role as "social ecologist" rather than management consultant.

"Marketing alone does not make a business enterprise. In a static economy there are no business enterprises. There are not even businesspeople. The middleman of a static society is a broker who receives his compensation in the form of a fee, or a spectator who creates no value.

A business enterprise can exist only in an expanding economy, or at least in one that considers change both natural and acceptable. And business is the specific organ of growth, expansion and change.

The second function of a business is, therefore innovation - the provision of different economic satisfactions. It is not enough for the business to provide just any economic good and services; it must provide better and more economic ones. It is not necessary for a business to grow bigger; but it is necessary that it constantly grow better...

Above all innovation is not invention. It is a term of economics rather than technology. Non technological innovations - social or economic innovations - are at least as important as technological ones.

In the organization of a business enterprise, innovation can no more be considered a separate function than marketing. It is not confined to engineering or research, but extends across all parts of the business, all functions, all activities." Peter Drucker, Management: Tasks, Responsibilities, Practices (1974)

At a 1934 Cambridge seminar by John Maynard Keynes, "I suddenly realized that Keynes and all the brilliant economic students in the room were interested in the behavior of commodities, while I was interested in the behavior of people." Peter Drucker, The Ecological Vision, p. 75-76, (1993)

"A manager's task is to make the strengths of people effective and their weakness irrelevant--and that applies fully as much to the manager's boss as it applies to the manager's subordinates." Peter Drucker, Managing for the Future: The 1990's and Beyond (1992)

In an equally distinguished career, Douglas Engelbart has been enormously influential in creating and inspiring the creation of technology we use today (far beyond his invention of the mouse), but Doug's goals have always been expressed in terms of improving the abilities of groups to address complex, difficult and important problems:

"By 'augmenting human intellect' we mean increasing the capability of a man to approach a complex problem situation, to gain comprehension to suit his particular needs, and to derive solutions to problems. Increased capability in this respect is taken to mean a mixture of the following: more-rapid comprehension, better comprehension, the possibility of gaining a useful degree of comprehension in a situation that previously was too complex, speedier solutions, better solutions, and the possibility of finding solutions to problems that before seemed insoluble. And by 'complex situations' we include the professional problems of diplomats, executives, social scientists, life scientists, physical scientists, attorneys, designers--whether the problem situation exists for twenty minutes or twenty years. We do not speak of isolated clever tricks that help in particular situations. We refer to a way of life in an integrated domain where hunches, cut-and-try, intangibles, and the human 'feel for a situation' usefully co-exist with powerful concepts, streamlined terminology and notation, sophisticated methods, and high-powered electronic aids." Douglas Engelbart Augmenting Human Intellect: A Conceptual Framework, Introduction, (1962)

On the term "social software", I believe it's fair to blame it on Clay Shirky - who had the misfortune to introduce a term that's perfectly respectable for a sociologist who studies how technology influences group behavior:

“It's software that supports group interaction. I also want to emphasize, although that's a fairly simple definition, how radical that pattern is. The Internet supports lots of communications patterns, principally point-to-point and two-way, one-to-many outbound, and many-to-many two-way.” − Clay Shirky, A Group Is Its Own Worst Enemy O’Reilly Conference (April 2003)

If the term "social" must be deprecated, I hope its banishment takes with it all Social X marketing buzzwords, job titles, twitter tags, and the well-earned disco ball reputations of the so-called Social Media gurus.

On "Return on investment" debates, I believe that Taylorist time-and-motion studies would show gains that exceed the modest costs of introducing and using Enterprise 2.0 software. However, for knowledge work where the potential business value is much greater than transactional (e.g. reduced time to handle a purchase order) value studies are difficult to design and far too easy to fudge. Long term experimental studies measuring business improvement are even more difficult:

"A very important surgeon delivered a talk on the large number of successful procedures for vascular reconstruction. At the end of the lecture, a young student at the back of the room timidly asked, 'Do you have any controls?' The great man hit the podium and said, 'Do you mean, "Did I not operate on half the patients?"' ... The hall grew very quiet and the voice at the back of the room very hesitantly replied, 'Yes, that's what I had in mind.' The surgeon's fist really came down as he thundered, 'Of course not, that would have doomed half of them to their death!'...The room was then quiet, and one could scarcely hear the small voice ask, 'Which half?'" - Dr. E. E. Peacock, Jr., University of Arizona College of Medicine; quoted in Medical World News, p. 45 (September 1, 1972) quoted by Edward Tufte in Beautiful Evidence (2006)

I believe the value of Enterprise 2.0 techniques comes from small to mid size groups within an organization who intentionally strive to improve their own ability to get work done, while opening the direct and indirect record of their work to others who then may become better aware of what their enterprise plans to do, is doing or has done - and who knows what.

Finally - having demonstrated the unerring truth of the Strict Druckerian position regarding the nature of Enterprise 2.0, I declare both the Strict Solutionist and Strict Proletarian interpretations to be false, heretical, and anathema. Living in our tolerant and civilized times, I found it difficult to imagine an appropriate way to separate those who obstinately cling to these heretical beliefs, until I ran across this nugget:

Nike does "email archeology" to decompose email thread to expose one part of a specific collaboration. :>) @lehawselive (4:20pm Nov 4, 2009)

So if you don't agree with me, I hope you spend the the rest of your corporate life decomposing email threads from your corporate archive into Google Waves or Traction TeamPage comments where others can benefit from your labor if not from your ideas.


[ And so much more. It's the Web - you could look it up - or follow the fun on Twitter ]



This was far too much fun to write. I hope I haven't needlessly offended anyone, but I'm also happy to defend the essence of the Druckerian position in more serious terms; Enterprise 2.0 is a big tent and I hope it stays that way.

I also value the term Enterprise 2.0 for a reason over and above the Druckerian fantasy. Unlike terms invented to express a desire to sell software to managers (X Management - you do want to manage X don't you?), Enterprise 2.0 expresses a simple, grounded wish:

"I wish the software I used every day at work allowed me to find what I want; discover what I need to know - along with surprises; and connect with people I don't even know to get my job done, learn more, and work in an enjoyable place." or much more narrowly: "Why can I find what I need with Google on the Web, but have to pull teeth to find anything useful when I go to work?"

This is a grounded wish since everyone in business has a direct basis for comparison - what they or their children see, use and enjoy on the public Web every day. This doesn't mean that expectations, behavior, and (uh sociology) of the public Web and the internal/external web of connections used in an enterprise are the same - but they are comparable with respect to desired experience.

To the extent that corporate barriers dash expectations, read Peter Drucker on how to get rid of those barriers or find a better employer.

To the extent that enterprise technology differs with respect to needs for privacy, finding information in a link-deprived environment and sharing access to confidential sources or legacy applications, Enterprise 2.0 offers the opportunity for vendors and community projects to create products that respond to that simple, grounded wish and measure the difference.

I'm not sure where Professor Andrew McAfee sees himself in this ecclesiastical model. I'd be happy to support his claim to any sub-numinous position.

Update Remembering Doug Engelbart, 30 January 1925 - 2 July 2013

Update 6 Jun 2013: In the original version of this post I used Strict Technarian to refer to those who believe there is a purely technical - specifically Web or Internet - solution to every problem. Since then the term solutionist has gained popularity, generally through the acerbic criticism of Evgeny Morozov. I switched the awkward Technarian to Solutionist.

Although I don't agree with all of what Morozov says - or the way he says it - I believe solutionist is a useful term. See James Temple's 3 April 2013 column Why Silicon Valley needs critics like Morozov

Update 21 Nov 2014: Enterprise 2.0 - Are we there yet? Is there a 'there' for Enterprise 2.0, or is it more like shaking a sleepy beehive?

Introducing Proteus (demo)

November 2, 2009 · · Posted by Greg Lloyd

Traction Software Director of User Experience Michael Angeles introduces Traction's new Google Web Toolkit (GWT) based Proteus user interface with a brief tour (video below).

See also

TUG 2009 Providence | Thank you!

November 2, 2009 · · Posted by Greg Lloyd

ImageI'd like to thank all of the Traction customers, partners and friends who traveled to Providence last month to make TUG 2009 Providence as enjoyable as it was enlightening. Special thanks to keynote speakers Carmen Medina, Chris Nuzum, Stewart Mader and all of the customers and partners who participated in the Oct 14 Main event. And my personal thanks to everyone on the Traction Software team who worked so hard to bring TeamPage R4.2, the Oracle RDB backend, Attivo Advance Search, and the Proteus Google Web Tookit (GWT) UI to life. I don't know what we'll do to top TUG 2009 next year - but TUG members provides some excellent ideas! See TUG 2009 Providence | Keynotes by Carmen Medina, Chris Nuzum and Stewart Mader for links to TUG videos, slide shows, interviews, tech talks and more, along with how become a TUG member and join the conversation. TUG registration is free and open to the public.

ImageYou're also welcome to review the the TUG 2009 dinner menu at Gracie's Restaurant in Providence. This year we had an outstanding five-course tasting menu with paired wines at one of Providence's best restaurants. Gracie's was kind enough to give TUG folk the main restaurant when we outgrew the event room. In past years, TUG events featured two full McGrath's Rhode Island clambakes (lobster, clams, mussels, corn etc seaweed steamed over a hardwood fire) and a crab fest. Between Gracie's and the good folk at the Hotel Providence, TUG members this year were well nourished physically as well as mentally and we'll carry on the tradition at future TUG events!

Where's Greg?

October 21, 2009 · · Posted by Greg Lloyd

ImageYou may have noticed a slow down in blog posts by Jordan and myself, and attributed that to our work for TUG 2009 Providence last week, and you'd be partially right (but it was fun - as you'll learn). You can also blame our slower blog posting to time spent on Twitter, both as individuals: @roundtrip (Greg Lloyd) and @jordanfrank and using the Traction Software corporate feed @tractionteam (which broadcasts the title and a shortened link to new content posted on as well as original tweets).

I'll continue to blog notes that take more than 140 characters here. But for peek at what's I'm tweeting about Enterprise 2.0, KM and more with my trusty iPhone while having coffee at Seven Stars bakery, please follow @roundtrip. Here's a sample of recent tweets:

ImageOn Twitter you can also follow the Traction-Software List of Traction's team members, customers and friends. See Explaining Twitter - One of Three Places for People on how I use Twitter, Facebook and Traction TeamPage every day.

Structuring for Emergence

September 23, 2009 · · Posted by Jordan Frank

Enterprise 2.0 Social Software is appealing for many reasons, but a core value is the facilitation of emergence. Many in our community may quibble with McAfee's definition of Enterprise 2.0 but I think all will agree that the need to support emergence is a key trait. However, an emergent discussion shines a light on the interacting role of structure and emergence.

Bas Reus started the discussion with Self Organization Defined which gathered 42 comments. He continued with our interview, and a really nice interview inspired write up on Coordinated Chaos. Paula Thornton continued with E2.0: Unleashing the Potential where she says structure should be "Minimized, not Eliminated." In comparison to a lava lamp, Thornton says "Emergence does not evolve from nothing -- it requires structure."

In fact, structure lays the stage for the emergent outcomes - and can lead to very different consequences. The Emergence page in Wikipedia talks about how emergent order relies on the interaction rather than co-existence of the parts that come together in a system. In Thornton's lava lamp example, its the interaction of goop and liquid in a closed system of a certain shape and temperature that make the emergent outcome effective in its goal of being delightful to the eye.

Similarly, the Emergence page in Wikipedia, uses the example of ripple patterns in a sand dune. Sand and wind alone do not create the ripples. There are wider forces including the overall weather patterns and the shape of the underlying earth that leave this dune with a beautiful, emergent, pattern rather than a pile of sand.


Emergence is especially appealing to people who've come from rigid software systems which demand that work flows go through a prescribed process. It makes people work through a prescribed flow rather than work in the flow of content and dialog.

As one concrete example, I just got off the phone with a Fortune 100 customer who has happily made the transition from a document approval process done in a workflow system, to an approach where documents for approval are posted for anyone to comment and then considered approved when enough of the right people have weighed in. Their comments act as a digital signature and compliance goals (in their context) are met. This is a simple, emergent process, that frees the group from having to constantly fine tune the rules of a rigid workflow system.

In a project management case, Glen Alleman, the blogger at Herding Cats, just posted PM 1.0, PM 2.0, How About Just Project Management where he argues that "irrational emergences has little chance of succeeding, no matter the current buzz word tool or process." It's not adequate to drop a project team in a Wiki, there are certain basic artifacts and structures that will point the emergent discussions and collaborative content development in a direction that results in emergent order rather than chaos.

To enable a collaborative culture, all arrows seem to point to a conclusion that Control Doesnt Scale, but that you have to balance best practices and starting structures to achieve the most fluid, most intuitive outcomes that facilitate collaboration rather than confuse it with starting structures (or lack thereof) that misalign the natural processes that are used to work in the flow of communication and collaborative content development.

2.0 Adoption Council | Neat Tweet!

September 22, 2009 · · Posted by Greg Lloyd

Susan Scrupski (aka @ITSinsider) tweets Sep 22, 2009: reading a great preso by a Council member. great testimony for e20 vendor Traction Software @TractionTeam

Thanks Susan! Susan recently founded the 2.0 Adoption Council to bring together managers of large enterprises who are early adopters of Enterprise 2.0. See this 2.0 Adoption Council Intro. She describes the Council:

We are a collection of managers in large enterprises that are charting the course for 2.0 adoption. Although we may use different platforms and tools, we all share a common enthusiasm for bringing a new way of working to our representative companies. We call ourselves “internal evangelists” and some say we have one of the most difficult, yet exciting jobs in the global marketplace...

The 2.0 Adoption Council is a self-service community of passionate early adopters. From members with over 100K seats under management to members experimenting with departmental deployments, we all share a common goal of delivering 21st century collaboration and social connectivity to the enterprise. In a recent survey, our members indicated 36% are managing budgets between $500K and $1M; although another 40% is still in the planning stages and can’t assess their total budget spend.

... We are not admitting sellers of IT software or hardware products, consultants, agencies, press, or analysts into the 2.0 Adoption Council. The group exists as strictly a peer support channel for customers to help each other and share experiences. We will be launching an external community soon for all friends and fans of the global enterprise 2.0 movement.

To apply to become a member of the Council, send us an inquiry on LinkedIn and we will get back to you in 48 hours.

We're delighted that Traction TeamPage customers are active and articulate members of this Council, and encourage Enterprise 2.0 early adopters to follow @20Adoption and join the 2.0 Council.

To hear more from Traction TeamPage customers - and two great Enterprise 2.0 keynotes - also put the 13-16 October 2009 Traction User Group Conference on your calendar!

As We May Work - Andy van Dam

September 7, 2009 · · Posted by Greg Lloyd

On April 17, 2008 Professor Andy van Dam of Brown University delivered the keynote address of the Enterprise 2.0 Summit 2009 Tokyo. Andy's title is a play on Vannevar Bush's July 1945 essay As We May Think. As We May Think inspired creation of pioneering hypertext systems by Andy, Ted Nelson, Doug Engelbart and others, leading to Tim Berners-Lee and the World Wide Web. The creators of these hypertext systems originally envisioned an environment where individuals could write, link, comment on and share what they wrote as well as search and read what others had written - core capabilities of what we now call social software for the public Web or an Enterprise. Andy's keynote is a personal history, and a vision of how the Web provides a new context for work as well as public communication, socialization, commerce, scholarship and entertainment. For the full slide set see As We May Work (.ppt 8.8MB), posted here with Andy's permission.





I've known Andy since 1967 as a teacher, friend and trusted advisor, and thank him and Rosemary Simpson for their thoughtful work on this presentation.


The Rise of Enterprise 2.0, Andrew McAfee | Video | Enterprise 2.0 Summit 2008 Tokyo
Enterprise 2.0 - Letting hypertext out of its box
Reinventing the Web
Traction Roots - Doug Engelbart

Is Twitter Like Going Out for a Smoke? - And Other stories

September 3, 2009 · · Posted by Greg Lloyd

Bill Ives posted an interesting post Is Twitter Like Going Out for a Smoke?, responding to a Twitter / Water Cooler analogy by Arie Goldshlager and a smoker's network analogy pointed out by Stewart Mader and Gil Yehuda in Lessons from New York Smokers. I commented: Bill -- An interesting post and topic! I think there's likely an interesting history (and sociological studies) of how informal groups form and cross-link in businesses and other organizations.

The most interesting groups seem to be cross-functional and distributed - with some difficulty before the Web and email, with less difficulty now.

A few examples:

1) Watercooler - physically collocated, somewhat cross-functional (but often cube neighbors)

2) Smokers - physically collocated, cross-functional and cross-hierarchical

3) IT Tech support, Admin Assistants - folk who talk a lot with a wide variety of others in the enterprise, and have their own network or grapevine of contacts with their peers.

4) The NCO / Chiefs network - Anyone whose been in the military knows that NCOs (Sergeants and Chief Petty Officers) use an informal network of local - and globe spanning - contacts who know what's up and how to make something happen. This probably dates to Roman times.

With the advent of cheap and ubiquitous Web technology, it has become easier for networks to form, keep in contact, and scale beyond previous limits of space and number of participants.

Is there a Doctor of Sociology in the house with a few good references?

A few of my notes with links on

Connections & McAfee Bullseye model of strong, weak, potential ties

Twitter: world's largest floating cocktail party, coffee break, and trade show happy hour
Explaining Twitter - One of Three Places for People

[ In the interests of non-smokers and former smokers everywhere - no smoking photo with this post! Join the followup conversation on Twitter ]

Project Artifacts - Risks, Issues, Questions, Requirements and more

August 14, 2009 · · Posted by Jordan Frank

Glen Alleman at Herding Cats offers really nice distinctions in Risks and Issues Are Not The Same. In the course of working with a lot of teams as they deploy TeamPage as a project wiki, I've seen a wide range of terms for project artifacts. The more these concepts are discussed and hashed out, the better.

To risks and issues, you can add questions, requirements and ideas.

In some contexts, the terms are changed but mean the same thing. For example, in a software development shop, Requirements are Features and Issues are Bugs.

Quoting a DOD Risk Management Guide, Alleman describes risks as "a measure of future uncertainties in achieving program performance goals and objectives within defined cost, schedule and performance constraints."

He describes an issue, by contrast, as "impediments to the progress of the project."

As he notes, people often have a hard time distinguishing between risks and issues. For that matter, there is a fuzzy line between issues and questions.

When I helped John Evans at ShoreBank deploy his TeamPage system for IT Project Management, we spent considerable time figuring out which artifacts he would need in his project wiki and blog. I wasn't sure if we should include both Questions and Issues - and though that if he could tell me the difference, then we could use both.

"John, what's the difference between a Question and an Issue?"

"That's easy. Issues are showstoppers. Questions are accelerators."

That was as good a distinction as any, so we included both items. Characterizing Issue as show-stopper in John's terms or impediment in Glen's terms works really well. Over at KUKA Systems, the enterprise applications teams setup an Issues blog for each enterprise system. This opened the door for people to contribute and characterize issues as they came up, and a transparent way for the team to comment back on how they will be resolved.

Here is a list of basic project team artifacts that teams may include a in a blog or a wiki:

  • Milestone: A point in time (that often moves!!) around which a set of requirements and other project artifacts and activities are aligned.
  • Requirement: A description of a actions or processes that must be taken to solve a problem. Alternate terms may (accurately or inaccurately) include feature, specification, or objective.
  • Risk: Defined above as a measure of future uncertainties in achieving program performance goals and objectives within defined cost, schedule and performance constraints.
  • Issue: An impediment or showstopper along the road to building against the requirements associated with a milestone. An issue may be the manifestation of a Risk.
  • Idea: The alter-ego of an issue, an idea is a suggestion for actions or changes that will improve a system that is working or otherwise on track to be built. An idea may turn into a requirement or be referenced by a separate requirement.
  • Question: A knowledge accelerator. Usually, a person can figure out the answer to a question through experimentation or research - but can get a faster, better answer by asking a crowd.
  • Status Report: An update on progress against requirements, issues, and other activity.
  • Bulletin: A resource that is an important touchstone in the project. This may include a basic working policy, documentation of a team process, or other key information.

When it comes to wiki and blog technology as the basis for project team collaboration and communication, there is a good fit because of how all these artifacts are continually updated, reflected upon, and added to a system. In that light it's obvious how the context offered by a wiki and blog approach beats "traditional" project team tools which generally include email, word documents and task lists.

Skiing on the Slope of Enlightenment

August 12, 2009 · · Posted by Jordan Frank

At our market launch in 2002, I recall all kinds of skepticism passing off the wiki and blog markets as a fad. Today, with a complete social software platform and the most robust wiki framework on the market, we are skiing on Gartner's Slope of Enlightenment. Gartner reports that Social Software suites are headed for the trough of disillusionment (a good and necessary transition before hitting the slope of enlightenment), though our customer case studies show little illusion about the tangible and necessary business value delivered by Traction TeamPage. » Read Gartner's press release and ReadWriteWeb's report. ReadWriteWeb's writeup.

Compliance and Enterprise 2.0 - For the right reasons

July 13, 2009 · · Posted by Greg Lloyd

ImageBurton Group analyst Mike Gotta writes Compliance Doesn't Sell E2.0 … But It Should in his personal Collaborative Thinking blog. Mike summarizes a June 2009 E2.0 conference interview with Alexander Howard, quoted in Compliance concerns dog Enterprise 2.0 collaboration platforms. Howard asks:

Can an enterprise leverage collaborative software like blogs, wikis and microblogging platforms and retain compliance? It can, if collaboration platforms are built in-house from selected technologies, as opposed to an all-in-one suite from an Enterprise 2.0 (E20) vendor. Enterprise 2.0 compliance, in other words, is something best baked in from day one?

Mike says:

"The enterprise is tougher than consumer environments because of so many contrived regulations. There should be higher expectations of the enterprise 2.0 vendors to prioritize the features that will help enterprises manage compliance."

When asked if E2.0 Vendors "get" compliance, Sameer Patel said:

"Nope, not yet. It may be overkill, but spending 10 minutes with enterprise content management vendors or the IBM collaboration group exposed how little E20 has attended to this."

I certainly agree that Enterprise 2.0 compliance is something that needs to be "baked in" rather than tacked on. In my opinion, failure to address compliance and security can block use of Enterprise 2.0 technology in contexts where the greatest value, greatest potential for innovation - and most sensitive information - lives.

And I'll claim that Traction Software really "gets" compliance for reasons that accept, but go beyond regulatory requirements.

An ad-hoc wiki used solely within an IT department may not need much more than the basics. But to use Enterprise 2.0 technology widely within or crossing firewalls, authentication and security (including permission models around activity streams) are absolute requirements - particularly for highly regulated industries such as health care, pharma and finance.

Boundaries that make sense, WebDAV file versioning, Page / content moderation, audit trails and other compliance related capabilities are also crucial when working with external clients (including supplier and resellers as well as customers) or in contexts such as R&D or project management where the payoff for Enterprise 2.0 innovation is greatest, and the distinction between work-in-progress collaboration and an internal or externally binding agreement (or consensus) is important.

It's great to have wiki pages open for general editing wherever possible. It's also great to support the most open possible work-in-progress draft collaboration while creating a plan, budget, or other agreement that will be become binding on all parties when agreement is reached.

But it's also important to be able to distinguish pages that represent an agreement at a specific time - the approved budget, product specification, reseller agreement in a way that can't be confused with casual work-in-progress (or prankish) change.

People who want to be able to use wiki pages for reliable reference to the current approved budget, specification etc need to be able to distinguish the "last stable / approved version" and any work-in-progress drafts. Otherwise how would you know if a change that cuts the budget of a new project by 25% and schedule by 2 months is real, a proposed change, or just a prankish edit? If you're serious about using Enterprise 2.0 technology across the board, you need to address these issues to get work done, as well as satisfy the letter of the law.

Traction TeamPage has permissioned activity streams - for tag clouds, search results, email digests, RSS/Atom feeds and web navigation as well as microblogs. Features like WebDAV file versioning, Page / content moderation and detailed audit trails have been "baked in" to support use of Enterprise 2.0 technology in the context intentional as well as emergent practices.

"Baking in" support for these capabilities makes it possible to support wide open draft collaboration as well as "latest stable version" publication in the same collaboration space, as well as permission boundaries that disappear when you have permission to cross them but act as secure and reliable barriers when privacy counts. For example: clients of the same law firm can have separate spaces which become reliable barriers between clients but which slide down automatically for when members of the law firm with rights crossing all client spaces search, navigate, comment, link and tag anything they see.

Try to do this by slapping separate Social Software and ECM products together and you'll likely end up with something that works like JFK's description of Washington DC: "A city that honors the traditions of Southern efficiency and Northern hospitality."

We didn't go to all this work just to satisfy checklist requirements - I honestly believe it's what's necessary for widespread use and adoption of Enterprise 2.0 technology.

For more on related TeamPage features, see:

Boundaries that make sense - Patterns of collaboration.

Permissioned activity feeds - Including tag clouds, search results, email digests as well as rss / atom / microblog feeds

Moderation and work-in-progress collaboration - Enabling collaboration on content where consensus - or binding agreement - counts.

Audit Trail - Edits, tags, names, email and more.

And where this comes from Traction Roots - Doug Engelbart

How 1.5 is Greater than 2.0

July 9, 2009 · · Posted by Jordan Frank

I found Tom Davenport's discussion of Why 1.5 is Greater than 2.0 by way of Bill Ives in Mixing Old and New School Communication. Davenport talks about the social reasons in favor of a blend between social and traditional approaches. I think an answer to How 1.5, in this context, is Greater than 2.0 is both social and structural.

The Social Side of 1.5

Reinforcing the social example, Davenport says that when seeking therapy "You'd listen to what the medical establishment prescribes for your ailment, but you'd probably also check out blogs, wikis, and other patient-generated content and communities."

This cuts to the social issue where the Health 2.0 social community of patients augments the Health 1.0 information infrastructure born out of research and fact finding.

The "Web 1.0" approach in this context is, like traditional media, a (more or less) trusted system. Non-traditional news sources and blogs that don't have as much editorial oversight and don't have stringent guidelines for validation serve a social role by calling out traditional media while traditional media also serves as a validation backstop for rumor that could otherwise overwhelm social media.

The Structural Side of 1.5

The evolution of the Web 2.0 and it's Enterprise 2.0 counterpart is fascinating as the social and structural components reinforce eachother.

From a structural perspective, the "web 1.0" approach picked up where "KM 1.0" fell down. With a traditional taxonomic approach to organizing information, the web would be a different (and less useful) environment altogether.

That a flat, disorganized web of pages and links published by people operating independently could outperform a well planned information infrastructure was shocking to many but is a clear and obvious outcome.

In the "Web 2.0" scenario, blogs (and blog like systems like twitter) add more pages, more links and a timeline to the web. This just reinforces and improves upon the Web 1.0 structure.

Enterprises will lag as most haven't even gotten from KM 1.0 to Web 1.0 information approaches, but hopefully they can make up for it when deploying E2.0 in force. While doing so, a key takeaway for enterprises here is following a plan that relinquishes control while mixing "blog" conversation, "wiki" knowledge product, and ample opportunities to link and annotate enterprise information resources such as ERP, CRM, PLM and HR systems.

What's Social About Software? And Why It Matters.

June 25, 2009 · · Posted by Jordan Frank

Innovation starts with words, and ways to convey them.

Given a platform for communicating, Communities and Project Teams come together around the identification and discussion of problems and facts. The result is forward progress through Decisions, Plans and Discoveries.

Blog & Wiki page based publishing, with integrated discussion and tagging, open the door for innovation at a scale and with fervor we can only imagine.

See my presentation from Enterprise 2.0 2009 for more on the evolution of written communication and how blogs and wikis bring us up a re-usability, distribution and authorship power curve that will do for teams and communities what the printing press did for scientific communities.

Having versus Using Enterprise 2.0 Software

May 15, 2009 · · Posted by Greg Lloyd

Gil Yehuda wrote a very good post today Enterprise 2.0 Thoughts to end the week. He talks about Enterprise 2.0 maturity, second wave adoption, focus on work, and levels of the conversation. It's a great post you should read in full and reflect on. One particular point caught my attention; Gil says: "... having a wiki, forum, blogs, etc. on the intranet and using a wiki, forum, blog effectively to improve the transparency and productivity of collaboration are very different indicators of progress."

Businesses (or vendors) who say “We have a wiki; we have a blog; we’re an Enterprise 2.0 company” remind me businesses in 1995 who said “We have a web page; we’re an internet company”.

I like Andrew McAfee’s analysis in general and his specific observation - backed by studies that he cites: “… since the 1990’s a combination of the Web and IT spending on enterprise information systems has shifted the ability of businesses to recognize and deploy good ideas; that this has raised the pace and level of competition, making effective innovation more valuable, and more strongly differentiates winners and losers in competitive markets.

McAfee further claims that the Web and IT changes they analyze appear to be step functions:

This new, nastier competition does not depend on continued IT innovation. It only depends on continued managerial innovation. If all the technology vendors were to close up shop tomorrow competition in all industries would not eventually revert to where it was prior to the mid-1990s. The current IT toolkit lets companies propagate business ideas faster, more broadly, and with higher fidelity. That’s all that’s necessary to increase the pace of competition, and to keep it high. Of course, the tech vendors are not about to shut themselves down and we’ll see a lot more innovation from them; this will only serve to further increase competitive nastiness. But technology innovation is the icing on the cake of managerial innovation. - Andrew McAfee; Curb My Enthusiasm

The technology of Enterprise 2.0 is most significant as an enabler of new patterns of communication, collaboration and awareness that astute businesses can use to gain a sustainable competitive advantage. I believe this is very similar to W. Edwards Deming’s work which enabled businesses in Japan and the rest of the world to gain great competitive advantages by continual improvement of processes and systems.


Andy Keller talks about Traction's use of GWT | Video

May 13, 2009 · · Posted by Greg Lloyd

May 12, 2009 5:38pm rotkapchen Great explanation: Traction Director of Engineering Andy Keller tells why Traction's chose GWT (Google Web Toolkit) for TeamPage's new interaction layer. View video inline below or

Video by Paula Thornton, Experience Design Strategist
Twitter: rotkapchen
LinkedIn: iknovate

See where this choice led:
Traction TeamPage 5.0: Social Software for Work
Traction TeamPage 5.1: Social Software, Meet Project Management
Action Tracking and Project Management

And particularly Traction TeamPage Videos

#E2L09 Innovation Starts with Ideas. Wiki will Cross the Work 2.0 Frontier When TeamPage 5.0 Carries Ideas into Action.

May 8, 2009 · · Posted by Jordan Frank

These case studies are a taste of how ideas and issues turn into action, how tasks evolve from conversations and how boundaries have to appear to disappear for W2.0 ideas to meet E2.0 execution. See you at E2.0.

Can't stuff the Web back in a box ...

April 19, 2009 · · Posted by Greg Lloyd

On April 16 2009 Oliver Marks wrote The CIA's Collaboration Growth Curve & IBM's Lotusphere ecosystem connecting three topics: 1) the transformation of the CIA's collaborative practices; 2) how this relates to the concept of the collaboration curve introduced by John Hagel III, John Seely Brown (JSB), and Lang Davison, and 3) his reaction to IBM's Lotusphere Comes to You roadshow event in San Francisco that day. It's a great post which motivated me to add a comment which I expanded a bit below.

I've added one key quote for context on my comment - please read Oliver's full post for his insightful analysis.

Oliver writes:

John Hagel III, John Seely Brown (JSB), and Lang Davison discuss their concept of ‘the collaboration curve‘" on, and there are some interesting parallels to the cultural and process challenges of the CIA’s historically deep rooted processes, as they relate to Intellipedia.

There’s a classic story in economics primers illustrating the power of network effects. It tells how the first fax machine gave little value to its owner–after all, there was no one else with whom to send and receive faxes. As time went by, however, the value of that first machine increased as other people bought fax machines, and soon its owner could send faxes to the far corners of the earth, and receive them in return.

The point of the story is how the value of a node in a network rises exponentially as more nodes are added to it. These are called network effects.

Now let’s add a twist to the story. What would happen if, at the same time more fax machines joined the network, each machine rapidly improved its performance? The result would be an amplifying effect on the first level of exponential performance. One exponential effect occurs from growth in the number of nodes. A second amplifying effect arises from the improving performance of the machines themselves.

Fax machines, of course, don’t perform better as you add more of them to a network. But people and institutions do. And that’s where the concept of network effects gets more interesting–when we apply it to how people might perform better.

Oliver -- I think the three parts of this post fit together very well, particularly the network effects and the collaboration curve theme.

The JH, JSB, and LD quotes make the point: People and institutions are the 'nodes' that can enable a collaboration network to perform better as you add more of them to a social network ('social' in the broad sense - not party time).

But I think it's also important to note that the Web has become an open platform that allows the work product of collaboration networks to be created, linked, annotated, signaled, searched and analyzed at scale that would have been unimaginable in the heyday of Lotus Notes. In that respect the Web *is* like the "self-improving fax machine" whose limits we won't see for a very long time.

You muse: "... on the idea that the agility of modern enterprise collaboration techniques and technologies are arguably far more powerful when consciously assembled to achieve given objectives, as opposed to people attempting to work within the manufactured framework of a product suite, when watching the Lotus demos."

I believe that's right. In every previous generation hypertext system, the ability to read, search, link and communicate came with a terrible price: it might work well, but only if you were willing to put everything you wanted to work with into some sealed box, and convince everyone you wanted to work with to use the same box.

Ironically most successful collaboration box that the Web allowed people and institutions to escape was -- Lotus Notes. If IBM focuses on building a product suite rather than a platform that works with and like the web I think there's a problem.

See Enterprise 2.0 - Letting hypertext out of its box
based on a 2007 debate / discussion between - Mike Gotta and Andrew McAfee.

Enterprise 2.0 and the importance of Silo Smashing!

April 14, 2009 · · Posted by Jordan Frank

Recent posts by Michael Sampson, John Tropea and Thomas Vander Wal converge on the need for Enterprise 2.0 tools to smash the silos segregating content types and isolating workspaces.

Smashing Content Type Silos

John Tropea wrote about the need to unify the data model for blog posts, comments, and tasks to support natural cross-referencing - for example when you want to comment on a task, or turn an item mentioned in a blog post into an action to be tracked and performed.

All too often, collaboration platforms take an easy route when adding new functionality: they staple it on by creating a new table.

A collaboration platform originally built for file sharing may just add a new table space for blogs, another for Wikis, another for discussion, and yet another for tasking. In most cases, this low level decision is brought forward to the interface as a design constraint. Rather than allowing the flexibility to create dashboard views over any cross section of content and tags, these platforms will partition a workspace into "wiki" content, "blog" content, and even "discussion" content. This breakdown can be useful for navigation, but becomes a problem when it creates artificial barriers to cross-linking, tagging and commenting across different content types.

How We Solve the Problem: In TeamPage, all entries are created equal, even comments. Any entry may have items, tags, comments, attachments, and wiki page names. Comments and tags can be attached to any item in a post, page or comment. Display is handled by easily configured sections on the front page and each project workspace. In a customer example like ShoreBank, you can easily see where the "blog stream" of status reports, meeting notes, issues, and questions surround the "wiki islands" of milestones and requirements.

Smashing Workspace Silos

SharePoint 2007: Gateway Drug to Enterprise Social Tools may be one of the best blog posts of all time. Thomas Vander Wal does a good deed for the market by explaining a key problem with Sharepoint. To be fair, however, the problem he identifies is inherent in the many platforms that do not support interaction and views that span workspaces. He wrote:

Many who deployed SharePoint, thought it was going to be the bridge that delivered Enterprise 2.0 and a solid platform for social tools in the enterprise is summed up statement, “We went from 5 silos in our organization to hundreds in a month after deploying SharePoint”. They continue, “There is great information being shared and flowing into the system, but we don’t know it exists, nor can we easily share it, nor do much of anything with that information.” I heard this from an organization about 2 years ago in a private meeting and have been hearing near similar statements since. This is completely counter to the Enterprise 2.0 hopes and wishes they had for SharePoint...

One of the largest complaints is the information is locked in SharePoint micro-silos and it is nearly impossible to easily reuse that information and share it. Not only is the information difficult to get at by people desiring to collaborate outside the group or across groups, but it is not easily unlocked so that it can benefit from found in search. The Microsoft SharePoint model is one that starts with things locked down (focussed on hierarchies) then opens up, but unlocking is nowhere near as easy a task as it should be.

Essentially, Enterprise 2.0 is only as good as your ability to leverage content across workspaces. Vander Wal is reflecting the angst that many Sharepoint customers feel when they feel success coming on, only to confront the chaos that ensues when essential information burrows its way into 1,000's of micro-silos that don't offer ways to, in his words, "do much of anything with that information." It feels more like the warehouse scene at the end of Raiders of the Lost Ark than a step forward.

Permissions are an essential challenge in Enterprise 2.0 which is not present in Web 2.0. Web 2.0 generally envisions a set of public services like blogs, news sources, wikis, RSS feeds and Google searches.

While E2.0 models like Andrew McAfee's SLATES and his Second definition of Enterprise 2.0 are useful for explaining Web 2.0 and ideals for the enterprise, they tend to downplay the business need for of access controls and how this can limit bi-directional linking, social tagging, and signals. Supporting collaboration that, in Greg Lloyd's words, spans Borders, Spaces, and Places requires that a platform unify content types and boundaries that make sense, offering a set of features that work across spaces, rather than just within them.

How We Solve the Problem: My answer would be no match for Michael Sampson's when he wrote about TeamPage: Michael Sampson's Currents: "TeamPage - the One System to Rule It All". Sampson shares an example of how TeamPage's permission model supports boundary spanning conversation and tagging in the context of a single entry. That's the tip if the iceberg when it comes to presenting and delivering views based on any cross-section of content, workspaces, and permissions.

Mixing Tasks and Conversations, and KUKA as the "seminal enterprise 2.0 solution"

April 14, 2009 · · Posted by Jordan Frank

A tweet from John Tropea identifies our Kuka Systems case study as the "Seminal enterprise 2.0 task based / process solution." THANKS! I can't imagine a better endorsement of a case study, or the product supporting it.

With respect to the mix of task and process in Enterprise 2.0, I think John is referring back to an excellent entry he wrote about Conversations that revolve around task objects where he elaborates on how teams get together to tackle tasks and how software should support unification of the task and conversation stream. He wrote:

In a past post I suggested some social tools designed where each task object has a conversation stream. The task object itself can have comments, but also a forum or blog post may be tagged with the object ID, so when you look at the object, not only do you see it’s own comment stream, you also see blog and forum posts that refer to it (kind of like a trackback). I believe both Traction and Basecamp do something similar to what I just explained.

The Kuka case study explains how they use TeamPage to do just that: they allow anyone to post issues, support tracking of those issues, facilitate a conversation stream that relates comments and linkage between a taskified issue and anything referring to it.

Should Software Vendors Also Sell Professional Services? YES!

April 14, 2009 · · Posted by Jordan Frank

This conversation started with Stewart Mader and continues with Bill Ives. While most of our customers run the easy installer and are up and running readily, many benefit from our front end advice as well as more formal professional services engagements. This exchange offers two simple benefits that are strategic to the customers and to the software producer (and, in turn, to the customers).

1) Customers benefit from our best practice knowldge: Inasmuch as pure emergence is perfectly good ideal, a balance of structured collaboration and collaborative creativity is the Yin and Yang that combine to support success.

I spent some time with a prospect recently who installed TeamPage and started establishing workspaces with no problem. His first few steps were to make a workspace for each competitor. In just a few moments of discussion, we agreed he would be better off with a Market Research workspace containing a tag for each competitor. Despite anyone's judgement as to what % of collaboration success is attributed to Technology vs. People, getting the technology right and configuring it in such a way that meets rather than defeats a need is a Door 1 pre-requisite.

There is no question that our contribution to customers like ShoreBank, the Department of Defense, and a European Pharmaceutical Group made a material difference to their respective success with the platform.

2) We learn from working with customers: Besides building best practice knowledge with each successive customer deployment, closely working with customers helps to peel layers off an onion that reveals their needs and issues as well as a treasure-trove of ideas with respect to how we should develop solutions that meet those needs.

Sure, you can tactically improve your software by observing user behavior, looking at click streams, and analyzing system generated bug reports, but strategic improvements require intimate knowledge of customer's business problems, user issues, system environments, and complementary tool sets. Working on projects with customers helps to look and think well outside the box to deliver solutions that work.

I Can't Tweet & Trusting Online Services

March 30, 2009 · · Posted by Jordan Frank

ImageLast fall, I pointed out an issue of trust as part and parcel of Web 2.0 security (See What Web 2.0 and E2.0 Security Means to Me). When we accept social services like Facebook and Twitter as Two of Three Places for People, we entrust them to manage our data securely, to keep consistent terms (i.e. they don't suck us in and then suck us dry by starting to charge for basic services), and to be there when we need them. Today, I felt muzzled as I was touched by the uptime issue. I got this "over capacity" memo when I went to Tweet an answer to Dave Lamp's Question. I've received the "over capacity" messages several times and will continue, for now, to trust they'll iron things out over at Twitter HQ.

Reading blogs at 800 MPH

March 27, 2009 · · Posted by Jordan Frank

I took a long needed vacation last week and came back to the usual firestorm of post-vacation pile-up that makes one pause before entertaining the idea of another break. Anyhow, after meeting a few high priority deadlines, I had time this afternoon to review everything posted to our TeamPage server in the last 2 weeks.

After moving at a rate of 800 Messages Per Hour, for one hour, I am up to date and am only left with the 12 browser tabs that I launched for further review in the process.

The average over the time period, 80 articles or comments per day, is fairly normal for us yet it's still not hard to keep up with the message flow and routine email. On a busy day, we'll see as many as 161 new articles and comments (plus edits, attachments, tag changes and so on - see All in a Day's Work - The Magnitude of Collaboration).

Being able to stay on top of things and keep my e-mail box clean is just one way that I Address the Question of Enterprise 2.0 ROI.

Ada Lovelace Day | Professor Lee S. Sproull, Stern School, NYU

March 23, 2009 · · Posted by Greg Lloyd

For this first Ada Lovelace Day I've chosen to write about Professor Lee Sproull an internationally-recognized sociologist whose research centers on the implications of computer-based communication technologies for managers, organizations, communities, and society. Professor Sproull is a pioneer and visionary in the rigorous study of what we now call social software.

I heard Professor Sproull talk at the MIT/Brown Vannevar Bush Symposium celebrating the 50th Anniversary of Bush's As We May Think. After the symposium I read and enjoyed her 1991 book Connections: New Ways of Working in the Networked Organization (co-authored with Sara Kiesler). Connections is based on original field research, social and psychological experiments the authors performed to understand how computer based communication technology - email, bulletin boards, computer networks - changed the way people communicate, work together, and make decisions.

In her 1995 talk at the Bush Symposium, Information Is Not Enough: Computer Support for Productive Work, Professor Sproull said:

Any vision of a new technology implies a vision of human beings and their behavior. In this talk I describe the vision of human behavior associated with the most influential technology visions of personal computing, epitomized by Vannevar Bush's Memex -- the vision of the solitary thinker and problem solver. I contrast this vision with an alternative view of how human productive behavior actually occurs -- in interdependent social relationships. I review the current state of computer support for social actors and propose an alternative view in which information processing is subordinated to relationship managing. - Abstract

Professor Sproull conducted research in Fortune 500 firms, scientific communities, municipalities, universities, software development teams, households, and electronic groups. In all of these settings she has documented how technology induces changes in interpersonal interaction, group dynamics and decision making, and organizational or community structure. She has been a visiting scholar at Xerox PARC, Digital Cambridge Research Lab, and Lotus Development Corporation and has published the results of her research in eight books and more than sixty articles including Essence of distributed work: The case of the Linux kernel, First Monday Volume 5, Number 11, Nov 2000.

At present Professor Sproull is Vice Dean, Academic Affairs and Professor of Information Systems & Management, Lawrence N. Stern School of Business, New York University.

About Ada Lovelace Day
On January 5, 2009 Suw Charman made a pledge to publish a blog post about woman in technology that she admires, but only if 1,000 other people pledged to do the same. Suw named this Ada Lovelace day in honor of the world first computer programmer and author of the first description Charles Babbage's Analytical Engine. Suw wrote:

Ada Lovelace Day is an international day of blogging to draw attention to women excelling in technology. Women’s contributions often go unacknowledged, their innovations seldom mentioned, their faces rarely recognised. We want you to tell the world about these unsung heroines. Whatever she does, whether she is a sysadmin or a tech entrepreneur, a programmer or a designer, developing software or hardware, a tech journalist or a tech consultant, we want to celebrate her achievements.

See the Ada Lovelace Day blog for news and special events, including Ada Lovelace day at the London Science Museum

New: Meet meet Ada Lovelace herself in a video interview by the original Analytical Engine!

Explaining Twitter - One of Three Places for People

March 22, 2009 · · Posted by Greg Lloyd

Last week a friend who just signed up on Twitter said: "... just like Jon Stewart, I can't figure out how it works or why anyone would want to tweet or get anyone else's twitter. I had no idea what grunt and stalker is but I am assuming that is reality too. I put this all in the pocket with second life (stupid bulky awkward and totally useless)." So I reluctantly joined the crowd attempting to explain why people who have a job and have a life might be interested in Twitter. I decided to describe Twitter as one of three distinct places on the Web where I socialize every day: the public commons. The others two are my neighborhood and my workplace.

The mechanics of Twitter aren't hard describe: you can post short messages of up 140 characters ("tweets") with a name you choose on Twitter's site. There you can: read tweets made by people you choose to follow (as one merged stream); reply directly to any tweet with one of your own; let people follow whatever you tweet; see the profile of anyone including: recent tweets, who that person follows, and who follows them. You can also search for people by name, search the content of tweets, or use a variety of applications built over Twitter to see what's going on and how topics or people are connected in many neat ways that evolve very quickly. For an explanation in pictures see Twitter in Plain English.

One problem with Twitter in Plain English is that it explains Twitter just as a way to keep in touch with your friends, which is just one use - and relies on the assumption that your friends are either already using Twitter or you can convince them to do so.

I'll call this the "I just picked up more cat food" use - and yes I believe than many people do have friends and family from whom a stream of these tiny updates is enjoyable and valuable even when the content is as mundane as the dullest blog in the world. Tweets are very short and don't demand a lot of attention. The background chatter of friends or family - like the chatter of children playing - is comforting, enjoyable and entertaining especially when you're physically separated. You should note that Twitter currently allows you to either make your account public (anyone can read) or private (only followers you OK can read what you tweet) so using Twitter for private "friends and family only" tweets become awkward at best and precludes use of the same account for public conversation on Twitter.

At the opposite extreme, Twitter becomes a platform for individual or corporate brand promotion. I'll call this the How to promote yourself as a branded channel for fun and profit use. If you post to Twitter you'll automatically pick up promotional followers who hope you'll automatically follow them back to increase the reach of their channel. If this bothers you - or you pick up followers who look really dubious - Twitter allows you to block followers to remove them from your profile. Celebrities, pundits, experts, brand managers and just plain folk with something interesting to say can build a large following to create or extend their brand.

For me, the most interesting use of Twitter is as host of the world's largest collection of personal channels: you can find, follow or reply to people adept at the 140 character tweet. For example, I enjoy David Pogue (pogue) and Steven Fry (stephenfry) for their ability to mix notes, quips and links. I also follow a sampling of folk interested in hypertext, social software and technology - at least those who don't just repeat what I scan in more detail from their RSS feeds. I'll occasionally reply or rebroadcast a tweet ("retweet"), but I also don't feel bad about un-following folk whose posts I'd rather read in RSS, or tune out as the only way to keep the signal-to-noise ratio of what I read under control. If you attempt to follow a very large number of people, you'll end up reading a random sample or facing a signal to noise problem:

Venkatesh Rao (vgr): 9:44AM Mar 21: Twitter needs a 'more like this'/'less like this' reinforcement learning to lower my SNR :(. Fave tweet types, not people.

My reply (roundtrip) about 12 hours later: @vgr agree. There's a great difference between following friends & family where everything counts & topics you care about x everyone.

I'll call this use of Twitter the world's largest floating cocktail party, coffee break, and trade show happy hour, where you're free to tune in to what anyone is saying to the world - and talk back if you wish. Just like any party the roof is an introduction, but you can also just step back and enjoy the flow. It's a fragmented, freewheeling and noisy place - but you choose channels you want to listen to and change channels any time. It's like tuning dials on a hypertext radio until the sum of social chatter, news, business, fun, and off the wall discovery makes you happy. You can't do that at a real party.

People aren't the only ones invited to the party. As Jeremiah Owyang astutely points out, mining Twitter gives CRM vendors, advertising agencies and market analysts valuable analytic insights and opportunities for engagement. If the government does this it would be a privacy scandal; if vendors do this it's called a business model for Twitter.

So if you don't keep in close contact with friends and family using Twitter, promote your brand, understand your market or enjoy the opportunity to mix, mingle and listen to the flow in Twitter's world-wide public commons I guess you don't have a good reason to become a Twitter enthusiast. But Twitter one of many competing and complementary places for socialization on the Web.

Is there a Doctor of Sociology in the House?

I believe the most interesting point is that Twitter defines a place that escapes the scaling limits of the physical places we're all used to, but invites social creatures like us to build social norms and expectations over the public commons and specific affordances that Twitter created.

Great architects of physical places know that people bring expectations and norms about the kind of behavior that's appropriate and enjoyable to any physical space. Architects are skillful in designing spaces to match their clients desires and expectations by providing cues that are easy to perceive and appropriate for the intended purpose, but a lot of the norms of the same physical space become clear only from social context.

If you walk into a conference room with a group of people you don't know talking quietly around a table - and someone closes the door behind you - you'll likely speak and act differently than if you walk into the same room with people you know laughing, eating and drinking. If you walk into a theater you'll probably seat yourself quietly in the audience rather than striding onto the stage (see the Re-Placing Space reference).

What fascinates me about social software is how we're learning to create places with perceived affordances - features and user models - that seem natural for different purposes and intentions. I use Facebook, Traction Software's TeamPage server, and Twitter as three separate places: my neighborhood, my workplace, and the public commons I like to use.

Facebook: To me this place is a neighborhood where you can choose your own friends and neighbors. I use Facebook mainly for informal friend, family, alumni keep in touch posts and links. Because Facebook friending automatically builds a two-way follows relationship versus Twitter's one-way user model, it's easy to build and maintain a neighborly feel by default. I enjoy status updates and posts (like tweets with structure for videos, web links and Facebook apps) from "friends" and keep my posts open to members of my college's Facebook Network. The Facebook posts I write and read are generally for smile value or status updates that would only be of interest to folks who know one another and find the chatter comforting rather than noise. Although it's possible to turn down the volume of posts from folk who tend to update a lot, signal to noise is not really a problem with a neighborhood of tens to hundreds of folk. Just like in real life you know how to act and what to expect in your Facebook neighborhood.

Traction Software's TeamPage server: It's the place I work - along with other employees of Traction Software, customers, reseller partners, technology partners, Board members, consultants, advisors, friends of Traction, contractors, and our legal and PR firms. TeamPage makes it easy to support many different spaces (or places) on the same Traction server with different membership rules. Like Facebook each individual on a TeamPage server has their own profile page whose content can be customized - by default it shows the set of most recent posts and comments by that individual which you have permission to read. Like Twitter you can use TeamPage's LiveBlog skin to share brief notes, comments and replies - within a space shared by a group with access to that space. Traction has over three hundred spaces on our corporate TeamPage server - including spaces for all customers, product development, support, each technical and reseller partner, each major account, board of directors, our PR firm etc. Boundaries separating spaces you have permission to read automatically slide down so you can link, search, or syndicate content using spaces just to group content for navigation. Your rss feeds, tag clouds and search results reflect only the content you have permission to read. See Michael Sampson's Traction TeamPage: the One System to Rule It All.

Twitter: For me it's ultimate mashup of technical conference coffee breaks and trade show happy hours. I enjoy listening, meeting new people, and just shooting the breeze. I think of Twitter a place for listening and conversing with an ever changing cast of characters rather than a neighborhood where I live or a place where I get work done. The fact that Twitter is a hot, popular public place is more significant that its technology particularly as Facebook adds public and fan permissions to its walled garden privacy rules (which might complicate or sacrifice Facebook's "neighborhood" feel). If I want to "tweet" among friends and neighbors I do it in Facebook; If I want to "tweet" to get work done, I use TeamPage.

I like the idea of having three recognizable places corresponding to: neighborhood, workplace, and commons and want to keep then clearly separated in a social if not technical sense.

Metaphorically, if I want to talk to the neighborhood I'll go outside and speak with the expectation that anyone in the neighborhood can hear me (if they want) and I can shout out to anyone by name. If I want privacy I can walk inside and close the door. When I go to work I can speak in my office so that other TSI folk can overhear me (if they want), or walk into a conference room that's clearly marked for the Board, a specific technology partner, a specific customer, or an all customer commons and know that everyone in the room has the same expectation of place and privacy. When I want to join (my own) selection from the global commons, I'll walk into a bubble of babble (the converse of a cone of silence) and pay attention and respond in a different way that I would to the chatter of friends, internal collaboration at work, or conversations with external clients who expect - and demand - privacy and security for many working conversations.

Just like a good architect knows how the to use the affordances and relationships of physical spaces to help cue behavior, architects of social software should aim to use software affordances to make socializing in the neighborhood, workplace, and commons as natural as possible. I think this will require cues to signal and differentiate as well as connect places. The goal should be to help people read context and act comfortably in different places whose norms they can quickly learn, understand and trust. As Harrison and Dourish write:

"A conference hall and a theatre share many similar spatial features (such as lighting and orientation); and yet we rarely sing or dance when presenting conference papers, and to do so would be regarded as at least slightly odd (or would need to be explained). We wouldn't describe this behaviour as 'out of space'; but it would most certainly be 'out of place' and this feeling is so strong that we might try quite hard to interpret a song or a dance as part of a presentation, if faced with it suddenly. It is a sense of place, not space, which makes it appropriate to dance at a Grateful Dead concert, but not at a Cambridge college high table; to be naked in the bedroom, but not in the street; and to sit at our windows, peering out, rather than at other people's windows, peering in. Place, not space, frames appropriate behaviour." - Re-Place-ing Space: The Roles of Place and Space in Collaborative Systems

I look forward to the day when identity, syndication, security and search standards are robust enough to allow me to search, link and communicate across many different places for my own convenience, preserving sensible boundaries as well as appropriate expectations of privacy. I believe that's how the Web will evolve in the not too distant future.

If you don't like my explanation of Twitter, try one of these:

Why I use Twitter Mar 1, 2009 George Millington replies to his friend's similar questions and objections.

Explaining Twitter to Eggheads Jan 4, 2009 - Jay Rosen asks readers to help him write an essay on why he's on Twitter - to be published in the Chronicle of Higher Education (print edition and Chronicle Review web site). I think this is the outline of a really good article and provoked a rich stream of comments. I guess I fit Jay's target audience, and will happily add a link to the essay when Jay publishes it.

"Facebook is for those you used to know, Twitter is for those who you will know".

Ask Twitter! - The Newest Q&A Source Mar 20, 2009 Aaron Asay blogged: "I've heard more than once: “Facebook is for those you used to know, Twitter is for those who you will know.” " which was quoted by mjasay in Twitter Mar 21, 2009 about 8:15AM and retweeted (RT'd) by windley about 8:18AM, which I noticed about 9:20AM and replied as roundtrip (me) "... and E2.0 is for those you work with" about 10:20AM.

For the hopelessly pedantic: A Google search finds that Andreas Ringdal suggested - in a comment on Steven Arnold's Mar 3, 2009 Twitter Facebook Analogy post - that this quote "as someone brilliantly put it" might be identified by reading Ivor Tossal's Dec 25, 2008 Globe and Mail 903 word story: Teeny-tiny Twitter was the year's big story which I'm too cheap to purchase for $4.95 plus tax and find out - thank you very much

and finally ...

Twitter Sucks, so change your friends Mar 16, 2009 Steve Lawson. His analysis and examples are even better than the title.

Feeling pretty meta about this post, and deciding that's not bad

ImageYou can find me on Twitter as roundtrip, and follow Traction Software as TractionTeam. Follow Traction-software for a list of all Traction Software team members, customers, and friends. Please tweet back! Cheers! For live @roundtrip Twitter updates see Where's Greg?

See also
The Future of Work Platforms: Like Jazz
Ask an Engineer: What do you think of the Facebook Terms of Service Flap?
Reinventing the Web
Who's on Your Team ?
Borders, Spaces, and Places
Re-Place-ing Space: The Roles of Place and Space in Collaborative Systems (.pdf)
by Steve Harrison (Xerox PARC) and Paul Dourish (EuroPARC), online draft of paper presented at CSCW '96.

Kuka Systems TeamPage Case Study

March 14, 2009 · · Posted by Greg Lloyd

See Kuka Systems for an excellent TeamPage story Jordan wrote in cooperation with this Traction TeamPage customer. KUKA is one of the world's leading suppliers of robotics as well as plant and systems engineering and has been in the automation technologies business since 1898. They build robotics systems for factory automation and are a leading worldwide supplier of assembly and welding systems, and other related machinery, servicing the automobile, aerospace, and energy industries.

KUKA's Enterprise Applications Group started using TeamPage for collaborative issue tracking in 2006 and has expanded their use to support capture of procedural knowledge, audit compliance, and six sigma style continuous improvement processes. They are further expanding use of TeamPage as a wiki to document key business processes and core knowledge that's required for every day management and support of their business. It's a great manufacturing use case complete with background and TeamPage screenshots.

Providence Geek Talk | Frank and Nuzum speak out: How Pages Crush Documents

March 9, 2009 · · Posted by Jordan Frank

Image Chris Nuzum and I had a chance to speak to the Providence Geeks about what we've done with Traction TeamPage and how "Pages are Crushing Documents." I do a history of our company and transition into a history of communication and collaboration that runs the course from stone tablets to books through email and documents and finally culminates in wikis and blogs. Now that wikis and blogs are becoming the new currency of collaboration and communication, my presentation focuses on how "packaging matters" with particular focus on the ways pages can be re-used and distributed in ways that can improve communication performance and enable innovation like we've never seen it before. Caught on "film" are my talk followed by a video podcast interview.

The Presentation:

The Video Podcast Interview:

Water Cooler ROI - Putting Social Software to Productive Work

March 3, 2009 · · Posted by Jordan Frank

Matt Hodgson's the ROI of Being Social at Work points to recent MIT research suggesting 40% of productivity for creative teams is a direct result of communication and employees with the most extensive digital networks are 7% more productive.

This complements research I discussed in Collaborating Across Boundaries, Searching People for Answers which offers tangible evidence for the productivity gains achieved by reducing search chains (to find experts) and collaboration across workgroups or divisions.

Per Euan’s Semple's point suggesting that if you "Keep the I really small then people won't give so much hassle about the R," the I that you might spend on a social software project is miniscule compared to the benefits that can be unlocked.

Trying to quantify benefits with more traditional approaches like calculating storage saving from e-mail may “pay the bill,” will miss the point.

Managers are on board with this approach. In a study of Competitive Intelligence operations, most managers say they measured return based on customer satisfaction (where the customers are internal users of the intelligence information).

Faster innovation, better decisions, shorter search chains and greater productivity result when you move communication and collaboration from e-mail to a social software based "water cooler."

Clarity Amid the Hype

February 26, 2009 · · Posted by Greg Lloyd

Image Mike Gotta posted Enterprise Twitter: Clarity Amid The Hype analyzing - and generally agreeing with - points raised by Adina Levin (Socialtext) in her excellent post What's Different about Enterprise Twitter? I agree with Mike's analysis and Adina's thoughtful points (read them both) but want to focus on Mike's conclusion:

[like fragmented email conversations] ... Twitter-like systems are also difficult to follow - the tools so far do not do a great job of isolating conversation threads, manage/filter messages over time, etc. On top of this - do we really think that companies will have wide-open conversation spaces without applying permission models that limit access rights based on a variety of business reasons? I don't disagree with the concept of transparency - but you have to consider policies related to role, separation of duties, security, confidentiality, intellectual property, compliance and so on. There are very good reasons to have bigger walled gardens within enterprise organizations - and some organizations will be much more public than others - but we do get back to addressing barriers encountered by other messaging tools.

BTW - many (if not all) of these concerns and issues apply equally to "activity streams". The need for activity streams to support permission models, and comply with logging/audit/compliance/discovery requirements should be pretty clear. For vendors offering "Twitter for the Enterprise" or "Activity Streams" - making sure you support security (permission/access controls), identity, and records management requirements has no down side. - Mike Gotta

The concept of transparency and "borders that seem appropriate to users" (to borrow Andrew McAfee's phrase) are closely related to people's natural expectations for shaded degrees of privacy based on the context of the conversation or activity - and apply to blog posts, wiki pages, comments, rss feeds, and search results as well as enterprise "tweets". As Facebook found last week, it's difficult to come up with a simple explanation of privacy rules that: 1) meet natural expectations; 2) can be accurately described in legal prose; 3) correspond to promises that your software system actually implements.

I won't claim that Traction TeamPage's security model "has no downside", but we've worked pretty diligently with some of the most demanding - and innovative - customers in the world. Our objective has been to make it straightforward to meet natural privacy and security expectations with a model that's easy to use - even if it's not easy to implement.

For an enthusiastic ("I think that rocks") reaction from collaboration and Microsoft Sharepoint expert Michael Sampson, see his Traction TeamPage: The One System to Rule It All posted Feb 23, 2009. Note that the same example Michael uses to show how it's possible to interleave, link or tag more private discussions on any paragraph in a wiki page applies to all TeamPage personal or group blog posts, LiveBlog "tweets" or comments. It's easy to understand - but I don't think you'll find any other Enterprise 2.0 product which lives up to these promises.

See Also Borders, Spaces, and Places
Ask an Engineer: What do you think of the Facebook Terms of Service Flap?
Reinventing the Web
Live blog with Traction TeamPage

Traction TeamPage: The One System to Rule It All

February 24, 2009 · · Posted by Greg Lloyd

Needless to say I'm delighted with Michael Sampson's Currents: "TeamPage - the One System to Rule It All". I like One System to Rule It All angle, butassume that would make me a metaphorical Elven-smith of Eregion rather than Sauron of course. Hmmm

Why Software is a Good Investment

February 24, 2009 · · Posted by Jordan Frank

In tough economic times organizations are faced with hard budgeting choices as they weigh the cost and benefit of investing in durable goods, people, marketing and software. Here are some reasons why software should be at the top of the list:

  • Software helps people do their jobs better - whether they are engaged in collaborative activity on a wiki, making decisions about supply chain issue, or managing sales activity.
  • Software allows organizations to monitor and leverage their marketing activity.
  • Software helps organizations leverage their investments in durable goods like manufacturing systems by optimizing and tracking the flow of material through the supply chain.

While computers, cars, and manufacturing equipment ultimately age and depreciate to $0 (or worse, if you have to dispose of them), software is generally likely to appreciate over time through a series of upgrades and patches. Beyond the simple benefit of not falling into disrepair, software value increases as data is added and information externalities develop.

Taking Traction TeamPage as an example:

So, if you are trying to figure out how to put together your 2009 budgets, consider software. And if a track record of technology leadership is any indicator, get Traction.

See also Do Something Differently - Spend less for better results

Ask an Engineer: What do you think of the Facebook Terms of Service Flap?

February 18, 2009 · · Posted by Greg Lloyd

If you haven't been paying attention to this week's flap on Facebook's revised terms of service - posted three days ago and retracted today - Andrew Lavelle of the Wall Street Journal published a good recap today. The controversy relates to what rights does Facebook get to content that an individual Facebook user posts? There are a lot of good arguments about what rights people think Facebook should be able to retain, but there's a second level of discussion that relates to how people expect Facebook privacy settings to work, and how these expectations make it difficult to craft an agreement that seems fair, makes sense, and corresponds to what Facebook actually implements and enforces.

Lavelle quotes Techcrunch's Erik Shonfeld: “If I upload a picture which I later regret uploading, why shouldn’t I be able to erase it from Facebook forever, even if some of my friends have already seen it?”

Facebook's Mark Zuckerberg's Monday 5:09PM post said:

"Our philosophy is that people own their information and control who they share it with. When a person shares information on Facebook, they first need to grant Facebook a license to use that information so that we can show it to the other people they've asked us to share it with. Without this license, we couldn't help people share that information.

One of the questions about our new terms of use is whether Facebook can use this information forever. When a person shares something like a message with a friend, two copies of that information are created—one in the person's sent messages box and the other in their friend's inbox. Even if the person deactivates their account, their friend still has a copy of that message. We think this is the right way for Facebook to work, and it is consistent with how other services like email work. One of the reasons we updated our terms was to make this more clear."

These examples show the difficulty in defining privacy policy based on two different and irreconcilable sets of expectations. If you don't grant Facebook legal permission to share what you post based on your privacy settings, Facebook doesn't work as you expect. And if Facebook's implementation doesn't enforce your privacy settings correctly, you have a right to be upset (or sue). But if you change your mind - or cancel your Facebook account - what happens to content that you've granted Facebook the right to share with other Facebook users? Here are two alternatives:

1) Grant Facebook rights subject what you ever posted to your Wall or someone else's Wall subject to your privacy settings which you can change at any time. This require Facebook to restrict future access to whatever you have posted or shared directly or indirectly with others using Facebook when you subsequently change your mind or leave Facebook and cancel your account (e.g. Ted Nelson style enforcable “transcopyright”).

2) Grant Facebook rights to use copies of your content (the copyrighted email message model) that you post to your Wall or someone else’s Wall directly or using a third party’s Facebook API. You arguably have a legal right to restrict future use of copyrighted content distributed to others via third parties, but don’t have a practical way to retract content that has been copied and stored outside Facebook’s direct control.

Zuckerberg argues that the content of your Wall might disappear or be restricted based on your privacy settings (or disappear if you cancel your account), but whatever you've posted to someone else's Wall might be retained by Facebook - and deleted or restricted by the owner of that Wall. This may or may not be what you want - and not how I read what Facebook's promised to do in Mondays (retracted) revised terms:

"You are solely responsible for the User Content that you Post on or through the Facebook Service. You hereby grant Facebook an irrevocable, perpetual, non-exclusive, transferable, fully paid, worldwide license (with the right to sublicense) to (a) use, copy, publish, stream, store, retain, publicly perform or display, transmit, scan, reformat, modify, edit, frame, translate, excerpt, adapt, create derivative works and distribute (through multiple tiers), any User Content you (i) Post on or in connection with the Facebook Service or the promotion thereof subject only to your privacy settings or (ii) enable a user to Post, including by offering a Share Link on your website and (b) to use your name, likeness and image for any purpose, including commercial or advertising, each of (a) and (b) on or in connection with the Facebook Service or the promotion thereof. You represent and warrant that you have all rights and permissions to grant the foregoing licenses."

My reading of this was a promise to respect an individuals privacy settings for whatever that individual posted to their own Wall or anyone else's Wall - directly or indirectly - in exchange for rights to copy distribute that content. If so, Facebook is setting a pretty high bar for what they have to implement.

I read Monday's version as a promise to track sharing rules based on Facebook privacy settings as you may change them over time. If so, it looks like developers who use the Facebook API need to reference the current value of per user privacy settings that are authoritatively maintained by the Facebook platform. Not a bad position for Facebook as the gatekeeper for all runtime access - but not easy to craft an agreement that “make sense”, is broad enough to protect Facebook, matches what they actually implement, and can be enforced on their Facebook API developers who also need access to user content.

For comparison, Traction TeamPage uses run-time transclusion with permission checking to grant or deny access to to posts, pages, comment and tags (as well as what you can see by navigating, searching, Jabber or email notification and RSS/Atom feeds).

The TeamPage model uses permissions attached to the content of specific work spaces rather than individuals, but allows private comments in one space (e.g. the Support project) to be added to any paragraph of a more public space (e.g. a customer Forum), and shown only if the reader has permission to read the top level entry and the spaces(s) in which comments on that entry are posted.

This makes it easy add or remove a person from the access list of the Support project, and instantly change the page content, comments, tag clouds and search results that person can see.

See Borders, Spaces, and Places
Reinventing the Web
Enterprise 2.0 - Letting hypertext out of its box

President 2.0

February 17, 2009 · · Posted by Jordan Frank

We've seen our US Government and state level customers seek out and achieve great success as they make their own migrations to "2.0" style collaboration with TeamPage. While "grasss roots" action at the agency level is encouraging, top down involvement and mandates tend to accelerate the proces. With Obama's Transparency and Open Government mandate, perhaps we have it!

What are you good at?

January 30, 2009 · · Posted by Jordan Frank

I like what Seth Godin says in What are you good at? Where he talks about the distinction between content (domain expertise) and process (emotional intelligence skills you have for managing projects, visualizing success, dealing with priorities and so on).

I've generally referred to the same concepts by distinguishing between Tangible and Intangible skills. I went to business school to learn the tangible skills (how to read a balance sheet, how to write a data model). My application emphasized this, and emphasized that I could bring my own intangible skills (specifically selling skills, most of which I learned apprentice-style from Jacob Farmer at Cambridge Computer Services) to the community.

Tangible skills can be learned readily (how to formulate a strategy) whereas intangible skills (how to formulate a winning strategy given a set of circumstances) require a mix of an individual's intellectual compass and their experience set (collectively, I think this is better referred to as Wisdom).

Seth says that the internet is useful for learning domain knowledge, which can be derived from content alone. I think the mix of blogs and wikis - the union of codified knowledge and the narrative around it, can, however, relay the experience necessary to develop tacit knowledge. In KM is the Forest, Enterprise Blogs are the Path, I quoted Gary Klein who said "It is usually easier to teach people by developing a series of vignettes that bring that tacit knowledge to life for others." The vignette approach is helpful for teaching domain knowledge and it's altogether mandatory to teach intangible skills like selling, strategy making, persuasion, priority management and so on.

There's a good debate to be had with respect to whether these intangible skills can simply be learned through reading vs. life experience or apprenticeship. But if they can be learned, the mix of blogs and wikis is just the right medium.

Seth says super-talented people become enterpreneuers, because "they can put their process expertise to work in a world that often undervalues it."

I think the issue is much greater than the matter of the world undervaluing intangible skills, it's about fitness for the job. I'd add that the successful entrepreneurs have the wisdom to navigate a market when there is little tangible data to support a well informed decision making process. Entrepreneurial ventures, by definition, require such wisdom, to simply get lucky, or, more often, both!

At What Scale Can Web Services Survive?

January 30, 2009 · · Posted by Jordan Frank

One more data point in line of my Whither Web 2.0 Social Networking Discussion which questions the revenue models of web services (with web social networking as a focal point): An on-line service the scale and scope of Microsoft's Online Services is running into red ink of proportional scale. It lost $471 Million per last quarter. The clear and present issue is not whether a profit may be turned at some even-large scale, but what will change about the business model and how will that affect users?

Reinventing the Web

January 12, 2009 · · Posted by Greg Lloyd

John Markoff wrote a really good Jan 11 2009 New York Times profile, In Venting, a Computer Visionary Educates on Ted Nelson and his new book, Geeks Bearing Gifts: How the Computer World Got This Way (available on Markoff notes that Tim Berne