Launching the ‘Future of Collaborative Enterprise’ Project

By Thierry de Baillon

Organizations are facing today the most challenging conditions of their history. Turbulent times in economy, geopolitical threats, environmental and societal issues, are setting the stage for what might be the biggest changes since the industrial revolution in the early XIXth century.

At the same time, the rabid evolution of technology allows everyone to connect to everyone and to share information and knowledge with no other limit than the speed of light, creating a full spectrum of new opportunities (as well as, let’s face it, threats) for businesses.

State of the art

But the collaborative enterprise, as an organizational model as well as an operational framework, is still in its infancy. Many of the tools we will use in ten years from now and that will shape our behaviors, in the workplace as well as in our personal life, still do not exist. In this context, trends & buzzwords are over saturating the infosphere. It is often hard to know which trend is authentic, has a potential for business and if it is actionable or not.

It might be time to ask ourselves whether all the noise about Enterprise 2.0, collaboration, social business and so forth were true business opportunities for a company leveraging the different aspects of heralded approaches, or if they were an empty shell resulting from the literature published by the prolific minds of so-called gurus and agile marketers (consulting firms and platform vendors are becoming incredibly clever into packaging their offer) looking for new markets on which to sell both software and methodologies. In other words: Is the collaborative enterprise real or just a concept to justify massive investments in various business fields & applications?

The project

To try better envisioning what will come next, and to better understand the challenges and opportunities rose by the disruptive changes involved today, Frédéric Gilbert and myself are launching the Future of the Collaborative Enterprise project, task which kept me away from blogging for some time.

While surveys and white papers usually depict the state of the art in a domain, what we want to do is sketching possible (probable?) scenarios about what the future of work will look like. What could it look like? How can a company embrace the potential of collaboration? And what are the different challenges that we are facing to make it effective on large scale? Can it work for everyone and how?  Asking these questions we think will allow acting, anticipating & using the potentials of collaborative initiatives.

To get actionable clues, we are interviewing experts and thought leaders from many disciplines around the world, asking them to react on a set of ten questions framing the main aspects of collaboration: organizational structure, change, technology, and information While many more are on the go, you can see who we already interviewed on the project’s website.

Get involved and help us make it happen

Next step is, through design thinking and future thinking methods, to extract patterns and build plausible future scenarios from the gathered material, and then to further challenge thought leaders on societal, cultural and organizational topics in their knowledge and foresight.

Frederic and I, think that it takes more than words & methods to make things happen, and we emphasize on the importance of people and of the authentic will required to make the workplace a better place to be in order to bring this positive energy to our homes.

Harnessing the collective intelligence is an intrinsic part of the Future of Collaborative Enterprise project. All interviews will be published on the project’s Youtube channel and website as they are conducted and transcript, and all material will be published under a Creative Commons license.  We have published the very same set of questions we asked all interviewees onto Quora, and will watch this space for the most insightful answers. You can add your vision there, or send short videos of your answers through the Future of Collaborative Enterprise website’s contact page.

We have also created a Facebook page dedicated to the project, to help you follow its developments, additions and conversations. The more material we will get, the more we will be able to set up the grounds for a truly collaborative enterprise, and to build up an actionable framework to help businesses which want to undergo the path to more value co-creation.

Whether you are consultant, software vendor, business leader, academic researcher or simply want to add your voice to our project, we’re looking forward to understanding the Future of Collaborative Enterprise with you!

Tackling Complexity and Wicked Problems with Design Thinking

By Thierry de Baillon

This post is the second of a two-parts article on design thinking co-written with Ralph-Christian Ohr (@ralph_ohr). You can read first part here.

The world we live in becomes increasingly complex. Complex systems in different areas of our life, such as business, environment, economy etc. involve ever larger numbers of interacting elements. Particularly human interactions are non-linear and result in a basically unpredictable system behavior. One major consequence of complexity is the fact that we have to deal with rising problem wickedness. Ted Cadsby remarks in an interesting post:

“The hallmark of a wicked problem is that it cannot be reduced to a single-cause explanation. Complexity arises from the interconnections between things – how parts within a system interact via intricate feedback mechanisms. The information signals we need to make sense of complex things are buried in a lot of noise, and we, unfortunately, are not adept at digging for cues. We have been conditioned by thousands of years of evolution, as well as our daily routines, to draw speedy conclusions by picking out simple, linear, cause-effect connections. This approach works well with straightforward problems like securing food, shelter and sex, or crossing a busy street. But we are now living in a world where multivariate and non-linear causal connections hide below the surface of our immediate perceptions, and diverge to different possible interpretations.”

Wicked problems are termed as “divergent” as opposed to “convergent” problems. For a so-called ‘tame’ problem, the problem definition is – though it might be very complicated – well understood and promises a solution. The more it is studied, the more various answers sooner or later converge. A divergent problem isn’t well defined and does not promise a solution. The more it is studied, the more people inevitably come to different solutions and interpretations. The process to tackle tame problems is assumed to be fundamentally linear, comprising a sequence of steps leading to a desired outcome / solution. In a complex environment not even a shared problem understanding can be taken for granted. We don’t know what we don’t know.

The question arises how wicked problems, emerging from complex systems, can be properly addressed. We’d like to suggest three ‘pillars’ that seem to be crucial in this context:

Experimentation

Complex contexts and wicked problems require an experimental approach. Because outcomes are unpredictable, decision makers need to focus on an environment from which good things can emerge, rather than trying to bring about predetermined results. This comes along with a tolerance of failure and the ability to refrain from imposing order. It’s essential to let patterns emerge and to determine which ones are convenient. Every experiment exposes new aspects of the problem, leading to further adjustments of the following solution proposal. In place of finding ‘the right solution’, problem understanding and solution must be woven together from beginning to end through explorative iterations.

Diversity and collective intelligence

Wicked problems solving naturally involve a diversity of stakeholders with different perspectives and interpretations. Given that many people care about or have something at stake in how the problem has to be / could be resolved, the process of solving a wicked problem is fundamentally social, and solving a wicked problem is fundamentally a social process. Shared understanding turns out to be a prerequisite for tackling wicked problems. It requires that stakeholders understand each other’s positions to have fruitful exchange about their different viewpoints of the problem – and to leverage collective, holistic, rather than fragmented or individual intelligence, to solve it.

Interpretive approach

A wicked problem usually implies a radical uncertainty, i.e. not simply an inability to predict which of several options will turn out to be the preferred one. No shared problem understanding exists and the context appears so complex that not even the possible outcomes are known. And in the absence of a specified solution, no analytical problem solving can be applied by breaking the problem up into a set of separable parts that can be assigned to different specialists. According to Lester and Piore (“Innovation – The Missing Dimension”), an interpretive approach is indicated in this case. This approach doesn’t target at solving problems or negotiating between contending interests, but at initiating and guiding conversations among individuals and groups. Involved people work through ambiguity and construct shared meaning. Through that process the participants come to understand each other – and themselves – better than before. It’s an open-ended process allowing insights and novelty to emerge.

The distinction between analytical and interpretive approach determines two different ways of understanding teams:

• Analytical perspective: teams are formed and re-formed of different members with particular competencies required,
• Interpretive perspective: teams can be organic groups that develop their own language and understanding over time and become greater than the sum of their competencies.

These ‘pillars’ get back to the constituting elements of a complex adaptive Design Thinking framework, outlined in the first part of this post.

Complexity doesn’t nullify present business models and processes, but it taints more and more of their effectiveness and relevance. In order to be prepared to face increased wickedness and complexity, organizations need to make sure to implement those pillars. Leadership is required to set directions, rather than goals, and to facilitate a culture where experimentation, ambiguity and uncertainty tolerance are valued.

This ambiguity should be reflected in the organizational design itself, as wicked problems often arise “on the edge”. Even if disconnected to main business operations, dedicated spaces need to be created for collaboration, empathy and conversation. Those spaces allow for transformation of diverse, subjective perspectives into collective insight and understanding. Furthermore, it’s mandatory to educate and hire appropriate people, being capable of following this approach and of unfolding their potential in such a collaborative environment.

Takeaway:

Increased complexity requires a transformation in the way we approach problems. While conventional problem solving is highly analytical, resolving wicked problems can be tackled by a design-oriented approach. Through combining experimentation, diversity and interpretive collaboration, subjectivity of individual stakeholders can be transformed into shared insight. Design Thinking based on these elements has true potential to be leveraged as social framework to utilize collective intelligence.

The Catch Behind Design Thinking

By Thierry de Baillon

This post is the first of a two-parts article on design thinking co-written with Ralph-Christian Ohr (@ralph_ohr). As businesses are more and more challenged by the wicked nature of the problems they face, whether in strategic or operational context, we need to integrate more divergent and resilient reasoning in our decision-making practices. Cleared from all the fuss which so often surrounds it, design thinking could provide the ongoing transformation of businesses toward “social” with an actionable framework to leverage the true potential of collaboration.

Design Thinking is quite a strange animal. Attempts to define this discipline, in fact as old as creativity, framed by Tim Brown, IDEO’s CEO, in his HBR article published in 2008, are as numerous as practical evidence of design thinking in action are. Trying to broaden the scope of design thinking from the design field to the one of complex business and societal problems had raised the need for a much more formalized approach. Practical reasons abound: how could you sell services based on a methodology which only defines and unfolds itself during execution? How could you convince executives that pattern matching and sense-making are as much relevant than proven tracks of expertise in a given domain?

Connecting design thinking with the broader context of problem solving has lead to the growth of two equally harmful myths: the guru designer and practice as a process, emphasizing on subjectivity or linearity where empathy, empowerment and divergent thinking are needed. Design thinking isn’t saving the world or revolutionizing business, for sure, mostly because of these two illusory paths. But before throwing the baby out with the bath water, and stating, with Bruce Nussbaum, that “Design Thinking is a Failed Experiment“, it is worth considering what is turning wrong. Speaking of creativity, learning from failure (if any) is usually a much more fruitful attitude than shooting the messenger.

A process is a process is a process

To allow design thinking to tackle business problems beyond design, it was assimilated to a process. One can easily understand that design thinking doesn’t fit the usual focus on linearity and convergence, so important in the conventional culture for efficiency most organizations emphasize on, and suitable for most traditional innovation approaches. This is an important issue, don’t misunderstand me, but do you really think that companies which give so much credit to Six Sigma or CMMI would welcome design thinking as a serious problem solving discipline? My bet is no. Of course, framing it as such a kind of process was, from the beginning, deemed to failure. There is a problem with “design thinking as a process”, but where does it really lie?

Contrary to expectations, “process”, in the business universe, has no straightforward definition. Processes do not necessarily rely on linearity and certainty might sometimes be fuzzy (think Adaptive Case Management), or divergent. Nevertheless, every flavor of business processes shares a common feature: an intrinsic independence from the people operating them. In this context, even when confronted with the most innovative organizational culture, “design thinking as a process” cannot fit. Not because of the mess and fuzziness associated with creativity, but because of the subjectivity involved: design thinking is highly interpretive and subjective, and most of its outcomes are dependent from the designer’s capabilities. Here lies the catch: this subjectivity is the disease which prevents design thinking from living up to its promise. Here lies also a paradox: subjectivity is as much a problem as it is a necessity. Without it, we fall into the dry world of business processes, unable to sparkle creativity. With too much of it, the ugly head of the guru designer shows up, enforcing a vision which fits more the designer’s ego and reputation than true business needs.

A complex adaptive framework

Most of the problems design thinking intends to solve have no unique formulation, no single solution. Despite the many definitions given, framing design thinking itself is a challenge. For many reasons, it can be considered as a complex adaptive framework aimed at addressing other complex dimensions of business. I view the whole design thinking approach as navigation through a fitness landscape: the problem occupies the base plane, while the third dimension symbolizes the “validity” of possible solutions. Framing the problem means picking up a starting point on the problem plane, then the whole approach consists in climbing up the hills in several directions, through iterative methods, until maxima are reached.

The choice of a starting point is highly subjective, and relies on designers’ personal background, experience, empathy and intuition. There is nothing wrong here, except that complex systems behave according to initial conditions, and this behavior cannot be mastered unless all parameters are known. Little changes might lead to vastly different outcomes, and further actions might well end up in dead-end local maxima, far from optimal solutions. It takes a leap of faith for businesses to follow such tracks. Who will decide which starting point is better, if both satisfy the context? How could the degree of “fitness” of any chosen direction be measured, unless pursuing them all up to the end?

Fractal behavior is another characteristic of complex adaptive systems which closely relates to design thinking. As prototyping and testing takes place, design thinkers progressively gets into details from feedbacks, those details belonging to the same initial formulation of the problem at different scales (global design, ergonomy or touchpoints, realization capabilities,etc), each scale being as important as the initial approach in the overall solution taking shape. A problem is that, at some point, one scale might not fit the solution at all, and little overlooked changes might produce huge changes in the overall system. You might, for example, tumble into a feature which might disrupt the manufacturing capabilities of the company you are working with. At that time, what can be done? It is usually a matter of jettisoning the work made at larger scales and jumping back into a different part of the problem space, switching to a vastly different solution because of a tiny, but critical, detail. Such a disruptive move means creative destruction, and isn’t an easy decision to make, as it involves highly subjective dimensions. Design thinking is about decision making – instead of boiling down a problem to one large decision, designers make lots of little decisions, learnings as they go. Therefore, navigating complex problems and ambiguity through small, iterative trials is highly determined by a subjective and continuously challenged assessment of the context.

Design thinking = critical thinking + design doing

In the hope to be better accepted in the business world, design thinking has given up the subjectivity associated with experimentation, and without which creativity simply doesn’t exist. Similarly, in its search for a better way to find solutions, it has forgotten that problems cannot always be framed without ambiguity.

Back in the eighties, I remember attending a meeting in a Japanese fabric company. The meeting’s goal was to agree on next season’s trends to start the manufacturing of new fabrics. Attendees, which included designers, product and sales managers, discussed about colors and textures for several hours, often taking little thread samples in their hand and rolling them together to get a concrete view of how it would look like. At the end of the meeting, no decision was made. Attendees didn’t agree on anything but general color trends, but kept some of the hand-made thread samples for further exploration and technical feasibility, ready to produce fabric samples for testing.

This was an enlightening experience for me, and still is thirty years later. It superbly illustrates how design thinking could thrive at resolving complex business problems. Critical thinking among stakeholders is a much better way to seed creativity than relying on individual designers. Early parallel and conflicting exploration holds more promise than relying on individual bias. The activity out of which something innovative emerges, is social and highly interpretive. It involves guiding connected conversations among individuals and groups to determine the range of alternatives from which convergent choices are made.

Subjectivity is a key component of design thinking which, to be accepted and profitable for businesses, should be tightly tied to organizational context. This requires a novel, and more resilient, approach to design thinking: we need designers who have a sound understanding of all the parameters involved, leaning on networks and groups of stakeholders, harnessing critical thinking, and linking outcomes to their own range of experience and expertise, through design methods. Let us call that parallelogram-shaped designers (strong specific business understanding linked to strong design expertise) in a collaborative enterprise. I sense this might also be a good definition for management 2.0.

Read Part Two

Moving Beyond “Work as Usual” in a Complex World

By Thierry de Baillon

As ever increasing speed and amount of available knowledge are reshaping day after day the world we live in, it looks like a gap is widening between the way most businesses still operate and the capabilities needed to deal with our environment’s growing complexity.

Organizational responses to overall increasing speed too often are costs reductions, automation and optimization. Efficiency has become the new business’ black, and BPR is its credo. But speed isn’t only a factor we have to cope with; it is deeply transforming the nature of our relationships to the world. As Paul Virilio wrote: “The speed of light does not merely transform the world. It becomes the world. Globalization is the speed of light.” When considering speed as an external constraint, companies are keeping themselves deliberately out of many of today’s new fundamental dynamics. Pushing the gas pedal won’t drive anyone faster than the engine was built for, and current business engine was assembled in the — industrial – XIXth century, and amended more than thirty years ago with the rise of the process-driven enterprise.

The shy face of Enterprise 2.0

On every subject, for every aspect of our life, the quantity of information available is so tantalizing, that we cannot simply store all information we need at some time into our memory anymore. Such abundance has transformed our cognitive process: we now mostly remember links and references to information, extending our memory map, our knowledge, to a network of peers and sources. The more information is made available, the stronger and wider this network becomes, and the faster knowledge is able to flow. This networked nature of our representation of the world in turn participates in increasing the global speed of the world.

One major Enterprise 2.0 frameworks’ motto is to help companies to deal better with this information overabundance, to make organizational knowledge expandable and faster to access, with the help of social software: connecting with the right information at the right time. So far so good. Power has shifted from knowledge to knowledge sharing. Cool; but for how long? Even if there is little hope to break the 90-9-1 rule in organizations, information is becoming ubiquitous in an exponential way.

A recent attempt to deal with this growing quantity of knowledge flows is content curation, to allow for a better distribution of information. Unfortunately, this only helps facilitating knowledge acquisition when the desired outcome is already known, since what is relevant to you isn’t necessarily so for someone else, or even in another situation. Context is missing here. What we need is another way to filter information in context, another way to make information usable through non-deterministic tasks. The real power resides in knowledge use, not in knowledge sharing.

Another motto is to start with clear objectives. Business objectives… When quantity of information and speed of transmission are changing our way of thinking, are deeply transforming our lives, is it reasonable to believe that aligning corporate practices with private habits will spare us to rethink the way we work, the way we do business? Can we seriously think that getting from silos to clusters will save us deeper organizational transformations? Yes, we have to set up business objectives to any collaborative initiatives, but we have to consider which new kind of objectives can be achieved through social business, and what it means for the future of business.

The poor performance of processes

Umair Haque recently stated that “Making Room for Reflection Is a Strategic Imperative“. This is a nice injunction, backed with lucid and thoughtful arguments, but can we just “stop doing”, in an environment where speed has become the very stuff of things? I don’t believe so, taking a break is no more an option, and what we really need instead is to think differently. Accelerated growth of available data requires new ways to acquire knowledge and put it into action. In such a situation, unlearning has become as important as learning.

As most of our knowledge is now stored outside of our memory, the challenge not only lies in matching real-world situations with experiences stored in our memory, but also in pairing those situations with the right external connections, in order to gain access to the relevant knowledge. Not only do we have to deal with data, in anything but routine thinking, but with people, and our cognitive process now encompasses our networks. Information retrieval, and learning, had become inherently hyper-connected.

From internal “social” initiatives (let us consider them as knowledge networks rather than true collaborative environments for demonstration purpose) to customers’ relationships, present process-based approach to business is broken. Business processes expect a deterministic output; they rely on repeatability and explicit workflows, which often proves itself far from the nature of human relationships. The cognitive process, instead, is a non-linear mechanism, able to make sense from disjointed information. Cognition doesn’t appeal for processes, but for patterns. Furthermore, processes suit perfectly machine-to-machine communication. Human-to-machine communication needs to take into account user experience, which hardly resumes to processes, and human-to-human communication is all about weak signals and pattern recognition.

Knowledge work is all about patterns

Venessa Miemis has written a great post about the importance of patterns recognition in the cognitive process. To quote her: “there are strong and weak signals all around us, patterns, which indicate a change has happened, is happening, or has the potential to happen”. Business processes work as long as nothing changes, or at least changes slowly, which happens less and less in present business environments. Dynamic patterns, instead, are emergent phenomena of complex systems. They are highly adaptive and relate not only to existing flows (whether they be knowledge, work, customer journey, etc.), but also to how these flows change over time. In other words, they can be harnessed as predictive tools as well as operational routines design. A simple change in an underlying process might translate into huge and fast modifications of related pattern. Looking at the way patterns change (sometimes dramatically) in our networks provides us critical clues on how to improve broken processes, or on when to seamlessly switch to another one.

Here is a short summary of dynamic patterns versus processes characteristics:

Patterns are already used in business context. Emergent practices leveraged from online communities are patterns. Ethnography, and many design thinking methods, invoke pattern recognition to decipher customers’ behavior. Social learning implies the use of patterns in knowledge acquisition. Dynamic patterns are much more adapted to knowledge work than business processes are.

As they can be broken down to processes, monitoring patterns’ evolution in networks represent a promising way to handle the exceptions crippling most of the processes in which human interaction is involved. Integrating pattern recognition into work might require dedicated competencies, but it also requires new approaches. Adaptive Case Management is a promising framework to help dealing with knowledge flows rather than with processes, considered the fact that not only should we focus on information, but also on the way information, and connections to it, changes over time. Time has come, to understand that information is not only the blood of our networked organizations, but also their bones.