The Executive Diagnostic and Governance Toolkit
Assessing and Evidencing IT Service Desk Performance
Score your own function red, amber or green, find out which part is weakest, and walk into the next budget round able to defend what you want to fix. Built for leaders reviewing they already hold the IT service desk playbook: the implementation guide, the roadmap and the working files, so repeating any of that is worthless. What is missing is the layer after implementation. How to assess the function honestly, what evidence to retain, how to score maturity, and how to put the result in front of a manager, an auditor or a client who was not involved. The immediate question: for one month of IT service desk work, can you show what was measured, against what target, and what changed as a result.
Each order is checked and updated against the latest insights before delivery. That is why access takes up to 24 hours rather than being instant.
| 1 |
You stop guessing where you stand. You finish with a score, not an opinion: every part of your function rated red, amber or green, with the weakest ranked first. Evidence: a Quick Scan for the shape of it, then seven domain assessments of 30 scored questions each, 210 in all, rolled into one scorecard, plus a maturity radar and a current-versus-target gap analysis. |
| 2 |
You can defend the decision. You walk into the budget round with the gap named, the owner named and done defined, instead of a case built on instinct. Evidence: project charter, scope statement, RACI, requirements traceability and work breakdown structure, pre-filled in your domain's language. |
| 3 |
The work actually moves. The month after the decision is already built, so nothing stalls waiting for someone to design a form. Evidence: more than 60 project templates across all five PMBOK process groups, plus runbooks, SOPs, a KPI framework, audit checklists and a risk matrix. 55 to 65 files in total. |
| 4 |
You use it the day it lands. No blank templates to interpret. Every workbook opens with what it is, who uses it, when, how, a 1 to 5 scoring guide, what good looks like, and a worked example you delete and type over. |
The situation this is built for
You hold the implementation playbook, roadmap, and files. But when a manager, auditor, or client asks 'What did we achieve last month?' you struggle to show measurable progress. You know the tickets are closed, but can you prove maturity improved? Without a structured way to assess, evidence, and report, your work remains invisible. The tools exist to implement. None exist to prove.
Who this is for
The IT service desk owner responsible for ongoing performance, reporting to leadership or compliance teams, and required to demonstrate measurable outcomes beyond ticket volume.
Who this is not for
This is not for consultants selling service desk tools, nor for teams still building their first ticketing system. It is not for executives seeking high-level summaries without operational depth.
What you walk away with
- Assess the real maturity of your IT service desk
- Build evidence packages that satisfy auditors and managers
- Score performance against measurable benchmarks
- Report outcomes using standardised, repeatable formats
- Turn daily operations into documented organisational value
How this maps to your situation
- Defining what to assess and why
- Measuring current state objectively
- Capturing proof systematically
- Maintaining visibility over time
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed to be completed alongside regular work over 8-12 weeks.
How this compares to the alternatives
Generic ITIL training covers implementation but skips evidence and assessment. Vendor-specific certifications focus on tools, not outcomes. This course fills the gap with field-tested methods to prove service desk value, not just run it.
Also included: the full course, for when you want the reasoning behind a finding (12 modules, 144 chapters)
Depth reference. The diagnostic and the templates stand on their own; this is what to read when you want the reasoning behind a finding.
- Identifying core service desk functions for review
- Mapping stakeholder expectations to assessment goals
- Setting boundaries for incident management review
- Determining scope for service request analysis
- Including problem management in assessment scope
- Excluding non-operational functions from review
- Documenting scope decisions for transparency
- Aligning assessment with service level agreements
- Using support hours to define functional coverage
- Reviewing change advisory board interactions
- Assessing knowledge base usage completeness
- Finalising scope with team leads and managers
- Selecting initial response time benchmarks
- Measuring first contact resolution rate baseline
- Tracking average handle time across teams
- Calculating ticket volume per support tier
- Benchmarking escalations to level two and three
- Recording service request fulfillment duration
- Measuring reassignment frequency per ticket
- Tracking resolution within SLA percentage
- Assessing user satisfaction survey participation
- Measuring feedback collection consistency
- Establishing knowledge article creation rate
- Documenting baseline metrics in audit format
- Choosing evidence types for each KPI
- Setting retention periods for ticket logs
- Standardising screenshot documentation formats
- Creating audit trails for escalation paths
- Logging manager approvals for major incidents
- Capturing root cause analysis documentation
- Archiving post-incident review summaries
- Recording service request approval workflows
- Preserving user feedback response records
- Maintaining version control for runbooks
- Storing change implementation confirmations
- Building evidence folders by calendar month
- Configuring automated ticket tagging rules
- Setting up real-time dashboard alerts
- Scheduling daily metric export jobs
- Integrating monitoring with shift handovers
- Automating SLA breach notifications
- Linking monitoring to team leader reports
- Validating data accuracy from source systems
- Reviewing alert fatigue in current setup
- Adjusting thresholds for false positives
- Documenting monitoring rule changes
- Ensuring compliance with data privacy rules
- Testing backup evidence capture processes
- Adapting maturity model to service desk size
- Defining level one: initial capability
- Identifying level two: repeatable processes
- Scoring level three: defined procedures
- Assessing level four: managed performance
- Evaluating level five: optimised outcomes
- Mapping incidents to maturity indicators
- Scoring problem management consistency
- Rating request fulfillment predictability
- Assessing knowledge management completeness
- Reviewing change management integration
- Publishing scored results to stakeholders
- Scheduling quarterly internal assessment dates
- Assigning assessment roles to team members
- Preparing evidence packs for review
- Running mock auditor interviews
- Documenting findings from internal walkthroughs
- Identifying missing evidence gaps
- Prioritising findings by risk level
- Creating action plans for deficiencies
- Tracking closure of internal findings
- Updating runbooks based on review outcomes
- Measuring improvement over cycle intervals
- Reporting internal results to management
- Structuring monthly performance dossiers
- Including evidence for each reported metric
- Writing executive summaries for leadership
- Formatting appendices for auditor access
- Validating data against source systems
- Signing off reports with team leads
- Archiving reports in secure locations
- Preparing client-facing summary versions
- Including maturity score progression charts
- Highlighting improvements from prior periods
- Adding commentary on outlier events
- Ensuring report consistency across months
- Scheduling review meetings with stakeholders
- Distributing pre-read materials in advance
- Preparing presentation decks from reports
- Anticipating challenging questions
- Practicing responses to common objections
- Using visuals to explain maturity trends
- Facilitating discussion on improvement areas
- Capturing decisions from meeting minutes
- Tracking action items assigned to owners
- Following up on unresolved concerns
- Adjusting reporting based on feedback
- Documenting stakeholder acknowledgments
- Identifying root causes of performance gaps
- Writing specific and time-bound actions
- Assigning owners for each corrective item
- Setting deadlines for implementation
- Linking actions to maturity score goals
- Tracking progress in shared dashboards
- Verifying completion with evidence
- Adjusting plans based on blockers
- Escalating stalled actions to management
- Integrating fixes into team workflows
- Measuring impact after implementation
- Closing actions in audit tracking system
- Analysing user satisfaction trends over time
- Identifying frequent complaint categories
- Mapping feedback to process weaknesses
- Prioritising changes based on impact
- Updating service request templates
- Revising escalation criteria for incidents
- Improving knowledge base article structure
- Adjusting staffing models based on volume
- Enhancing training materials with examples
- Testing changes in pilot groups
- Measuring effectiveness of design updates
- Documenting service design evolution
- Onboarding new staff to evidence protocols
- Including evidence in performance reviews
- Conducting refresher training sessions
- Auditing compliance with documentation rules
- Recognising consistent evidence contributors
- Updating templates for process changes
- Reviewing retention policies annually
- Aligning practices with new regulations
- Sharing best practices across teams
- Measuring adherence through random checks
- Updating playbook based on experience
- Maintaining continuity during leadership changes
- Identifying candidate teams for rollout
- Adapting assessment for team size differences
- Transferring evidence frameworks to new units
- Training regional leads on scoring models
- Standardising report formats globally
- Harmonising metric definitions across sites
- Scheduling staggered assessment cycles
- Consolidating results for enterprise view
- Addressing local compliance requirements
- Sharing maturity dashboards with HQ
- Measuring consistency across locations
- Scaling playbook for multi-team use
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
Thousands of organisations have bought from The Art of Service since 2000.