Agile and Knowledge Management, part 1

At our Knowledge Worker Toronto event on January 23, 2013 our speaker, Gil Broza, spoke about the human side of Agile. Now, Agile, for those of you who don’t regularly interact with software developers, which I imagine are many of you who read this blog, is about iterative and incremental design and development of software applications. Gil was speaking about lessons that could be learned from the experience of software developers in this area and transferred to other areas of the organization. That activity in itself is a knowledge management activity: knowledge transfer of lessons learned, but I digress.

Gil spoke about 10 lessons that the rest of the organization could learn and apply:

  1. People are not resources
  2. Focus
  3. Nurture the joy of delivering value
  4. Take small, safe feedback-rich steps
  5. Mind the physical environment
  6. The social environment matters too
  7. Want high-performance teams? Be ready to invest
  8. Manage less, lead more
  9. Collaboration rocks
  10. Human conduct trumps “best practices”

There was a discussion after the presentation and Q&A ended about how this talk fit in with Knowledge Workers/Knowledge Management, this is what I contributed to the discussion: these 10 lessons are about how knowledge workers like to work. In the KM consulting that I do, I often have a section in the report about knowledge workers, especially when I’m working with an organization that is hierarchical. Knowledge work and knowledge management thrives in a flatter organization model, one where sharing and working together is expected, and the silos of a hierarchy are detrimental to achieving the goals of the organization.

Anyone else have any thoughts?

Collaboration versus Command and Control

This post is about differing management styles and approaches to not just knowledge management but to business and ultimately life.

Do we believe there is a limited “pie” and so we need to compete and create hierarchies to control it (whatever “it” is in our own particular case) or do we believe in working together to make the pie bigger and be content with our own slice of pie, however big or small that may be?

As a small business person, I am not particularly interested in growing my business to be bigger than it is. I like doing consulting and giving focused, specialized service to my clients, I don’t need, nor do I want to grow my business to 25, 50, 100 or more people, I wouldn’t be able to do what I like to do in those scenarios. If a client or potential client wants services that I don’t offer, say development work for a particular software platform, I am perfectly willing to refer them to someone I know who specializes in that work rather than do it myself, or hire someone to work for me to do it for the client.

In my KM practice I often talk with people about what it takes to be successful with KM; people are often looking for that “magic bullet,” but there is none. It takes hard work to be successful with KM in any organization, but the more open and collaborative the organization is, the more likely it is to be successful.

Being open and collaborative is hard for a lot of people, especially for those who believe in a limited “pie” and hierarchy. Being open and collaborative goes against everything they believe in–command and control. They believe the worst about people, that people have to be told what to do, that without that command and control structure people will not do their jobs. They believe there is a limited “pie” and they are going to compete and they are going to win by whatever means possible, because that is the way the world works. Except that it’s not.

If you assume the worst about people, you get the worst; if you assume the best, you get the best, that is the way the world works. At least that is the way my world works, and the way the world that I want to live in works.

Being open and collaborative helps us all work together to produce a desired outcome, because we want to, because we believe in it, because we trust and respect ourselves and our colleagues. It makes a bigger “pie” possible, it also helps us to be content with the slice of “pie” we have.

Bigger is not better, more is not better.

So when I see KM people behaving in a command and control fashion, it confuses me. How can they be good at implementing and managing KM in an organization with behaviour like that? It smothers KM and sharing to be controlled. KM and sharing grows exponentially when it is given space (Nonaka’s ideas around Ba come to mind) and is allowed to happen; when it is supported and enabled, not controlled. Maintaining that openness is hard, it’s hard to have a lack of solid ground under us, we want the certainty of the rules and the ground, but to be successful in KM and in life we have to be okay with that uncertainty.

It takes a lot of self-knowledge and self-esteem to be okay with uncertainty and to manage in that way, but it’s the way to get the most out of your KM program and life.