PM Commentary by Stacy Goff.
Last month’s article, where we interviewed Knowledge, and gained many new insights about her and her family, must have been an interesting one. It received even more “hits” than normal, and not just from spammers… The time viewers spent on the page was also higher than most, a good indicator of perceived value—or maybe they were trying to figure out that strange anthropomorphism of Knowledge. I’ll cover a few loose ends on the themes we covered, and finish with the importance of the Opposable Thumb.
Discoveries at the NASA Knowledge Forum
I took last months’s article with me to this year’s Knowledge Forum. I shared the article with Larry Prusak, one of the key people in Knowledge Management (KM) practice. After reading the article, he sent a polite email. He suggested that the data to information to knowledge relationships are more complex than my simple assertions. I agree, and will leave it at that. After all, that was a 30+ year-old story.
At the NASA event, I saw a difference between my naïve understanding, and these really bright people in KM practice. And, there were some striking parallels. For example:
- My perspective about Knowledge is on the individual side: How individuals grow, develop, and improve their performance. I realized that KM is much more oriented to the organizational accumulation and sharing of knowledge.
- They view Knowledge along the lines of a complete Bloom’s Taxonomy of Learning. At the higher levels, you are dealing with synthesis. They are speaking of “Big K” Knowledge, not drill-and-test memorization—“little k” knowledge. That was a big aha for me.
- My former KM biases were based on this: Much of my time spent in helping project teams (and organizations) succeed, I spend overcoming the flaws of “little k” knowledge. This is manifested by people who memorize enough to pass an exam, rather than to learn how to apply the topic in a project.
- In the NASA event final exercise, participants worked in teams to identify ways to improve the success of organizational KM. During that session, I had another aha! moment. We were all identifying exactly the same actions, These are the ChangeAgent actions I have coached executives, project management offices and functional managers in for years. In what context? To help organizations adopt and adapt project management methodologies—to improve organizational PM performance.
The take-away: Project Management and Knowledge Management have many strong parallels. And, success in improving one in your area will also help in improving the other—for those who are so inclined. We saw exactly the same pattern with the successful Quality movements of the 1980s. Here is an example of the mutual reinforcement of KM and PM: Lessons Learned are one of the greatest opportunities for sharing knowledge in any organization. And yet, in many cases, they are merely recorded—then the same “learnings” are repeated in project after project, over again. That shows nobody learned anything. With a KM approach that actually institutionalizes applied prior knowledge, all projects will benefit, and performance will soar.
This is one reason why the best PM methodologies have a unique project kick-off action: Review the Lessons Learned from similar projects, including those with this team, this technology, and this customer. This might be a good KM policy for you to implement in your organization, if you do not already follow this savvy practice.
Counting the Knowledge-Related Words
Also in last month’s article, I realized, as I read through it later, that I used many words that are surrogates for Knowledge. Those include such words as reflect, understand, insight, grasp, content, perspective, absorb, concept, material, and abstraction. But wait, there’s more: components, decisions, assimilate, mastering, cognitive, learner, answer, intelligence, and application. Clearly, Larry Prusak is right: Knowledge is much broader and more complex than I imagined!
The insights I gained at the NASA Knowledge Forum caused me, on my return home to go online to order a bunch of books. I sought books written by, or edited by many of the people I met at the conference. I never thought I’d be this eager to learn more about this knowledge, no, Knowledge. No longer do I deem Knowledge to be merely the entry-level step of the PM success progressions I promote.
About the Opposable Thumb
A confession: In last month’s article I cheated, when I placed Performance as the top step in the Performance Progression. It is not at all the top step in a progression, but is, in fact, a whole ‘nuther thing. My assertion was that all the other items in the progression are merely Inputs. I often repeat the difference between evaluating all the inputs and processes, versus just evaluating the results. It is just smarter (and more cost-effective) to do it that way. And, this is true whether you are evaluating learning development, or assessing a competent project manager. Or, for an individual’s PM Certification, or identifying the strengths and opportunities for improvement of an entire organization.
About the Opposable Thumb: Rather than Performance being a similar step at the top of the Intelligence Progression, it is a different thing altogether. Just as is the opposable thumb. How many fingers do you have on one hand? Some say four, some five; others may have a different answer. Is a thumb just another finger, or a special category of its own? Thumbs have similar attributes to the “other” fingers, but also have very special characteristics. Thumbs can do a lot more than the other fingers, including repositioning and circumduction. And, thumbs differentiate primates from many other animals. They work with the fingers to strongly grasp, to allow us to use tools; to apply our motor skills, to write, or type, even! These differentiations are so important that Bloom, in his taxonomy, had a separate six-level scale for motor skills!
In the world of projects and programs, PM Performance is not just the top of the Intelligence Progression. It is the opposable thumb. Those who master it wield the tools needed for the team to deliver. To executives, internal or external customers, and all other stakeholders exactly what they want: Business results. These key stakeholders don’t care about all those inputs, they disdain the mystical processes. They want their project results when they need them, and your PM Performance in achieving that is what counts.
Outside of projects there are many other uses for this opposable thumb. See the “thumbs-up” sign, at right, for example. It is curious, the thumbs-up earned by the successful and performing project team could be confused by the uninformed. They might confuse it with the hitchhiker’s futile thumbed request. Of course, different national cultures might disagree about the use of either gesture.
And as a side note: There are a few marsupials, reptiles, amphibians, and others, that also have opposable thumbs. Some even have opposable thumbs on their back feet, something most of us have not yet achieved. But they do not write blog post articles—or hitchhike—yet.