Archive for the 'Networks' Category

The nature of the firm, and why it matters

Jordan Furlong‘s justified question, “Why do law firms exist?” is something that isn’t just relevant to partners (or potential investors in firms). Those who support the core functions of the firm need to be aware of its implications. I’ll come back to Jordan’s question, but first I want to reflect on something else.

Thanks to the generosity of Headshift, I was able to attend the Dachis Group’s London Social Business Summit at the end of March. One of the most interesting sessions that day was the presentation by Dave Gray of XPLANE. Dave outlined his current thinking about the nature of the company, which can be found summarised in the initial post on his new site, The Connected Company.

Dave is concerned about the short life span of the average company:

In a recent talk, John Hagel pointed out that the average life expectancy of a company in the S&P 500 has dropped precipitously, from 75 years (in 1937) to 15 years in a more recent study. Why is the life expectancy of a company so low? And why is it dropping?

He is also worried about their productivity:

A recent analysis in the CYBEA Journal looked at profit-per-employee at 475 of the S&P 500, and the results were astounding: As you triple the number of employees, their productivity drops by half (Chart here).

This “3/2 law” of employee productivity, along with the death rate for large companies, is pretty scary stuff. Surely we can do better?

I believe we can. The secret, I think, lies in understanding the nature of large, complex systems, and letting go of some of our traditional notions of how companies function.

The largest complex system that still seems to work is the city.

Cities aren’t just complex and difficult to control. They are also more productive than their corporate counterparts. In fact, the rules governing city productivity stand in stark contrast to the ominous “3/2 rule” that applies to companies. As companies add people, productivity shrinks. But as cities add people, productivity actually grows.

A study by the Federal Reserve Bank of Philadelphia found that as the working population in a given area doubles, productivity (measured in this case by the rate of invention) goes up by 20%. This finding is borne out by study after study. If you’re interested in going deeper, take a look at this recent New York Times article: A Physicist Solves the City.

Drawing on a study of long-lived successful companies commissioned by Shell Oil, Dave spots three characteristics of those companies also shared by cities:

Ecosystems: Long-lived companies were decentralized. They tolerated “eccentric activities at the margins.” They were very active in partnerships and joint ventures. The boundaries of the company were less clearly delineated, and local groups had more autonomy over their decisions, than you would expect in the typical global corporation.

Strong identity: Although the organization was loosely controlled, long-lived companies were connected by a strong, shared culture. Everyone in the company understood the company’s values. These companies tended to promote from within in order to keep that culture strong. Cities also share this common identity: think of the difference between a New Yorker and a Los Angelino, or a Parisian, for example.

Active listening: Long-lived companies had their eyes and ears focused on the world around them and were constantly seeking opportunities. Because of their decentralized nature and strong shared culture, it was easier for them to spot opportunities in the changing world and act, proactively and decisively, to capitalize on them.

The whole post is worth reading and reflecting on. Dave’s prescription for success, for companies to be more like cities, is to shun divisional structures, and to build on networks and connections instead. This has been refined in a more recent post into a ‘podular’ system.

A pod is a small, autonomous unit that is enabled and empowered to deliver the things that customers value.

By value, I mean anything that’s a part of a service that delivers value, even though the customer may not see it. For example, in a construction firm, the activities valued by customers are those that are directly related to building. The accounting department of a construction firm is not part of the value delivery system, it’s a support team. But in an accounting firm, any activity related to accounting is part of the customer value delivery system.

There’s a reason that pods need to focus on value-creating activities rather than support activities. Support activities might need to be organized differently.

This idea appears to be closely related to Steve Denning’s notion of Radical Management, as described in his latest book. It also reflects the way that some professional service firms organise themselves. That’s what brings us back to Jordan Furlong’s question.

Why do law firms exist? Or, more properly, why should law firms continue to exist? (One important reason why they exist is that their history brought us to this point. What might happen to them in the future is actually more interesting.)

Jordan’s post starts with Ronald Coase, but also points to a number of ways in which law firms might not meet Coase’s standards.

Companies exist, therefore, because they:

  • reduce transaction costs,
  • build valuable culture,
  • organize production,
  • assemble collective knowledge, and
  • spur innovation.

So now let’s take a look at law firms. I don’t think it would be too huge a liberty to state that as a general rule, law firms:

  • develop relatively weak and fragmented cultures,
  • manage production and process indifferently,
  • assign and perform work inefficiently,
  • share knowledge haphazardly and grudgingly, and
  • display almost no interest in innovation.

That’s an inventory of defects that would make Ronald Coase wonder exactly what it is that keeps law firms together as commercial entities.

Worse than that, Jordan points to a range of recent commentaries suggesting that things aren’t getting any better. I think he is correct. In fact, it is interesting to note that John Roberts spotted the germ of the problem in his 2004 book, The Modern Firm.

Many authors, including Ronald Coase and Herbert Simon, have identified the essential nature of the firm as the reliance on heirarchic, authority relations to replace the inherent equality among participants that markes market dealings. When you join a firm, you accept the right of the executives and their delegates to direct your behaviour, at least over a more-or-less commonly understood range of activities. …

Others … have challenged this view. They argue that any appearance of authority in the firm is illusory. For them, the relationship between employer and employee is completely parallel to that between customer and butcher. In each case, the buyer (of labor services or meat) can tell the seller what is wanted on a particular day, and the seller can acquiesce and be paid, or refuse and be fired. For these scholars, the firm is simply “a nexus of contracts” — a particularly dense collection of the sort of arrangements that characterise markets.

While there are several objections to this argument, we focus on one. It is that, when a customer “fires” a butcher, the butcher keeps the inventory, tools, shop, and other customers she had previously. When an employee leaves a firm, in contrast, she is typically denied access to the firm’s resources. The employee cannot conduct business using the firm’s name; she cannot use its machinery or patents; and she probably has limited access to the people and networks in the firm, certainly for commercial purposes and perhaps even socially. (The Modern Firm, pp.103-4)

The benefits Roberts identifies are almost always missing in a law firm. The firm’s name may be less significant than the lawyer’s and there is little machinery or patents. In the seven years since the book was published access to networks and people has become infinitely more straightforward, thanks to developments in social software and similar technologies.

Joining Roberts’s insights with those of Dave Gray and Jordan Furlong, I think it is likely that we will see much more fluid structures in law firms in coming years. Dave Gray’s podular arrangement need not be restricted to one organisation — what is to stop clients creating their own pods for specific projects, drawing together the good lawyers from a variety of firms? Could the panel arrangement now commonly in use by larger companies be a Trojan horse to allow them to pick off key lawyers whenever they need them? Technology is only going to make that easier.

So that leaves the support functions. In Dave Gray’s podular model, support is provided by a backbone, or platform.

Podular platform

For a podular system to work, cultural and technical standards are imperative. This means that a pod’s autonomy does not extend to choices in shared standards and protocols. This kind of system needs a strong platform that clearly articulates those standards and provides a mechanism for evolving them when necessary.

For small and large companies alike, the most advantageous standards are those that are most widely adopted, because those standards will allow you to plug in more easily to the big wide world – and the big wide world always offers more functionality, better and more cheaply than you can build it yourself. Platform architecture is about coordination and consistency, so the best way to organize it may not be podular. When it comes to language, protocols, culture and values, you don’t want variability, you want consistency. Shared values is one of the best ways to ensure consistent behavior when you lack a formal hierarchy. Consistency in standards is an absolute requirement if you want to enable autonomous units.

Interestingly, there is often little variation between different law firms in terms of their technical standards. In some practice areas, these are dictated by external agencies (courts, industry associations, etc.), whilst in others they converge because of intervention by common suppliers (in the UK, many firms use know-how and precedents provided by PLC) or simply the fact that in order to do their job lawyers have to share their basic knowledge (first-draft documents often effectively disclose a firm’s precedents to their competitors). It is a small step to a more generally accepted foundation for legal work.

Will clients push for this? Would they benefit from some form of crowd-sourced backbone to support lawyers working for them in a podular fashion? Time will tell, but don’t wait for the train to leave the station before you decide to board it.

Knowledge sharing: it may not be what you think it is

John Tropea is one of my top Twitter friends for sharing interesting links and insights. Yesterday, he unearthed a great blog post from Patrick Lambe dating from 2006 (“If We Can’t Even Describe Knowledge Sharing, How Can We Support It?“). Patrick’s post starts calmly enough:

A combination of two very different incidents reminded me this week of just how incompetent we still are in KM at capturing the complexity, richness and sophistication of human knowledge behaviours. In the first incident I was asked to do a blind review of an academic paper on knowledge sharing for a KM conference. In the second, knowledge sharing was very much a matter of life and death. Although they shared a common theme, they might as well have represented alien universes.

From there, he becomes a bit more immoderate:

Let’s look at the conference paper first. After working my way through the literature review (a necessary evil), I started into the research proposal with my stomach starting to knot up and a growing sense of incredulity.

Although the authors had adopted Davenport & Prusak’s perfectly respectable definition of knowledge as a “fluid mix of framed experience, values, contextual information, and expert insight” it was becoming increasingly apparent as I worked my way into the paper that what they really meant by “knowledge sharing” was confined to contributing to and consuming from an online KM system. The research being described was designed to identify the factors that would indicate propensity for or against said behaviours. A knowledge sharing system that could, theoretically, be engineered.

Shame on them. After a good decade of practical effort and research focused on KM, how can people still think so mechanically and bloodlessly?

Justly immoderate, I think. Read on to see why.

Tonderghie Steading

It has to be right that knowledge in action is more valuable to organisations than inactive knowledge. Rory Stewart’s walking and engaging with people, as I wrote yesterday, shows one way in which high quality insight into complex systems can come from simple interactions rather than formal organised learning and knowledge. This is a point that Patrick made at greater length in an excellent paper he wrote in 2002 called “The Autism of Knowledge Management” (it’s a 23-page PDF downloadable from the linked blog post).

It depresses me that I have only just discovered this paper. Patrick wrote an incredibly useful critique of some traditional and ingrained organisational attitudes to e-learning and knowledge sharing. It should be much more widely known.

Here is his starting point:

There is a profound and dangerous autism in the way we describe knowledge management and e-learning. At its root is an obsessive fascination with the idea of knowledge as content, as object, and as manipulable artefact. It is accompanied by an almost psychotic blindness to the human experiences of knowing, learning, communicating, formulating, recognising, adapting, miscommunicating, forgetting, noticing, ignoring, choosing, liking, disliking, remembering and misremembering.

Once he has expanded on this, carefully defining what he means by ‘autism’ and ‘objects’ in this context, Patrick then presents and deals with five myths that arise as a result of this way of thinking. These are the myths of reusability, universality, interchangeability, completeness, and liberation. Of these, the one that struck me most was the myth of completeness:

The myth of completeness expresses the content architects’ inability to see beyond the knowledge and learning delivery. Out of the box and into the head, and hey presto the stuff is known. The evidence for this is in the almost complete lack of attention to what happens outside the computerised storage and delivery mechanism – specifically, what people do with knowledge, how it transitions into action and behaviour. How many people in knowledge management are talking about synapses, or the soft stuff that goes on in people’s heads? Is it simply assumed, that once the knowledge is delivered, it has been successfully transferred?

[…]

Knowledge only has value if it emerges into actions, decisions and behaviours – that much is generally conceded. But few content-oriented knowledge managers think through the entire lifecycle of the knowledge objects they deal in. Acquiring a knowledge artefact is only the first stage of what’s interesting about knowledge. We don’t truly know until we have internalised, integrated into larger maps of what we know, practised, repeated, made myriad variations of mistake, built up our own personalised patterns of perception and experience.

I can think of few more succinct and clear expressions of the process of knowing. In the organisational context, we need to be sure that everyone takes responsibility for developing their own knowledge — they cannot just plug themselves into a knowledge system or e-learning package. This statement shows why. The impact of this personal responsibility becomes clear within the section on the myth of interchangeability, where Patrick makes a valuable point about information and insight that resonated especially given my blog post from yesterday.

Beyond a basic informational level (and value added knowledge and learning need to go far beyond basic informational levels), when I have a specific working problem such as how to resolve a complex financial issue, the last thing I want is a necklace of evenly manufactured knowledge nuggets cross-indexed and compiled according to the key words I happen to have entered into the engine. Google can give me that, in many ways more interestingly, because it will give me different perspectives, different depths and different takes.

What really adds value to my problem-solving will be an answer that cuts to the chase, gives me deep insight on the core of my problem, and gives me light supporting information at the fringes of the problem, with the capability to probe deeper if I feel like it. Better still if the answer can be framed in relation to something I already know, so that I can call more of my own experience and perceptions into play. Evenness and interchangeability will not work for me, because life and the situations we create are neither even, nor made up of interchangeable parts.

We do have an evolved mechanism for achieving such deep knowledge results: this is the performance you can expect from a well-networked person who can sustain relatively close relationships with friends, colleagues and peers, and can perform as well as request deep knowledge services of this kind.

I suspect that (whether inside our organisations or otherwise) we can all identify people whose personal networks add significant value to their work and those around them. (And probably plenty whose silo mentality brings problems rather than focus.)

In his conclusion, Patrick presents “six basic principles that seem to work consistently in our knowledge and learning habits; principles that knowledge management and e-learning technologies need to serve.” These are:

  1. Highly effective knowledge performers prefer knowledge fragments and lumps to highly engineered knowledge parts.
  2. Parts need to talk to their neighbours.
  3. The whole is more important than the parts.
  4. Knowledge artefacts provide just enough to allow the user to get started in the real world.
  5. Learning needs change faster than learning design.
  6. Variety is the spice of life.

I need to read this section again — it didn’t resonate as well for me as the rest of the paper. That said, reading the paper again will be a delight rather than an imposition. I recommend it highly to anyone with an interest in knowledge and learning processes, and the systems we create to support them.


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,222 other followers

RSS Recent mini-blog posts

  • An error has occurred; the feed is probably down. Try again later.

Recent micro-blog posts

Categories

Interesting stuff...

Bookmark and Share

When…

May 2013
M T W T F S S
« Nov    
 12345
6789101112
13141516171819
20212223242526
2728293031  

Follow

Get every new post delivered to your Inbox.

Join 1,222 other followers

%d bloggers like this: