Future of Legal KIM: ‘Death of Difference’ and the need for effective legal project management

A really timely thought piece ‘Becoming the law firm clients really want’ landed on my desk this week. The future of LawBy Peppermint Technology Research, it characterised the future of law firms as being ‘the death of difference’ noting that legal will become much like other sectors. This scenario has profound implications for lawyers, professional support lawyers and legal knowledge & information management (KIM) professionals.

On December 9th Martin White and I will be hosting a breakfast breakout event at the RSA The future for Legal KIM: An Outside-In perspective.  In it we will look at some of the issues facing KIM professionals. Martin and I have worked in many industries across many countries; we’ve seen and been involved in seismic shifts in the KIM roles in engineering, energy, the 3rd sector, publishing, software and finance. Our thinking in putting this event together was to share some of our experiences in a relaxed setting with like minded legal KM’ers.

So over the past few weeks in the run up to the event we have been looking at the four big issues research had told us were near the top of the legal professions ‘must do’ list.

  • Lawyers come and go – capturing knowledge at speed
  • Getting the best from virtual teams
  • Collaboration and KM beyond the firewall
  • Bringing it all together – legal project management

I began with Going but not forgotten: knowledge capture in a hurry, Martin then wrote  The opportunities for digital workplace adoption by law firms and  Certifying virtual teams – a key skill in digital workplace implementation.

bringing it all together – legal project management

Today I am going to focus (from a KIM perspective) on the challenges of setting up a project management infrastructure that allows an organisation to learn from previous experiences and feed back learnings from the project back into the business.

There are many project management disciplines being used in industry. The Stage-Gate new product development (NPD) methodology is one example in which the veracity of new products are assessed and resources allocated according to a set of criteria for each stage of the process. Knowledge capture is built into the process.

Irrespective of the system you adopt below are a few of the questions you will need to be asking (I’ve omitted the obvious budget ones):

set up (learning before)

  • What do we know about this subject and what has been done before?
  • Who is an expert (internal and external) and can we get their input before starting the project?
  • Who should we invite to the Kick Off meeting and how do we want to structure that?
  • What structures are we going to use for management, monitoring and decision making?
  • Who is going to be on the Project Steering Group and how do we manage those stakeholders and others? How often should they meet and in what format?
  • How are we going to capture the outcomes of meetings, store the material we generate and make people aware of what’s happening?
  • How do we collaborate across teams and boundaries to ensure the best possible decisions are made based on the best?

conduct (learning during)

  • Who do we go to for answers to tricky questions that arise and how do we do that?
  • How often are we feeding learnings back into our project?
  • Who is providing updates and in what format?
  • Where are we storing progress reports?

conclusions (learning after)

  • What format will the debrief take and who will be invited?
  • When and where will you hold it?
  • Who will be tasked to action the outcomes?

I remember a conversation once with Professor Victor Newman on his Baton Passing Technique which arose in part to ensure project knowledge is passed on.  He said:

The big problem in managing learning to have an impact is to know what knowledge is useful, to whom, the form it should take, where and when it is best applied and when best to share it

Baton PassingAlongside is an extract from the slides Victor and the British Council made available.  It works, I’ve tried it!

I have used in addition: After Action Reviews, Pause & Reflects, Retrospects to name but three.

 

 

Earlier this year APQC published an interview with me in which I described the concept of DEBRIEF as a technique for capturing learnings at the end of various stages of projects. I will talk more about that on the 9th.  It’s not too late to sign up here!

and finally

Too often the KIM team are excluded from the project management processes in favour of an accredited (Prince 2 trained) Project Manager. In my view that’s a grave mistake, there are KM techniques for each step of the process and the good KIM’er will be well versed in facilitating such interventions.

If you fail to learn from what you’ve done then you will not improve as a business and will be uncompetitive with those who do.

 

 

 

‘…there’s zero collaboration or institutional knowledge’: learning lessons from winning teams

So says Paul Azinger, the last US Captain to win the Ryder Cup, in the aftermath of the 2014 event and the accompanying soul searching. He implicitly acknowledges the importance of building on what ‘you’ know as an institution if you are to be successful.  This is what he said:

A big difference between us and them is that Europe always has a succession plan. McGinley was surrounded by past captains and future captains, and they all reap the benefits. We’re lone rangers as far as captains go. Nobody knows what we’ve done in the past. There’s zero collaboration or institutional knowledge.

 

why Team Europe’s victory is relevant to business

Why is the outcome of a biennial golf match of interest to lawyers and others who work in highly rewarded and individualistic roles? Because the players are all ‘Rock Stars’ in their own right who come together sporadically to play (and win) against their peer group.

What stands out about the European approach? Meticulous planning, attention to detail, clarity over roles before, during and after each Ryder Cup match and a willingness to acknowledge that no one player is bigger than the team.  Business is no different relying on a collaborative team approach and a set of shared values.

In October 2012 Apple CEO Tim Cook reshuffled his team, this is how it was reported in a Bloomberg Business Week interview:

“The key in the change that you’re referencing is my deep belief that collaboration in essential for innovation – and I didn’t just start believing that. I’ve always believed that,” said Cook. “It’s always been a core belief at Apple. Steve very deeply believed in this.”

Cook said that he wanted to ensure that Apple takes its already “enormous” level of collaboration even higher. “There are many things. But the one thing we do, which I think no one else does, is integrate hardware, software, and services in such a way that most consumers begin to not differentiate anymore.”

“You have to be an A-plus at collaboration,” Cook continued. “And so the changes that we made get us to a whole new level of collaboration.”

Here’s how commentator Kristine Kern (@kristinekern) of the Table Group saw this move:

Let’s be clear: Ousting a rock star from your team — or asking them to change their ways — is not always something you can do. But it’s something you should consider. “Like most things, it’s not black and white,” Kern concludes. “Organizational health requires rock stars do both stellar and healthy work. Which shouldn’t be a problem: Most true rock stars rise to a challenge. Just don’t be afraid to demand it.”

why shared values matter

Some time ago I was the Business & Strategy Advisor to an Anglo-Dutch company in the professional services / software business. It was around the dotcom boom period when investors were falling over themselves to back the next hot opportunity. Company valuations were bizarre: at one point on revenues of $20m we had a market cap that was 40 times bigger. Our AIM share price went from £1.25 to £16+. It was easy to be profligate, we weren’t and I take personal pride in having taken the lead on travel budgets and integrating the acquisitions we made.

As we grew (acquiring first a US firm, then a German one) and shifted our centre of operations (and development) from Europe to the USA the Executive Management team all recognized the importance of having a set of values and a structure that could transcend global operations while recognizing cultural nuances peculiar to the location of each office.

What might go down well as a motivational incentive in Denver would need tweaking to be embraced in Maastricht let alone in Guildford. We needed a framing device that everyone in the business could buy into and in the management’s case the cojones to ‘get with the programme’. So we organised a cross company group of all levels to work through what they wanted out of the business – how they wanted to be treated as employees and in most cases, shareholders.

To this day I can remember the constituent parts:

  • a clear vision understood by all
  • a meritocracy that rewarded success and took action on poor performance
  • inspiring and visible leadership
  • a place that was fun to work where you could pick up the phone to anyone.

We had 6 locations and office sizes ranged from 12-50.  We had a central sales/CRM system everyone used and we had quarterly conference calls with the management team where people could ask what they wanted. Board meetings rotated around the various offices, one was virtual the next in situ. When tough decisions were required we were clear about why they were being taken and communicated that.

Of course technology and process played a role, the corporate intranet was a good information source. We conducted Peer Assists, After Action Reviews; we fed our learnings back into the development process and we used what we learned to reengineer the business around the Stage-Gate New Product Development Process.

The going got tough, people got let go, yet Sopheon survived and today has an award winning software, Accolade, with embedded Knowledge deployed in the innovation and new product departments across hundreds of organisations globally.

so what

Whether business or sport, people respond to good leaders who provide guidance and clarity, hold people to account for poor performance and recognize/reward exceptional performance. They are also good at making the right decision and leading teams through implementation by inspiration, perspiration and collaboration. I’m sure those will feature prominently when Captain McGinley releases the inevitable ‘Building a winning Ryder Cup Team’, book.

Good decisions are informed by good knowledge: of clients, of markets and of resources. Knowledge Management when performed well becomes ingrained behaviour and Knowledge Sharing is a core element.

and finally

I am indebted to Euan Semple (who talks and writes common sense) for my summary. Taken from his excellent tome ‘Organisations Don’t Tweet, People Do‘ Euan argues that in today’s interconnected world it is increasingly important to be seen to add value and to be seen to be knowledgeable and willing to share that knowledge. He goes further:

In the old days ‘knowledge is power’ used to mean holding on to it and only giving it out judiciously to certain people. In an Internet world there is no point in having knowledge if people don’t know you have it, and if you are not prepared to share it. Web tools enable more knowledge to flow more readily around your organisation. Taking part in this process is going to be more obviously a part of being more productive than ever before. Being able and willing to share your knowledge will become a key business skill.

Collaboration is the mechanism by which Knowledge is often shared. It is something Apple and the US Ryder Cup designate (a forecast from me – Azinger to be the US Captain in 2016) recognise as being a core ingredient for a successful venture. So should you!