Reducing Complexity to Manage Better

Emma Stewart writes today in a Harvard Business Publishing blog about the futility of Scenario Planning exercises, saying that

.. if you want to avoid fixes that fail and move towards sustainability in today’s complex operating environment, I invite you to resist the instinct to resort to scenario exercises, or only do so in conjunction with systems thinking approaches.

I can see her point, but the elaborate systems thinking approach she is referring to does exist already – generally embedded deep into the fabric of any successful organization. The organizational processes and systems are designed and maintained to weather the ‘normal’ levels of complexity. Scenario Planning, on the other hand, tries to peer into the future in order to develop some decision making criteria as and when needed.

Complexity in business and its operating environment is a given constraint in management. Management challenges exist along two completely opposite paradigms.

At one end we need to delve deep into existing complexity – define it and automate the processes and decisions there – so that we are ‘shielded’ from the known complexity or the static view. The system or the model works just fine within the frame of its original assumptions. Taken to an extreme, all possible complexity can be modeled given enough time and data.

On the other end is the unknown complexity introduced as soon as we recognize that we live in a real world of dynamic, moving components that can interact with each other in unpredictable ways to create new scenarios. This is where we need to abstract the complexity into simple models like the famous (or infamous) 2×2 matrices. We need to make empirical decisions quickly because the environment is changing at the same time. Decision models need to be simple and adequate – a criteria difficult to achieve, but still better than trying to stop the world while we analyze our way into paralysis.

Good management needs to manage complexity by instituting structure – enough to be affordable – and by developing abstracted, simple decision models – enough to be useful.

Business Processes and CRM Systems

Ann All is pointing out the convergence between Customer Relationship Management (CRM) systems and Business Process Management (BPM). She writes

Too often CRM is a disjointed mishmash of departmental or divisional activities. CRM touches a number of enterprise systems, including operations, accounting and e-commerce, so companies must make a better effort to integrate their CRM data with these other systems….

Business processes across the enterprise are either directly or tangentially concerned with customer interactions. Since a 360 degree view of the customer is key for managing the relationship, it follows that all processes need to be considered and relevant customer data lined up for the CRM system to be effective.

For organizations used to working with enterprise-class systems like SAP, an integrated process-based approach is easier to visualize and execute. It is the organization with departmental silos that gets attracted to ‘partial’ solutions that address the contact management functions of CRM. Despite the customer being so central to the modern enterprise, customer relationship management questions quickly devolve into the basic question of, “who owns the customer?” Very rarely do all business departments sit together and design a common integrated process focused on the common customer.

A true customer focused organization will need to take an enterprise-wide process view in implementing CRM.