Email and Broken Business processes

Luis Suarez pointed to an interesting post "Broken business processes contribute to our email overload". The core of the post is:
Socialtext has connected the dots between a few reports to discover that a great deal of our email comes from handling exceptions. Because business processes don't have a system to translate them into practice, we spend more than a quarter of our day emailing about the exceptions to the business process rules.
Worse than the volume of email is the amount of mental energy required by each email recipient, ergo worker, to parse each exception and determine what to do with it. E-mail was once intended to increase productivity and has now become so voluminous it is counter productive. Basex determined that business loose $650 billion in productivity due to the unnecessary email interruptions. And, the average number of corporate emails sent and received per person per day expected to reach over 228 by 2010.
Email overload due to broken business processes... Wow. I've never thought about it in that way. This would be very interesting to investigate in more detail. To which part of the email overload does this account? I don't think all of it. Because email also helps us communicate over business processes. Not all our work - I'm happy to say - can be defined or is related to business processes.

Comments

  1. AnonymousAugust 26, 2008 at 10:49 AM

    Samuel,

    Interesting finding, and one that I can relate to. In my experience as a communications consultant I have often seen that a so-called communication problem is really an organization problem. We are not bad communicators, just bad organizers. The core of the organization problem is often the total lack of understanding of the core processes that we work on, and the lack of clear division of work related to these processes . Hence, the need to align, ask questions, cover our asses, stop bad interventions, you name it. This is a great angle to approach the e-mail overload.

    ReplyDelete

Post a Comment

Please leave a comment! Just log in using one of the formats and if you want me to get back to you. Otherwise comment anonymously.

Popular posts

Keep the Intranet Small

Image
This tweet by Jonathan Phillips ( @digitaljonathan ) triggered to finalize this post, that's been burning in my draft box. I've always been intrigued by how unsuccessful many intranets are. And there are all kinds of good reasons for intranet failure. One of the things that is hardly ever mentioned is: Shouldn't the intranet be smaller? Usually intranets are huge. Lots and lots of pages with lots and lots of content. With complex navigation. The intranet  evaluation surveys almost always show employees only use the news page and people finder. But still we build and maintain nice big intranets. Not only stats point to smaller intranets. There are others reasons as well. I came up with a few. If you have more, just leave a comment. Here's my list: -            user requirements: users don't require large intranet -            search/navigation: searching and navigating a small intranet is easier than in a large intranet -            mobile: the content of the
Read more

Enterprise 2.0 Research

Image
There's not too much fundamental research on Enterprise 2.0. Deloitte recently published interesting research done on enterprise 2.0 implementations and their return-on-investment. In the EU research has also done as well. Study is being done for the European Commission and it was carried out by Tech4i2, IDC and Headshift. What was the goal of the study? Goals of the study To provide a clear definition of Enterprise 2.0 is, describe the market and the positioning of EU industry, also in comparison with US and Asia; To analyze the take-up of Enterprise 2.0, the organizational requirements, and the role on the transition to a knowledge based low-carbon economy; To collect evidence on its macro-economic impact, as a market opportunity for the European Software industry and as a productivity tool for European business; To identify and analyse both the direct and contextual challenges, including the need for Next Generation Access and the legal barriers; To analyse an
Read more

Innovation in Turbulent Times

Image
I love reading articles about innovation. And every now and then you read one that is very interesting. "Innovation in Turbulent Times" by Rigby, Gruver, Allen (in HBR, June 2009) is one of them. This article takes fashion companies as an example for continuous, year-by-year innovation. And how successful fashion companies are usually led by two people: a left-brainer and a right-brainer. "If you don't have highly creative people in positions of real authority, you won't get innovation. Most companies in other industries ignore this lesson." They extend this to show that successful non-fashion companies have the same kind of leadership. And this kind of leadership is usually also characterized by a long-term relationship. I think this concept can also be extended to teams and projects as well. More often than not, people are good at one or the other: thinking up great concepts or ideas, or, making them. In teams and projects we can learn from this as
Read more