Representative IT service management plan for a midsize company

A comparison of service management platforms for a growing internal IT team that needs better request, incident, change, asset, and knowledge workflows.

Scenario

Illustrative company: a 650-person technology-enabled business with 18 IT agents, requests split across email and chat, Jira and Confluence already in engineering, incomplete asset data, and a four-month service desk target.

Illustrative assumptions

The first phase covers employee IT support, incident, request, knowledge, service levels, and basic asset visibility.
Enterprise-wide HR and facilities workflows are later phases.
The team needs cloud delivery and identity integration.
Current ticket volume, service levels, and resolution data can be baselined.

Decision risks

The tool changes but email-based behavior remains
Asset data is treated as a one-time import
The platform scope expands before core IT support works
Automation is added without clear exception ownership

Options and validation work

Jira Service Management

Possible fit: A credible candidate when Jira, Confluence, development collaboration, and a unified Atlassian operating model are important.

Validate: Agent tier, portal design, asset scope, incident and change processes, integrations, guard controls, support, and total cost.

Freshservice

Possible fit: A credible candidate when rapid ITSM adoption, packaged workflows, and a simpler administration model matter.

Validate: Plan, asset needs, orchestration, AI add-ons, reporting, identity, regional requirements, implementation, and support.

ServiceNow ITSM

Possible fit: A credible candidate when enterprise workflow scale and a broader service management platform are justified.

Validate: Scope discipline, implementation partner, platform administration, integrations, licensing, timeline, and operating cost.

Illustrative direction

Illustrative direction only: pilot employee request, incident, major incident, knowledge, change, and asset scenarios with real agents. Do not select the broadest platform unless the organization funds the governance and administration needed to operate it.

Implementation workstreams

01Service catalog and baseline metrics
02Workflow and portal design
03Identity, chat, monitoring, and engineering integrations
04Asset data cleanup and ownership
05Agent pilot and knowledge migration
06Rollout, service reporting, and improvement backlog

Official sources used in this example

Capabilities, prices, and terms can change. Confirm the current vendor page and obtain a binding quote before a decision.

Questions about this example

Which ITSM processes should a midsize company implement first?

Start with request, incident, knowledge, service levels, major incident, and a controlled change process. Add advanced asset, problem, portfolio, and enterprise workflows when ownership and data are ready.

Should existing Jira use favor Jira Service Management?

It is a material integration and adoption factor, not proof of fit. The team still needs to test service workflows, portal experience, assets, reporting, controls, administration, and cost.

How should an ITSM pilot be measured?

Measure portal adoption, ticket deflection, response and resolution time, reopen rate, knowledge use, service-level performance, agent effort, and the quality of incident and change records.

When is ServiceNow too large for the requirement?

It may be excessive when the organization only needs a focused service desk and cannot fund platform governance, administration, process ownership, integration, and continuous improvement.

Build a plan around your actual requirements

Describe the challenge, constraints, current stack, budget, and timeline. PilotPlan researches the options and assembles a sourced implementation plan.

Start a plan