Home labs & practical projects

Improve a recurring incident through a service value lens

A project to do with your own tools, with guidance on what to create and capture.

Design project Suggested time: 90–120 minutesNo hardware required for the design

What you could create

A support team closes the same printing incident every week but has not addressed the recurring cause or user impact.

Example evidence format

Project evidence map (example)

Service workflow and recurring-issue analysisScope and inputs

Continual improvement proposalDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Service workflow and recurring-issue analysis	Show the inputs, scope and decisions behind this record. The improvement addresses an observed cause or constraint.
Continual improvement proposal	Include the evidence supporting your conclusion. The measure goes beyond counting closed tickets.

What you'll need

Document, spreadsheet or diagram tool

Create six fictional incident records with resolution times, affected users and repeated symptoms. Define the service outcome that matters to the users.

Project record

Keep the working files for service workflow and recurring-issue analysis and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.

The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.

Suggested milestones

1
Plan and investigate
Map the current flow from report to restored service.
2
Develop your approach
Separate immediate restoration from problem investigation and improvement.
3
Verify and explain
Propose one small change with an owner and a measure of user impact.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
Service workflow and recurring-issue analysis
Show the inputs, scope and decisions behind this record. The improvement addresses an observed cause or constraint.
2
Continual improvement proposal
Include the evidence supporting your conclusion. The measure goes beyond counting closed tickets.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your service workflow and recurring-issue analysis needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Create six fictional incident records with resolution times, affected users and repeated symptoms. Define the service outcome that matters to the users.

What a good result looks like

The improvement addresses an observed cause or constraint.
The measure goes beyond counting closed tickets.

Finish the project

Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.