Five capabilities, one engineering practice.
Most engagements draw on more than one of these. A platform needs integration; integration surfaces data problems; anything in production needs somewhere to run and someone watching it.
The model
How the capabilities fit together
We describe the work as five capabilities because that is how organisations procure it, but they are not separable in practice. Strategy work sets the boundaries that platform engineering builds within. Platforms generate the data that reporting depends on, and only reach the rest of the estate through integration. Everything in production depends on the delivery and reliability practice underneath it. An engagement that treats any one of these as somebody else's problem tends to discover it later, at higher cost.
How the five capabilities relate
Strategy and architecture sets the boundaries and sequence for the other four. Digital platforms produce and consume the operational data. Systems integration connects platforms to the rest of the estate and to external systems. Data, analytics and AI reads from the platforms and the integration layer to answer questions. Cloud, DevOps and reliability runs underneath all of them, providing the environments, delivery pipeline and observability that every other capability depends on in production.
How they connect
- Strategy & Architecture supports Digital Platforms — Sets boundaries, data model and sequence
- Digital Platforms supports Integration — Exposes and consumes interfaces
- Integration supports Data, Analytics & AI — Supplies reconciled data
- Digital Platforms supports Data, Analytics & AI — Produces the operational record
- Cloud & DevOps supports Digital Platforms — Provides environments, pipeline and observability
- Cloud & DevOps supports Integration — Runs and monitors the exchange layer
Capabilities
What each one covers
Digital Platforms
Design and delivery of the operational systems an organisation runs on -- portals, registries, case management, dashboards and the web and mobile products built on top of them.
ExploreIntegration
Making separate systems work as one -- APIs, data exchange, integration architecture and the modernisation work that makes an older system reachable without replacing it.
ExploreData, Analytics & AI
Turning operational data into something an organisation can act on -- reporting platforms, decision support, data products, and applied AI where it solves a real problem rather than decorating one.
ExploreCloud & DevOps
Deployment architecture, delivery pipelines, observability and the operational practices that decide whether a system stays available, stays affordable and can still be changed a year after launch.
ExploreStrategy & Architecture
Solution architecture, technical discovery, system assessment and roadmap work -- the decisions made before a build starts, which are the ones that cost the most to reverse.
ExploreNot sure which of these your problem is?
Most are more than one. Describe the situation and we will tell you where we think the work actually sits -- including if the answer is that you do not need us yet.