“technology…processes by which an organization transforms labor capital, materials, and information into products and services of greater value.”
Clayton Christensen, The Innovator’s Dilemma

Technology?

The term “technology” is as misused as the word “diet”. Anything you eat makes up your diet. You can’t go on a diet, you’re already on one. You can, however, go on a “restricted diet” or a “reduction diet”. The key modifiers are often dropped.

Andrew McAfee purports that Enterprise 2.0 is “not not about the technology.” Using the Christensen definition noted above, this is true. But is Andy missing a modifier? His writings seem to focus on “digital technology”, which can indeed enable Enterprise 2.0. And yet, many of these technologies have been available for over a decade. How significant then are these technologies and where’s the issue?

Digital technologies labeled Enterprise 2.0, will not provide 2.0 results if implemented with 1.0 thinking.

2.0 Thinking: Embrace Dichotomy

How is 2.0 thinking different? It relies on a shift away from many commonly held beliefs. It is not an abandonment of such beliefs, but requires that they be suspended to move to a more flexible, adaptive middle. It requires the ability to embrace dichotomy, to simultaneously consider opposing concepts to find new possibilities (see “The Opposable Mind” by Roger Martin, Rotman School of Business and “The Innovation Paradox” by Richard Farson and Ralph Keyes).

Digital technologies are, well, fundamentally digital. They operate off of algorithms and binary code. As such, they provide approximations of reality. But knowledge work is not inherently defined by processes. Forcing knowledge work into processes defined by algorithms and binary code introduces ‘rounding errors’. The more algorithms and binary code you string together into a single solution, the more error you introduce.

The promise of object-oriented theory was to create reusable pieces of code. This was a fallacy. The true potential was not in the code itself, but in reusable functions – algorithms of process (the real essence of SOA).

Consider the following continuum:

Based on observations from Roger Martin, the adaptive middle requires a move away from (not an abandonment of) binary code. The entire continuum is relevant — optimal flexibility synthesizes all of these. Where the dynamic middle falls, depends on the context of the problem or opportunity at hand. Consider the left side Art and the right side Science. Synthesized, they lead to the optimal: context-relevant design.

One discipline that relies on the synthesis of art and science is architecture. While digital architecture might be considered both art and science, Enterprise 2.0 requires a form of Enterprise Architecture akin to, but not equal to the Zachman Framework (frameworks, the conceptual equivalent to technology platforms). No one individual can or should defend the various perspectives needed to shape such an architecture.

Structure Minimized, Not Eliminated

Fundamental to Enterprise 2.0 is simplicity. The most simplistic form in nature is that which emerges, governed by the laws of complexity – the middle between chaos and order (basic premises of complexity science, including feedback loops are assumed and not detailed here).

Emergence is strangled by order and dissipates in chaos. It requires “Small Pieces Loosely Joined”. In his book by the same name, David Weinberger lays out a “unified theory of the web”. Enterprise 2.0 embraces a unified theory of work, celebrating the most adaptive resource a company has: its people.

Enterprise 2.0 unleashes the potential of corporate resources by shifting control. While management does not go away, it is not an activity in the hands of a few.

Gary Hamel suggests, “Management is out of date. Like the combustion engine, it’s a technology that has largely stopped evolving…” Management is not a group of people with a title, it’s “the capacity to marshal resources, lay out plans, program work, and spur effort” and “is central to the accomplishment of human purpose.”

Fluid Structure: Think Lava Lamp

There’s no ‘big bang’ theory. Emergence does not evolve from nothing – it requires structure. Endless possibilities of form emerge from the elements and constraints of a lava lamp. Break the container and the possibilities of the elements end.

Where does structure come from? It depends – this, the ultimate design answer. The right answer comes from the context of the business.

There are no checklists for creating an Enterprise 2.0-enabled environment. The business is already operating. The challenge is akin to repurposing a Boeing 777 into a 787 Dreamliner mid-flight, except there is no ‘finished’ design, but there is a starting architecture (heuristics). Most progress is tested/validated in-flight.

The term “repurposing” should not be taken lightly. Tremendous potential exists for leveraging what’s already in place: “Thus the task is not so much to see what no one yet has seen, but to think what nobody yet has thought about that which everybody sees” Arthur Schopenhauer. One form of this is the mashup, but there are many other ways to leverage existing resources by using pieces of existing designs and solutions or modifying them with new functional or UI patterns.

While digital technologies contribute to the structure, they are only seeds. At the lowest level construct, Blog technology is not different than a Wiki: both provide functions to create and display content in a specific format. The main distinctions in Blogs and Wikis are the functions and formats they provide. But the same is true for all other common desktop applications. A Blog or a Wiki is no more inherently social than email.

Indeed, Blogs and Wikis are common to desktop applications in one very negative way: they can create more silos of information faster. This is the antithesis of the flexibility required by Enterprise 2.0. There must be a guiding architecture for Enterprise 2.0 success, one that separates the UI from the functions, the format from the content and data. A digital technology that earns an E2.0-relevant label, will be built around or support such an architecture, one that understands and leverages the fundamentals of fluid structure.

Architectures rely on operating assumptions: an HVAC system must be kept in good repair to maintain comfortable temperatures for building occupants. Enterprise 2.0 requires some form of facilities maintenance. The evolving details of the care and feeding of the environment can be embodied in a Governance Model, not to be confused with highly regulated models often used for restraint. The E2.0 version is more heuristic than algorithmic, but includes a blend of recommendations and process. It may define formal and informal roles. It simply reflects agreements.

No Beginning, No End

There is no prescribed starting point for Enterprise 2.0, but there is one capability that emergence fundamentally depends on: the ability for people to find each other by things that define relevance – work, topics, skills, affiliations, trust. As well, people must have ready access to relevant ‘raw materials’ for their work. Shorten the distance to finding relevant resources.

To be truly emergent, Enterprise 2.0 must be seamlessly integrated with knowledge work. It cannot be an appendage; it should not require adoption.

Enterprise 2.0 is inherently social. It is not about managing knowledge but is about rendering knowledge. It is enabled by, but is not achieved by installing a digital technology. It unleashes the potential of humans not with workflow, but by flowing work and thought on persistent conversations.