The service lead's job: services, catalogue and the desk
A restaurant has a menu. You do not walk into the kitchen and shout what you want; you pick from the menu, the waiter writes it down, and the kitchen knows what to make. An IT service desk needs a menu too, so people know what they can ask for and how.
- Before this course: Systems Administration: users, networks and updates (course 7.10.3). There you looked after machines and accounts. A service lead looks after the service: what users can get, how fast, and how well.
- IT service management means running IT as services that give users value, not as a pile of devices. The best-known framework is ITIL. PeopleCert's ITIL 4 Foundation page lists what the foundation level covers: service management concepts, the service value system, the four dimensions of service management, the seven guiding principles, the service value chain, ITIL practices, continual improvement, service level agreements, and key metrics and KPIs.
- Service desk: one front door (one email, portal or phone number) for all IT requests and problems. Users should never have to guess who to ask.
- Two kinds of tickets: an incident is something broken ("I cannot print"); a service request is something new or standard ("I need a laptop for a new starter"). They follow different paths, so count them separately.
- Service catalogue: the "menu". Each entry lists the service, who can ask for it, how to ask, what it costs the business (if anything), the target time, and the owner.
| Service | Who can ask | How | Target (example) | Owner |
|---|---|---|---|---|
| New starter setup (account, laptop, email) | Managers | Portal form, 5 working days ahead | Ready on the start day | Service desk |
| Password and sign-in help | Everyone | Portal, chat or phone | Same working day | Service desk |
| Shared folder access | Everyone, with manager approval | Portal form | 2 working days | Systems admin |
- Roles on a small desk: service lead (owns the process and the numbers), tier 1 (first contact, common fixes), tier 2 (deeper fixes, systems admin work), knowledge owner (keeps articles current) and change approver. One person may hold several roles; write down who.
- Pick a made-up organization for this course, for example a 60-person clinic group with three sites.
- List the 8 to 10 things people ask IT for most often.
- Sort them into incidents and service requests.
- Write a catalogue table for the service requests: who can ask, how, target, owner.
- Write the one front door: the single address or portal users should use, and what happens to requests sent anywhere else.
- Write the roles and the names (made-up) for each.
- Check: a new employee could read your catalogue and know exactly how to ask for a laptop and who will help.
Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.
Read the video script
[Host] "A good restaurant has a menu. A good IT desk has one too."
[Screen: a service catalogue with three rows] "The service catalogue lists what people can ask for, how, how fast, and who owns it."
[Text on screen: Incident = broken. Request = something new.] "Broken things are incidents. New things are requests. Count them separately."
[Host] "And give everyone one front door. Nobody should have to guess who to ask."
Write the first version of your service catalogue (at least five services) and a one-paragraph "how to get IT help" note for staff, with the single front door.
ClaudeStuck? Copy a ready-made prompt for Claude
Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.
For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.
I'm learning "IT Service Lead: service management and certification paths" on The Future Market. Lesson 1: "The service lead's job: services, catalogue and the desk".
What the lesson teaches:
- Before this course: Systems Administration: users, networks and updates (course 7.10.3). There you looked after machines and accounts. A service lead looks after the service: what users can get, how fast, and how well.
- IT service management means running IT as services that give users value, not as a pile of devices. The best-known framework is ITIL. PeopleCert's ITIL 4 Foundation page lists what the foundation level covers: service management concepts, the service value system, the four dimensions of service management, the seven guiding principles, the service value chain, ITIL practices, continual improvement, service level agreements, and key metrics and KPIs.
- Service desk: one front door (one email, portal or phone number) for all IT requests and problems. Users should never have to guess who to ask.
- Two kinds of tickets: an incident is something broken ("I cannot print"); a service request is something new or standard ("I need a laptop for a new starter"). They follow different paths, so count them separately.
- Service catalogue: the "menu". Each entry lists the service, who can ask for it, how to ask, what it costs the business (if anything), the target time, and the owner.
- Service - Who can ask - How - Target (example) - Owner
- New starter setup (account, laptop, email) - Managers - Portal form, 5 working days ahead - Ready on the start day - Service desk
The exercise I'm working on:
Write the first version of your service catalogue (at least five services) and a one-paragraph "how to get IT help" note for staff, with the single front door.
I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.I'm a parent helping my child (about 8 years old) with a lesson called "The service lead's job: services, catalogue and the desk" from the course "IT Service Lead: service management and certification paths". Here's what the lesson says: A restaurant has a menu. You do not walk into the kitchen and shout what you want; you pick from the menu, the waiter writes it down, and the kitchen knows what to make. An IT service desk needs a menu too, so people know what they can ask for and how. The activity: Write the first version of your service catalogue (at least five services) and a one-paragraph "how to get IT help" note for staff, with the single front door. Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words. Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Sources
- PeopleCert, ITIL 4 Foundation: www.peoplecert.org/browse-certifications/it-governance-and-service-man
Service levels: SLAs, targets and the numbers that matter
This lesson is part of full access: every course and every level for one payment.
Major incidents, problems and changes
This lesson is part of full access: every course and every level for one payment.
A knowledge base people actually use
This lesson is part of full access: every course and every level for one payment.
Ticket records: privacy, access and how long to keep them
This lesson is part of full access: every course and every level for one payment.
Certification routes for you and your team
This lesson is part of full access: every course and every level for one payment.
Training the team and reviewing ticket quality
This lesson is part of full access: every course and every level for one payment.
Final project
This lesson is part of full access: every course and every level for one payment.
Quiz
What is the difference between an incident and a service request?
An incident is something broken; a service request is something new or standard that a user asks for.
What is a service catalogue?
The desk's "menu": each service, who can ask, how, the target time and the owner.
What is the difference between an SLI, an SLO and an SLA?
An SLI measures the service, an SLO is the target for that measure, and an SLA is the agreement with users that includes what happens if targets are missed.
Why set an internal target tighter than the SLA?
To keep a safety margin, so problems are fixed before users notice a missed promise.
188 of 200 tickets met the target. What percentage is that?
94%.
Name the four roles in a major incident.
Incident commander, operations, communications and planning.
What makes a review "blameless"?
It looks for causes in systems and processes, not for a person to blame, and ends with actions, owners and dates.
What is the difference between an incident and a problem?
An incident is one disruption to fix fast; a problem is the underlying cause behind one or more incidents.
What should a technician do before solving a ticket in a knowledge-centred desk?
Search the knowledge base, link the article used, and fix or create an article before closing.
Why should ticket records have a retention schedule?
Some records must be kept for a set time by law, and keeping personal data longer than needed can break privacy rules.
Why check the current exam version before studying for a certification?
Exams are updated (for example, a new Security+ version), so you must study for the version you will take.
What is reverse shadowing?
The new team member does the work while the coach watches and gives feedback.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.