01
Measure definition
A documented catalogue of every reported measure: meaning, source system, calculation, exclusions, reporting frequency and the individual accountable for the result.
Service · Infrastructure and Managed Services
Service performance, reported consistently in every cycle
Reporting that is rebuilt manually each month arrives late, varies in definition and is disputed rather than acted upon. X-Shift defines the measures once, automates their collection, and operates reporting and performance review on a dependable cycle: operational detail is provided for those operating the service, and a summary for those accountable for it.
Measure catalogue · v3Resolution within service level
Change-controlled- Source
- Ticketing system
- Calculation
- Resolved in target ÷ resolved
- Exclusions
- 2 · shown in report
- Owner
- Service desk manager
Six cycles, a single definitionResultTarget 90%
Pack issued
- AprDay 3
- MayDay 3
- JunDay 3
- JulDay 3
- AugDay 3
- SepDay 3
Reporting and Performance ManagementConsult X-Shift
What we do
Define once, automate, then review
The engagement commences with definitions: what each measure means, the source system from which it is derived, how it is calculated, what constitutes an exclusion and who owns it. These definitions are documented and agreed, so that the figures are no longer contested. Collection from the source systems is then automated and the reporting layer is established: operational views for the teams operating the service, service level reporting against contractual commitments, and a concise summary for executives. History is retained so that trends are visible across periods. Significantly, the performance review itself is operated by X-Shift: a regular session in which results are examined, causes of variance are explained, and actions are agreed and tracked to closure rather than repeated in the next cycle.
- 01Measures defined once
- 02Collection automated
- 03Operational detail
- 04Summary for owners
- 05Trends visible
- 06Reviewed with the client
Scope
What the service covers
Reporting can encompass X-Shift managed services, the client's internal operations, or both together.
- 02
Operational KPIs
Day-to-day measures for the teams operating the service (volumes, resolution performance, availability, utilisation, backlog and throughput), at the frequency that operations require.
- 03
SLA reporting
Measurement of performance against contractual service levels, calculated from source data, with exclusions applied transparently and exceptions explained in the report.
- 04
Performance dashboards
Live dashboards designed for their audience: detail and drill-down for operational teams, and summary and exception views for service owners and management.
- 05
Automated data collection
Collection from monitoring, ticketing, platform and operational systems on a schedule, eliminating manual assembly and the transcription errors associated with it.
- 06
Trend analysis
Comparison across periods to demonstrate direction rather than snapshots, identifying gradual degradation, seasonal patterns and the effect of changes already implemented.
- 07
Executive reporting
A concise periodic summary covering service health, service level position, significant incidents, risks and the actions being taken, prepared for a non-technical audience.
- 08
Performance review and actions
A regular review session in which results are examined with the client's team, causes of variance are explained, and improvement actions are agreed, owned and tracked to closure.
Service commitments
What is committed, and how it is demonstrated
A reporting service that cannot be held to its own delivery has no standing to report on the performance of others. The following are its commitments.
What is measuredHow it is reportedWho owns it
01Report and dashboard delivery against the agreed cycle
How it is reportedReported as issued on time or late, with the reason stated; a late pack is declared rather than backdated
Who owns itX-Shift reporting lead
02Completeness of collection from source systems
How it is reportedReported per source, naming any system that failed to supply data and what was done about it
Who owns itX-Shift data owner, with the client's system owners
03Exclusions applied to service level calculations
How it is reportedShown in the report itself, with the rule that permitted each exclusion, and not applied silently
Who owns itX-Shift reporting lead, with the client's service owner
04Restatements of previously reported figures
How it is reportedDeclared openly with the corrected value and the cause, since a retrospectively altered history undermines the purpose of reporting
Who owns itX-Shift reporting lead
05Measure definitions under change control
How it is reportedReported as a versioned catalogue, so a shift in a trend can be checked against a definition change
Who owns itX-Shift reporting lead
06Improvement actions arising from review
How it is reportedMaintained with an owner and a date and verified at the following review, rather than restated
Who owns itJointly owned with the client's service owner
Reporting cycles, audiences and measure sets are agreed per engagement and reported against that agreement. Where a measure is found to encourage undesirable behaviour, changing it is a governance decision taken openly and not a reporting adjustment.
How it runs
The operating cadence
Once definitions and automation are in place, the reporting and review cycle is repeated at an agreed cadence.
STRUCTURE BEFORE TECHNOLOGYThe platform follows the design, and never the reverse.
01 / 06
01
Definition and onboarding
Measures, sources, calculations, exclusions and owners are agreed and documented, and reporting frequency and audiences are established with the client's team.
OutputA documented measure catalogue with source, calculation, exclusions and a named owner per measure
02 / 06
02
Automation and build
Data collection from source systems is automated and the operational, service level and executive reporting layers are established and validated against known figures.
OutputAutomated collection from source systems, validated against figures that the business already trusts
03 / 06
03
Scheduled reporting
Reports and dashboards are produced on the agreed cycle from source data, with exceptions and service level breaches flagged and explained.
OutputReports and dashboards issued on the agreed cycle, with breaches and exceptions flagged
04 / 06
04
Variance analysis
Results outside expected ranges are investigated for cause prior to the review, so that the discussion commences from explanation rather than speculation.
OutputA variance explanation prepared prior to the review rather than during it
05 / 06
05
Performance review
A regular session with the client's team examines results, agrees improvement actions with named owners and dates, and verifies progress on actions from previous cycles.
OutputReview minutes with improvement actions, named owners and dates
06 / 06
06
Definition maintenance
Measures are revised as services, contracts and priorities change, ensuring that the reporting remains relevant rather than accumulating figures that no party utilises.
OutputAn updated measure catalogue whenever a definition changes
When this is required
The monthly pack is delivered late and is disputed
Every reporting cycle commences with a week of manual collection and concludes with a dispute over definitions.
Figures are obtained from several systems, each counted slightly differently. Two teams present the same measure with different values, so that the review addresses methodology instead of performance. Trends are not visible because each pack is constructed afresh, and by the time the report is circulated, the period it describes has long since elapsed.
Client responsibilities
What the service requires from the client
Reporting disputes rarely concern the reporting itself. They concern definitions that no party has agreed and owners that have not been named, which is where this service requires the client's organisation to commit.
- 01
Read access to the source systems, with a designated technical contact for each
- 02
The stakeholders who currently disagree on definitions, convened once in the same session, in order to resolve them
- 03
A named owner per measure who is accountable for the result, and not solely for supplying the figure
- 04
Attendance at the performance review by individuals who are empowered to agree an action and be held accountable for it
Outcomes
Reviews address performance, not methodology
What this changesWhen definitions are agreed and collection is automated, the figures cease to be the subject of the meeting. Reporting is delivered on time in a consistent form, trends become visible, and improvement actions carry owners and dates instead of being restated each cycle.
- 01
Every measure defined once, with agreed source, calculation and named owner
- 02
Reports produced automatically on schedule instead of being assembled manually
- 03
Service level performance evidenced from source data, with exclusions shown openly
- 04
Improvement actions recorded with owners and dates and checked the following cycle
Common questions
Questions commonly raised before contracting
How does transition operate, and how long is required before reporting is trusted?
Definitions are established first, followed by automated collection, and then a period in which the new reporting is operated in parallel with existing reporting until the figures reconcile. This parallel period is where trust is either established or lost, and shortening it to save time typically results in greater cost later.
What is the impact on the personnel who currently compile the monthly pack?
Manual assembly is eliminated, which typically represents several days each month, and the analytical workload increases. Some individuals welcome this and some do not, because a manual pack carries an influence that an automated one does not. It is advisable to acknowledge this openly at the outset.
How do we know the reporting is honest about bad results?
Because the same service reports its own delivery, its own exclusions and its own restatements. Exclusions appear in the report with the rule that permitted them, and corrected figures are declared rather than silently replaced.
What is the exit process?
The measure catalogue, collection logic, report definitions, dashboards and the retained history are transferred with a support period. The history is the principal asset, as it is the only element that renders the next period comparable to the last.
Next
Recommended next steps
01
Commence with definitions
A short exercise that resolves what each contested measure means, the source from which it is derived and who owns it. This alone frequently ends the monthly dispute.
Applicable where two teams report the same measure with different values.
Consult X-Shift02
Remediate the data source first
Where the underlying operational data is incomplete, reporting will present that gap more clearly rather than close it.
Applicable where the systems behind the figures do not record the work reliably.
Data and Business IntelligenceReporting influences decisions only when an individual is accountable for acting upon it. Without this, the service produces a better-presented pack and nothing further.
Related offerings
Related
Service
Monitoring and Observability
The detection layer that supplies much of the underlying data
Service
Service Desk and Technical Support
Incident and request data behind service level reporting
Service
CX Measurement and Analytics
Measurement of customer experience alongside operational and service level reporting
Solution
Data and Business Intelligence
Wider reporting and analytics beyond managed service performance
Is this the work required?
A short conversation is typically sufficient to establish whether this is the appropriate engagement, a narrower one, or an alternative.