By Thierry de Baillon
Version française ici.
Business processes has recently became quite a buzzword among the Enterprise 2.0 community, notably since June’s Boston conference. It suddenly seems that the whole discourse has changed from a leadership-fueled point of view to a down-to-the-ground (and to the balanced scorecard) vendor’s one. Pragmatism? I rather think that this approach is severely flawed, in three places at least: core processes concepts, knowledge handling and customers’ consideration.
When cats are called dogs
I recently wrote about SAP StreamWork and the fact that, despite their claim, this new tool is not a collaborative decision-making solution, but allows for better collaborative problem analysis, which is not, and by far, the same. Mistaking the mean for the goal is a clever tactic: this allows for frictionless adoption of an otherwise useful tool into existing processes, with the added hype of 2.0 technologies.
In a much more subtler register, Bertrand Duperrin made a common mistake in one of his last posts ‘Community management and processes by the example’. What he calls “process” is in fact a resource lifecycle, describing who is involved, when, in relationship to whom, where a process is a matter of chained actions allowing to progress through this lifecycle. Substituting communities for individual along the flow is of course an improvement of the entire lifecycle, but has de facto no impact on the process design or execution. The difference is important, since processes were developed to minimize variability and risks, specifically facilitating and streamlining execution when different silos, different business logics, are working in parallel through complicated operations and/or organizations. Moreover, there are designed to be as people independent as possible. They are typically built to avoid “reinventing the wheel”; but what would happen if tapping into the networks comes out with a solution which doesn’t require a wheel at all? Predictability is processes’ mainspring and, unless breaking them into much smaller, adaptive, parts, which contradicts their efficiency chasing goal, socializing resources lifecycles won’t have any positive impact on existing processes, besides giving the opportunity to integrate 2.0 technologies into workflows. This clearly is a dead-end for anybody believing that Enterprise 2.0 is more than technology.
Processes are Taylorist knowledge
Cecil Dijoux recalled Michael Grives’ interesting distinction between processes and practices. Unfortunately, practices, built upon people’s behavior, and not upon the least variable output available, still fall short from giving us a way to harness collaborative work. When it comes to knowledge, they behave quite the same, fossilizing thinking into formal procedures.
Fostering the use of tacit knowledge, which represents 80% of available knowledge in an organization, requires a much more flexible framework than those given by processes and practices. Knowledge is variable, unfocused, complex, and messy. By building automatic workflow rules, by assuming that today’s conditions are the same as yesterday’s ones, processes segment knowledge into bits of repeatable information and decision making guidance, exerting a division of knowledge similar as the division of labour envisioned by Adam Smith. Socializing business processes won’t take advantage of collaborative work, but of specialized cooperative knowledge. The only feature of processes which might benefit from social integration is their ownership.
The customer-centric Enterprise
Besides owners, processes have customers. Dealing with internal customers is usually a matter of connecting dots, which often means offering predictable output through connected, repeatable, actions. This could be fine, regardless of the two precedent points, as far as external customers are not involved. But the social web is transforming the way customers act and react in a radical way, and maintaining our business processes to engage and interact with customers is nonsense. If capturing internal tacit knowledge in a non obfuscating way is a challenge, ignoring customers knowledge about your products and services will soon become a deadly attitude. Business processes, with their inability to deal with uncertain, irreproducible knowledge, are the least suitable tools to establish and maintain any kind of relationship with your customers.
Wait, we need processes
Yes, we need business processes. Not as we know them today, driving our organizations from end to end, but we need them as an infrastructure, to free knowledge workers from complicated tasks, even collective ones. But they must now be considered as tools at our disposal, not as our organizations’ backbones. Besides that, not any company is destined to become a social business, not any product or service is meant to be discussed about on the social web. The future of business is both brands and commodities, and that will be the subject of my next post.
By Thierry de Baillon
Version française ici.
I am often puzzled by the way organizations and agencies tackle social media, as if conversational marketing and Enterprise 2.0 were living in separate worlds, addressing totally different issues, pursuing irreconcilable goals. Do they?
Of course, when considering the ‘media’ part of Social Media, open Innovation, co-creation, social CRM, have very few to deal with Facebook campaigns or multi-millions views viral videos. But the ‘social’ part, a word which deeply unsettles more than a few from my Enterprise 2.0 colleagues, tells us a completely different story, made up of conversations, insights, and exchange of knowledge. More than ever, I see a whole continuum taking place in the Social Territory, setting the customer’s experience at the center of business and harnessing all those conversations to get things done in a better way and gain decisive competitive advantages. Social Learning, which involves leveraging knowledge gained through informal networked flows, appears to be the necessary link between Social Media and Social Business.
More on that in the presentation below:
By Thierry de Baillon
Version française ici.
As time goes by, I see more and more surveys and positive case studies about Enterprise 2.0 adoption. This is good, but not so much. Most of the time, use of technologies such as instant messaging or web conferencing is viewed as concrete steps toward Enterprise 2.0 adoption. But is there any behavioral difference between meeting up face to face with someone and talking via IP networks? Barely any; this helps saving fossil fuels for our planet’s health and sets up a hypothetical technological ground for some later adoption. Not that much to jump for joy about.
Monitoring Enterprise 2.0 adoption should instead focus on communities, networks, and flows of knowledge, These are the real bricks on which to measure change, with a lot of precautions nevertheless.
Communities of practice exist for some time now in big organizations. They gather people with similar or related roles in a company, and are built around practical cases sharing, knowledge emergence and collaborative problem solving. While this is a great move toward new modes of collaboration and new, tacit, knowledge capture, these communities are often heavily structured and managed, just to insure that they “work”. Regular fixed-date gatherings, mandatory outcome, fixed agenda and assigned roles are among common practices. In other words, keeping control on the internal working of communities of practice allow organizations to fit roles, responsibilities and (collaborative) productivity all together.
But communities are inherently dynamic and have fuzzy boundaries. Networks, which may both encompass or be nested inside them, are often unpredictable, uncontrollable, activate and dissolve on purpose, instill passion and disruption into communities. In networks relies the real power of communities. Without purposely enabling them and fully fostering their capabilities, which means giving up control and deeply changing the way we think about work, online communities are, and ever will, only be technology assisted para-hierarchical structures. Communities are the bodies, while networks are the souls of the collaborative enterprise. Without a real cultural change, ‘change toward Enterprise 2.0 adoption’ merely means creating Zombies 2.0. Is your company into ‘socialwashing’?
By Thierry de Baillon
Version française ici. R8WDSZFCZWAY
Among the most overheard and misused buzzwords in companies are, you guessed it, ‘communities’ and ‘networks’. One of the side effects of Marketing 2.0 is, besides embodying new relationships between brands and customers, raising awareness among top managers about the potentials of collaborative work.
Of course companies, particularly the biggest ones, are dealing with internal communities for a few years now, often without truly understanding how to energize and leverage their power, but goofy expressions such as “Facebook for Enterprise” are now making their way into executives wish lists and discourses. Social platforms vendors aren’t helping either. Socialtext’s claim is ‘Social Networking with Enterprise 2.0 Collaboration’; Jive Software presents its SBS software as “robust social networking software for employee communities”. An awful 2.0 mess…


Technology itself, introducing more and more real-time capabilities into platforms, contributes further in blurring the lines between communities and networks.
Both concepts have their place in the connected Enterprise. Not only is the understanding of what differentiates them is key to successfully implement socio-collaborative initiatives, but harnessing their complementarity also provides us with a valuable framework of building blocks to leverage the internal ecosystem of Enterprise 2.0.
|
Communities
|
Networks
|
| Structure |
Stable |
Self-arranging and complex |
| Scope |
Adaptive – Defined perimeter |
Disruptive – Global perimeter |
| Goals |
Collaboration over time |
Specific |
| Governance |
Managed leadership |
Organic leadership |
| Level of integration into existing flows |
Department / Role |
Project / Task |
| Interaction mode |
Mostly asynchronous |
Real time |
| Adoption |
Gradual, built on purpose |
Affinity based, spontaneous |
Rather than fighting each other, communities and networks may, while serving different purposes, raise quality of connected work inside enterprise. Being fluid and highly interactive, networks can address specific issues out of the scope of a single community. They can be setup on demand, self-arrange to solve problems, then dismantled or put at sleep once the issue resolved. Networks act as powerful ad hoc task forces, their power amplified by real-time tools. Lot has been written about the need or not to embed community-based outcome into existing business processes. I do believe than working in a connected environment will ultimately lead to replace our actual processes by some new adaptive individually empowered mechanisms, and we can already put this vision at work: correctly driven (and understood, which means they must not been implemented as a substitute for communities but built ASIDE them), social networks have the tremendous power to deliver.