Horizontal networking often creates dissonance in the vertical enterprise
The vertical structure of knowledge did not foresee the coming of horizontal networking tools now shaping today’s workplace.
Today, there's a lot of chatter about bottom-up versus top-down, the collective wisdom of the organizational crowd, and various related themes. However, there’s also ongoing dissonance or competition between the methods behind structured, highly-defined organizational forms and activity and the growing world of hyperlinked flows in which knowledge and meaning are built layer by layer, exchange by exchange (all those hyperlinked interactions that increasingly make up what we call "knowledge work") which social computing enable.
At the heart of the issue is the way work is designed and the organizational structure that contains the work. A primary tool in designing work and structure is job evaluation (and derivatives like accountability mapping and redundancy analysis). The methods used today were created in the mid-1950's and haven't changed much since then. Their core assumptions are directly derived from, and have helped embed, Taylorism at the core of the modern organization.
I don’t mean job evaluation as in assessing a person's performance on the job – I mean the function usually managed by HR departments that 'measures' or 'weighs' jobs, and assigns them to levels and pay grades based on job “weight” with respect to skill, effort, responsibility and working conditions (the legal criteria for assessing pay equity). I believe that these tools and their underlying assumptions are used to create the skeletal architecture of hierarchical organizations, the pyramid we all know.
Dissonance in job requirements
The methodology of job evaluation is a very useful place to look at some of the key critical reasons for the ongoing dissonance and resistance to change we are seeing and will continue to experience. The methodology of job evaluation situates jobs in the organizational hierarchy and creates pay grades, pay practices, thresholds for entry into bonus schemes and often is the main criterion for distinguishing between management and non-management jobs.
Fundamentally, job evaluation (work measurement in the professional jargon) relies on the core assumption that knowledge is structured, and used, hierarchically. It follows that she or he (and the job requirements) who has more of the knowledge —on paper—is she or he who deserves to be "higher up" in the organization.
Redesigning work requirements
There are four or five major, well-known methodologies for measuring work. They all use very similar factors (sometimes described a bit differently semantically, with a couple more or less factors or sub-factors) and they all essentially measure the same thing.
These fundamental principles of work design need to be examined and re-conceived if the significant power of social computing is ever to be realized. As an example I will use the measurement factors used by the Hay Guide Chart Method, as I know them the best. I have also worked with the other major methodologies - they are essentially all the same: the Aiken Plan, and the Towers Perrin and Watson Wyatt job evaluation methodologies (now Towers Watson) in the past.
The Hay Method describes work as having three phases—input, throughput and output—and it employs three core factors to measure that input/throughput/output:
1. Know-how (input) - knowledge and skills acquired through education and experience.
2. Problem-solving (throughput) - the application of the said knowledge to problems encountered in the process of doing the work.
3. Accountability (output)- the level and type of responsibility a given job has for coordinating, managing or otherwise having impact on an organization's objectives.
There is a fourth factor called working conditions, but in many cases this is treated almost as a throwaway factor, especially when it comes to knowledge work. It typically relates to physical factors such as lighting, air-conditioning, the presence of fumes or chemicals, outdoor exposure, dangerous physical conditions, unusual exogenous stress, etc.
As noted above, the core assumptions of these methods are derived from the philosophy of Taylorism (aka scientific management) and the divisions of labour and packaging of tasks that have underpinned the search for efficiency and scale ever since the beginning of the 20th century. On the face of it, they seem eminently reasonable and the Hay Method (and the related ones cited above) have since the mid-50's largely served organizations quite well for segmenting and dividing labour, identifying necessary expertise and specialization and, in effect, designing one or another particular hierarchical pyramid. Today these methods are put into practice along with other key assumptions from that industrial era when organizations grew and prospered - mid--50's to approximately 2000.
Changing assumptions about knowledge
These methods set out a fundamental, foundational assumption about the nature of knowledge. They assume that knowledge and its acquisition, development and use is relatively quite stable, that it evolves quite slowly and carefully and that knowledge is based on an official, accepted taxonomy - a vertical arrangement of information and skills that are derived from the official institutions of our society (Jane Jacobs has a fair bit to say about this in Chapter 3 titled Credentialing vs. Educating in her last book Dark Age Ahead, as do others like John Taylor Gatto and Alfie Kohn, and as does David Weinberger’s Everything Is Miscellaneous – the power of digital disorder).
Above I have offered an example (paraphrasing the Hay Method's semantic scales for measuring a job's knowledge). It describes a vertical arrangement of Know-How (knowledge) and the method creates, supports and sustains vertical reporting relationships. The other two factors (problem-solving and accountability) derive from, and reinforce, the know-how factor. For example, the rules of job evaluation are such that you cannot have a problem-solving or accountability factor assessment that is of a higher order than the know-how slotting.
The definitions of the know-how (knowledge and skills ) factor levels are paraphrased from the semantic definitions on the actual Hay Guide Chart.
A - Unschooled and unskilled
B - Some school, some skill
C - Basic high school, routine work
D - Vocational school, community college, trades, senior administrative
E - University graduation, senior trades, managerial (reads the books)
F - University plus 10 years experience, grad school (puts the books to use)
G - Deep knowledge and expertise (writes the books)
H - God (has others write the books)
These methods did not envision or foresee the Web, hyperlinks and the exchanges of information which have spawned and carry the bit-by-bit layering and assembly of knowledge and peer-to-peer negotiation of results and responsibilities we are seeing emerge with greater frequency in this new networked world.
Multiple ways to structure knowledge
We are beginning to understand that the main way we have structured knowledge is only one way, and that this way is captive to core assumptions about the ordering and classification of information as created by some of the great thinkers, organizers and classifiers of information and knowledge who helped build up our growing understanding of the world around us (Linnaeus, Darwin, Dewey, etc.).
What we have developed into solid and maybe seemingly unassailable beliefs about knowledge are built upon the principles we have inherited from a time when human progress benefited greatly from regular and related discoveries about the world around us, both natural and man-made.
For example, it’s clear that there was a proliferation of written / printed material from the 1600’s through the 1900’s, containing amongst other things much codification of discoveries of the knowledge we use today in a wide range of domains and disciplines. More and more (too much ?) of this knowledge is accessible very rapidly on today’s Web in ‘fragments of one’ (nod to Dave Snowden’s assertion that the brain works most effectively with fragments of information) connected by search engines, hyperlinks and a range of easily used publishing platforms.
So ... now let's look at how information is shared and exchanged in order to build and use knowledge amongst networked individuals or groups. The use of knowledge in a networked context is very often much more horizontal, sideways and based on accessibility and collaboration - much more so than is the (official) use of knowledge in formally structured hierarchies.
Linked knowledge
What we know today is that people with vastly different types and forms of knowledge can be or are linked together for a wide (and potentially limitless) range of purposes (though clearly we are learning quickly about the limits to cognitive attention as lessons in social cognition surplus are offered up to us almost every day).
In networks-of-purpose, addressing Purpose A connects individuals with Skill and Knowledge Set B, Interests and Knowledge Set B, and Connections and Knowledge Set C (and of course the second-order concentric ring of connections each of them brings to any given network in which any of them participate). Each of them subscribes to different sets of feeds and has access to different sources of flows of information than each of the others, but can forward to all those in the on-purpose network anything that comes across their attention that may be pertinent to the purpose at hand.
In the dynamics of attention, flow and circulation of pertinent and relevant information such as this comes the power of social computing that KM practitioners may have been noticing as Web 2.0 tools, service and capabilities become more firmly ensconced in knowledge work in the guise of platforms for collaboration—the domain increasingly called Enterprise 2.0.
I think it is (very) safe to say that problem-solving or accountability is assigned or accepted in that situation based on negotiation of ‘who knows what’ or ‘how to get something done’, and often a call (Tweet, blog post, Skype chat, email) is put out to find and access some additional skill or knowledge that is required, and accountability is negotiated based on the constraints of the purposeful activity at hand.
Any of us familiar with medium to large sized organizations can begin to see, I believe, that the fundamental Taylorist assumption that knowledge is structured vertically and put to use in siloed pyramidic structures and cascaded down to the execution level must be straining at the seams in the increasingly highly-connected social networks in which many people work today.
Social computing – first dissonance, then participative flow ?
Thus, it seems clear that the introduction of wikis, blogs and RSS feeds (and now micro-blogging a la Twitter) for project work, for analysis and planning, for research and development and for other knowledge-intensive work is likely to introduce some reasonable levels of dissonance into the common and accepted organizational dynamics (or "organizational sociology") of formal, traditionally structured organizations.
This is an area where David Weinberger's phrase from the Cluetrain Manifesto — “hyperlinks subvert hierarchy” (or expose it, which may be better)—is likely to have real impact.
Take Weinberger’s additional concept of first- , second- , and third-order organization of emergent knowledge (outlined in his "Everything Is Miscellaneous"), combine it with hyperlinks and spaces designed for interaction based on core usability principles and you have a potent recipe for looking at the design of socially-networked work groups.
In some senses, we’ve been here before … social interaction with other knowledge workers is the foundation of (for example) Fred & Merrilyn Emery’s theory and method of Participative Work Design and is at the heart of socio-technical systems (STS) methodologies for organizational development and change. These theories and methods by and large reflect “getting the whole system into the room”.
Of course, with the arrival of the Internet and the advent of the interactive participative environment that is generally called Web 2.0, “the room” is larger and “the whole system” increasingly does indeed mean everyone, or at least the whole of the organizational crowd that makes up that organization.
Reams have been written about the Internet’s potential to democratize the access to and use of information. It does seem clear that the use of the Web, collaboration platforms, software-as-a-service, and cloud-based social computing by organizations that see information, knowledge and responsive innovation as mission-critical are core factors enabling the growth of network-based ways of creating pertinent and useful just-in-time knowledge and putting it to work.
Vertical knowledge disrupted
This causes dissonance and ambiguity because typically performance objectives, job assignments, compensation arrangements and bonus schemes are generally almost always predicated on causality derived from the vertical arrangements of knowledge and its use in planned and structured initiatives. As more and more knowledge work is carried out by people communicating and exchanging information using hyperlinks in social networks (where knowledge lives ) and routing it to where it is needed at any point in time, vertical arrangements of knowledge are disrupted, if not subverted.
Call for organizational redevelopment
Based on the notions I have explored above and in previous writings, I believe there is a rapidly-growing need for what I call eOD (enterprise Organisational Development). With greater fanfare It's also been called Social business. As social business initiatives continue to proliferate, I cannot see how the latent dissonance I have tried to articulate will be avoided. I think it will have to be addressed by using new design principles for knowledge work.
Many parts of knowledge work have been routinized and standardized with the ongoing marriages of business processes and integrated enterprise information systems. What has not changed much yet is the adaptation of structures and culture to permit easily building flows of information into pertinent, useful and just-in-time knowledge, or fanning out problem-solving and accountability into networks of connected workers.
I think many executives and senior managers sense massive challenges to the power and status relationships (the core of yet-to-change organizational structure) that exist in most of today's larger organizations. This sense of a growing challenge is behind many senior managers' and executives' struggles to understand or become enthusiastic about the possibilities of Enterprise 2.0. There is no Guide Chart yet about networked know-how, problem-solving or accountability.
Never mind that there is much rhetoric about the need for leadership at all levels, or about the empowerment and democratization of workers in organization X or Y. Performance management, grade levels and compensation have yet to recognize how work gets done in networked environments and in a networked world.
And if any of you have any experience with performance management programs or in assigning someone in a job to a different grade level, or in making changes to levels of pay or bonus schemes, you know what a minefield those can be.
]]>
