How to manage an intranet
Traditional managers often lack the skills required to understand if an intranet is successful or not.
I was once talking to a manager about how the intranet could save staff time and make things easier, when he shook his head dismissively. “It’s not the job of management to make life easier for staff,” he told me. “And the only time I’m interested in is firing time. If you say you can save me one man year, I want to know which man I can fire. Otherwise, I’m not interested.”
Some time later, I was telling another manager that if we made a particular task easier we could save 5 minutes every time that task was completed, and that many thousands of staff members needed to complete that task every month. He shrugged. “5 minutes saved? They could be out smoking a cigarette.”
Indeed they could be. But it is management’s job to manage time effectively. Properly managed, those 5 minutes could help make another sale or help a customer solve a problem. But because of a poorly designed intranet this time was being lost every time a staff member needed to complete this task.
Organizations are simply not structured to allow for time management when that time runs across the organization. Managers manage within the framework of departments or units. They also tend to be obsessed with head count rather than efficiency.
Let’s say that Organization A has 30,000 employees. Let’s say each employee does a particular task on average 50 times a year. Let’s say it takes 10 minutes longer than it should because it’s badly managed. This is costing the organization 15 million minutes a year in lost productivity. That’s 250,000 hours. Or 33,333 days. Or 150 person years. It’s significant.
By improving this task you can save the entire organization 150 person years; but that doesn’t necessarily mean firing anybody. What it does mean is making the entire workforce more efficient, more productive.
Most managers will not be very impressed. They want to know which 150 people they can fire. Otherwise it’s not real savings, not real efficiency. But you can’t fire everybody. Surely it is still logical and practical to make sure that those employees who are still left with the organization can do their jobs more efficiently. Shouldn’t management also have a role there?
The origin of management, in the late Nineteenth Century, was about making the tasks factory workers carried out on a day-to-day basis more efficient. However, when management pioneer Frederick Taylor said that he could make the job of shovelling coal faster and easier, he was initially met with skepticism.
The intranet is the factory of the information worker. And it’s not in a very good state at the moment. No organization would allow its physical factories to be managed with the level of messiness, carelessness, confusion, waste content, and general untidiness that occurs daily on most intranets.
There is a much better way; focus on time and efficiency.
dara says:
Added on December 14th, 2008 at 4:11 pmDear Gerry:
Thank you for the ongoing series of articles.
I think you are very far off the mark in terms of the potential of the Intranet. If it is used to squeeze out five minutes here and there is will become just another rewards and punishment tool for employees. Of course it needs to have a healthy structure but also must adapt to the new ways people are sharing ideas, knowledge and information that is much more ad hoc than in the past. What 20 year old University graduate would want to work in a staid rigid structured environment when they have spent their past few years using the net in all its creativity to learn and share and explore their professions?
Your summary – “focus on time and efficiency” sounds like a statement from the old factories where time motion studies were the be all and end all of control. Those have been replaced by the many better approaches in team work, quality circles and collaborative environments.
Saving time on the mundane tasks is always a good thing and some of the tools on the intranet will help but is not what makes an organization effective or a leader.
The Intranet is best used as a tool to enable employees to collaborate better, to exchange ideas on how to help customers and other employees with their work. By creating a collaborative creative and enthusiastic environment you build innovation, higher productivity and drive out bad practices more quickly.
The best profitable organizations are focused on leadership, teams, collaboration and exploring better ways to achieve goals. If I thought I worked for a company looking to save a few minutes here and there using intranets I would quickly move to an organization. An organization that gets productivity through , as per Don McLeod “people doing what they do well working together with other people doing what they do well” and this is where we can get major boosts in companies.
I am always amazed at the great productive ideas and solid approaches that come from customers, team members, outsiders across network spaces.
Mike Riversdale says:
Added on December 14th, 2008 at 9:10 pmI actually agree with James Robertson that “saving time is a bad metric” and don’t really bother with it: http://www.steptwo.com.au/columntwo/25-reasons-why-saving-time-on-your-intranet-is-a-bad-metric/
Gerry McGovern (blog author) says:
Added on December 14th, 2008 at 10:22 pmDara,
My experience of intranets is very different from yours. I find that young and old staff want to do very basic things like access their pay details and find other people. Now they may well be looking for those other people in order to collaborate with them, but if they can’t find the right person, then so much for collaboration.
Most intranets aren’t even at Web 1. They’re at Web 0. The staff directory isn’t even kept up to date. So let’s get the basics fixed first, and then I totally agree that collaboration can be extremely powerful
Gerry McGovern (blog author) says:
Added on December 14th, 2008 at 10:42 pmMike, we’ll have to disagree here. And while I very much admire James’ work, I disagree with practically everything he says in the article you link to.
His first reason for not measuring time is:
“We’re not measuring end-to-end task completion.” Says who? If I want to find out if I qualify for unpaid leave, or for a mileage allowance, or if I need an image for a sales presentation–these are all end-to-end tasks.
And so what about it being end-to-end? If you can’t fully complete the task in a specific environment, then the efficiency within that environment doesn’t matter? That’s a strange logic.
If a task has five steps, and two of them are completed on the intranet, and three over the phone, then we should’t seek to improve the two intranet steps because …?
“Time saving and productivity is complex,” James writes. But so is life. Does that mean we shouldn’t live life because it’s complex? “So we’ve saved each staff member 2 minutes a day, do they now spend all that time in productive ways? Or do they spend it reading the newspaper or chatting on Facebook?” But isn’t this exactly what management is about–making productive use of time. By this logic we’d leave forest workers with axes because if we gave them chainsaws, they’d die of lung cancer due to all the cigarettes they’d be smoking during all that spare time.
I could go on but I won’t. Maybe you and James are lucky to deal with a whole other class of intranets than I meet in my weekly work. But what I hear from staff time and time again in organization after organization after organization, in continent after continent, is that their intranets are a giant and insufferable waste of time.
James Robertson says:
Added on December 14th, 2008 at 11:12 pmHi Gerry,
This is certainly a contentious topic! Always worth the discussions necessary to find the middle ground.
Now, I’m going to stand by my post on this topic, and will move on to bigger topics:
Something I’ve written about in the past is that there are four fundamental purposes for an intranet:
* content
* communication
* collaboration
* activity (the ‘intranet as a place for doing things’)
http://www.slideshare.net/jamesr/the-four-purposes-of-an-intranet/
If the intranet just focuses on content and communication, there is no ROI. All we can talk about is reducing the time needed to “find things”, which is very weakly correlated with staff’s actual activities.
Instead, we need to increasingly focus on activity, such as allowing people to actually book travel onling, and not just find the travel policy.
The ROI on these activities can be easily measured, and time (or dollar) savings quantified. This is the intranet becoming more *useful* rather than just *usable*.
So I attack the “time saving” metric to encourage intranet teams to look beyond merely justifying what they’ve already done, and instead to find what else they can do for their organisations.
Let’s get beyond debates over dodgy numbers, and instead explore how we can really make intranets into the invaluable business tool that we all want.
(And no, the intranets I see are no different to the ones you have seen.)
Cheers, James
David Carley says:
Added on December 15th, 2008 at 9:44 amGerry, I agree, it’s the day-in, day-out tasks that company employees need to accomplish quickly and efficiently, it’s no good staff phoning HR to find out when their Christmas holiday is.
This is similar to companies who create ‘awesome’ websites, without taking into account that only a very small percentage of users have 4GB of RAM, and the site ignored all aspects of search.
There seems to be a new definition of manager, they now seem to want to be in a position of control, not in a position of managing.
Yet when it starts to go wrong, what’s there solution - fire someone, or pay out even more money getting someone else to fix it.
Marilyn French-St. George says:
Added on December 15th, 2008 at 1:05 pmIn my experience, inefficient processes (whether internet based or not) become institutionalized and over time start to define the work requirement. I have worked with business teams that insist that the job is defined by multiple steps in a process. They often have difficulty extracting the real business goal from the institutionalized processes. In its worst case, task effectiveness is defined by completion of tasks that do not relate to any defined business goal. While Gerry talks about relatively simple intranet tasks like checking pay details, my experience comes from business contexts that are starting to embed web applications into their work flow processes. Even if there is a glaring need to support collaboration,information retrieval and informed decision making, these goals can often get lost in a morass of inefficient processes.
As a final point I would like to add that time to complete a task and minutes saved are just a couple of ways of looking at efficiency measures. While harder to measure, users’ perception of task complexity vs business goal can often be a more meaningful measure of how mind numbing inefficient processes can become.
Gerry McGovern (blog author) says:
Added on December 15th, 2008 at 2:25 pmJames, I think we’re maybe using slightly different language, and that could be causing confusion. I now focus on tasks– in all their different variations. I see content/applications supporting tasks. I think that’s close to what you call “activity”–and in this sense we are much closer to agreement.
I do think time is a critical measure because I see so many staff dismiss the intranet because they think it’s a “waste of time.” And I think that’s true because intranet teams don’t really, truly focus on treating the staff member’s time as precious and scarce.
Gerry McGovern (blog author) says:
Added on December 15th, 2008 at 2:29 pmDavid–thanks. The amount of times I dealt with organizations with truly terrible intranets that have become drunk on the latest techie gizmo or Web 2.0 fad… Fix the basics. Fix the basics.
Marilyn–excellent point. Strange processes seem to embed into particularly large organizations that sense no useful purpose. Maybe they did ten years ago but they keep getting done long after they stopped delivering value.
Jonathan Phillips says:
Added on December 18th, 2008 at 3:38 pmTime savings are an impressive metric to make intranet teams feel good about the work that we do, but should not form the core of your business case for development.
CFOs might be impressed by the notion of a “million saved minutes of productivity” but in reality, you can’t bank it. Putting a new intranet in will not the dollar equivalent of those minutes to the bottom line. Similarly, it’s also impossible to demonstrate the impact to the business of those reassigned million minutes and it would be a foolish intranet manager who attempts this.
The answer, I think, is to focus on the processes and people that you can explicitly remove as a result of your intranet as they are tangible and bankable.
Marilyn French-St. George says:
Added on December 22nd, 2008 at 2:51 pmI fully agree with Jonathan’s statement that time savings should not form the core of the business case. However the corollory probably should. The system/application should support business tasks in a way that enables users to function more efficiently, effectively AND with confidence. Important business tasks should have outcomes that are measurable. Success criteria can be applied to these measurable outcomes. At the end of the day investment in designing interfaces that optimize tasks to users’ mental models will be mesaured not in minutes saved but rather by such things as reduction of user errors, improvments in the time to get to a decision, greater client and user satisfaction with system/application response (in terms of information returned and time to receive the information), etc
Gerry McGovern (blog author) says:
Added on December 23rd, 2008 at 10:23 amI’m afraid I have to disagree with Jonathan and Marilyn. In my experience intranet teams are scared of time measurement, because most of the intranet teams I deal with come from Communications, and Communications people are not used to being measured in such a way.
However, the overwhelming message that comes back from staff again and again and again is that the intranet is a waste of time because it’s too hard to find stuff and they stuff they find is often not relieable. So, staff seem to think their time is precious. And many intranets are not used nearly as much as they could be for that very reason.
I think time is absolutely at the heart of it, and practically every bit of genuine success I have had on the Web has revovled around treating the time of the customer as the most valuable resource.
Matt says:
Added on December 28th, 2008 at 11:54 pmI’m not sure anyone here, including James, is arguing that it’s not worth treating people’s time as precious, or not worth ‘fixing the basics’ on the intranets we work with in an attempt to make savings.
James makes some good points when it comes to *measuring* these savings on an intranet, though. I find it hard to believe you disagree with ‘practically all’ of his post, Gerry - perhaps you are exaggerating that metric ?!
I’m sure we’ve all seen examples which assume that 10,000 staff members perform task X three times a week and it takes two minutes, so improving it to one minute will save 30,000 minutes a day which at $10/hour means $300K. In all but the simplest of jobs, this is hugely misleading as it assumes that people are otherwise 100% efficient and always have something productive they could be doing instead (and often the number of people and time saved per task look a little over-estimated too).
To put it another way, if each person worked for 5 minutes extra every day, would their organisations benefit from an equivalent % increase in earnings ? Probably not, in most cases.
Gerry McGovern (blog author) says:
Added on December 29th, 2008 at 4:11 pmMatt–Good points. And I think you’re right; it was an exaggeration on my part. (On a general point, I think James is one of the most influentual thinkers and practictioners when it comes to intranets.)
But I do come back to tne main point: time. You can certainly waste time. But you can also use it productively. But if that time is lost, then it not not there to waste or use prodtively. I think time is the bottom line, particularly in advanced economies where wages are high, and which seek to compete with low wage economies.
The productive use of time is the challenge of management. That is why the function of management exists. A great intranet saves time carrying out top tasks.
John Stark says:
Added on January 27th, 2009 at 6:53 pmHow about look at the time savings from another perspective?
Couldn’t those managers who can only justify efficiency by the number of people who could be fired also look at these efforts as a means to keep the organization from needing to hire additional employees?