A completely impractical yet thought-provoking guide to the holidays
Easter is here. Chocolate eggs are hiding in gardens, families gather around decorated tables, and Easter bunnies deliver treats with impressive levels of service. But have you ever stopped and thought: what's really missing?
We have. And the answer is obvious: a proper framework.
What if Easter was governed by ITIL?
Incident Management – when the egg is not found
No Easter celebration goes without a hitch. A hidden egg that is not found within a reasonable time immediately triggers a P2 incident. Affected parties are escalated: parent, uncle with an unusually good grasp of the garden's topography, and in extreme cases – the dog. A post-incident report is documented and archived for next year. Root cause: eggs were placed behind the pot that no one has touched since 2019.
Problem Management – why are there always too few eggs?
Year after year, the same incident is reported: too few eggs, too many applicants. It is time to stop handling this reactively. A problem record is opened, root cause analysis is carried out using the 5-why method:
- Why were not all the eggs found? → Because one was hidden behind the pot no one touches
- Why are eggs hidden where no one looks? → Because the person hiding does not document their choices.
- Why are the hiding places not documented? → There is no process.
- Why is there no process? → Change Management has not prioritized this.
- Why has CAB not prioritized it? → There is no owner.
Known error is registered: "Egg behind the pot by the patio door cannot be found without a clue." Workaround is documented. Permanent solution: mapping all possible hiding places is classified as an improvement initiative and added to the backlog for next year.
Change Management – switching from vanilla to salted licorice
No flavor changes to this year's Easter candy will be made without an approved RFC (Request for Chocolate Change). Is it a normal change or an emergency change? It all depends on whether Grandma has already bought licorice eggs. All affected stakeholders will be informed with at least seven days' notice. The CAB meeting will take place on the Thursday before Maundy Thursday.
Service Level Agreement – Easter Bunny Service
The Easter Bunny's delivery obligations are regulated in an SLA with clear KPIs. Delivery time: 100% of eggs must be hidden by 08:00 on Easter Day. Availability: 99.9% (exception: heavy snow, see Appendix C). Customer satisfaction is measured via NPS survey, sent by 10:00 at the latest. Escalation path in case of SLA violation: directly to Problem Management.
Knowledge Management – Grandma's egg-shaped Mazarin recipe
Critical knowledge that has existed for 40 years as "oral tradition" is now classified as a Single Point of Failure. The recipe should be immediately documented in the CMDB, versioned, and made available in a searchable knowledge base. Owner appointed. Review cycle: every two years, or at generational change.
Continual Improvement – next Easter will be better
Every Easter ends with a retrospective. What went well? What can be improved? The number of eggs hidden against the number of eggs found is measured as a KPI. This year's gap analysis showed that the kitchen was significantly underrepresented as a search zone. An improvement initiative is being initiated for Q1 next year.
Yes, it might be a bit overkill to ITIL-ify Easter
But the fact remains: the best services – whether it's IT support or egg hunt logistics – are built on clear processes, clear accountability, and continuous improvement.
We know that.
Happy Easter from us at Easit!
May your SLAs be met, your incidents be few, and your chocolate eggs be well hidden – but not too well hidden.
→ Would you like to see how Easit GO supports your ITSM processes? We'd be happy to tell you more.

Henrik Traveler
Commercial Product Manager
henrik.resare@easit.com
+46 70 249 36 06