Knowledge Matters

Understanding knowledge relationships

Is Project Management a Knowledge Management Activity?

scheduleIs project management a knowledge management activity? To answer this question we must first define “project” and “project management”, and then see how it relates to knowledge management (I’ll use the definition of knowledge management that I posted yesterday ).

Projects are different from business as usual, or operational activities, in that they are unique undertakings, are non-repetitive, and often deliver revolutionary change rather than evolutionary change. The Project Management Institute, which is widely recognised as the world peak body for project management, picks up on the uniqueness and temporal ideas by defining a project as ‘… a temporary endeavour undertaken to create a unique produce, service or result’ (PMI 2004, p. 368). Similarly, the United Kingdom Office of Government Commence, which is also a world peak body for project management, defines a project as being ‘… a temporary organisation that is created for the purpose of delivering one or more business products according to a specified business case' (Office of Government Commerce 2005, p. 6).

The key is that projects are finite and have defined timelines; this allows them to be staged. They always consume additional human and other resources, and they involve an element of organisational risk, which often creates conflict and increases complexity. Project management might be defined as:

‘… the application of specific knowledge, skills, tools, and techniques to realise business value through the delivery of a set of tasks, usually in a constrained time frame and an environment of uncertainty and risk’.

Project management is therefore at least a change management and cannot exist without a business context. It is undertaken for a reason, which is usually to gain something for a business entity, be it is a government department, a commercial company, or a non-profit organisation. However, is project management a knowledge management activity?

Well is seems to me that project management is a problem-driven discipline, requiring the application or discovery of discrete knowledge, and I guess this knowledge should be “managed”. My problem is the temporal dimension of a project seems to be at odds with the implicit assumption of knowledge management, which is to preserve or make available knowledge in the medium to long term (otherwise why do it?). On the other hand Reich (2007, p 8) says:

‘Knowledge management in the context of a project is the application of principles and processes designed to make relevant knowledge available to the project team. Effective knowledge management facilitates the creation and integration of knowledge, minimizes knowledge losses, and fills knowledge gaps throughout the duration of the project’.

This makes knowledge management subservient to project management, but I would submit project management as temporary activity is subservient to knowledge management, which is or should be an organisation-wide activity. I’d be interested in your thoughts.

Regards Graham

Reich, B 2007, 'Managing knowledge and learning in IT projects: A conceptual framework and guidelines for practice', Project Management Journal, vol. 38, no. 2, pp. 5-17.

Comments

Preserving knowledge

Hi Graham, My problem is the temporal dimension of a project seems to be at odds with the implicit assumption of knowledge management, which is to preserve or make available knowledge in the medium to long term (otherwise why do it?). Actually, you could argue that the preservation of knowledge is not always a high priority.  Particularly in areas where there is a rapid turnover of knowledge currency, maximising exposure to new knowledge and optimising sharing of this knowledge in the organisation might be more important.  But I would still call that KM! This makes knowledge management subservient to project management, but I would submit project management as temporary activity is subservient to knowledge management, which is or should be an organisation-wide activity. I actually think PM and KM are orthogonal disciplines.  You need both and they don't conflict.Project Management, at its core, is an exercise in information gathering and dissemination.  This is perhaps a little trite but I think I can defend it.  Here's the high level steps of a project as defined by Bob Lewis's Bare Bones Project Management:
  • Sponsorship and governance - who makes decisions?
  • Understanding the project - setting objectives, context, goals, deliverables, and scope
  • Project staffing - who's on the team?
  • Planning the work - who is doing what?
Up until this point, there's no real "problem solving" involved, at least as we would think about KM problem solving.  Lastly we have:
  • Communicating about / doing / finishing the work - obviously KM can shine here, but there's also nothing inherently "project-y" about the actual "doing" of the work.  Exceptions in a project context are again information gathering tasks, eg progress on individual tasks, tracking expenditure, forecasting schedules etc.
 Anyway, just a thought.  Let me know what you think!

Re: Preserving Knowledge

Hi Stephen,

It's good to make contact again, and as usual your posts provoke thought.

I can't disagree with your comment on knowledge currency and maximising knowledge exposure, but I also think there is an element of knowledge preservation in both.  In order for one to know something is current it is first necessary to know that something is not.  

I'm not really sure what you mean by orthoganal disciplines.  Without wishing to sound or be condescending, orthogonal means "at right angles to or perpendicular".  I wonder if you really mean complementary, but if you do mean orthoganal then I need to give this some thought. The notion of an orthoganal discipline is interesting because it implies neither is superior or subserviant - no matter which way you look at a right angle it is a right angle!

I agree that project management at its core is an information (knowledge) gathering and dissemination exercise, but isn't that what knowledge management is about?  Project management by definition is a temporary activity aimed at solving a specific problem.  Perhaps this is too simple, but it is the essence of the definitions provided by the peak bodies. 

I think much of the problem is the simplicity the peak bodies impose.  I've tried to look at this using a blend of the Cynefin Model and Remington and Pollack's structural, technical, directional, and temporal complexity - see "Cynefin, Complexity and Project Management ".

Regards Graham

 

Orthogonality and currency

Hi Graham, I'm certainly not trying to say that knowledge preservation is never needed.  The question is one of systemic focus. I'll use the example of a Help Desk or Service Centre.  Imagine two extremes in how one of these could be set up:
  • All solutions to client problems are documented and managed centrally.  Operators are only expected to refer to the central "bible" for answers, and deviations from this script are heavily punished.
  • No solutions to client problems are documented and managed centrally.  Operators may choose to document and maintain their own set of solutions in the course of their work in any way they choose, but no central authority for "good" solutions exists.
In the first scenario, the knowledge being preserved is only as good as the operators contributing to the organisational knowledgebase.  If the turnover of knowledge is high, the inevitable inefficiencies in this system will lead to user workarounds, incomplete knowledge capture, and worse, low quality organisational knowledge. In the second scenario, knowledge walks out the door as users do, but there is also complete freedom for operators to learn how to operate best on their own.  Let's also assume that operators are judged fairly on performance both individually and as a team in a non-competitive way, so there is an incentive for them to always share and improve their knowledge, practices and procedures.  In this case, we would rely on network effects for operators to rapidly re-obtain necessary knowledge as required without explicit "preservation". I agree that project management at its core is an information (knowledge) gathering and dissemination exercise, but isn't that what knowledge management is about?  Project management by definition is a temporary activity aimed at solving a specific problem. I did mean "orthogonal", I find it a very useful term to visualise non-competing disciplines.  I would tweak your definitions a little, since in my book information is not always knowledge.  I think of "knowledge" as information that provides an entity with tools to solve problems and adapt to change.  So the ability to apply PM principles is knowledge, but the WBS and resourcing schedule is "just" information. Hence my definition of PM is "a temporary activity that enables solving of a specific problem".  A small change, but if you consider KM the actual detailed problem solving bit, and PM the co-ordinating framework, it has some fairly profound implications for how we think about the two disciplines.

Re: Orthogonality and currency

Great response Stephen.  Ilike the tweak to the definition and will incorporate it into my PhD, and a post that is in development at the moment.  The more I think about it the more I like the idea of orthoganal disciplines.  Thanks for contributing.

Best Regards, Graham

project management's core

Maybe project management's core is actually about getting things done, and gathering and disseminating knowledge is a method of getting there?That's looking at it from an outcome perspective and challenges your definition, but OCG's isn't the only definition of project management.And knowledge management is about improving effectiveness (and efficiency) by retaining the lessons from the past, right?If you were to assume PM is a subset of KM would a Project Manager just become a communications hub?  Don't we do more than this? Manage people? Solve problems? Analyse and design things?And projects are often run by people new to 'business domains' where there is very little organisational knowledge available?  Is KM working for them, or is it PM?I think PM and KM are orthogonal disciplines.  That's a good call. 

Re: project management's core

Hi Craig,

Thanks for the comment.  It's been a while since we communicated.

I actually like your outcome approach, which is mine. I'm just using accepted definitions and trying to get a feel for what people really think.

That said the more I think about it the more I think "orthoganal disciplines" nails it.  I discussed it with my PhD supevisor today and I'm going to develop and explore the idea a bit further.  I'll blog my thoughts in the coming days and weeks.  

Many thanks to Stephen Bounds for the idea.

Best Regards Graham 

Copyright © 2004 -2012 Knowledge Matters™ - all rights reserved
The Webpages and Occasional Blog of Graham Durant-Law
E-mail: graham@durantlaw.info

Clicky