ITIL 4 Problem Mgmt study plan
ITIL 4 Problem Mgmt · Give each week a clear focus.
8 weeks · About 6 hours per week
Problem management concepts and principles
Define problem management in your own words and distinguish it from incident management, change enablement, and continual improvement using three concrete scenarios you write yourself.
Map the seven ITIL 4 guiding principles to problem management decisions and record one example of each principle applied to a real problem investigation you have seen or can imagine.
Explain how problem management contributes to the service value chain by identifying which value chain activities it touches and what inputs and outputs flow between them.
Build a one-page glossary of at least 15 problem management terms (problem, known error, workaround, root cause, problem record, error control) with your own definitions.
Your checkpoint
A one-page glossary plus a written comparison table showing problem management versus incident management across at least five dimensions (trigger, goal, ownership, output, closure criteria).
Problem management concepts and principles
Describe the three problem management phases (problem identification, problem control, error control) and state the purpose and key outputs of each.
Explain the difference between reactive and proactive problem identification and list at least four triggers for each type.
Analyze the relationship between problems, incidents, and known errors by drawing a state diagram that shows how a record moves from problem to known error to resolution.
Identify at least three key metrics for problem management (for example, problems resolved within target, percentage of incidents linked to known errors, backlog age) and explain what each metric reveals and how it can be gamed.
Your checkpoint
A state diagram of the problem-to-known-error lifecycle with at least five states, plus a short note on the entry and exit criteria for each state.
Problem management processes and activities
Walk through the problem identification activity and specify the inputs, triggers, and decision criteria used to decide whether an issue warrants a formal problem record.
Draft a problem prioritization scheme that weighs impact, urgency, incident volume, risk, and effort, and test it against five hypothetical problems.
Describe how problem records are logged, categorized, and linked to related incidents, changes, and configuration items.
Explain how the problem manager decides to close a problem record and what evidence should be required before closure.
Your checkpoint
A completed prioritization matrix applied to five realistic problem scenarios, with a written justification for the ranking of each one.
Problem management processes and activities & Problem management concepts and principles
Explain the problem control phase, including root cause analysis steps, workaround design, and how findings are documented as known errors.
Describe error control activities, including how known errors are recorded, how workarounds are published, and how resolution is triggered when a permanent fix is available.
Outline how problem management interfaces with incident management, change enablement, and knowledge management at each phase boundary.
Summarize the concepts from Domain 1 without notes, then check your summary against your week 1 and week 2 materials and correct any gaps.
Your checkpoint
A process flow document covering identification, control, and error control with named interfaces to at least three other practices, plus a self-scored Domain 1 recall check.
Problem management roles, responsibilities and organizational structure
List the key roles involved in problem management (problem manager, problem owner, technical resolver groups, process owner) and describe the accountability of each.
Distinguish between accountable, responsible, consulted, and informed duties for problem management activities by building a responsibility assignment matrix.
Explain how problem management is organized in different operating models (centralized, federated, and embedded in DevOps or product teams) and state one advantage and one risk of each.
Describe the competencies and skills a problem manager needs, including facilitation, analysis, and stakeholder communication.
Your checkpoint
A responsibility assignment matrix covering at least six problem management activities and four roles, with a paragraph explaining how you would resolve a conflict between two roles.
Problem management tools, methods and techniques
Compare at least four root cause analysis techniques (five whys, Ishikawa or fishbone, fault tree analysis, Kepner-Tregoe problem analysis) and state when each is most appropriate.
Explain how problem management uses data from monitoring, event management, CMDB, and service desk tooling to identify trends and recurring incidents.
Describe how automation and AI-assisted analytics can support problem identification and known error matching, and name the risks of over-reliance on them.
Design a simple problem record template that captures symptoms, impact, workaround, root cause, known error status, and resolution actions.
Your checkpoint
A completed problem record template plus a worked example using one root cause analysis technique on a realistic multi-user outage scenario.
Problem management tools, methods and techniques & Problem management processes and activities
Apply a root cause analysis technique end to end to a scenario you invent, documenting the evidence trail and the conclusion reached.
Evaluate how knowledge management practices keep known error records accurate and how stale records should be reviewed and retired.
Explain how continual improvement and measurement feed back into problem management priorities and process effectiveness.
Review your Domain 2 process flow and update it with the tools and techniques you have learned.
Your checkpoint
A full worked case study of one problem from identification through error control, including the analysis technique used, the known error entry, and the closure evidence.
Problem management concepts and principles & Problem management processes and activities & Problem management roles, responsibilities and organizational structure & Problem management tools, methods and techniques
Consolidate all four domains into a single summary sheet of at most two pages that you could revise from in the final days.
Answer at least 60 practice questions across all domains under timed conditions and review every incorrect answer to identify the underlying concept gap.
Revisit your weakest two domains and rewrite the relevant sections of your summary sheet with corrected understanding.
Rehearse explaining problem management, its phases, roles, and techniques aloud in under ten minutes without notes.
Your checkpoint
A two-page consolidated summary sheet plus a logged practice test result with a written remediation note for each incorrect answer.
Milestones
Week 2: You can explain the three problem management phases and the problem-to-known-error lifecycle from memory, and your glossary and state diagram are complete.
Week 4: You can describe the full process flow from identification through error control and name the interfaces to at least three other practices without referring to notes.
Week 6: You can assign accountability for six problem management activities across four roles and justify the assignment, and you have applied at least one root cause analysis technique to a worked example.
Week 8: You score at least 80 percent on a timed 60-question practice set spanning all four domains and have a written remediation note for every incorrect answer.