Ever heard of Knowledge-Event Management? This new technique, developed at the University of Central England, is designed to help construction firms squeeze out wisdom from what they know. Project director David Boyd tells all.

The bricklayers are here, bright-eyed and bushy-tailed. Brilliant. But they鈥檝e got no mortar because the builders鈥 merchant hasn鈥檛 delivered the sand like they said they would. There goes the programme, there go the bricklayers, there goes the site manager鈥檚 juicy bonus.

How many times has this happened before? Even more depressing: how many times will it happen again?

Construction is filled with bright, capable and experienced people, but in a real sense we just never learn.

How can we? It was that very question that launched us on an 18-month experiment with 12 small and medium-sized companies across the country. We wanted to try a knowledge management technique that would turn site managers鈥 day-to-day problems into the sort of wisdom an entire company can not only absorb, but act on.

Knowledge management (KM) has been around for some time, but it tends to involve costly consultants or sophisticated software, so it鈥檚 usually the preserve of big companies.

Most UK construction firms are small. In 2002, 99% of them had less than 59 staff, employing 62% of the industry鈥檚 workforce and delivering 44% of the industry鈥檚 workload (in monetary terms) [DTI, 2003]. Compared to big companies, these small-to-medium sized enterprises (SMEs) cannot invest heavily in innovation and development, and take a less-formal strategy in management with an emphasis on survival and cash flow. Their staff are heroic multi-taskers but they鈥檙e stretched, so knowledge in SMEs tends to be local, oral, tacit and contextual 鈥 in other words, trapped in the heads of these busy individuals.

Looking for an easy KM technique for them, we came up with Knowledge-Event Management (KEM). It鈥檚 simple. You don鈥檛 need squadrons of management consultants, or company-wide IT rollouts. You just need a Dictaphone and someone to talk to.

Power learning

Site managers rarely have time to reflect on their experiences, so knowledge gained is lost from one project to the next. As a result, mistakes are repeated, resources are wasted, and organisations do too much fire fighting.

Why? In 1984, organisational behaviour expert David Kolb argued that effective learning requires the full journey around the four stages of a cycle, namely concrete experience, reflective observation, abstract conceptualisation and active experimentation. The problem is that we tend to evolve skills in one area and so 鈥榮hort-circuit鈥 the full cycle. This means we don鈥檛 learn as much as we could. 鈥淪o,鈥 we wondered. 鈥淗ow can construction SMEs process their hard knocks more profitably?鈥

In this project, 28 site managers used audio diaries to record events that upset the flow of things. They could have been technical issues or people issues. Written diaries might have worked, but we felt the need for writing would put people off. It takes a certain skill and too much time. Besides, construction is a markedly oral industry. The spoken word is richer in meaning because of nuances, body language and context. So we decided on Dictaphones: cheap, easy-to-use, and readily available.

But just recording events wasn鈥檛 enough. How do you encourage deeper reflection or create knowledge that can be transferred? We used the military concept of debriefing 鈥 mining an experience to develop new strategies. So after a number of audio diary entries, we debriefed participants for half an hour and made a chart, called a target diagram that helps identify the issues that sparked the event 鈥 not just the obvious triggers, but the wider issues at play.

The next step was getting what we learned out to the rest of the company. This wasn鈥檛 easy. Wider dissemination requires multiple methods, as there are different types and levels of knowledge. Factual knowledge can be communicated easily through poster, newsletter, email and web page. Process knowledge needs more interaction between people so we used workshops, quizzes and informal critical conversations.

In action

We did 109 debriefings and they really show the complex decision-making managers have to undertake 鈥 sand not arriving on time, for example. This really happened.

Mr T, the site manager on a small site, had to decide what to do: upset the bricklayers by laying them off without pay, keep them on and lose the money or pay through the nose for an emergency batch from another merchant, losing time and money. In the end he negotiated with the bricklayers and laid them off for half a day.

Speaking into his Dictaphone while it was all still fresh, Mr T said materials delays were common and that the supplier was to blame. He thought he should be stricter on suppliers and order earlier if space and cash flow allowed. But in the debriefing, a deeper discussion led to some more profound learning points that the company as a whole could take on board.

There were the usual constraints: top bricklayers are scarce, a good relationship takes time to build, you can鈥檛 store much on a small site, head office orders the sand and chooses merchants on lowest cost, so you can鈥檛 cancel this merchant and re-negotiate with another, etc.

While taken for granted, these factors also combine to ensure that disruptions will happen 鈥 like the non-appearance of sand when it really matters. So Mr T can have words with the merchant, by all means, but the firm can learn a few things too, such as:

  • Setting up good working relationships with subcontractors and individual workpeople allows more flexibility and minimises disruption from problems.
  • The service from a merchant needs to be negotiated as well as price.
  • The relationship between head office and site needs to be clearer regarding responsibilities for site costs, site performance and individual bonuses.

Costing Knowledge

We found that KEM helped us put a price tag on disruptive events. For example, a half day鈥檚 money for bricklayers wasted 拢400; the acceleration cost of overtime to the bricklayers was 拢600; the time involved in contacting the supplier, negotiating with the bricklayers and other trades, extra work for head office ordering and contract managers and reprogramming was calculated at six hours (equivalent to 拢300). At the same time, there was a reduction in the site manager鈥檚 productivity both due to the missed opportunity of improved efficiency and the demotivation due to the frustration, estimated as 拢200 (this could be a lot higher if the manager was prevented from closely monitoring risks). The total for this small incident was over 拢1500. However, if the repetition of this is considered then in this 拢400,000 project, then maybe 拢6000 is wasted in rescuing failed delivery. This might amount to 20% of the profit. You can see how small incidents like this are haemorrhaging money from the company.

Did it work?

Yes. We surveyed participants and this turned up some notable results. For instance, two thirds of respondents said their organisation did not recognise the skills they had, which I think indicates the richness of the tacit knowledge embedded in organisations and the huge potential for companies to benefit from it. All respondents agreed that it was possible to make improvements through learning from events and debriefing.

60% liked the audio diaries, 90% agreed that debriefing was effective. 60% believed their companies could perform KEM themselves, although there were barriers, such as an unwillingness to share knowledge, reluctance to change, and incoherent company strategy.

Industry Self-operation

Ultimately, firms should be able to do KEM themselves without us facilitating. A number of the companies are looking at using it in their own way, like doing the event collection and debriefing at the same time at site meetings, or taking one or two events to the post project review meeting and using the target diagram to analyse them. These variations should work fine. What matters is the act of recording, reflecting and then using the knowledge.

A free handbook is available, which allows companies to operate KEM themselves. You can start with one-off activities involving a few people with little commitment, and see how it feels before moving to a substantive, company-wide exercise.

You may not be surprised to learn, too, that we鈥檙e available for consultation, so get in touch if you want more information.

Bob Macpherson - Director, Pettifer Construction

I started in the industry 40 years ago with basic calculators, no fax, no email, no CAD, no web, no mobile phones... But I鈥檓 not convinced our communications have improved much. How many times do we reach for the keyboard instead of the phone or, better, meet people face to face? We鈥檝e introduced a bespoke safety management system on all its sites and when that鈥檚 done, we鈥檒l be using some of the lessons learnt on the KEM project.

It showed the ripple effect of small events on site 鈥 the far-reaching repercussions they have. Late supply and incorrect information from consultants put pressure on the site managers. Our guys have a tough job on site and perhaps consultants - and indeed our own office management - don鈥檛 always appreciate this.

Leeon Wong - Project Director, Spring & Co

Initially the MD asked me to get involved so of course obliged. But I soon got interested in the whether KEM could be done without new IT systems, and whether it worked.

We started implementing it early this year. We haven鈥檛 introduced any new IT systems. We use existing ISO 9000 methods.

A member of staff records an event once a week. They鈥檙e on a monthly rota. The MD鈥檚 on it, too. Each month we do a debrief. Debriefers rotate as well, so everyone experiences it. From debriefing we raise improvement logs proposing actions. In the first year we expect to raise 48 of these logs. We鈥檒l do a yearly review of the logs with senior staff to ascertain trends and make strategies.

We did this with relative ease because we want to use KEM. But you鈥檝e got to understand the method and the thinking behind it. It is very easy to just transfer the information onto a database, but you wouldn鈥檛 get the most out of it.

KEM encourages the spread of any new successful process. It identifies training needs. It improves staff relations. People know each other鈥檚 capabilities more. We hope it will lead to improved staff retention. We hope staff working remotely will feel more listened to.

Paul Dockerill - Contracts Director, William Sapcote & Sons

KEM turned stories into data that can be used by all. Take the missing sand story. Ironically, the site manager in this instance was allowed only 拢50 petty cash at any one time. He鈥檚 responsible for a 拢1,000,000 project, procuring all site materials, co-ordinating sub-contractors and all health and safety on site, but he couldn鈥檛 be trusted with more than 拢50 petty cash!

When this sort of knowledge is identified, simple decisions can be made to increase productivity in the simplest of ways. We found that sending tapes in the weekly post for line managers to put in a central database doesn鈥檛 consume site managers鈥 precious time.

We鈥檒l introduce it in our partnering contracts and look to promote it with our supply chain partners to tap into the wealth of their knowledge. But be realistic: not all people will buy in, so be selective with candidates. Basic training is required and in many respects it is as simple as a Tool Box Talk.