What we demonstrate
The environments below are running software, not slide decks. The screenshots are taken straight out of the running system. Two are in preparation and are marked as such.
Every one of them runs on a fictional composite estate with generated data. That is a deliberate constraint rather than a limitation: it means a demonstration can be shown to anybody, and that what you are looking at is the method rather than somebody else's numbers.
A desktop logon journey, measured end to end
Ten steps from remote connect to in-session responsiveness. Three vendor tools correlated on one view, the logon drawn as a distributed trace, and objectives generated from a register rather than typed into a dashboard.
A payment, followed from mainframe to microservices
A tier one payments estate mid-migration: a monolithic core, the services carved out in front of it, and the cloud native path replacing both. One payment followed across all three, with the objective held where the customer stands rather than at each hop.
In preparationA citizen service, end to end, including the model
A cloud native citizen-facing service: the journey through it, the platform underneath, and the AI assistance inside it. Measured where it matters to somebody filling in a form once, rather than where it happens to be easy to instrument.
In preparationHow a briefing works
A demonstration is normally a screen share, because it lets us stop on whatever you want to interrogate. Where it is useful for you to explore the environment yourself, access is issued to named people for a scheduled window.
Either way there is a written pack with the screenshots, the reasoning and the honest limitations, so there is something to circulate afterwards to people who were not in the room.