One organisation. Fragmented technology.
Enterprise teams often organise customer technology around platforms, functions and channels. Each boundary can introduce a new version of context, a separate decision rule or another orchestration path. The customer experiences the accumulated result, not the organisation chart behind it.
The Engagement Fabric is a model for the connective operating architecture. It starts with an encounter—something a customer does, needs or experiences—and traces how the enterprise senses it, assembles permitted context, decides what should happen, coordinates the response and learns from the outcome.
The unit of design is the customer encounter, not the channel.
Engagement Fabric principle
Six capabilities make the fabric operational
- 01
Encounter sensing
Recognise the event, need or change in state that may require a response.
- 02
Governed customer context
Assemble what is known, permitted and relevant without treating every system record as equally usable.
- 03
Decisioning and arbitration
Apply policy, rules, models and priorities to determine the next appropriate action—or whether to act at all.
- 04
Orchestration
Coordinate the decision across journeys, campaigns, service processes and operational constraints.
- 05
Activation
Deliver a coherent response through the channel, person or process best suited to the encounter.
- 06
Feedback and accountability
Capture the outcome, measure whether the decision was useful and make ownership visible for the next cycle.
Expose the real operating system.
- Which encounters matter enough to require a coordinated enterprise response?
- Which context is necessary, trustworthy and permitted at the point of decision?
- Where are decision rules duplicated across platforms, teams or channels?
- Who arbitrates when commercial, service, risk and customer priorities conflict?
- How does the outcome return as evidence for the next encounter?
Apply the model
Trace the encounter first.
Follow the context, decisions, hand-offs and feedback from signal to outcome. The gaps will show where architecture, governance and operating ownership need to change.