Learning lessons about lessons learned

Well I am back at my desk today after a full day of workshops in Melbourne.

I wanted to share the approach we have recently undertaken in identifying lessons learned from a major project we have been delivering for the last 7 years.

During this time we had over 250 people work on the project so we took a hybrid approach which I had developed in a ‘previous life’.

We decided to survey all participants asking ethnographic questions. The questions came in different forms but all looking at the same outcome – capturing anecdotal fragments.

Questions went something like this:

  • You find yourself at the first Friday drinks and you are approached by a close colleague who you have worked with many times before. They tell you they have been asked to work on similar project to [Project X] and ask you for advice.
    • What are some of your experiences you would tell them about that would encourage them to join the project?
    • What would you tell them about that would discourage them?
  • You have been asked by a Proposal Leader to join in a workshop for a bid we are putting together for a similar project to [Project X].
    • What successes did you experience on the project that you would share?
    • What challenges did you face on the project that you would share?
  • A new project is undertaking some planning workshops and you have been invited to come along and share your experiences.
    • What would you recommend we stop doing on Projects?
    • What should we start doing on Projects?
    • What should we continue to do on Projects?
  • What are some of the key technical and procedural innovations we developed on [Project X]?
  • If you could go back and change one thing on [Project X], what would it be?

We had 66 people participate from a sample of 250. From this we collected about 300 fragments.

We have also interviewed several leaders from the project asking them similar questions to the survey and adding their responses to the mix.

We then took these fragments and undertook a sense making activity to identify themes to then hold more focussed face-to-face workshops. The sense making was undertaken by a a group of people with diverse areas of expertise and had no involvement with the Project itself. The reason for using people who had not been involved on the project was that during the interviews we had observed some dismissive behaviours where people denied certain perspectives because “they didn’t know the real story”.

Four distinct themes emerged from the sense making exercise:

  1. Project Management capability and practice
  2. Design Management practice and procedures
  3. Leadership and Decision Making
  4. Project Culture

We decided running workshops on the first three and then touch on culture in each workshop.

We then talked with the project sponsor and leader about who the right people would be to have in the room. We decided to have three 2 hour workshops in the one day as an initial pass and see what we would uncover to follow up on.

In order to get at least 10-20 people in the room we invited 40 people to the workshops. There was some initial hesitation from the sponsor on inviting so many people but after sharing our experience with running these sorts of workshops and having only a third accept and then having last minute drop outs, they agreed to see what happened. Sure enough we had 14 people accept invitations and 3 people pull out the day before the workshops.

We gave people the opportunity to attend one or more workshops and had consistent turnout across the three workshops to have diversity of fields, expertise, seniority and age.

We ran each session as a 90 minute anecdote circle with conversation mapping on a projector (mind map) followed by a 30 minute breakout session working on actions and communications plans on what was discussed.

We opened with introductions, learning peoples expectations and outlined what a lessons learned exercise is.

We then laid some ground rules which put us in good stead:

  • No rank
  • Safe environment
  • No blame, no repercussions
  • Open, honest, adult, professional discussion
  • Learning focus
  • Values based conduct, respect others

We also used some points to manage expectations around conflict management:

  • People have different perspectives
  • There is no right or wrong, there is only diversity
  • Listen and respect other peoples perspectives
  • Learn why they are different
  • Don’t take things personally

This set us up well. We came across various perspectives of what had been happening. There were some epiphanies and the best thing I observed in the workshop was the most senior leader in the room setting a fantastic example by sharing his perspective that he had been involved in some decisions that proved to be have made things worse and he approached it as something he has learnt and changed the way he now makes decisions.

The questions we asked worked best with the audience when we couched them like “What advice would you give to someone else about to do one of these?”.

So the collection and analysis has been undertaken. Now it’s time to plan action.

We talk with people in the business about Lessons Learned Exercises (not just workshops) providing two things:

  • Actions – Things that need to be improved or changed like policies, procedures and processes. This links to our quality management area and our business systems.
  • Advice – Tips and advice you can give to someone in your position that can minimise risk and give them a better chance of success. This links to our risk management approach and communication through various channels including our Communities of Practice.

So now to working on Improvement requests and change management strategies.

Wish us luck.

Cory

Practicing what you preach

So here is the story.

I’m checking LinkedIn tonight and something pops up in one of the side columns in the space that shows any roles being advertised on LinkedIn that may match your profile.

Here are the details of the role. I have removed the title and the organisation until later in this post:


Type:
Full-time
Experience:
Associate
Functions:
Writing / Editing, Consulting, Project Management, Production
Industries:
Logistics and Supply Chain, Human Resources, Management Consulting, Publishing, Financial Services
Posted:
November 20, 2009 by ???

Job Description

Position Concept: 
[Company] is seeking highly qualified individuals with expertise in Supply Chain Management, Human Capital Management or Financial Management to produce and promote [Company] research content through the development of informational products focused on metrics, best practices, thought leadership, and case studies. The [Role] will support [Company’s] content strategy by developing and publishing thought leadership to [Company] standards and requirements. Thought leadership and related content pieces will be developed in support of member consumption, content and demand generation marketing requirements, and pay-per-click revenue-generating pieces. Examples of thought leadership that will be produced include white papers, articles, case studies, and other Web-centric content. The individual will work with [Company’s] research services, membership, and marketing departments to develop and deploy fact-based points of view and other thought leadership deliverables.

Responsibilities:
•Managing and delivering to [Company’s] supply chain, human capital, and financial management publishing requirements
•Maintaining and delivering to the functional content publishing calendar
•Coordinating input and research activities across stakeholders and subject matter experts
•Identifying primary and secondary research requirements in order to publish fact-based, differentiated business insights
•Developing papers and slide decks that present client-ready, compelling insights
•Delivering briefings to internal and external audiences
•Working with marketing and membership groups to deploy thought leadership content internally and externally through events, press quotes, articles, podcasts, and other media
•Contributing to the evolution of strategic thinking across assigned functional area

Skills

Qualifications:
•At least 3–5 years of experience writing content associated with the relevant functional area
•Advanced degree in relevant field
•Solid written and oral English, other languages a plus
•Demonstrated research and analysis abilities
•Strong project management and relationship management skills
•Ability to understand business structure, improvement, and decision-making needs within large enterprises in a way that allows the individual to extract relevance from existing research and frame information in a point of view


Ok. If you are still with me, there are two things that bother me about this.

  1. Position Title
  2. The Company

1. Position Title

I must say it was the title that first got my attention, but after reading the role description, I’m not sure of the accuracy of this role being called a Knowledge Manager.

2. The Company

Now understandably there are many different opinions of what Knowledge Management is and a fair number of different descriptions of the Knowledge Manager role. What frightens me the most is an organisation who is well recognised in the field and proclaims themselves as a thought leader in the space, such as APQC, could call such a role a Knowledge Manager.

What do you think?

(Role advertised on LinkedIn)

Cory

Tool Time at KMRt

Just ran the group at KMRt through a few tools that are available our there in the wild wild web. These and others can be found in my delicious > tools tag.

What have you seen?

Cory

KM Program Comparison

I have just been through a exercise with the Knowledge Management Roundtable in Victoria. It worked out quite well so I thought I would share.

It is a combination of Sense making, Knowledge Market, Speed Dating and Maturity Models.


Step 1.

Get people to write on sticky notes the various activities/initiatives/services that their organisation is undertaking/providing that are related in some way to KM.

Also write your organisations name on them.

Step 2.

Get everyone to put their sticky notes on a large wall.

Step 3.  

Invite the group to then cluster the sticky notes into groups.

Step 4.

Name the Groups. The names this group came up with were:

  • Knowledge Strategy & Implementation
  • Organisational Development/Learning & Development
  • Knowledge Sharing Culture
  • Intranet/Portals
  • Information Management/Library
  • Enablers/Information Technology
  • Business Process

Step 5.

Create a map for each of the Groupings that has a matrix with a vertical axis of complexity (simple. complicated, complex) and a horizontal axis of implementation lifecycle (concept, business case, buy/build, implemented). These were placed on flipcharts and stuck up on walls around the room.

Step 6.

Move the grouped sticky notes to their related map. Everyone then had to put their own sticky notes in the relevant position on the matrix.

Step 7.

People were then invited to look at each of the maps and identify other people who may have already implemented something they are currently working on the concept for. They then found the people and sought advice on any tips or tricks and organise follow up after the workshop.


Some fantastic connections were made and discussion bubbled away across the room.

Something to take back and see how it could be applied in other areas.

Cory

Immortality

I was really impressed today by something I spotted in someone’s office.

immortality

Here’s to achieving immortality.

Cory

Digital Habitats with Nancy White

I was in Melbourne today to start off a few days of workshops, meetings and KM Roundtable.

Today it was an afternoon with Nancy White and a few dozen members of the KM Roundtable.

Nancy took us through some of the concepts covered in the new book Digital Habitats written with Etienne Wenger and John D. Smith.

Key points included:

  • There was a moment of clarity around the bands of Individual, Community and Network and some good discussion around the difference between communities and networks.
  • Triangulation in looking at who and what you need (internal and external) to have on board to get things changed in an organisation.
  • Understanding that you design for groups, that will be experienced as individuals
  • Group Polarities:
    • Togetherness       -        Separateness
    • Participation          -        Reification
    • Individual               -        Group
  • A fantastic spider diagram where you can look at the activities of a community that included dimensions of:
    • Meetings
    • Projects
    • Access to expertise
    • Relationships
    • Context
    • Community cultivation
    • Individual participation
    • Content publishing
    • Open-ended conversation

Nancy used a set of cards in some of her activities to break the ice and spark conversation. They are the IDEO Method Cards. A set of 51 cards that have an image on one side and the description of a creative activity on the other.

I am still not sure why they use the word reification.

We have been designing a scorecard for CoP health. There was plenty of stuff to consider and I am asking our librarian to get a copy of the book as well as getting one for myself.

Sharepoint resources

You all know I would rather talk about the people side of KM but I have had a few people asking me about my experiences with Sharepoint recently.

In particular people are looking for recommendations on resources and tips on configuring Sharepoint (not server and database administration). So here are a few I have found handy that I have stored in my Delicious bookmarks.

See what you think and let me know of any others you might have?

Cory

Knowledge Strategy

In our organisation September means strategy time. I find myself in the unusual position of working in Australia for a US company that operates on a Nov-Oct financial calendar on a period (4 weeks, 13 periods a year) basis.

So I am discussing with people the best way to go about developing a knowledge strategy. There are a few key things learnt from previous experience which I thought might be good to share. I’ll add more as they come to mind. Feel free to contribute.

Knowledge Strategy Tips and Tricks

  1. Use the strategy model your organisation uses
  2. Show alignment with strategic objectives, don’t measure against them.

  3. Balance above and below the line (new v’s renew)

  4. Maturity model measures may be better than classic financial performance.

  5. Show how you will support other peoples activities

  6. Look for relatives; can you kill two birds with one stone

  7. Clearly separate strategic objectives from tactical initiatives but show the relationships.

  8. Depending on your environment, show bias: Every other strategy in the business is going to be concentrating on financial performance and customer intimacy. You need to balance this with the knowledge aspect. You may need to be loud to be heard above the hubbub.

  9. Engage with your stakeholders, don’t just do it on your own.

  10. Measure different things to the rest of the organisation. Everyone else is measuring profit and budgets. Provide some diversity.

  11. Embed as much as you can in the overall business strategy instead of having a separate knowledge strategy.

  12. Include initiatives that other areas are running that support knowledge management principles and objectives (e.g. HR may be running the Mentoring Program)

  13. Mention things you are going to stop doing (not just about doing new things -stop, start, continue)

Cory

Enterprise 2.0

I had the opportunity to catch up with Ross Dawson whilst I have been in Sydney this week.

This was the first time Ross and I had met face-to-face so we took the opportunity to discover each others background and current activities.

The conversation worked it’s way around to the recent work Ross has done in publishing Implementing Enterprise 2.0.

I provided a perspective of the Enterprise 2.0 concept and some deeper elements that should be surfaced.

So my view was based on a theme of Business Change and Improvement  as opposed to specifically Enterprise 2.0.

For me it’s deeper. It’s about teaching the business to be a surfer. To be able to paddle out and wait for the right wave to catch and get ahead. Social media is just the current wave. The business needs to look at it’s change readiness and at the value proposition for change, not just change for change sake and certainly not to just keep up with the Joneses.

I’ll save my opinions about Enterprise 2.0 being about the tail wagging the dog for another occasion.

Cory

The week that was…

A big week has just come to an end before an even bigger week commences.

As some of you would know the KM Australia conference was held in Sydney (Luna Park) this week. I was asked by Patrick Lambe to assist in facilitating a session around the KM Cards and some new Culture Cards. About a month ago I was asked to fill in a gap they had on the last session of the last day. This turned into a double session giving flight to the design of an interactive session on problem solving.

So the plan was to attend the pre-conference Dave Snowden workshop, help out Patrick with his session, catch up with KM comrades,  meet some new kmers, take in some intresting presentations and then round off the conference with an energetic finale.

As with the best laid plans of mice and men there is always the unknown ready to jump all over it.

A couple of weeks ago I received an invitation to attend our organisation’s strategic planning worksop. This was the top 40 leaders in the business coming together to review our strategic direction and plan for the foressable future.

Fortunately the planning session was also in Sydney, and just across the harbour from Luna Park (I could see it out the window from where we were at Pier One). Unfortuately I would not be able to attend most of the conference and only made the pre-conference workshop and the afternoon of the last day. Apologies to Patrick (Still trying to work out how to make it up to him. Any tips from readers?).

Needless to say the strategic planning sessions were challenging, enjoyable (except for the part where I was told to shutup) and draining. We did well to come off the back of this and give (by most accounts – post by Dave Snowden, tweets #kmaus09) and enjoyable and energetic session to finish off the conference. The jury is still out on the use of the cow horn to signal the end of activities in the exercise. Big thanks to Sarah for logistics and the facilitators for wearing the costumes and kepping people on track (Sarah, Darren, Lance, Michelle and Matt).

So now a few things to tie up the week (blog post, slides up on slideshare etc..) and then it’s off to Singapore to present at the KM Singapore conference.

More to come.

Cory