Title: Original Traction Product Proposal


I hope you'll enjoy reading the original Traction Product Proposal, dated October 1997. Many early Traction concepts carried over directly to the Traction® TeamPage product first commercially released in July 2002, but we've also learned a lot since then - as you might hope! The Proposal and its 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 Okutsu'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 blogl. You can also follow or message me on Mastodon as @Roundtrip@federate.social if you have questions. To review all of my posts on this TeamPage group blog, see Greg's Blog Posts.

The scribbled picture above from about the same time was my visualization of the Traction goal: To link and use anything of interest that crosses a business person's desk using the Web as a platform, rather than 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 article Traction: Weblogs grow up. So did Jon Udell in his 2002 InfoWorld review: 'Getting Traction - Tranction’s enterprise Weblog system gets a grip on corporate KM.

In 1996, Eric Lundquist wrote:

"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 quote from Traction Product Proposal 

The core Traction 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. Comments, tasks, and tags can cross spaces - so it's simple for internal team members to have a more private discussion linked to a more public paragraph or question posted by an external customer. Streams, discussions, notifications, digests, navigation, tag clouds, and search all obey permissions defined by business rules to show you what you're interested in and have permission to see and nothing more - 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 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 to TeamPage since that user's previous Digest was emailed. The content of each Digest is clipped to conform to what the person receiving the digest is permitted to see.

The Digest remains a popular features of TeamPage. It was 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. Automatically threaded email replies was requested by a major consulting firm using TeamPage to post quick replies using mobile email. I agree with Alan Lepofsky's point that email is one of many channels for messages: 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 links in the Proposal still work, many point to sites which have been moved, including Doug Engelbart references which have moved from bootstrap.org to dougengelbart.org. In some cases a bit of creative Googling may find the referenced page in a different location. Links to dead sites can often be recovered using the Internet Archive's Wayback Machine. if a good backup is found, you can replace the dead link with the Wayback Machine's backup link. If people are interested, I'll publish an editable version of the Annotation References section that can be used to share updated URLs for broken links.

More



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



Related



Tripping Up Memory Lane - Hyperkult 2015: Hypertext lessons learned talk by Traction Software CTO and Co-founder Chris Nuzum. Chris writes: "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."

Teampage hypertext journal: Design concepts, by Takashi Okutsu Director of Traction Software's Japanese Business Office. Takashi explains how TeamPage's append-only journal models editable content, links, and relationships − while maintaining a full audit trail. 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.

Traction Roots - Doug Engelbart - In the late 1960's Doug and his SRI team created the NLS / Augment system (including a shared journal as a database model, the mouse, shared-screen interactive hypertext and video, dynamic outlining, and many other inventions) to support high performance problem solving teams. Traction's time ordered journal database, entry + item ID addressing, and many Traction concepts were directly inspired by the NLS model; the term TeamPage Journal is named in Doug's honor. The major use cases for Traction TeamPage follow Doug's CODIAK model for collaborative, dynamic, continuous work: "A result of this continuous knowledge process is a dynamically evolving knowledge base as shown in Figure-7 below, consisting of three primary knowledge domains: intelligence, dialog records, and knowledge products (in this example, the design and support documents for a complex product)." Traction TeamPage aims to directly support collaborative work that spans dialog records, references to external intelligence, and the creation and use of knowledge products.

Traction's enterprise Weblog gets a grip on corporate KM - Jon Udell writes a 12 July 2002 Infoworld product review of Traction TeamPage, with a 'Deploy' recommendation and 10/10 rating for innovation and interoperability. Udell writes: "THERE IS STILL NO sure-fire recipe for KM (knowledge management) success, but the ingredients must include the staples of the knowledge worker: e-mail, the Web, and Microsoft Office. With Traction® Software's KM solution, content flowing through all these channels is easily captured by the Java-based Traction Server, which can be best described as an enterprise Weblog system...Traction can be regarded as an ultrasophisticated PIM (personal information manager). That's just the quality you need in a KM product to get people to actually use it."

Traction - Weblogs grow up - Clay Shirky reviews Traction in the May 2003 issue of Esther Dyson's Release 1.0 Newsletter, a special issue on Social Software: A New Generation of Tools: Taking their cue from people’s actual behaviors rather than some idealized projection, a number of startups are designing tools that help people get what they want from group interaction. Shirky writes: "Traction attempts to utilize the simplicity and ease of use of blogging software to publish and annotate content, while allowing better control of security and access than standard blogging tools. The tool lets employees report their efforts and observations in a weblog. Other interested parties (and, in the case of sensitive material, only those parties) can then have access to that material in one place and on-demand, rather than piecing things together from a dozen Cc:ed e-mails."

“Each project space has its own team and its own audience. Project spaces can be opened up to a wider group of peers or senior management, or kept private, as the project group wants.” Lloyd uses Traction’s own customer relations operations as an example: “We create one project area for each customer, visible only to that customer and us, as well as one group project for all the customers. When we have a new announcement – an updated SDK, say – we post it to the group project and everyone sees it. But if one of those customers wants to talk to us about helping them implement it, that conversation happens in our separate shared project, away from the other customers.

Supernova 2005 | Why Can't a Business Work More Like the Web? - Greg Lloyd was on the 22 Jun 2005 SuperNova Connected Work Panel. Quoting from Greg's SuperNova 2005 Point paper: "If you can easily find what you want, and stay informed about what matters to you across a network as large and chaotic as the World Wide Web, why should you settle for less in your business? I don't think you will...

The new generation Internet can provide a model that makes everyday working communication simpler, while keeping everyone with an active (and valid) interest well informed. It can provide much better awareness but cut non-productive reporting overhead...

Here are two characteristics I believe are challenging but important for use at the extended enterprise level – for networks of thousands to millions of participants within and across organizations.

1) Address selected Audiences - Create weblogs, wikis and syndication feeds that encompass a selected audience of internal and external stakeholders. For example: include customers, contractors, consultants, and resellers as members of an extended product development team.

2) Support global identity and local permissions - Your globally known identity and role within an enterprise should be sufficient gain direct - or indirect - access to any locally permissioned weblog, wiki or syndication feed owned by that enterprise. Indirect access includes use of network scale permissioned alerting, syndication and search services across all of the content you have permission to read. ...

Without a rich selection of more private and more public spaces, a lot of important discussion will simply take place outside the system and lose its direct and indirect value. The network record should include the messy but critical tradeoffs, debates, discussions and decisions - right or wrong - for the enterprise's long-term benefit as well as those of the core team."

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 siloed."

Borders, Spaces, and Places - With TeamPage, when you navigate, search, or link information, the borders separating the customer and internal spaces you have permission to read become transparent. You can still use the names of spaces created for particular customers to focus your attention on a particular issue or collection of content, but you effectively see one big wiki / weblog. Borders help you visualize the business context and intended audience. If a customer logs in to your TeamPage server, they see only the content, search results, tags, feeds, cross-reference links, and space names clipped to what they have permission to read. The content - and existence - of private collaboration spaces of other customers or reserved for internal use are hidden. Traction TeamPage extends faceted search, automatic notification, email digest content, commenting, and inline discussion to work transparently across spaces you have permission to read, while redacting content you don't have permission to see.

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."

Enterprise 2.0 and Observable Work "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... 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." Jim McGee 23 Jun 2010  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.

The Work Graph Model: TeamPage style - the social dance of getting things done and dealing with exceptions, while staying aware of what’s going on around you. TeamPage watches what you do, and automatically maintains two-way links and relationships as you edit, keeping an accurate version history of everything. 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. 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. Learn how TeamPage uses integrated Solr search for indexing, visualizing, and using work that crosses boundaries, linking customers, suppliers, partners and internal teams.

1 November 1997 | The Godfather: The Manhattan Project, Silicon Valley, The World Wide Web - G. Pascal Zachary writes in Wired Magazine: "Wherever you look in the information age, Vannevar Bush was there first... Some ambitious efforts to tame the Web's chaos are avowedly inspired by Bush. At Twisted Systems Inc. in Providence, Rhode Island, engineer Gregory Lloyd is designing better ways to record a user's associations between different Web sites. "There are Web tools that manage bookmarks, that help you find your place," Lloyd says. "Bookmarks are a start. But then the problem is managing your bookmarks. They can degenerate into a slush pile, which is not what Bush wanted." Lloyd is tight-lipped about his work toward a solution, but says flatly, "I'm building a memex, the holy grail."



Attachments:
What is Traction - Traction PD rev U [CC Aug 2015] (page 10 of 52).jpg
Team Problem Solving - Traction PD rev U [CC Aug 2015] (page 8 of 52).jpg
Weblogs-Grow-Up-Traction-CShirky-Release10May2003.pdf
CODIAKProcess-rectangle.jpg
CODIAKProcess-rectangle.jpg
Related Articles
referenced by (8)
Blog3560: Clash of the Titans 2020 - Peter O'KellyBlog3514: Clash of the Titans - Peter O'Kelly at TUG 2010Blog3001: Chris Nuzum Hyperkult XXV Video | Tripping Up Memory LaneBlog2386: Thought Vectors - What Motivated Doug EngelbartBlog2183: The Work Graph Model: TeamPage styleBlog2121: Remembering Doug Engelbart, 30 January 1925 - 2 July 2013Blog384: Enterprise 2.0 - Letting hypertext out of its boxBlog50: Traction Roots - Doug Engelbart
references (14)
Press1757: Jun 2020 | TeamPage uses Solr for faceted navigation and searchBlog2752: Teampage hypertext journal: Design concepts, by Takashi OkutsuBlog2741: Tripping Up Memory LaneBlog2709: Eat your spinach: Email is good for you, but it could taste a lot betterBlog2183: The Work Graph Model: TeamPage styleBlog1424: Intertwingled WorkBlog1351: Enterprise 2.0 and Observable WorkBlog691: Borders, Spaces, and PlacesBlog384: Enterprise 2.0 - Letting hypertext out of its boxBlog50: Traction Roots - Doug EngelbartPublic390: 20 June 2005 | Supernova | Why Can't a Business Work More Like the Web?Public104: May 2003 | Traction - Weblogs grow upPublic72: 12 July 2002 | Traction's enterprise Weblog gets a grip on corporate KMPublic49: 1 November 1997 | The Godfather: The Manhattan Project, Silicon Valley, The World Wide Web
Article: Blog2804 (permalink)
Categories: :Blog:TractionHistory, :Blog:thoughtvectors, :Blog:key
Date: August 24, 2015; 5:39:04 PM Eastern Standard Time

Author Name: Greg Lloyd
Author ID: grl