Getting it right in government

by Elizabeth on 20/06/2007

The UK Government’s Public Accounts Committee has put together a report called ‘Delivering successful IT-enabled business change,‘ about how government projects are performing.  The report concludes that some projects actually turn out pretty well, but those learnings are not carried across to other projects run by other departments.
This won’t come as a surprise to project managers.  We know the value of post-implementation reviews, but the process of sharing the information that comes from them with colleagues is not easy, for several reasons:

  • projects normally have a degree of uniqueness about them, so it is hard to transfer the lessons learned to other projects
  • there is no clear, industry-standard way of managing this transfer of knowledge – databases rely on individuals going to search for the data and face-to-face meetings rely on individuals holding all the company’s lessons learned in their heads
  • we rely too often on the project team members present during the post-implementation review to cascade the minutes/outcomes of the meeting to their departments: if teams of project managers can’t transfer lessons learned between themselves there is little hope that other departments will manage the feedback and learn from it for their next involvement in projects.

Is there a simple way of communicating lessons learned in a way that makes that knowledge accessible to everyone at the time that they need it?  Now there’s a product that really could improve the success rate of government projects (and everyone else’s projects too).

Share

No related posts.

  • http://www.passion2publish.com Bud Caddell

    Elizabeth,

    Fantastic Blog!

    I work for Imagination Publishing, and am helping to produce feature content for PMI.org. I’m interested in finding sources that know how to write for the web and of course, know project management. If you’re interested in pitching ideas or writing stories, please send me an email and we can follow up.

    Thanks!
    Bud

  • http://fantastic-machine.com/penina/ Penina

    Hi Elizabeth,

    Is it a product? or a culture? or a combination of both…?

    Taking lessons learned across project boundaries requires time and space to process those lessons. Maybe it’s that “Meeting room C” you spoke of in a previous post. When we can relax and bounce ideas and impressions off colleagues, and across departments, formal “lessons learned” become internalized, become wisdom, and form positive professional relationships. Those relationships become vast and pertinent resources that cannot be matched by any written resource.

  • http://www.elizabeth-harrin.co.uk Elizabeth

    Penina, you’re right, of course. The problem with just having it as a culture means that once people move on, they take that organisational knowledge with them. Culture and formally recorded lessons learned can work together to ensure that the knowledge is at least shareable – we should be encouraging both!

  • http://fantastic-machine.com/penina/ Penina

    Hm… my son is going to be annoyed, because I promised I would get off the computer… but…

    I totally agree with recording lessons, but I keep wondering when and how others would avail themselves of that recorded knowledge.

    If there has been cross-departmental discussion, then the information *hasn’t* remained with a single person or team. It has been received and consciously absorbed by those who participated in that discussion.

  • http://www.elizabeth-harrin.co.uk Elizabeth

    ‘Consciously absorbed’ – let’s hope so! I’m a great one for documentation, but I don’t think I have ever gone to someone else’s PIR notes to learn what I could improve for my project. I do it by talking to other project managers who have worked with those departments/products before to get an idea of the challenges faced.

Previous post:

Next post: