ITSM for Small Teams: A Lightweight Way to Start

Small teams often assume that IT service management belongs to large organisations with dedicated process staff. The assumption is half right. The tooling and the formal roles are usually too heavy for a small team. The underlying habits are not. A small team that runs a service for other people already handles requests, incidents, problems and changes. The only question is whether it does so deliberately.

Four habits to start with

• One front door. Pick a single place where requests are raised, publish it and route the rest into it. This ends the situation where requests arrive by chat, email and a tap on the shoulder, and half are lost.
• A written outage procedure. One page that says who decides it is an incident, who is on call, how severity is set, where the team coordinates and how users are told. Practise it once.
• A short review after any serious incident. Fifteen minutes, three questions: what happened, what made it worse, what will we change? Write the answers down and give each change an owner.
• A light change habit. A short description of the change, a second pair of eyes, a place on a shared calendar and a way back.

What to skip, for now

• A configuration management database. Maintaining one costs more than it returns until you have many interdependent systems.
• A change advisory board. Peer review and a shared calendar are enough until risk justifies more.
• Elaborate service catalogues. A list of your ten most common requests, each with a form, is a catalogue.
• Dozens of categories and priorities. Three priorities and a handful of categories are enough.
• Contractual SLAs with timers. Set internal targets first and learn what you can meet.

Choose tools that match the size

At small scale, the tool is a place to hold work. A shared workspace with forms that create tasks, an inbox for triage, a rota for on call and a way to run an incident covers most needs. Atlas provides these: forms and email-to-task for intake, inbox triage, automation rules, incident management with on-call schedules and escalation, incident reviews with known causes, and Release Management for software changes. Incident Management is included from the Team plan. Atlas is not a full ITSM suite and has no configuration database, service catalogue or request SLA timers. See the ITSM tool requirements checklist to decide.

When to buy a dedicated suite

• Request volume is high enough that you need automated fulfilment and timers.
• Contracts require formal SLA reporting with pauses and breach evidence.
• You must track many assets and their relationships to assess the impact of changes.
• An auditor requires a particular formal change process.
• Several teams need to share one service desk with separate queues and permissions.