Availability and traffic establish the original dashboard.
Quiet value loss
What does losing value quietly look like?
Here is one example in full, because one is enough. A licence renewal arrives eight per cent higher than last year. Nobody blinks, because nobody is measuring usage against it. Three of the modules on the invoice were switched off two reorganisations ago, and one was never switched on. The platform is fine. The bill is wrong. No alert exists for that.
There are more signals like this one, and each looks like an annoyance from up close and a rounding error from far away. Added together across a year they are neither. We keep the full list inside the health check itself, partly because it is the product, and mostly because a list without an inspection behind it just gives people new things to worry about in the wrong order.
The drift
Manual steps and unused capabilities sit outside monitoring.
Delays and coordination costs become normalised.
The platform is still live, but the business receives less from it.
A platform can look stable while operational drag continues to grow outside the incident dashboard.
The measurement gap
Why doesn't monitoring catch it?
Dashboards answer yesterday's questions. They are built in the platform's first year, around the risks everyone worried about at launch. The drag arrives later and lives elsewhere: between the CMS and the translation agency, between the campaign calendar and the release cycle, between what the licence covers and what the team actually uses. Nobody's dashboard points at a gap.
The other reason is human and kinder. People normalise workarounds the way anyone normalises a sticking door in their own house. The engineer who exports content to a spreadsheet every Thursday stopped noticing it years ago. The person who would mind has never seen it.
Attribution format to confirm before publish
Nearly every health check we have run has surfaced something that needed attention. Not a crisis. Cost, sitting quietly where nobody was looking.
Richard · Alliances Lead, TBSCG
The inspection
What is a DXP health check?
A fixed-scope inspection of a live platform, run by engineers who have spent twenty years doing them. It looks at the platform, the process around it and the value coming out of it, and produces something rare: a report a leadership team can actually read. What is healthy, what is leaking, what to do first and what genuinely does not matter, with a view on AI readiness included because that question now arrives in every boardroom anyway.
What it checks stays inside the check. That is deliberate. An inspection is worth paying for precisely because it is done by someone who has seen a hundred of these, on your platform rather than in the abstract.
20+
Years
Of running platform inspections on live enterprise systems.
ONE
Report
Leadership-readable: healthy, leaking, and what to fix in what order.
2 MIN
Readiness check
Score your own platform with the calculator before anyone calls you.
Asked plainly
Frequently asked questions.
Why don't dashboards catch a platform losing value?
Dashboards measure what someone once decided to measure, usually availability and traffic. The expensive problems live between systems and between teams, as workarounds and delays that never register as incidents.
What is a DXP health check?
A fixed-scope inspection of a live digital platform by senior engineers, producing a leadership-readable report of what is healthy, what is leaking value, and what to fix in what order, including an AI-readiness view.
How do I find out if my platform needs one?
Start with the two-minute readiness check on this site. It scores the platform against the criteria an inspection uses and tells you whether a full health check is worth a conversation.
Next step
Find out where you stand.
The two-minute check scores your platform against the same criteria an inspection uses. If the score earns it, the full health check is a thirty-minute conversation away.