Learning Paths and Certification
Learning paths match what a person needs to learn to the role and problem in front of them, and certifications are one input among many; build skill through practice on real work, use certificates for shared vocabulary and for the cases where a customer or employer requires them, and never treat a certificate as proof that an organization is capable or compliant.
Why this matters
Service management draws on many bodies of knowledge: ITIL, agile methods, DevOps and site reliability engineering, security, data, and now AI. Each has books, courses, and certification schemes with their own communities and sales pitches. A newcomer asks where to start. A manager asks what to fund. An organization asks how to build capability across a hundred people with different jobs. The answers are often "buy the course" or "get the certificate", and the results are often disappointing.
Courses and certificates do real things. They give a shared vocabulary, so that people from different teams mean the same thing by "incident" or "change". They give a structured introduction and a prompt to study. They signal to employers and customers that someone has invested time. Some contracts and job descriptions require them. But a certificate shows that someone passed an assessment, usually of knowledge, and it does not show that they can run an incident, lead a postmortem, or design a pipeline. Skills grow mostly from doing the work with feedback.
This topic helps to build learning paths that combine the guide's topics, practice, and, where useful, certification. It offers paths by role and by problem, explains how the main schemes relate, and describes how to judge readiness by what people can do. It applies no endorsement to any provider. Schemes and content change, so check each owner's current publications. It connects to team conversations (Topic 8.4 — Team Conversations), organizational change (Topic 8.3 — Organizational Change and Adoption), AI skills (Topic 5.7 — AI Skills and Prompts), and the AI operating model (Topic 5.8 — AI Operating Model and Skills).
Core concepts
Learning path. An ordered set of learning activities for a defined role or goal, moving from foundation to depth. Wikipedia describes learning pathways in education. A path names the outcome (what the person should be able to do), the topics and practice, the support, and how progress is shown.
Competence, not coverage. The aim is that people can do things, not that they have read things. Wikipedia describes competency-based learning, in which progress depends on demonstrated ability. Define each path's outcomes as observable actions, such as "run an incident review that produces tracked actions".
Stages of skill. The Dreyfus model of skill acquisition, which Wikipedia describes, proposes stages from novice to expert, in which people move from following rules to judging by experience. Novices need clear steps and examples; experts need real problems and peers. A path should serve the stage, not give everyone the same material.
Learning by doing. Skill grows through practice with feedback, which Wikipedia describes as experiential learning. Courses give concepts; practice on real tasks, with coaching, builds ability. On-the-job training, apprenticeship, shadowing, pairing, and mentorship, all described on Wikipedia, are central. See Topic 2.10 — Agile Management and Learning.
Communities and peers. Communities of practice, described on Wikipedia, let people learn from each other's work. Regular sessions, shared examples, and a place to ask questions often teach more than a course. See Topic 8.3 — Organizational Change and Adoption.
Learning by role. Different roles need different depth. A service desk analyst needs the practices at the front line; a product owner needs ownership, flow, and measurement; a leader needs governance, risk, and the economics of automation and AI. The table below suggests paths using this guide.
| Role | Start with | Then | Add as needed |
|---|---|---|---|
| New to service management | Topic 1.1 — Service Management, Topic 1.5 — ITIL Guiding Principles, Topic 1.7 — The Service Value Chain | Topic 3.1 — Service Desk, Topic 3.2 — Incident Management | Topic 3.6 — Service Request Management |
| Service desk or support analyst | Topic 3.1 — Service Desk, Topic 3.2 — Incident Management | Topic 3.9 — Knowledge Management, Topic 3.6 — Service Request Management | Topic 5.3 — AI Service Desk and Virtual Agents |
| Operations or on-call engineer | Topic 3.2 — Incident Management, Topic 3.10 — Monitoring and Event Management | Topic 3.3 — Problem Management, Topic 2.6 — Site Reliability Engineering | Topic 6.6 — Runbook Automation and Auto-Remediation |
| Developer or delivery engineer | Topic 2.2 — Continuous Delivery, Topic 2.5 — DevOps | Topic 3.4 — Change Enablement, Topic 6.4 — Pipelines and Automated Change | Topic 6.3 — Infrastructure as Code and GitOps |
| Product or service owner | Topic 2.8 — Product and Service Ownership, Topic 3.7 — Service Level Management | Topic 2.3 — Flow and Kanban, Topic 7.3 — Measurement and Reporting | Topic 4.5 — Financial Management and FinOps |
| Change, release, or practice owner | Topic 3.4 — Change Enablement, Topic 3.5 — Release and Deployment Management | Topic 2.9 — Agile Service Management, Topic 3.15 — Continual Improvement | Topic 8.1 — Governance, Risk, and Compliance |
| Analyst or data specialist | Topic 7.1 — Analytics for Service Management, Topic 7.2 — Data Foundations and Governance | Topic 7.6 — Process and Value Stream Analytics, Topic 7.5 — Predictive Analytics and Forecasting | Topic 7.7 — Experience and Sentiment Analytics |
| Security, risk, or compliance | Topic 3.13 — Information Security Management, Topic 8.1 — Governance, Risk, and Compliance | Topic 5.6 — AI Governance, Risk, and Compliance, Topic 3.14 — Supplier Management | Topic 3.12 — Service Continuity Management |
| Manager or leader | Topic 1.4 — The Service Value System, Topic 2.10 — Agile Management and Learning | Topic 8.3 — Organizational Change and Adoption, Topic 5.8 — AI Operating Model and Skills | Topic 6.1 — Automation Strategy |
| Anyone starting with AI | Topic 5.1 — AI in Service Management, Topic 5.7 — AI Skills and Prompts | Topic 5.4 — Generative AI for Incidents, Knowledge, and Changes | Topic 5.5 — Agentic AI and Human Oversight |
Learning by problem. Often a better start is the problem in front of you: too many alerts (Topic 3.10 — Monitoring and Event Management), changes stuck in approval (Topic 3.4 — Change Enablement), requests that wait (Topic 6.2 — Workflow Automation and Orchestration), costs that surprise (Topic 4.5 — Financial Management and FinOps). Use the index and glossary to find the home topic.
Certification. A formal credential awarded after an assessment, by a body that sets the standard. Wikipedia describes professional certification. Schemes differ in what they assess (knowledge, application, or demonstrated experience), in how long they last, and in whether they require renewal.
ITIL certification. ITIL certifications are awarded to people, in stages, by the owner of ITIL (see Topic 1.2 — ITIL). PeopleCert's page for the ITIL Foundation Bridge (Version 5) describes a bridge for ITIL 4 certification holders that covers the updates in ITIL Foundation (Version 5); it did not give a release date for ITIL 5 itself. See Topic 1.3 — ITIL 5. Check the owner's pages for the current scheme, levels, and pathways. ITIL certification does not certify an organization; for that, see ISO/IEC 20000 in Topic 1.8 — Service Management Frameworks and Standards.
Other schemes. Agile and delivery certifications exist for Scrum, scaling frameworks such as SAFe, and DevOps and reliability practices; project and product bodies, such as the Project Management Institute, offer their own. Governance and audit bodies offer credentials related to frameworks such as COBIT and standards such as ISO/IEC 20000 and ISO/IEC 27001. Cloud and AI vendors offer product certifications. Wikipedia describes some of these frameworks, and each scheme's owner is the authority on what it covers. This guide does not endorse any scheme or provider.
Choosing a certification. Ask what the person will be able to do afterwards, whether the assessment tests application or only recall, who requires or values it, what it costs in money and time, and how it is kept current. For a team, ask whether a short, practical course and a community would serve better.
Certificates and capability. A certificate is evidence of study. Capability is shown by performance: the quality of incident handling, the clarity of a runbook, the results of changes. Wikipedia describes credentialism, the over-reliance on formal qualifications. Use both, and judge readiness by observed work.
Micro-credentials and continuing learning. Shorter credentials, described on Wikipedia as microdegrees or microcredentials, and continuing professional development, also described there, keep skills current. Technology changes fast; learning must continue.
Learning with AI. AI assistants can explain concepts, generate practice scenarios, and give feedback on drafts, and they can also give confident wrong answers and weaken the habit of working things out. Use them as a tutor to check against sources and to practice, not as a substitute for understanding. See Topic 5.7 — AI Skills and Prompts.
Equity and access. Not everyone has the time, money, language, or support to take courses and exams. Provide time at work, funding, and alternatives such as mentoring and projects, and avoid making certificates a barrier to roles where skills matter more.
Showing progress. Use portfolios of work, such as a postmortem a person led or a runbook they wrote, along with certificates. Peer review and manager observation give richer evidence than exam scores.
How the lenses fit. Learning supports all four lenses: agile practice, AI use, automation, and analytics each need skills. Agile practice treats learning as continuous, with short cycles. AI can support learning under care. Analytics can show skill gaps, with attention to fairness and privacy.
Best practices
- Define outcomes as actions. For each role, write what people should be able to do, such as "run a blameless review" or "build a pipeline check", and design the path to that.
- Start from the role and the problem. Use the table and the index to select a few topics. Do not assign everything to everyone.
- Make practice the core. Pair each topic with a real task, such as applying a topic's questions to the team's own work, with feedback from a colleague or coach.
- Use the topics as team conversations. Run short sessions with the questions in each topic. See Topic 8.4 — Team Conversations. Shared discussion spreads understanding faster than individual reading.
- Create peer communities. Support a regular forum where people share cases, prompts, and problems. Rotate the lead.
- Pick certifications for a reason. Choose a scheme when a customer, employer, or contract requires it, or when its content helps a defined need. Check the owner's current scheme and the cost in time and money.
- Judge readiness by observed work. Look at what people have done: reviews led, changes made, runbooks written. Use certificates as one piece of evidence.
- Allow time and give access. Provide paid time, funding, and alternatives for those who cannot take exams. Protect learning time from urgent work.
- Use AI as a tutor with care. Encourage practice scenarios and feedback from AI, with checks against sources, and keep human mentoring.
- Review and update paths. Check yearly whether paths reflect current practice, what people found useful, and what changed in the schemes you rely on.
Questions to discuss with your team
What can each person on our team do well today, and what do we need someone to be able to do next year? Ask people to describe skills in terms of actions. Expect gaps in less glamorous areas such as problem reviews or data. Follow up by choosing two skills to build, with a person and a method for each.
What is the last thing we learned from a course that changed how we work, and what made that happen? Ask for examples. Expect few. Look for conditions such as practice and support. Follow up by agreeing how to apply the next learning on real work.
Which certifications are we asked for, by whom, and why? List them. Expect some requirements that are assumed and some that are real. Follow up by checking the contract or job description.
How do we show that someone is ready for a role, beyond a certificate? Discuss portfolios, observation, and peer review. Expect that the current method is informal. Follow up by agreeing a small set of observable markers for one role.
Who in our team cannot easily take courses or exams, and what would help? Think of time, cost, language, and confidence. Expect some barriers. Follow up by agreeing one change, such as protected learning time.
How do we use AI to learn, and how do we check what it teaches us? Ask. Expect use without checking. Follow up by agreeing that AI explanations are checked against a source and discussed with a colleague.
In practice: a service management example
A regional water utility's IT department of 60 people is being asked to move to continuous delivery and introduce an AI assistant on the service desk. The manager has a budget for training and is considering sending everyone on an ITIL course and an agile certification. The training lead suggests a different approach.
She begins with roles and outcomes. For the service desk, the outcome is that analysts can resolve routine requests at first contact, write a useful knowledge article, and review the AI assistant's drafts. For on-call engineers, it is that they can lead a major incident and write a runbook another person can follow. For developers, it is that they can add a check to the pipeline and describe a change's risk. For managers, it is that they can use measures without gaming them and run a blameless review.
Each path uses the guide's topics, chosen by role, with a real task. The service desk team reads Topic 3.1 — Service Desk and Topic 3.9 — Knowledge Management over four weeks, and in each short session answers one question about their own queue; each writes two articles and has them reviewed by a colleague. On-call engineers run a rehearsal of a major incident and a review, and write one runbook each. A monthly community meeting shares prompts and cases.
For certification, the department agrees a rule: pay for a certificate when a contract or role requires it, or when a person has a plan to use the content, and give study time within work hours. Twelve people take the ITIL foundation exam because a government contract requires it, and, for those who do, the lead checks that the contract names a person-level certificate. The department's ISO/IEC 20000 plan is handled by a separate group. Staff who cannot attend evening courses are offered mentoring and a project-based route.
What changes: people can show work they have done, and the AI assistant's drafts are reviewed by analysts with a shared method. What remains hard: some staff feel that certificates matter more for promotion than the practical portfolio; protected learning time is cut when the service is busy; and the department cannot yet say whether the practice improved results. The lead tracks time to restore service and article reuse over the year and asks managers to count portfolio evidence in promotion decisions.
Four perspectives
Product and delivery teams
Learn by doing within your delivery work: add a check, review an incident, write a runbook. Share what you learn, and use certificates where they help, not as a goal.
Service and operations teams
Build skills through practice on real incidents and requests, with coaching and reviews. Join communities, and keep time for learning when it is quiet.
Leadership and governance
Fund time, practice, and communities as well as courses. Define roles in terms of what people can do, and judge readiness by evidence. Be careful about making certificates a barrier to those who lack access.
Customers and users
You may require certain certifications from providers. Ask what they show, and ask for evidence of how the provider's people handle real situations, such as reviews of past incidents.
Agile, AI, automation, and analytics
Agile
Learning is continuous: short cycles of try, reflect, and adjust, with real work as the material. Pair courses with practice, and review progress regularly with the team. Caution: do not add a certification program to a team with no time to learn; the effort will be wasted.
AI
AI can act as a tutor, generate practice scenarios, and comment on drafts, and it can also state errors with confidence. Name who guides its use, and encourage checking against sources and discussion with a peer. Caution: do not use AI to monitor individual learning or to evaluate people; it erodes trust. See Topic 5.7 — AI Skills and Prompts.
Automation
Automate enrollment, reminders, and records of learning, and offer sandboxes where people can practice safely. Caution: automated learning tracking can become surveillance; use it to support, and share it with the learner. See Topic 6.1 — Automation Strategy.
Analytics
Look at skills coverage by role, time to proficiency, use of learning resources, and links between learning and results such as incident handling quality. Caution: counts of courses or certificates reward activity, and links between training and outcomes are hard to prove; use team-level data and portfolios. See Topic 7.7 — Experience and Sentiment Analytics and the Service Management Metrics book.
Common failure modes
- Course as the whole plan. People attend and nothing changes. Add practice, coaching, and community.
- Certificates as proof of capability. A passed exam stands in for performance. Judge by observed work.
- Everyone gets everything. Time is wasted. Choose by role and problem.
- No time to learn. Learning is squeezed out by urgent work. Protect it and report when it is cut.
- Certification for its own sake. Cost without benefit. Choose when required or useful.
- Barriers to access. Some people are excluded. Provide time, funding, and alternatives.
- Out-of-date paths. Content and schemes change. Review yearly and check owners' current publications.
Maturity model
| Dimension | Initiate | Develop | Standardize | Manage | Orchestrate |
|---|---|---|---|---|---|
| Paths | None | Course lists | Role-based paths with defined outcomes | Paths reviewed against results | Paths integrated with careers and teams across the organization |
| Practice | Courses only | Some on-the-job tasks | Practice, coaching, and communities for each path | Practice quality and results measured | Learning embedded in daily work across partners |
| Certification | Ad hoc | Funded on request | Chosen by requirement or defined need | Value of certification reviewed | Certification aligned with roles, contracts, and capability evidence |
| Access and evidence | Uneven | Awareness | Time, funding, and alternatives provided; portfolios used | Equity and evidence reviewed | Evidence of capability shared across teams and with customers |
Checklist
- Each role has outcomes defined as observable actions.
- Paths are chosen by role and problem, using this guide's topics.
- Each path includes practice on real work with feedback.
- We run team conversations and a community of practice.
- We choose certifications for a stated reason, and check the owner's current scheme.
- Readiness is judged by observed work as well as certificates.
- People have protected time, funding, and alternative routes.
- We review paths at least yearly.
AI prompts
Draft a learning path for a role.
The role: [describe what the person does]. Their current experience: [describe]. The outcome we want, as things they can do: [list].
Draft a six-week learning path using only these topics from our guide: [list titles], with for each week one reading, one practice task on real work, and one way to get feedback. Do not name courses or certifications.
List what you are unsure of.
Compare a certification with a need.
Here is the description of a certification from its owner: [paste]. Here is what our team needs to be able to do: [list].
List which needs the description appears to cover, which it does not mention, and questions to ask the owner about assessment type, renewal, and cost. Do not judge the value of the certification.
List what you are unsure of.
Design a practice scenario.
Skill: [for example, leading a major incident review]. Learner level: [novice or experienced]. Our context: [type of organization].
Write a realistic fictional scenario of about 200 words and six questions the learner should answer, with notes for a coach on what a good answer would include. Do not use real names or systems.
List what you are unsure of.
AI skills
- training-needs-analysis: use to define the skills each role needs.
- service-management-guide-skill: use to choose topics for a role or problem.
- agile-coaching: use to coach people and teams as they build skills.
- getting-feedback: use to gather feedback on learning and its effect.
- maturity-models: use to assess team capability against a maturity table.
Key sources
- PeopleCert, ITIL certification pages (peoplecert.org): the owner's description of the ITIL certification scheme, including the Foundation Bridge (Version 5).
- Each certification owner's own publications: the authoritative source on what a scheme covers and requires.
- Anders Ericsson and Robert Pool, Peak (2016): on deliberate practice and how expertise develops.
- Wikipedia, "Professional certification" and "Dreyfus model of skill acquisition": overviews of the ideas.
References
- ITIL Foundation Bridge (Version 5) — PeopleCert — https://www.peoplecert.org/browse-certifications/it-governance-and-service-management/ITIL-1/itil-foundation-bridge-version-5-4158
- Professional certification — Wikipedia — https://en.wikipedia.org/wiki/Professional_certification
- Competency-based learning — Wikipedia — https://en.wikipedia.org/wiki/Competency-based_learning
- Dreyfus model of skill acquisition — Wikipedia — https://en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition
- Experiential learning — Wikipedia — https://en.wikipedia.org/wiki/Experiential_learning
- Community of practice — Wikipedia — https://en.wikipedia.org/wiki/Community_of_practice
- Mentorship — Wikipedia — https://en.wikipedia.org/wiki/Mentorship
- Apprenticeship — Wikipedia — https://en.wikipedia.org/wiki/Apprenticeship
- Learning pathway — Wikipedia — https://en.wikipedia.org/wiki/Learning_pathway
- Credentialism and degree inflation — Wikipedia — https://en.wikipedia.org/wiki/Credentialism_and_degree_inflation
- Professional development — Wikipedia — https://en.wikipedia.org/wiki/Professional_development
- ITIL — Wikipedia — https://en.wikipedia.org/wiki/ITIL