Dropbox Paper is a Wolf in Sheep’s Clothing

Last week, I wrote about the commoditization of the enterprise file sharing market and how pure play vendors are being forced to evolve their offerings to stay alive. My post focused on Hightail (originally YouSendIt) and its announcement of Spaces – a specialized file sharing, annotating and publishing offering for creative professionals.
Dropbox also made a product announcement last week, albeit quietly. The company has expanded beta testing of Paper, a new offering that was released in a highly limited beta, in March, under the name Notes.  Like Hightail’s new offering, Dropbox’s illustrates how they are responding to the functional parity that vendors have achieved with basic file sharing offerings and to their rapid downward price movement.

Yet Another Collaborative Authoring Tool?

Most commentators, including Gigaom’s Nathaniel Mott in his article from last week, described Paper as “a collaborative writing tool”. They compared it to Google Docs, Microsoft Office (especially its Word and OneNote components) and startup Quip. For sure, Paper has similar functionality to those products, and it allows people to write and edit documents together in real-time. However, I don’t believe that is the main point of Dropbox’s beta product. Instead, Paper is intended to be used as a lightweight case management tool.
Case Management is a discipline that brings resources, including relevant content, related to a single instance of a business process or an initiative into a common place – the case folder. While many think of Case Management as a digital technology, its principles were established in business activities that were wholly paper-based.
Think of an insurance claim years ago, where a customer filled out a paper claim form, and it  was then routed throughout the insurance company in a paper folder. As the process continued, additional paper documents, perhaps even printed photographs, were added to the folder. The last documents to go into the folder were the final claim decision letter to the customer and a copy of the check, if a payment was made on the claim.
Today, that same insurance claim process is likely to generate and use a mix of paper-based and electronic documents, although insurance companies are slowly moving as much of the process online as possible. However, the concept of organizing information related to the claim into a single folder remains, although the folder is now likely to be an electronic artifact, not a paper one.

A Wolf in Sheep’s Clothing

Take another look at Dropbox’s beta Paper. Do you see it? Paper is a single point of organization for new content, files stored in Dropbox (and other repositories), existing Web content and discussions on all of those things. It’s a meta-document that acts like a case folder.
Paper enables lightweight case management, not the industrial-strength, production kind needed to handle high-volume, transactional business processes like insurance claims. Paper is case management for small teams, whose work might follow a pattern over time, but does not conform to a well-defined, repeatable process.
Working on a new software product at an early-stage startup with only a few coworkers? Start a new document in Paper, then add the functional and technical requirements, business projections, marketing assets, sales collateral, even the code for the software. Everything that is relevant to the product is one place in which it can be shared, viewed, commented on, discussed, edited and used for decision making. Just like a case folder in Case Management.

A New Way of Working

Still not convinced? Dropbox Product Manager Matteus Pan recently said:
“Work today is really fragmented…teams have really wanted a single surface to bring all of [their] ideas into a single place.” “Creation and collaboration are only half the problem,” he said. “The other half is how information is organized and retrieved across an entire company.”
That sounds like case management to me, but not the old-school type that you are likely more familiar with. Instead, Paper reflects the newer principles of Adaptive Case Management.
Adaptive Case Management (ACM) is a newer technology set that has been evolving from Production Case Management (PCM) over the last few years. ACM helps people deal with volatile processes by including collaboration tools alongside the workflow tools that are the backbone of PCM.
Dropbox Paper may be viewed as an extreme example of ACM, one which relies completely on the manual control of work rather than automating parts of it. In that regard, Paper takes its cues from enterprise social software, which is also designed to enable human coordination of emergent work, rather than the automation of stable processes. As Paper is more widely used in the current beta and beyond, it will be interesting to see if its adoption is stunted by the same obstacles that have limited the wholesale changes to established ways of working that social software requires.

Crashing Waves

I have not yet seen a demo of Dropbox Paper, but the screenshots, textual descriptions and comments from Dropbox employees that I have absorbed are enough to reveal that the product is more than just another collaborative authoring tool. If I was asked to make a comparison between Paper and another existing or previous tool, I would say that it reminds me of Google Wave, not Docs or Microsoft Office. Like Wave, Paper is a blank canvas on which you can collaborate with team members and work with multiple content types related to a single idea or business process in one place.
Google Wave was a powerful, but unintuitive tool that failed to get market traction. Will Paper suffer the same fate? Perhaps, but Dropbox hopes that the world is now ready for this new way to work. In fact, Dropbox is, in some regards, staking its continued existence on just that, as it tries to differentiate itself from other purveyors of commoditized file sharing services.

Slack Posts New Functionality

Slack is widely acknowledged as the enterprise real-time messaging (work chat) tool with the most traction, having passed the million daily user mark in June. It seems that the company is not content to stay boxed into the work chat category, however. Yesterday, Slack announced and released Posts 2.0, a feature that enables the rich authoring of blog posts and publishing them to targeted collections of people.
Since its launch, Slack has had this feature, called Posts, that lets people write content that far exceeds the length of a normal chat message. However, it was so clunky that few people used it, if they were aware of it at all. To create a Post, one was sent out of the Slack application to a web browser, where text was written using a very simple editor and then saved back to Slack as an entry in the conversation stream of a specific channel or group.
The new Posts 2.0 includes an inline text editor, which improves the experience in two ways. First, it keeps users inside the Slack app. Second, it lets them create rich text with formatting styles like headlines, bulleted lists and checkboxes. Beyond that, the new editor also acts on embedded URLs by automatically displaying graphics, showing previews of websites and expanding tweets.
Once written, Posts can still be shared with specific individuals, channels and groups, whose members can comment directly on the entry (as opposed to creating an chronologically-ordered entry in the Slack conversation stream). This is one of two places in Slack where properly threaded discussions are possible; Files is the other.
There is another important new feature in Posts 2.0 – the ability to save and access Posts in the Files section of the Slack application. So rather than having to scroll through or search the Slack conversation stream to view a specific Post again, it can be easily found in the Files repository. Additionally, if an author stars a Post in the editor or a reader does so in the conversation stream, it will show up in Slack’s Starred Items list. 

Cool, But Do Businesses Need This? 

With Posts 2.0, Slack has complemented existing features with new ones that, in combination, begin to move the application beyond being primarily a work chat tool. Slack has now effectively become a lightweight Web Content Management System that enables blogging (to a targeted audience), file storage and sharing and threaded discussion (around Posts and documents stored in Files only). It’s a lightweight people directory with profiles too. Oh, and it’s still a communication and collaboration tool.
This expansion of mission is fine, but it immediately raises the question that I previously asked and continue to pose about Slack. Why? Do work teams really need an alternative to existing corporate communication and information management applications that already satisfy the same use cases that Slack is addressing? How is Slack better than the status update, IM, blogging, file sharing, and discussion tools for communities (groups) that are bundled in the enterprise social software applications and platforms that organizations have already licensed and deployed?
In addition to the functional redundancy, one also wonders if Slack will ultimately lose its audience by becoming the opposite of what it was originally. The application’s strong initial appeal was the simplicity of its user experience. By adding more communication and collaboration features, Slack risks becoming a complex mess of functionality that few will care to use, especially on mobile devices.
On the other hand, Slack may intentionally de-emphasize its application in the future, positioning and going to market as a platform on which developers can create their own apps. We’ll see. Many already refer to Slack as a messaging-centric platform. Time will tell if that is indeed their market strategy for the long-haul, but, for now, Slack is beginning to look like yet another bloated application.

Why do some teams gel while others fail at collaboration?

Nowadays nearly every team aims for collaboration, but far from all succeed, often for emotional reasons as well as rational ones. Now a new study is aiming to figure out what sets teams that gel apart from those that fall apart, and you can participate.

Eddy Cue promoted to Apple SVP, Internet Software and Services

Apple’s executive team is undergoing some changes, and one of those changes is a promotion for Eddy Cue to Senior Vice President of Internet Software and Services. Cue will continue to oversee Apple’s online stores and iCloud and take on the challenge of iAd, too.

File sync service Soonr gets team-based collaboration features

Cloud file sync and backup company Soonr has now launched Soonr Teaming to add team-based collaborative features to its service. Users can form project teams to work together virtually and access and edit files from anywhere, on Mac, PC or a number of mobile devices.

5 Reasons Why Virtual Teams Fail

Poor management, communications breakdowns, badly integrated team members, ill-equipped staff, personality clashes — there are many reasons why a virtual team can fail. What can you do to ensure that your team succeeds? Here are five common failings of virtual teams, and ways to avoid them.

Working Together: How My Virtual Team Collaborates

In an effort to better understand the dynamics of virtual teams, I decided to interview my own virtual team members at the social media marketing agency I co-own, Conversify, to determine what helps them to work well together. Here’s what they said.

Taking a Fresh Look at Glasscubes for Virtual Collaboration

Glasscubes, a virtual collaborative workspace provider, seems to be flying under the radar, but not for a lack of innovation. The company recently announced some new features and a shift in overall direction. I spoke with its founder to get some insight into what’s happening.

The Future of Web Working: Management

If you work from home now, congratulate yourself: chances are, you’ll be managing the web workers of tomorrow. As businesses move their workers out of central offices and embrace the distributed model, even jobs closer to the central core of an organization will be done remotely.