Is there a future for email?

3204310433_3059fe3c74
French company, Atos, cause a stir recently by repeating again its intention to ban internal email from 2014 that was announced earlier in the year. There has been a fair bit of misunderstanding on the Web about this so I suggest you read this BBC interview with ATOS CEO, Thierry Breton, that explains his thinking behind this strategy.

Most of the critical responses to this idea have expressed an incredulous attitude towards the idea of eliminating what most people consider to be a critical business tool (remember the reaction to the BlackBerry outage a few months ago?). In some respects, many of the arguments against banning email are reasonable:

  • Can you ban email if your customers and clients are using it? (to be fair to ATOS, they aren't planning on banning external email).
  • Rather than banning email, users just need to manage their inboxes better.

However, on balance I think there is good reason for aiming to effectively ban email. But rather than outlawing it, we need to reinvent how we utilise email as a software protocol and also the ageing paradigm of the inbox, particularly where the assumed effectiveness is built on false assumptions around utility and information ownership. At a software level, email offers a number of important features - such as:

  • Interoperability and extendability.
  • It can work offline (although this is becoming less important).
  • For the sender, it costs no more to send messages to 1 or many people where ever they are.
  • Both sender and receivers can store and organise copies of messages exchanged independently of each other.
  • Email addresses act a simple proxies for identification.
  • Email accounts can be created for individuals, groups and also non-human systems.

These features provide a great deal of utility, although we can look at each feature and find many negatives too - for example:

  • Email standards and extensions aren't implemented homogeneously, so users may have problems reading or processing an email.
  • When you go online after an extended absence, your inbox is flooded with new messages.
  • People send many messages that for the receiver are just transient or ambient information - but your inbox treats them as all the same.
  • The independent nature of email messages contributed to fragmentation of the information chain, making it hard to know who knows what and people who should know made end up getting left out of the loop.
  • An email address doesn't actually tell you anything about the user, who they are or why you should trust that identity.
  • High volumes of automatically generated notification emails from non-human systems contribute to information overload.

In summary, we can say that email works as a pragmatic solution, but not without creating numerous problems for individual users and organisations a like. As a result there many solutions out there that help us to deal with everything from email processing to email data management. Some solutions are technical in nature, like help desk ticketing software or records management systems, but others focus on the user as problem and attempt to fix individual behaviours. But ultimately none offer a way of making email the perfect tool and it will take a leap to improve how we communicate and collaborate.

So, what is stopping us taking this leap? Thinking about this from a social experience design perspective, I think there are four key issues that need to be addressed to create something better than the email we use today:

  1. Move to open work as the default. Email provides users with a simple system of directing messages at people - this falls into a mental information sharing model of open only by exception that is the default in most organisations, but it is also supported by a false perception that email is owned by the sender and private if we restrict the names included on the To, CC and BCC lists. Of course, this doesn't mean we stop supporting some private communication entirely!
  2. Everything is Miscellaneous. Centrally designed information systems that enforce fixed, common models for organising information and work process don't work. These were designed with good intentions, but they aren't effective and only encourage the use of personal information stores.
  3. Collaborate by staying apart. We need the same ease of interoperability between different social business software platforms that email offers - I shouldn't be forced to use your system, when I have my own, and neither should you.
  4. Who are you? We need to shift from email addresses as identifiers towards a model where organisations can offer a better user identifier and profile that will enable messaging to take place through the right channel or system.

Its entirely possible that email protocols will continue to play a role in this new environment, but I think it will also depend on other Web 2.0 protocols like Activity Streams, Open Social, and ATOM. This actually hints that the death of email will come incrementally, if we wait for the technology to rise up and present better alternatives. In practice, the tide of data created by other social business software tools will make the traditional email inbox an unsustainable proposition.

The water is rising slowly right now, but don't doubt that the inbox will need to be reinvented at some point - the question is really when and how, not if.

BTW if you found this interesting, you might enjoy this presentation, Architected for Collaboration.

Image credit: Inbox Art CC BY-SA

Misconceptions about social software and knowledge workers

In the early days of Enterprise 2.0 (mid-2000s) enterprise social software was good at toolkit-style functionality. Blogs and wikis gave people useful frameworks and reference materials for doing bespoke tasks. But there wasn’t much functionality for businesses that run a lot of routinized process.

These early tools appealed to high-end consultancies, law firms, PR agencies, and tech startups, which lean towards more bespoke activities. I suspect that’s where people first got the idea that enterprise social software was for “knowledge workers.”

But social software has changed, and changed fast. In the past year, business has started to embrace social software for more routinized processes as well.

Michael Idinopulos highlights an important misconception that enterprise social software is only useful for certain industries or white collar professionals. I agree also that associating these technologies tightly with the concept of the knowledge worker also adds confusion (for the record, I've never agreed that Enterprise 2.0 was the evolution of KM).

I've certainly come across a number of examples in my own work this year that break that traditional view of where and how we apply these technologies. But, I also think we have barely scratched the surface.

I draw encouragement from the non-profit sector where we can more easily see evidence of service (re)design and social innovation at work. Examples such as the LIFE Programme and Patchwork show there is potential for a much richer dynamic that can impact the fundamentals of how we use IT to support people inside critical or complex business processes when they are working at scale. In fact, this goes beyond Idinopulos' call to integrate the common enterprise social software patterns of activity stream and wikis - the focus is really about humanising IT systems.

Just as they are emerging in the non-profit sector, there are opportunities for the profit making enterprise to do the same in their respective domains. But they will only get there if we address the underlying misconceptions about social software and narrowing the use case to supporting the classic, office-based knowledge worker.

Utopia is... touch screens and surfaces

Nicholas Carr thinks these kinds of techno-utopian videos are creepy. I'm not sure about that, although both of these videos are some what homogeneous and perhaps a little 'antiseptic' - but they are marketing pieces, not true works of science fiction. They actually remind me of rather badly thought out 'perfect' user journeys. If you want something a little grundgy, try William Gibson.

For more on Microsoft's vision, see their Office Labs site.

Gary Hamel on management for the 21st Century

In the aftermath of the credit crunch people are thinking about the way banks work, the way financial markets operate, and the values and purposes of the companies that use those markets.

And some of the big management thinkers are beginning to put forward ideas that challenge many of the assumptions that have dominated the way business has worked for the past several decades.

In this progamme Peter Day hears from management guru Gary Hamel and gets his thoughts on the future of capitalism.

I only just got around to listening to this podcast, an interview with Gary Hamel. The title is perhaps a bit misleading, although Hamel did make me pause for thought in light of the #occupywallstreet movement. Is this what he meant by consumers mobilising?

However, this podcast actually contains a broader discussion about the difference between business in the 20th Century and the needs of the 21st Century. This isn't just about "Capitalism", but actually about why and how organisations are organised and managed. The active role of the citizen-consumer is also important and themes such sustainable profitability.

Critically he highlights the challenges this creates for large, legacy organisations built on 20th Century management principles. The practice of management is firmly in the sights of Hamel and he doesn't think academic management theorists will have the answers we need.

He mentions the example of The Morning Star Company, where:

"Our company is operated by colleagues without titles or a hierarchy of unilateral authority. Authority relative to other colleagues' activities is lateral, with our Mission as the guiding principle of action. Although we have grown significantly, we would like to maintain a culture of individual responsibility and self-management. A colleague's influence and success at Lucero Farms is relative to such colleague's integrity, competency, effort, persistence and straight-forward persuasiveness."

This, he suggests, is a model of management for the 21st Century.

Thinking about this example, if you step back for a moment to reflect on the technology changes and human events going on around us right now, then they suddenly stop being isolated phenomenon and instead you realise they are all taking place on the same backdrop.

Productivity And Business: Seize the day!

According to the lead researcher, Dr Christina Boedker, high-performing workplaces are up to 12 per cent more productive and three times more profitable.

...

The management practices that do best, according to the study, are being highly responsive to changes in customers' and suppliers' circumstances, encouraging high employee participation in decision-making, achieving on-the-job learning through mentoring and job rotation, making effective use of information and technology and attracting and retaining high quality people.

Emphasis Added

via smh.com.au

Ross Gittins, Australia's respected and clear thinking economics columnist for the SMH, reports on the government sponsored research into productivity by the Society of Knowledge Economics (SKE).

Ross notes that only 15 per cent of the research sample exhibit the characteristics of such "enlightened" business practices. I imagine that the other 85% are still waiting for bottom line ROI on the minutiae of individual practices, tools or technologies to be proved - symptom or cause do you think?

UPDATE: Here is the actual report. Hat tip to Nicky.

Amazon's new Kindle range


The Kindle Fire's reasonable price, together with the potential of widespread Android app support, makes the device an enticing option, especially for families who want to give a tablet to the kids without having to blast through five bills. The Kindle Fire is clearly first and foremost an entertainment-consumption companion to Amazon's services. The ability to install apps and do anything more with the tablet--handling email, sharing photos, and the like--really feels like a secondary operation. At that point it makes me wonder whether the Kindle Fire is truly a “tablet” or just a content-playback machine with some extra smarts.

In many ways, the Kindle Fire isn't trying to beat the iPad or the Android-tablet masses at their own game. The Kindle Fire is doing its own thing, and going after a totally different audience.

Amazon's refreshed Kindle e-reader product line has definitely caught my eye this week. In particular, despite its possible limitations, the new Andriod-based full colour Fire (but sans e-ink) "reader" looks like it really could shake up the overall tablet market. I have a family who love to read and its certainly feasible to imagine kitting the family out with the lower priced Kindles (we already have one). Unfortunately, the Fire at this stage will be available from November but only in the US.

Incidentally, there have been a lot of comments that the Fire looks like RIM's Playbook - apparently its because Amazon enlisted the assistance of the same manufacturer. A few people have also raised concerned about Amazon's Silk Browser, but I can't really see any difference (in terms of privacy risk) from other caching, social networking and other proxy services that already exist. If you don't like the Amazon Web Services (AWS) based acceleration feature, just switch it off or buy a different device :-)

Beware of Digital Taylorism

E2.0 tools today are typically not integrated with the rest of a company’s applications. So the unstructured / emergent / social work happens in a totally different digital environment than the structured / pre-defined / formal work. Orders get filled using the ERP system, while conversations about why the order’s not getting filled happen in email, IM, a wiki, and so on.

For some purposes, this is OK. Narrating your work via blogs or microblogs so that others can find you and access your expertise is a great standalone use case, as is narrating your ignorance —   asking questions to the enterprise as a whole without guessing in advance who will know the answer.

But most informal collaboration, I bet, happens ‘close to’ the formal work of the enterprise. So the digital environments that support the formal and informal work should also be very close to each other, either within the same application or across tightly integrated ones. Data and decisions (“OK, go ahead and increase the customer’s credit limit so we can ship the order”) should be able to flow easily between the systems for formal and informal work. This is not a new point, but it bears repeating for exactly the reasons Laurie mentions. Unless and until this happens, E2.0 is much less than it could be.

Yes, its easy to drink too much social 'Kool Aid'. But that applies as much to the process centric view, as it does to focusing only on the "social, humane, people-centric" perspective.

My point about the impact of electricity on industry still stands. Hard nosed contextual collaboration built around a bad or inefficient business process is only stop-gap measure (if even that), but is probably easier to sell in the short-term. This kind of digital Taylorism is bad not because it ignores the soft stuff, but because the pseudo-science of scientific management was debunked a long time ago.

Part of the problem is that we still get confused by the differences between ideas such as user-driven computing, lightweight enterprise IT approaches, creating good user experience in enterprise apps and social software. Each offers benefits and there is a strong relationship between these four, but they aren't mutually inclusive all of the time.

For example, improving a process might not be so much about contextual collaboration but could simply be about applying lighter Web inspired IT solutions to enterprise problems. I remember seeing this example of a shipping company having a bottom line impact with Enterprise RSS back in 2008.

The Lightbulb and Social Business

Factoryandlight

Can you spot the difference between the two photos?

There are probably quite a few you can identify, but the thing I want to highlight is the use of electric light in the second, modern factory example.

Its interesting to reflect on this and the perceived hype around social business and how different experiences point to the need for practical and pragmatic use cases. The main argument is that we need to integrate social tools into existing workflow.

Back in the early phase of the industrial revolution, factories were messy, dark places because the physical work environment was built around the constraints of their belt and pulley driven mechanised systems. There was no prior model of employment to set expectations on the impact on the workers themselves either!

So, my question:

Was it the lightbulb that revolutionised the industrial workplace or electricity?

My observations:

  • At the moment I get the impression we are focused on the lightbulb. The social media activitists are crying, "Install lightbulbs!" Its no surprise we will expect confused reactions and failure.
  • If that's the case then you need to be pragmatic. However, don't ignore the lesson that the electric lightbulb had a broader impact than just lighting the shopfloor - can you leverage that instead?
  • Finally, retro fitting electricity had less of an impact (and take up) than on the businesses that converted entirely to electricity - but this didn't happen all at once across industry, because it wasn't economic.

BTW This isn't the first time I've blogged about this historical comparison, but for a quick overview of the broader impact of the electric light see this micro-site from the Smithsonian.

Image Credits: Colt's armory complex - East armory workers CC-BY-NC-SA and Seagate Wuxi China Factory Tour CC-BY.