{"id":412,"date":"2017-05-14T18:24:14","date_gmt":"2017-05-15T01:24:14","guid":{"rendered":"http:\/\/www.ghosh.com\/blog\/?p=412"},"modified":"2018-04-17T11:22:54","modified_gmt":"2018-04-17T18:22:54","slug":"comparison-document-collaboration-methods","status":"publish","type":"post","link":"https:\/\/www.ghosh.com\/blog\/comparison-document-collaboration-methods\/","title":{"rendered":"6 Document Collaboration Methods…Compared"},"content":{"rendered":"

Do you collaborate on documents with co-workers? I.e., do you edit the same doc or file (I use \u201cdocs\u201d and \u201cfiles\u201d interchangeably herein) with one or more people sometimes?<\/p>\n

Duh, who doesn\u2019t, right?<\/p>\n

Unless your company has strict policies, you probably have some options on how you share documents. You could use browser-based apps like Google Docs<\/a> or Microsoft OfficeOnline<\/a>. Or you could email file attachments around.<\/p>\n

(I can\u2019t believe I\u2019m still writing about email file attachments for doc collab; but alas, status quo is hard to change<\/a>.)<\/p>\n

Different users have different preferences and different needs. Some are power spreadsheet users. Some don\u2019t need every word processing bell and whistle. Some are always online when they work. Some travel. Even each individual user may even have different needs at different times.<\/p>\n

Unfortunately, though, there\u2019s no perfect way to collaborate on docs (yet), so I attempt herein to qualitatively (as objectively as I can) compare the six main ways you can edit a doc and share it with others to review and\/or edit. You may use one method primarily, or you may use different methods depending on your current situation. Hopefully, this will help ensure you know your options and the impact to you and others.<\/p>\n

Doc Collab Methods<\/h1>\n

First, let\u2019s look at the 6 primary doc collaboration methods. The typical scenarios include desktop productivity apps (e.g., word processing, spreadsheets, presentations via Google Docs or Microsoft Office) and cloud storage providers (e.g., Box<\/a>, Dropbox<\/a>, Google Drive<\/a>, Microsoft Onedrive<\/a>). But these concepts can apply more broadly to most apps and cloud storage.<\/p>\n

<\/h2>\n<\/div>

1. Web App<\/h2><\/div>
<\/div>
\n

Some applications provide web-based versions that you access via standard browser (e.g., Apple Safari<\/a>, Google Chrome<\/a>, Microsoft Internet Explorer<\/a>, Mozilla Firefox<\/a>). E.g., Microsoft Office has \u201cweb app\u201d versions of Word, Excel, PowerPoint. Google docs only works via browser. If so, then you may have this option. How well integrated this is, depends on the app vendor and cloud provider.<\/p>\n<\/div><\/div><\/div>

2. Mapped Drive<\/h2><\/div>
<\/div>
\n

Many, but unfortunately, not all cloud services make it easy to map a networked drive to your storage in the cloud. (Third party tools like Mountain Duck<\/a> can provide drive mapping.) \u00a0Then, you just access it as you would any network-accessible storage. Latency may be longer, but access is virtually the same. \u00a0Of course, you only have access when connected online.<\/p>\n<\/div><\/div><\/div>

3. Manual Download \/ Upload<\/h2><\/div>
<\/div>
\n

You can manually download a file from the cloud and edit it with your desktop app. \u00a0But then you\u2019re responsible for uploading it back to the cloud properly. \u00a0Careful, though. Each cloud service may have a different way you must upload the doc, so it appears as a new version of the existing doc. Do this incorrectly, and you may lose all previous versions or create a duplicate file.<\/p>\n<\/div><\/div><\/div>

4. Auto Upload<\/h2><\/div>
<\/div>
\n

Some cloud providers will provide the ability (usually requiring some desktop software install) to simply select in the browser to \u201cEdit on Desktop\u201d. The file is automatically downloaded, edited with the correct desktop app; and any time you save, the doc is automatically uploaded to the cloud as a new version.<\/p>\n<\/div><\/div><\/div>

5. Background Sync<\/h2><\/div>
<\/div>
\n

Most (all listed above) cloud services provide the ability to automatically and continuously keep select files synchronized on your desktop with the cloud. Thus, you can simply edit the local copy of the doc and the cloud\u2019s background \u201csync\u201d program will upload it to the cloud as a new version automatically.<\/p>\n<\/div><\/div><\/div>

6. Email<\/h2><\/div>
<\/div>
\n

Traditional emailing of document around as a file attachment. \u00a0Depending on your email program, you typically have to download the attachment, edit it and email it back or on to the next editor. Savvy users will rename the file to indicate a version change because otherwise, it\u2019s difficult to tell which version is the latest.<\/p>\n<\/div><\/div><\/div>

<\/div><\/div>

Considerations<\/h1>\n

Next, let’s look at the main trade-offs when considering each collaboration method.<\/p>\n

<\/h2>\n<\/div>

App Functionality<\/h2><\/div>
<\/div>
\n

Do you need full application functionality? \u00a0Web versions almost always have less capability than desktop versions. \u00a0What you can do in a browser is limited or at least difficult. \u00a0Some may say they only use 20% of an app\u2019s functionality, but often different people use different 20%s, so the org uses a lot more than 20%.<\/p>\n<\/div><\/div><\/div>

Master Version<\/h2><\/div>
<\/div>
\n

Different versions of the same doc is a recipe for miscommunication. \u00a0Ideally, you want a sole master version of the doc, a “single version of the truth.\u201d<\/p>\n<\/div><\/div><\/div>

Edit Collisions<\/h2><\/div>
<\/div>
\n

When multiple users edit different copies of the same doc, then you end up with multiple inconsistent versions that must somehow (usually manually) be reconciled.<\/p>\n

Without File Lock capability, all desktop options will create edit collisions if multiple users edit at same time (before updating the cloud). So, some situations may be more prone (e.g., lots of co-editing at same time, larger files, etc.)<\/p>\n<\/div><\/div><\/div>

File Lock<\/h2><\/div>
<\/div>
\n

This \u201ccheck-in\/check-out\u201d, or \u201clocking\/unlocking\u201d prevents edit collisions by requiring editing by one person at a time. It\u2019s key to prevent edit collisions, but this prevents concurrent editing too. Users must be trained to check-in (unlock) asap to avoid preventing anyone else from editing.<\/p>\n<\/div><\/div><\/div>

Possibility of Lockouts<\/h2><\/div>
<\/div>
\n

With the ability to lock a file, comes the possibility to forget to unlock it again, preventing anyone else from editing the file. Usually, there are overrides, but then you\u2019re likely to lose the edits of the user who forgot to unlock the document.<\/p>\n<\/div><\/div><\/div>

Concurrent Editing<\/h2><\/div>
<\/div>
\n

Allow multiple users to edit the same document at the same time. Ideally, they can see each other\u2019s edits in real-time.<\/p>\n<\/div><\/div><\/div>

Offline Editing<\/h2><\/div>
<\/div>
\n

Ability to edit a doc when not connected to the Internet (offline – e.g., on airplane without connectivity).<\/p>\n<\/div><\/div><\/div>

Local Diskspace Usage<\/h2><\/div>
<\/div>
\n

How much local PC disk storage is required?<\/p>\n<\/div><\/div><\/div>

<\/div><\/div>
\"6<\/a><\/span><\/div>

Bottom Line<\/h1>\n

Unfortunately, there’s no perfect solution for all people in all situations.<\/p>\n

If you don’t need the advanced capabilities available in the desktop app, and you don’t need the ability to edit offline, using the Web App version is usually a great solution. \u00a0Keep in mind, however, the context of “you.” \u00a0For example, and individual may only use 20% of a mature application’s (e.g., MS Excel) capabilities, but if different individuals use different 20%s, then the organization may need to enable the choice of using the desktop application.<\/p>\n

Email is clearly not optimal for document collaboration or co-editing. \u00a0However, it’s probably still the most common method. \u00a0This has to do with many factors including status quo (effort to change habits), flexible enough to cover every edge use case, possibly slightly easier for the individual at greater expense to the group (a topic for behavioral economics).<\/p>\n

Selection of other methods that allow use of desktop app still requires consideration of the situation. \u00a0If it’s unlikely that lots of edits to the same doc will happen at the same time,\u00a0and<\/span> the overall storage requirements are not large, then automatic sync is easy and convenient. \u00a0However, in many organizations, the doc library can get too big to store on everyone’s PC (not to mention security concerns), so auto sync (without elaborate selective sync efforts) may be impractical.<\/p>\n

I did not get into security here, as there are lots of variables. \u00a0For example, editing a doc from a public kiosk is always risky, and each editing method has its own risks. \u00a0Obviously, any time you’re storing a local copy of a file, there’s a possibility that someone else may get to it. \u00a0Even the auto upload options inevitably are saving at least a temporary local copy of the file; who knows if proper housecleaning is being done. \u00a0And even browser apps cache data\u00a0locally, so beware of editing docs on insecure PCs.<\/p>\n

The good news is there are better doc collaboration options than email. \u00a0The bad news is there’s no perfect solution. \u00a0It’s easy to stick with the status quo, but if they really thought about the costs to team productivity or of making bad decisions, more teams and companies would proactively move to non-email doc collaboration alternatives as quickly as possible.<\/p>\n<\/div>

<\/div><\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":2,"featured_media":466,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,4,6],"tags":[],"class_list":["post-412","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-collaboration","category-email","category-knowledge-management"],"_links":{"self":[{"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/posts\/412","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/comments?post=412"}],"version-history":[{"count":5,"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/posts\/412\/revisions"}],"predecessor-version":[{"id":488,"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/posts\/412\/revisions\/488"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/media\/466"}],"wp:attachment":[{"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/media?parent=412"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/categories?post=412"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ghosh.com\/blog\/wp-json\/wp\/v2\/tags?post=412"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}