Learning is the work

continued from Why do I need KM?

Work is learning and learning is the work.

Why?

Because the nature of work is changing. For example, automation is replacing most routine work. That leaves customized work, which requires initiative, creativity and passion. Valued work, and the environments in which it takes place, is becoming more complex. Professionals today are doing work that cannot be easily standardized.

In complexity, we can determine the relationship between cause and effect only in retrospect. Think about that. It puts into question most of our management frameworks that require detailed analysis before we take action. It also shows that identifying and copying best practices is pretty well useless.

In complex work environments, the optimal way to do work is to constantly probe the environment and test emergent practices. This requires an engaged and empowered workforce. Emergent practices are dependent on the cooperation of all workers (and management) as well as the free flow of knowledge.

future jobs work valueWork in complex situations requires a greater percentage of implicit knowledge, which cannot be easily codified. Research shows that sharing complex knowledge requires strong interpersonal relationships. But discovering innovative ideas usually comes through loose social ties. Organizations need both, and communities of practice can help to connect tight work teams with loose social networks. Communities of practice can provide a safe space for professionals to challenge each other at the cutting edge of their expertise.

Effective organizational knowledge-sharing for this new world of work needs individuals who are adept at sense-making. One framework for this is personal knowledge management.

PKM is a set of processes, individually constructed, to help each of us make sense of our world, and work more effectively.

Personal = according to one’s abilities, interests & motivation
(not directed by external forces).

Knowledge = connecting information to experience
(know what, know who, know how).

Mastery = getting things done
(not being managed).

PKM connects work and learning, guided by three principles:

  • Seek playfully to connect.
  • Make sense and be empowered through learning.
  • Share to inspire through your work.

PKM is individuals sense-making and sharing their knowledge.

curation to socialThe future of work is customized, complex, and intangible. In this environment, sense-making and knowledge-sharing become critical skills. This will be in our teams, communities, and networks; but mostly it will be individual workers engaged in all three at once.

The most effective learning in the new world of work will be when engaged individuals, working out loud, share their knowledge. Training and education will remain inputs, but minor ones. One concrete result of this sense-making and knowledge-sharing should be performance support. As people work out loud, they can identify and develop tools and techniques to support emergent practices. In the 70:20:10 Framework, Charles Jennings describes workplace learning as based on four key activities:

  1. Exposure to new and rich experiences.
  2. The opportunity to practice.
  3. Engaging in conversation and exchanges with each other.
  4. Making time to reflect on new observations, information, experiences, etc.

This is where learning is the work.

70-20-10

Why do I need KM?

In response to my post on relevance, my long-time friend Ralph Mercer asked, “Why do I need KM at an institutional level when information is ambient at a global level and personal at a hyper local level?” This illuminates an observation made by Thierry deBaillon, which I have often quoted, “The basic unit of social business technology is personal knowledge management, not collaborative workspaces.” We are surrounded by information and have many ways to collaborate, but unless each person has effective sense-making processes, social business networks are mostly noise amplification.

Collaborative knowledge work must be coupled with cooperative knowledge sharing. Cooperation, or sharing without any quid pro quo, is the foundation of personal knowledge mastery. PKM is based on playfully seeking knowledge, not task-driven searching. It is also about sharing to inspire, not because you have to. The results of PKM can then be used in collaborative work.

pkm connects work learningPersonal knowledge management is the only solid foundation of organizational knowledge management (KM). Without PKM, there is no KM, just databases of (mostly) unused information. Only individual knowledge workers can transcend the divisions between work teams, communities of practice, and social networks. Individuals connect these entities through their participation in them.

PKM is the active process of being cognizant of our networks and engaged in our communities, while still working with our teams. These teams, and the organizations they work in, have an opportunity to harvest some of the PKM knowledge artifacts of their members. However, individuals have to retain control of their own PKM processes, due to the knowledge-sharing paradox.

individuals enable knowledge flowThe gap I see in many collaboration initiatives, enterprise social network software implementations, and other social business projects, is a failure to help develop PKM skills. A course is not the answer. Allowing time to develop skills, and providing feedback, is a much better approach. Developing PKM skills is probably one of the best investments any knowledge-intensive organization can make.

Why PKM?

Have you ever tried to find something you saw recently on the Net but don’t remember where you found it? On Twitter, I mark my favourites and review them every two weeks, with the best becoming Friday’s Finds. I think of it as a short-term memory helper.

twitter favesGo back in time and think about something you researched. Can you find it now? By creating a digital copy, you can retrieve it much more easily. I used the SPATIAL model in my Master’s thesis in 1998. I wrote about it on my blog in 2008 (and then our structures shape us) and was able to find a digital copy. The author even commented on my blog post. In 2012 I used the SPATIAL model to reinforce how important the initial design of an organization is, and gave examples of what happens when you pit a good performer against a bad system.  I was able to share it again, when, in-passing, I was asked if I knew anything about educational ergonomics. I was told that, “this model is ideal for our purposes and I am thrilled to learn of it.

Are you ever asked for help on a subject? A hot topic in our region is shale gas extraction using hydraulic fracturing. I knew nothing about it but decided to read what I could. Over the past year, I collected articles on the subject and saved them to Diigo, a social bookmarking service. I was recently asked by a friend if I knew of any resources on the subject. I only had to send him one link. I did this for myself, but was able to easily share with others.

Have you ever had to write a briefing note, white paper, or give a presentation to your colleagues? The posts on my blog are often the raw material for my professional writing. I now write blog posts as preparation for presentations. This helps me get my ideas together, in a more manageable format than a full-length paper. By making these public, I often find out about related resources, recommended by readers. I did this recently on the topic of institutional memory, with this series of blog posts that became a three-hour live presentation:

Lilia Efimova, the original inspiration for my PKM practices, has said that the main problem with personal knowledge management is that we need to take time now, in order to invest in the future. This is hard to see in advance. With a searchable knowledge base of thousands of blog posts and social bookmarks, all curated by me, I can see the value of PKM every day. It’s much more difficult when you start with a blank slate. That’s why a regular, disciplined process is the best way to start. As Jane Hart shows, if you take 10 minutes a day to learn something new, that’s about 50 hours after one year.

Barriers to Knowledge Work

If sense-making is a key part of knowledge work and is also essential for both innovation and creativity, does the average workplace help or hinder sense-making? I noted before that seeking works best with a playful attitude, exploring new possibilities in diverse networks with many connections in order to enhance serendipity. Sense-making, the most difficult aspect, requires a willingness to try new things, empowering through learning. Sharing is necessary in almost all work contexts today and it is through sharing that we can inspire and be inspired.

Barriers to seeking playfully

Jobs:

Jobs are designed around work that can be copied and workers who can be replaced, but anything that can be reduced to a flowchart will be automated. Relying on the job as society’s main wealth-sharing mechanism is a major mistake in the network era, but one that politicians and many others continue to make. We are entering a post-job economy.

Project Management:

Executives may believe that they want insights and innovations but are most receptive to new ideas that fit with existing practices and maintain predictability [e.g. project plans]. Business organizations treat disruptive insights and innovation with suspicion. – Gary Klein in Seeing What Others Don’t

Barriers to empowered learning

Designated learning & development specialists:

Staff who carry out day-to-day duties—and whose productivity you’re looking to improve—should ultimately be the source for defining what knowledge they need and what knowledge they know is valuable to others. – BloombergBusinessWeek

Training as a separate activity

As work becomes more networked and complex, the social aspects of knowledge sharing and collaboration are becoming more important. Learning amongst ourselves is getting to be the real work in many organizations.The New Challenge for Learning Professionals: (PDF)

Barriers to inspiration through sharing

Individual performance measurement:

Performance appraisals are like academic grades and keep the focus on the individual. In the collaborative, social enterprise this is counter-productive. There is no place for this practice in doing net work. In today’s enterprise, work is learning and learning is the work, and it has to be done cooperatively.

Enterprise software:

When it comes to knowledge, and learning, only open systems are effective. All closed systems will fail over time, especially if discovery and innovation are happening outside that system.

Seeing What Others Don’t – Review

Following Gary Klein on his search to find out how insight happens is a pleasurable, even mind-blowing experience. In Seeing What Others Don’t, Klein begins with an open mind and decides that he needs to stay out of the laboratory of puzzle-solving, described in the chapter on how not to search for insights. His perspective is based on what has been my professional practice for almost two decades: performance improvement. Klein says that PI is a combination of reducing errors & uncertainty PLUS increasing insights. Too often in organizations, management only focuses on reducing errors. Klein cites the overemphasis on practices like Six Sigma over the past 30 years as being detrimental to overall innovation; “Six Sigma shouldn’t be abandoned, it needs to be corralled.”

performance improvement klein

In examining 120 cases, Klein found that there are three main paths that insight can follow. [My overview lacks the depth of Klein’s explanations, so please read the book if you really want to understand this.] Klein’s Triple Path Model neatly describes the phenomena of gaining insights. I find the connection path the most interesting because I think it can be enhanced through practices like personal knowledge mastery. Also interesting is that gaining insight is about changing one’s stories. We have stories that we use to explain why we do things. These can be good anchors that give us the right perspective on a situation or they can weigh us down and stop us from gaining insight. For example, the prevailing theory of miasma stopped researchers from seeing that cholera was waterborne or that yellow fever was mosquito borne. It was when some people paid attention to the contradictions, that they gained insight. Once you have insight, that’s it. Klein quotes the author Hilary Mantel; “Insight cannot be taken back. You cannot return to the moment you were in before.” Which of course can make those with new insights seem like such a bother to the status quo.

triple path model kleinKlein has some advice on how “to strengthen the up arrow”, or improve insight. He sees stories as a strong way of sharing insight. Loosening the filters through which information and knowledge pass in the organization is another suggestion. I’d call that democracy. He also says that organizations need to increase their willpower to act on insight. This takes a shift in the corporate mind-set.

Klein counters some of the contemporary perceptions around insight in the research community.

The heuristics-and-biases community has provided us with a stream of studies showing how our mental habits can be used against us and make us look stupid and irrational. They don’t offer a balanced set of studies of how these habits enable us to make more discoveries.

I see the examples in this book as a collective celebration of our capacity for gaining insights, a corrective to the gloomy picture offered by the heuristics-and-biases community. Insights help us escape the confinements of perfection, which traps us in a compulsion to avoid errors and in a fixation on the original plan or vision.

I strongly recommend Seeing What Others Don’t, which provides new perspectives for a wide range of disciplines and practices. Finally, one of the best features of this book is the Story Index, making each one easy to find, even in the paper copy.

You can read more about the ideas in this book on Gary Klein’s blog posts at Psychology Today [thanks to Kenneth Mikkelsen for the tip].

Discerning with whom and when to share

Nick Milton talks about why knowledge does not get “re-used” very easily. Even if knowledge is captured it is not always used by others and Nick cites several blockers:

  • the knowledge was not to hand when they needed it

  • they had no time to go looking for the knowledge

  • they may not trust the provenance of the knowledge

  • the knowledge did not solve an immediate pain, but was more of a long term benefit (see blog post on why some ideas spread and others don’t).

  • they could get away with doing things the way they had always done, even though the new way was better.

In the PKM framework of Seeking, Sensing & Sharing, the latter may seem easy but it does not always equate to other people finding the knowledge artifacts that you have created while seeking & sense-making. For example, I can quickly find something on my blog in the thousands of posts here, that would take someone else much longer. I have the contextual memory of having created each post. This is why it’s also important to incorporate what I call the discern component of sharing.

Seek > Sense > Share

Since it is easier for me to find something I have created, then I should be open to opportunities to share, in order to optimize knowledge management in my workplace. My knowledge artifacts are almost always more “at hand” to me than to others. This is why PKM practices are so important in organizational knowledge management, but are often overlooked. So far, only humans are good at recognizing all the contextual signals in the workplace, making implicit connections, and then identifying something that might be useful to share.

One example of discernment is in “closing triangles“. This is when one person introduces two unknown associates to each other, thus closing the triangle. Discerning when to do this is also important. It would not make sense to make professional introductions as one person is going on a long vacation or when the other is extremely busy with an unrelated project. Sensing the right time and place to make connections is important in network weaving. It’s the same with sharing knowledge.

Integrating PKM practices with organizational knowledge management can help knowledge to flow better and not remain knowledge stock in some database. This takes time, practice, and a good sense of what others are doing. Discernment, like PKM,  requires mindfulness.

Three types of KM

In an organizational knowledge sharing framework, I put together several ideas to show how knowledge could be shared and codified. As I explain this to others I realize that these ideas go against many established assumptions about knowledge in organizations. For example, knowledge management is not a software system, but really three processes that are conducted in parallel and support each other; namely Big KM, Little KM and PKM [Patti Anklam].

Big KM is needed in larger organizations that have a lot of outputs, events and processes to keep track of. For instance, a company like P&G has a lot of history and many brands that each have a story. Just keeping track of all these products is a significant effort. This requires enterprise-wide systems. Big KM also provides the institutional knowledge that is needed to have common understanding amongst those working in the organization. It consists of the big, important stories.

Little KM helps groups make decisions given the knowledge they have at the time, but learning from each subsequent decision. By creating “safe-fail” experiments, they can try out new ways of working, with minimal risk. Little KM practices ensure that much of what is learned is shared and as much codified as possible. These feed into Big KM, institutional knowledge.

Little KMPKM is what individuals practice in order to fully participate in Little KM. I would say that PKM is the most important to keep organizational learning alive. Individuals who are actively engaged in their sense-making will likely be more participative in Little KM, and their sharing (as in Seek-Sense-Share) will contribute to Big KM. Imagine an organization where everyone blogs professionally. It would be very easy for an organizational curator to weave together the narrative threads from all employees, thus feeding into a Big KM system.

My experience is that Big KM is ‘relatively’ easy, but it does not guarantee knowledge-sharing. On the other hand, PKM is an individual skill that can be developed with practice. It benefits both the individual and the organization. Little KM, where teams share their learning and note their failures as well as success, is the most difficult. In large organizations, who probably have a Big KM system, I would focus next on PKM. Then, once sufficient people have PKM skills, Little KM (knowledge-in-action) can be put into practice. In the long run, it takes all three to ensure good institutional memory as well as a culture of learning.

knowledge organizational asset

Institutional Memory and Knowledge Management

This is a follow-up post on building institutional memory. The basic premises are stated in sense-making for decision memories. This presentation includes additional details and more explanations. It adds many new slides to help with the flow of the narrative, limited as it is with this medium.

The main themes are:

Memories are captured as knowledge artifacts, each limited by what it can convey, depending on its nature and the knowledge of the recipient.

Decision memories have a certain importance for organizations; to understand why decisions were, or were not, taken.

Knowledge management can provide a structure to capture institutional memory, but it requires more than a single approach.

Complex work, which is growing in importance in networked organizations, requires the sharing of implicit knowledge and this presents certain challenges.

We should take complexity into account and develop frameworks for sharing knowledge and storing institutional memory to help organizations deal with current events and prepare for an uncertain future.

institutional_memory

Knowledge Management for Decision Memories

Institutional decision memories can describe how and why we, as an organization, chose one course of action over another. As Brian Gongol notes:

“If a capital project has an expected service life of 20 to 30 years, it’s entirely possible that people working in an institution in their 20s will be middle or upper-level managers in the same institution by the time the project has to be replaced or upgraded. Unless someone documents the process by which the original decision was made, including notes on the alternatives not taken, the 50-year-old manager who’s been with the institution all along will usually be guided more by 25 years of habits and built-in bias than by a fresh look at the available alternatives. And the situation is likely to be even worse if the 50-year-old manager making the decisions came into the institution recently and doesn’t even have a memory for when the original project was completed in the first place.”

Over time, these memories can be codified and institutionalized. This is Big Knowledge Management, leveraging the power of enterprise software platforms to store decision, process, and event memories. Process and event memories, like project outputs, are relatively easy to capture and codify. But decision memories are often hampered by our tendency to justify decisions after they have been made, and even create elaborate, and often fictional, stories around them. For this reason, it is important to capture decisions as they are being made, not after the fact.

Explaining why other decisions were not made, should also be normal practice. For example, I was working with a client that made decisions on which chemical compound to develop out of a possibility of thousands. There was a cost to initially create any compound, so not all possibilities could be attempted. Decisions were made by a committee on which compound to pursue. However, the decisions on why the other compounds were not developed were never recorded. Several years later, the situation had changed due to improvements in technology and new research findings, and now some of the rejected compounds may have had potential for development. Unfortunately, no records were available to search the rejected compound database and find ones that met the new criteria. Sometimes our decisions not to do something are just as important as our selected course of action, from the perspective of the future. But we never know this in advance.

Recording and sharing our knowledge on a regular basis is what Little Knowledge Management is about, as it focuses on providing ways for groups to try new methods safely. Examples include curation, communities of practice, and mentoring. For complex work, Little KM is critical, as most of the knowledge required is implicit, and not easy to codify. According to the Cynefin framework, in the Complex domain “the relationship between cause and effect can only be perceived in retrospect, but not in advance, the approach is to Probe – Sense – Respond , and we can sense emergent practice.” Teams working in the complex domain have to make “probes” on a regular basis in order to understand the changing environment. It then becomes essential to develop ways to capture and share the decisions made with each one.

decision memories

Institutional memory, especially the decisions taken over time, has to be part of the workflow of any knowledge worker doing complex work and making decisions. Ewen Le Borgne writes that, “Institutional memory feeds off strong personal knowledge management among individual staff members“. I define PKMastery as a set of processes, individually constructed, to help each of us make sense of our world and work more effectively. PKM is an ongoing process of filtering information from our networks; creating knowledge individually and with our teams, and then discerning with whom and when to share the artifacts of our knowledge. As Roger Schank states, “Comprehension is mapping your stories onto mine.” PKM helps to put your maps out there for others to see.

We have to remember that all of this “knowledge management” is nothing without people engaged in the process. Viola Spolin, creator of the “Theater Games” actor training system, says that, “Information is a weak form of communication.” But, it can be improved, as Gary Schwartz notes, “Story becomes important in the ordering of all this information.” Stories are the glue, holding information together in some semblance of order, for our brains to process into knowledge.

stories are personal

Related Posts

Institutional Memory
The Storytelling Animal
Building Institutional Memory
An Organizational Knowledge Sharing Framework

Networked Professional Development

It can sometimes be difficult to see oneself as a node in multiple networks, as opposed to a more conventional position within an organizational hierarchy. We have become used to titles, job descriptions, and other institutional trappings. But network thinking can fundamentally change our view of hierarchical relationships.

For example, I once used value network analysis to help a steering group see their community of practice in a new light. For the first time, they saw it mapped as a network. They immediately realized that they were pushing solutions instead of listening to their community. As a result, they decided to change their Charter and develop more network-centric practices. Thinking in terms of networks can enable us see with new eyes.

effective networks are open

Managing in Networks:

Here are some recommendations for organizations moving to more networked and creative work.

  • Abolish the organization chart and replace it with a network diagram (some new tech companies have done this).
  • Move away from counting hours, to a results only work environment.
  • Encourage outside work that doesn’t directly interfere with paid work, as it will strengthen the network.
  • Provide options for workers to come and go and give them ways to stay connected when they’re not employed (like Ericsson’s Stay Connected Facebook group). Build an ecosystem, not a monolith.
  • Organizations should promote connected leadership.

Learning in Networks:

As we learn in digital networks, stock (content) loses significance, while flow (conversation) becomes more important – the challenge becomes how to continuously weave the many bits of information and knowledge that pass by us each day. Conversations help us make sense. But we need diversity in our conversations or we become insular. We cannot predict what will emerge from continuous learning, co-creating & sharing at the individual, organizational and market level, but we do know it will make for more resilient organizations.

Networked Professional Development:

A professional learning network, with its redundant connections, repetition of information and indirect communications, is a much more resilient system than any designed development program can be. Redundancy is also a good principal for supporting social learning diffusion. There is always more than one way to communicate or find something and just because something was blogged, tweeted or posted does not mean it will be understood and eventually internalized as actionable knowledge. The more complex or novel the idea, the more time it will take to be understood.

Programmers often say that you are only as good as your code. Credentials and certifications often act as blinders and stop us from recognizing the complexity of a situation. As Henry Mencken wrote, “For every complex problem there is an answer that is clear, simple, and wrong.

One approach to working smarter starts by organizing to embrace diversity and manage complexity.  Diversity is a key factor in innovation and there are few organizations that do not want to improve innovation.

At the Connected Knowledge Lab, we offer a place and time to develop network skills. Our next event will focus on building a professional network, providing resources and feedback for anyone interested in getting started. Our workshops are designed to give just enough structure, without constraining personal and social learning, all at a reasonable price.