Skip to content
ITSM ComparedITSM Compared

LEARN · COURSE

ITSM groundwork: rolling out ITSM without an admin team

IN SHORT

Ten short lessons in three tracks, written for IT teams of roughly 10 to 100 agents. They cover what to switch on first, how to build intake, automation and approvals without specialists, and how to extend the desk to other departments and add change and configuration management.

Plan the move: what should you decide before you buy?

  1. Lesson 1 · 3 min read

    What modernising ITSM means for a mid-market IT team

    Modernising ITSM for a team of 10 to 100 agents means getting more of ITIL's value with less administration: faster launch, settings instead of scripts, AI help on intake and a platform other departments can share.

  2. Lesson 2 · 3 min read

    Who runs the tool after go-live? Estimating admin load

    Admin load is the work of keeping a platform current after launch: new forms, routing changes, automations, plan upgrades. Estimate it before you buy by listing the changes you make in a normal month.

  3. Lesson 3 · 3 min read

    Scoping your first release: which practices to switch on first

    Launch with incidents, requests, a short catalog and knowledge. Add SLAs once you have a baseline, then change and problem management when volume and risk justify them.

Build it without specialists: how do you set it up yourselves?

  1. Lesson 4 · 3 min read

    Writing your first ten catalog items

    Pick your first ten catalog items from last quarter's ticket volume, write each form around what the person fulfilling it needs, and give every item an owner and an approval rule.

  2. Lesson 5 · 3 min read

    Rules, AI triage and AI agents: what each automates

    Rules automate what you can predict, AI triage sorts what arrives, and AI agents try to resolve routine requests outright. Most teams need all three, introduced in that order.

  3. Lesson 6 · 2 min read

    Approvals and routing without code

    Approvals and routing are the configuration a desk changes most often. Keep them simple, owned by IT, and editable through settings rather than scripts.

Extend and govern: how do you grow it safely?

  1. Lesson 7 · 3 min read

    Taking the desk to HR, facilities and finance

    Extending the desk to other departments works best after IT intake is stable. Give each team its own catalog, queue and privacy rules on the same platform, and check how the vendor packages it and what each extra team costs.

  2. Lesson 8 · 3 min read

    Change enablement for a team without a change board

    Most changes in a mid-market team are routine. Pre-approve standard changes, give normal changes one reviewer, and keep a record. Check which plan includes change management before relying on it.

  3. Lesson 9 · 3 min read

    A CMDB you can keep current

    A CMDB is only useful if it is current. Start with your most critical services, let discovery fill what it can, and keep the rest small enough to maintain by hand.

  4. Lesson 10 · 3 min read

    Cutting over from your current tool

    Bring open tickets, knowledge and catalog design across; leave most history in a read-only archive. Switch on a quiet day, freeze new automations for two weeks and review weekly for the first month.

Platform facts in these lessons come from vendor pages read on 27 September and 11 October 2026. The fit finder and the fact grid apply them to your own team.

Questions readers ask

Who is this course for?

IT leads and service desk managers in companies with roughly 10 to 100 IT agents who are choosing or rolling out an ITSM platform without a dedicated administrator.

Do I need ITIL certification to follow it?

No. The lessons explain the ITIL terms they use and link to the ITSM terms page.