So after exploring the reasons why users still send e-mail (part 1) and trying to analyse the reasons why people have not changed their ways and how products have not helped the people either (part 2). In this third and last part of the essay present six idea’s to fix the fact that people don’t just change easily. The ideas explored are technology driven idea’s that will help users to change habits effortlessly.
So where do we go with this?
Let’s innovate to close the gap now…
Finally, it’s time to present the six ideas that I think we need to fix the problem. Let try to close the gap between the future state and the current situation. The gap currently lacking typically in siloed products and inter-vendor integrations. Because let’s be honest there is no such digital space that is “perfect” but we can try and bridge that gap for end-users by iterating now.
Warning: The ideas are described using an end-user perspective. Not worrying about products limits or feature lack. They just describe what we need to close that gap.
Idea 1: Stop sending me attachments…
So the most common task that people do to collaborate is to send each other files. Of course we want them to use Connections Files. But the practical situation is that people don’t change their ways and still use attachments. So instead of trying to change the people, let’s just change the behavior of the mail client to help the end user. Every time a user clicks the “paperclip” to attach a file to a e-mail, the file attachment gets uploaded to Connections Files (or even just pick a file from his personal files). The user does not worry about “rights” to the file, so instead all receivers get access to the file automagically.
To make the user experience as seamless as possible we mimic the principle of sending an e-mail with a file attachment as closely as possible. So this means, if a file is attached, then the file is upload to Connections Files and a link is inserted into the mail instead. All recipients of the mail should automatically have access in editor mode to the attached file (no matter if that’s to, cc or bcc).
If an e-mail is sent outside the company’s boundaries, then the mail client (or infrastructure) will detect that and it should insert a unique link so that receiving users can fetch the file from the Connections Files implementation. By using unique links for each external recipient you can later on even see how picked up the file and who did not. The unique link to the shared file makes so that it can be fetched WITHOUT the need to login. This way to the sending and receiving users its the same as sending an attachment through e-mail.
Dialogue should be kept to an absolute minimum. All files that are attached this way are put in a separate folder, called “Attached Files” or something like that. So users can later see what files they have sent to others, separate from My Files.
Ps. if you think that the Connections Mail plugin actually already did this, you are wrong. It’s broken, a link is inserted, but the “rights” to the file need to be modified manually. So users get frustrated and stop using it 🙁
Idea 2: All incoming e-mails with attachments are converted to “Connections Files”
Any incoming email is automatically analyzed and attachments will be turned into links on the boundary. Files are automatically uploaded to the Connections Files repository. Users that receive the e-mail within the company’s firewall will get an email with links to the Files in the Connections Files repository. Stop sending me attachments remember. All receivers of the me-ail will be owners of the file, since the mail was sent to them, they own the file.
All files are always put in a user folder, called “Attached Files”.
Idea 3: Seamless integration between Office and Links to Documents
Currently if you have links to files in emails most people will launch a word processing client that uses the web http links to fetch the file and open it. This causes a very bad user-experience for the end user. There is no seamless integration between Office and documents stored in Connections Files. The idea is to change the behavior of the workplace. So that if the e-mail client opens a Web link that points to a “file” in the Connections Files repository. It always opens through the “Connections Desktop Connector” seamless for the user. When the users is done he can simply save the file back to the “Storage locations”. The result will be a more seamless experience. This would be a way better experience than through the http Web interface which is scaring people away.
Idea 4: Improved plugin within Notes to Connections Files and CCM
So in the real world of mixed environments we live in, we will have files in e-mail and links in e-mail files. But people want to have order. Add stuff to folders. With CCM (Quickr) and Notes Connections Files Sidebar plugins you can drag and drop files in nested folders. This helps people a lot to organize. They still want to move their files around and order them. Users want to put attachments into folders (Files) or even nested folders (CCM). From the Notes client it should be possible to drag and drop files into folders or CCM folders. AND a links should be left behind in the e-mails (when removing attachments from mail).
So users can find the file that was moved out of the e-mail. And in cases where files are still attached (old school) to e-mail it can seamlessly be moved into the folder, a link is inserted in the mail object, and the attachments are removed from the e-mail object itself. In all scenarios links are inserted, so a user can later read his e-mail and find the file that way (never forget: old habits die hard).
Idea 5: Forwarding e-mail with attachments
When a user forwards a e-mail with attachment(s) then the mail client should simply re-share the file using the Connections API, this way an user can even track the sharing of his file. The true power of sharing is knowing who files are shared with, even when mails are forward outside the IBM platform you could still track the fact that mail is shared. An user can also track the downloads of his file that was sent to external users this way, even have policies disabling the downloads.
Idea 6: Ditch and remove the whole option of attachments from e-mail clients (i.e. Notes)
So the most radical idea is to not “fix” something that is fundamentally broken, the whole idea of attachments is about sending documents around through a communication channel is flawed. At the time of inception there was nothing better around. So way back it made sense to send e-mails with attachment(s). So even though idea #1 fixes the way of sharing a document by putting it in a centralized place we should make users even think more. Remember the title: Stop sending me attachments!
Why not simply remove the option to “send” files or links? Just remove the option. That way people have to think again about how to communicate with others. Finally they might start to consider the sharing of documents by themselves. Put knowledge in a wiki or write up a report as a blog and share it more openly, instead of sending tasks via e-mail. People just might start using Activities to get their jobs done and communicate tasks with others, instead of dropping an e-mail that needs decoding by the receiver (bad habits die hard).
If the future state is a more holistic view on collaboration platforms, then ESN and e-mail should just melt and become a purposeful platform. You should be able to reply from within an e-mail (on any e-mail client) and the ecosystem should just make sure your “response” is put in the right place (a comment field, a reply to a status update, etc.).
Let’s iterate to the future…
So why this now? The future is bright, but is it not always that bright? Would we want to go forward if the future was bad? So I am a realistic optimist, we need to start to iterate. To take baby steps. It’s not just tools, it is also about people who need to change, too. But that takes time. In the mean time, it should become easier to collaborate. It should be a goal to break the unnatural boundaries of the current products out in the marketplace (and yes, I dream of looking beyond the “one” supplier). The current boundaries make it hard to see how this will end up.
So let’s make an effort to fix what can be fixed first, and in that try to walk toward the future state where people work effortlessly in a purposeful way and get the things done they need to get done in the most efficient way possible.