When missing ITIL practices matter for a mid-market team, and when they do not

Two platforms in this guide that document AI agents, simple configuration and other departments strongly, monday service and Zendesk, document little or no problem management, change management or CMDB on the pages we read. Whether that matters depends on your team, and this post is meant to help with that decision.

What exactly is missing?

On the pages we read on 27 September and 11 October 2026, monday service documents request intake, incident handling, SLA monitoring, knowledge and AI agents, but its product, pricing, IT and IT operations pages do not document problem management, an IT asset management module or a CMDB. A monday.com blog from 27 June 2026 describes change approvals built from configurable boards, a no-code workflow builder and automations, linked to incidents and assets; that is a build-it-yourself approach rather than a named change module. Zendesk's Employee Service pricing lists IT asset management from Suite Growth, but not change management, problem management or a CMDB.

At the other end, ServiceNow ITSM documents incident, change, problem and request management on one platform with a single CMDB, with change and problem management in its ITSM Advanced package. [ServiceNow] Ivanti lists 14 ITIL 4-certified practices, ManageEngine states 14 ITIL-certified practices for ServiceDesk Plus, and Freshworks states certification across 14 ITIL practices for Freshservice.

When do the gaps matter now?

They matter when the practices solve problems you have today:

• Changes cause outages. If a meaningful share of your incidents follows a change, you need change enablement with risk assessment, approvals, a calendar and links to what each change affects.
• The same incidents keep coming back. Problem management turns repeated firefighting into root cause fixes.
• You face audits. Many security and compliance frameworks expect evidence of change control. A request-type workaround may not satisfy an auditor.
• Your estate is complex. If nobody can say what a server change will affect, configuration data with relationships pays for itself.
• Your industry expects ITIL alignment. Some customers and regulators ask for it directly.

When can they wait?

They can wait when your main problems are elsewhere:

• Most of your volume is requests: access, equipment, onboarding and how-to questions.
• Your changes are few, low-risk and handled by a small team that talks daily.
• Your biggest gain would come from AI triage, self-service and bringing HR or facilities onto the same intake.
• You have a plan, and a date, for adding change and configuration management, either on the same platform as the vendor adds capability or through a later move.

What ITIL actually asks of you

ITIL 4 is guidance, not a checklist. Its guiding principles include starting where you are and progressing iteratively. A mid-market team that runs incidents, requests, knowledge and service levels well is practising good service management, even before change and problem management are formalised. PeopleCert's newer ITIL (Version 5), which it describes as AI-native by design, does not change that basic point.

How should you test the trade-off?

Use the ITSM fit finder. Answering that you need problem, change and formal control now, or a CMDB with relationships, makes those capabilities must-haves. Platforms that do not document them, including monday service and Zendesk on the pages we read, then move to the section for platforms missing a must-have, with the gap named. If you answer that incidents and requests are enough for now, they stay in the running and their strengths on AI agents and other departments count for more.

What should you ask a vendor with a gap?

Ask three things: whether the capability exists and was simply not on the pages we read; if it does not, whether it is on the roadmap with a date; and how current customers handle change records today. Get the answers in writing before you sign.

Where do the other platforms stand?

If change control and configuration data are firm requirements, the platforms that document both are Halo (formerly HaloITSM) in its single licence, Freshservice from Pro, Jira Service Management with change management on Premium and assets from Standard, SysAid on both plans with CMDB depth not documented, ServiceDesk Plus on Enterprise or through add-ons, and ServiceNow ITSM and Ivanti as part of their wider ITIL coverage. Each profile on this site shows which plan includes what, with a link to the vendor's pricing page and the date we read it.