15Signal Strength
Response Infrastructure
Response Infrastructure evaluates the instrumentation and operating cadence behind the digital estate: whether performance is measured meaningfully, and whether measurement leads to change.
Why it matters
- Without measurement, improvement is unattributable and therefore unfundable.
- Response speed compounds. Organizations that iterate monthly outperform those that iterate annually regardless of starting position.
- Instrumentation quality determines whether every other dimension can be managed at all.
What strong looks like
- Analytics correctly implemented, with conversion events tied to commercial outcomes.
- Evidence of iteration: changes shipped, measured and retained or reversed.
- Visible responsiveness — updated content, corrected errors, answered reviews.
- A defined cadence for review and prioritisation.
Common failures
- Analytics present but measuring pageviews rather than outcomes.
- Consent and tagging implementations that silently lose most of the data.
- Reporting that never results in a shipped change.
- Errors and broken paths persisting for months.
What we evaluate
- Analytics and tag implementation quality, including consent handling.
- Whether conversion events are defined and outcome-linked.
- Observable evidence of iteration and maintenance cadence.
- Responsiveness to errors, reviews and external signals.
How to improve
- Fix measurement before optimising anything; bad data produces confident wrong decisions.
- Define a small number of outcome events and instrument them properly.
- Establish a fixed review cadence with an owner and a decision at the end of it.
- Monitor errors and broken paths automatically rather than by report.
Standards it inherits from
Owned by Customer and service operations. This dimension is not invented here — it states an existing discipline standard as something observable and scorable.
- Support design practice
- Service recovery standards
- Published response-time expectations
Who owns it
Scoring anchors
- 3
- One unattended form; no stated response expectation and no alternative route.
- 5
- Contact routes exist, but responses are slow and expectations are unstated.
- 7
- Multiple routes, stated response times, and confirmations that set expectations.
- 9
- Enquiries are answered promptly through the route the customer chose, with the loop closed.
Illustrative median across published studies: 4.9
How to test it yourself
- Submit your own enquiry form and time the reply.
- Check whether the confirmation states what happens next and when.
- Try the alternative routes — phone, email, chat — and see which are attended.
- Ask what happens to an enquiry that arrives on a Friday evening.
Questions
- How is response time observed externally?
- Through published commitments, confirmation behaviour and mystery-shopper style enquiries recorded with the result.
Evidence
This dimension is scored from the following publicly observable sources. Where a source is unavailable for an organization, the limitation is recorded with the result rather than inferred around.
- Tag and analytics implementation inspection
- Consent configuration review
- Change and freshness signals over time
- Error and broken-path monitoring