Architecting simplicity
Introduction
Given the pattern for simplicity expressed in the previous pages (what is complexity?) the key principles required for architecting simplicity can be developed for an organisation.
The focus on simplicity is frequently handed to the IT domain which can deliver significant benefits on its own, however the potential improvements in efficiency will be multiplied if there is a similar, aligned approach taken by the whole business, encompassing products, offers, processes, financial and the organisational domains.
Techniques such as service orientated architecture (SOA) have parallels in both automated and manual processes. By defining the data flows and functions provided by each component of the systems including processes such as create product.
In a small start up or customer relationship business many argue that this stifles creativity and flexibility, businesses driven by a product relationship rather than a person to person relationship have the following characteristics :-
- costs proportional to transaction volumes;
- a tight retail market place where incremental price has to be matched by value in quality and predictability of customer experience;
- customers sensitive to price/brand where the need to quickly react to market dynamics can not compromise reliability.
These characteristics focus the strategy on architecting the businesses core systems and processes using principles and patterns to deliver a reliable and efficient business engine but providing flexibility in predetermined areas such as product configuration, pricing, billing etc. where required and creativity to focus on differentiating experiences or products through presentation, presence, and management of customer assets.
Related Topics
Business architecture using TOGAF.
Coming Soon: Overview of TOTEM’s approach to managing complexity.