OBLYTECH Logo
OBLYTECH Logo

Strategic IT Roadmap Development

Why Choose Oblytech for Strategic IT Roadmap Development?

IT service management teams can use a clear, dated roadmap to help decide which ServiceNow work gets funded first and which waits. Oblytech’s Strategic IT Roadmap Development service helps you connect your ServiceNow investments to your business objectives, so each funding decision can be checked against the result it was meant to produce.

black-man-trader-coach-and-screen-with-stock-mark-2023-11-27-05-19-35-utc

Our Strategic IT Roadmap Development Process

  • We begin by understanding your current IT landscape, challenges, and strategic objectives.
  • We’ll analyze your existing processes, identify pain points, and define key performance indicators (KPIs) for measuring success.
  • We’ll evaluate your current ServiceNow implementation (if applicable) and identify areas for improvement or expansion.
  • We’ll review ServiceNow capabilities relevant to your needs and identify features and modules to consider.
  • We’ll collaborate with you to develop an IT roadmap that outlines your ServiceNow goals, priorities, and implementation plan.
  • This roadmap is intended to guide alignment between your IT investments and your overall business strategy.
  • We’ll schedule periodic reviews to assess your progress, identify any challenges, and adjust the roadmap as needed.
  • Our goal is to help align your ServiceNow implementation with your evolving business needs and review the value it delivers.
  • We’ll help you develop a phased implementation plan that prioritizes key initiatives and minimizes disruption to your operations.
  • We’ll provide guidance on resource allocation, timeline estimation, and risk mitigation.

ServiceNow roadmaps that fail to change decisions

A roadmap is useful when it changes what gets funded, what gets started and what gets stopped. A ServiceNow roadmap can become a catalog of modules, features and aspirations rather than a set of decisions with owners and dates. Review whether it guides funding and work across departments. Strategic IT roadmap development is the consulting route for turning the platform’s possible futures into the handful of choices leadership actually has to make.

This page is written for the executive sponsor, the IT leader and the platform owner who must agree a direction, often over a planning cycle of a year or so. It describes what a roadmap has to decide, how dependencies set the order, and how the roadmap stays in use after the first workshop has finished.

Decisions a strategic roadmap must settle

Each item on a useful roadmap answers four questions: why it matters to the business, what must be true before it can start, who owns the outcome, and what happens if it is deferred. A roadmap that cannot answer those for each item is still a wish list. The table sets out the decision types a roadmap typically needs to settle, and the form of answer that makes each one usable.

Decision typeQuestion leadership must answerForm of a usable answer
Investment sequenceWhich two or three initiatives get capacity first?A ranked short list with the capacity each one assumes
Scope boundaryWhat is deliberately excluded from this cycle?A named list of exclusions, with the reason for each
OwnershipWho is accountable when two departments want the same platform capability?A single accountable owner per capability, and the forum where disputes go
RetirementWhich existing tools or processes will the platform replace, and when?A retirement date and the group that will confirm it
Readiness gateWhat evidence must exist before the next phase starts?Specific readiness criteria, not general statements of intent

In practice, strong roadmaps tend to be short on the first row and thorough on the last two. Teams often agree where to start. Agreement is harder on who owns a capability once it is live, and harder still on when an old system stops being supported.

Dependencies as the driver of roadmap order

Consider both leadership priorities and dependencies when ordering roadmap work. Review whether an analytics initiative has trustworthy data and whether a customer-facing portal has the knowledge it needs. Consider three kinds of dependencies. Data dependencies concern whether a source is reliable enough to build on. Process dependencies concern whether the business has agreed how work should flow. Capability dependencies concern whether the platform has the modules, integrations or skills the initiative needs.

Mapping those dependencies is one of the more useful pieces of roadmap work, because it exposes items that look independent but share a foundation. A single data ownership gap can delay several initiatives that each seemed to be progressing well. Seeing that early lets leadership fund the foundation first.

Deliberate exclusions from the roadmap

A roadmap that tries to include all requests can be hard for a team to deliver. Exclusion is a decision in its own right, and it should be recorded with a reason. Typical exclusions are capabilities the platform does not need yet, requests that duplicate work already in flight, and ideas that depend on a decision leadership has not made. Recording the exclusions protects the roadmap from being reopened every time a new request arrives, and it gives the sponsor a clear answer when a department asks why its item is not on the list.

Exclusion also protects the team. Without it, the platform function ends up absorbing request after request, and the quality of deliveries tends to fall. A short, honest exclusion list is a sign that the roadmap is being used.

Workshop output as a living plan

The first workshop produces a draft. The roadmap becomes a plan only when someone owns it between reviews. A practical arrangement is a standing review at a fixed interval, where the sponsor checks whether the sequence still matches the business, whether any dependency has resolved or slipped, and whether any exclusion should be reopened. The review should be short and should end with decisions, not with a restatement of the roadmap.

Keep the roadmap in the form people will read. A one-page view for leadership, a dependency map for the platform owner and a detailed plan for the delivery leads will serve better than a single long document that none of them finishes.

Platform limits a roadmap must state

A roadmap that describes what the platform will become, without its limits, is incomplete. Assess the release and existing customization when identifying limits for your ServiceNow roadmap. A credible roadmap states those limits next to the initiatives they constrain. A line such as “the approval redesign cannot start until the group structure is agreed” is more useful to leadership than a larger budget request, because it tells them what decision opens the work.

Limits also decide how ambitious each phase can be. Two initiatives that look equally valuable may differ sharply in how much of the platform they touch. The one that touches fewer shared components, and that can be tested in isolation, is usually the safer first phase, even when its business value is more modest. Putting that reasoning in the roadmap gives the sponsor a defensible basis for the order, and it keeps the conversation focused on evidence rather than on who argues most loudly.

It is worth stating the platform’s release position openly as well. Check whether a proposed upgrade would affect requested features or planned customization, and record any findings that change the roadmap sequence.

Leadership questions to test a roadmap

Before a roadmap goes to leadership, it helps to run it against the questions a skeptical executive will ask. Those questions are predictable, and a roadmap that cannot answer them is not yet ready. Typical examples include: what happens if this initiative slips by a quarter, which other initiative does it block, who will be using the result and whether they were asked, what the platform will stop doing once this is live, and how the team will know it worked. Each answer should be short, and each should point to a named person or a dated decision.

The exercise also reveals initiatives that exist only because someone once suggested them. If the sponsor cannot name the people who will use the outcome, the initiative is probably a candidate for exclusion, and the roadmap is stronger for removing it.

Roadmap change control over a planning cycle

Roadmaps drift in predictable ways. Items are added because a senior person asked, dates move without anyone recording why, and dependencies resolve without the plan being updated. A simple discipline prevents much of this. Record changes to the roadmap with their reasons and approvers where you can, and review items that slip rather than moving them silently. Over time that record becomes the most useful part of the roadmap, because it shows which kinds of commitment the organization tends to keep and which it tends to abandon.

The record also helps with the next planning round. When the same initiative has been deferred three times, the reason for each deferral tells leadership whether the cause is capacity, dependency or lost interest. Each of those calls for a different response, and only one of them is solved by adding a date to a plan.

How far ahead should a ServiceNow roadmap look?

Detail should be firm for the next planning cycle and provisional beyond it. Anything further out is a direction, not a plan, and it should be presented that way so that nobody treats a provisional item as a commitment.

Who should own the roadmap after the consultants leave?

A named executive sponsor, supported by a platform owner who can translate decisions into work. When ownership is split between two people with no shared review, the result can be two roadmaps.

Does a roadmap need a budget attached?

It needs an estimate of the capacity each initiative assumes, which can then be converted into cost by the finance process your organization already uses. A roadmap with no capacity view tends to promise more than the team can deliver.

What if leadership wants every item delivered in the first phase?

Show the dependencies and the capacity they require, then ask which items leadership is willing to defer. The question forces a real decision, which is the point of the exercise.

Inputs for a roadmap conversation

The first conversation is more productive when you bring the current list of requests, the names of the sponsors behind the largest ones, and a note on the platform modules already in use. Add any existing strategy document and the budget cycle dates, because the roadmap has to fit the moment leadership actually decides. How many departments must be consulted, and how much current-state analysis that requires, sets the size of the roadmap work. Both are worth establishing early.

Three related pages show how a roadmap connects to the rest of the platform. The roadmap prioritization page covers ServiceNow strategic roadmap prioritization, and the value realization operating model page covers value realization and the operating model for ServiceNow investment. The strategic portfolio and demand intake page covers strategic portfolio management and demand intake in ServiceNow. For the wider set of routes, the ServiceNow consulting overview is the starting point for the other ServiceNow consulting routes. When you are ready to set the direction, discuss your platform roadmap with the team.

How to plan a ServiceNow roadmap in six working steps

Consider this sequence for ServiceNow roadmap planning: record where the instance stands today, collect requests in one list, group the requests by the platform foundation they need, size them against available capacity, commit to one planning cycle, and then set the review rhythm. Adapt the order to your planning needs.

  1. Record the starting position. Note which modules are live, which release the instance runs on, how much customization sits on top, and who currently administers it. Read-only facts, not opinions. A ServiceNow assessment can help document this starting position.
  2. Put requests in one list. Requests hidden in email, team backlogs and sponsor conversations cannot be ranked against each other. One list, with a named requester for each line, is enough.
  3. Group by foundation, not by department. Several requests often rest on the same thing, such as agreed groups, clean reference data or a settled approval path. Treat that shared piece as its own roadmap item.
  4. Size against capacity. Count the people who can actually build, test and support work, then fit items to that number. Test and support capacity can be the tighter limit, so count it alongside build effort.
  5. Commit to one cycle. Fix the next cycle, mark everything beyond it as direction only, and name the sponsor who signs off.
  6. Set the review rhythm. Decide the interval, the attendees and the decisions the review may make before the first review happens.

Upgrades deserve their own line in the plan. If an upgrade is planned, consider reserving capacity early and see performance tuning and upgrades when you decide how much. Settle who owns the plan through your platform operating model, and check any release-specific behavior on your own instance.

Roadmap or backlog: which one do you need?

QuestionBacklog answers itRoadmap answers it
Time horizonThe next few weeks of workThe next planning cycle and the direction beyond it
Main readerDelivery teamSponsor and platform owner
What changes itNew tickets and fixesA funding or ownership decision

If your team only has a backlog, you have a delivery tool but no direction. If it only has a roadmap, nothing tells the builders what to start on Monday. You usually need both, with the roadmap feeding the backlog.

How to measure whether each roadmap item is paying off

Give each roadmap item one clear measure of success before it is funded. The measure should name the outcome, the current baseline and the date when the team will read the result. A baseline can help assess whether an item worked, so consider capturing it early.

Use two kinds of measure. Leading indicators show early whether people are changing how they work, such as the share of requests that arrive through the new path. Lagging indicators show the business result the item was meant to produce, such as the time taken to resolve one request type. Leading measures let the sponsor reorder the roadmap in the first months. Lagging measures decide whether an item earns a second phase.

Write each measure as a question the review can answer. Has the wait between approval and the start of work shortened for the teams using the new route? Phrases such as improved efficiency cannot be checked at a review, and they tend to be claimed by whichever item finishes first.

Agree where the numbers come from before build work starts. If a figure depends on a field that is filled in inconsistently, the baseline is unreliable and the trend will mislead. A short check of the data behind each measure shows whether the platform can report the number at all. A measure that cannot be reported usually moves its item behind the data work that makes it reportable, and that change to the order is often the most useful result of the exercise.

  • Name the outcome in plain words and the team that owns it.
  • Record the baseline and the report or query that produces it.
  • Set one leading and one lagging indicator, each with a review date.
  • Reshape or stop the item if neither measure moves by the agreed review.

Review the measures in the same session as the dependency map. An item whose measure has stalled often has a dependency that has slipped, and the two views together show which decision comes next. For how measures sit in day-to-day operation, see project portfolio governance. To baseline the platform before setting targets, see ServiceNow health checks and audits.

ServiceNow guides on this topic

Guides from the Oblytech ServiceNow library that explain the practice behind this page.

More in this section