Stay on Top of Enterprise Technology Trends
Get updates impacting your industry from our GigaOm Research Community
I’ve been exploring a growing list of web-based tools for the creation and management of what most would call ‘documents’ — assemblages of text, images, lists, embedded video, audio and other media — but which, are in fact, something quite different than the precursors, like Microsoft Word and Apple Pages documents.
The big shift underlying these new tools is that they are not oriented around printing onto paper, or digital analogues of paper, like PDF. Instead, they take as a given that the creation, management, and sharing of these assemblages of information will take place nearly all the time online, and will be social at the core: coediting, commenting, and sharing are not afterthoughts grafted onto a ‘work processing’ architecture. As a result, I am referring to these tools — like the pioneering Google Docs, and newer entrants Dropbox Paper, Quip, Draft, and Notion — as ‘work processing’ tools. This gets across the idea that we aren’t just pushing words onto paper through agency of word processing apps, we’re capturing and sharing information that’s critical to our increasingly digital businesses, to be accessed and leveraged in digital-first use cases.
In a recent piece on Medium, Documents are the new Email, I made the case that old style ‘documents’ are declining as a percentage of overall work communications, with larger percentages shifting to chat, texting, and work media (enterprise social networks). And, like email, documents are increasingly disliked as a means to communicate. And I suggested that, over time, these older word processing documents — and the use cases that have built up around them — will decline.
At the same time, I believe there is a great deal of promise in ‘work processing‘ tools, which are based around web publishing, web notions of sharing and co-creation, and the allure of content-centric work management.
Chat-centric work management, as typified by Slack-style work chat, is getting a tremendous surge in attention recently, and is the now dominant form of message-centric work technology, edging out follow-centric work media solutions (like Yammer, Jive, and IBM Connections).
Workforce communications — relying on a more top-down messaging approach for the mobile workforce — is enjoying a great surge in adoption, but is principally oriented toward the ‘hardwork’ done by workers in retail, manufacturing, transport, security, and construction, and away from the ‘softwork’ done by office workers. This class of tool is all about mobile messaging. (Note: we are planning a market narrative about this hot area.)
Today, I saw that David Byttow’s Bold — a new work processing app — has entered a private beta, with features that line it up in direct competition with Google Docs and the others mentioned above. Bold raised a round of $1 million from Index Ventures in January 2016.
The competition is hotting up.
Work Processing Will Be The New Normal
What I anticipate is the convergence on a work processing paradigm, with at least these features:
- Work processing ‘docs’ will exist as online assemblages, and not as ‘files’. As a result they will be principally shared through links, access rights, or web publishing, and not as attachments, files, or PDFs, except when exported by necessity.
- Work processing apps will incorporate some metaphors from word processing like styling text, manipulating various sorts of lists, sections, headings, and so on.
- Work processing will continue the notions of sharing and co-editing from early pioneers (Google Docs in particular), like edit-oriented comments, sharing through access-control links, and so on.
- Work processing will lift ideas from work chat tools, such as bots, commands, and @mentions.
- Work processing will adopt some principles from task management, namely tasks and related metadata, which can be embedded within work processing content, added in comments or other annotations, or appended to ‘docs’ or doc elements by participants through work chat-style bot or chat communications.
I am pressed for time today, and can’t expand on these ideas with examples, but I plan to do so quite soon in a companion post to this, called Work Processing: Coming soon to a ‘Doc’ near you.