By the end
What you'll build
- Design a catalogue entity model covering systems, components, APIs, resources and ownership
- Set up automatic registration and drift detection so catalogue data maintains itself
- Publish a software template that produces a service already meeting baseline standards
- Integrate technical documentation and runbooks so they stay linked to the services they describe
- Design a service scorecard that teams accept as fair and act on
- Measure portal usage in a way that distinguishes real use from incidental page views
Curriculum
What's inside
7 modules · 35 lessons
- 01
Why a service catalogue
5 lessons- The questions a service catalogue must answer during an incident
- Discovery, ownership and dependency in one place
- Portals compared with wikis and spreadsheets
- Failure modes of an unloved catalogue
- What the catalogue is formatch pairs
- 02
The entity model
5 lessons- Modelling systems, components, APIs and resources without over-modelling
- Ownership, groups and the link to on-call
- Relationships and dependency graphs
- Lifecycle and maturity fields that stay meaningful
- Naming the model correctlyfill blank
- 03
Keeping the catalogue true
5 lessons- Automatic registration: catalogue data that maintains itself
- Discovery from repositories and running workloads
- Reconciliation and drift detection
- Data quality scoring and nudges rather than mandates
- Moving off the spreadsheetsequence order
- 04
Templates and scaffolding
5 lessons- Publishing a template that produces a production-ready service
- Parameterising a template safely
- Template versioning and re-templating existing services
- Guarding templates with automated policy checks
- One more option, pleasescenario
- 05
Documentation in the portal
5 lessons- Docs-as-code alongside the catalogue
- Documentation ownership and freshness signals
- Search that finds the right page
- Runbooks linked to the services they cover
- Reading the docs signalsmatch pairs
- 06
Scorecards and adoption
5 lessons- Designing a service scorecard that changes behaviour
- Choosing checks teams accept as fair
- Publishing results without shaming teams
- Measuring portal adoption honestly
- A scorecard people believefill blank
- 07
Practice and check
5 lessons- Catalogue entities and what goes wrongmatch pairs
- Twenty minutes with a service you have never seensequence order
- What makes a portal worth openingfill blank
- Making the portal truescenario
- Course quizquiz
The shape of it
How this course works
Short lessons
35 lessons across 7 modules, each small enough to finish in one sitting.
Practice as you go
Every lesson ends with a small space for what you noticed — the doing is the learning.
Progress you can see
Your progress is saved lesson by lesson, ready whenever you come back.
Ready when you are.
Make an account and this course opens up — your progress is saved from the very first lesson.