Your ServiceNow Roadmap Starter-Pack: Get on the Right Road to Success

If you’re looking to implement ServiceNow at your organization, you probably already feel the pressure to ensure the rollout is a success, but how do you make that a reality?

Between convincing your stakeholders, building a strategic two-year roadmap, achieving quick wins that boost adoption momentum and captures early ROI, you may be wondering where to start.

But before you go full-on panic mode, understand that, like any big undertaking, it is a process. Remind yourself to go one step at a time and be thoughtful in your execution. The following four guidelines will help you to achieve success in your ServiceNow journey, from inception to expansion.

Get executive buy-in with a thoughtful ServiceNow vision

The first step to getting ServiceNow is building a business case that your stakeholders can’t say no to. So how do you do that?

Your sponsor, who is going to be making the final decision, will most likely be your COO, CIO, or CEO and they represent the functions of your business: IT, security, customer service, HR, etc. You need to think high-level. When you’re starting your pitch, don’t get over-excited about the technical processes and advancements; rather, focus on specific outcomes that matter to your stakeholders.

For example, defining a problem like your organization’s customer retention rate is down 10% over the last year and how ServiceNow can help fix that, addresses more critical business concerns, which your executive team will care most about.

In addition, the outcomes your promising should align with your executive goals and strategies whether that be productivity, modern experiences, improved employee or customer satisfaction, increased revenue, etc.

Now that you understand who you are speaking to, let’s break down how you go about your pitch in four easy steps:

1. Promote the ROI of ServiceNow. Get the research to back up your business case with ServiceNow’s commissioned Total Economic Impact Studies from Forrester research (available in our downloadable TEI Bundle). These studies include analyses of benefits, costs, and risks associated with your ServiceNow investment, plus case studies, which can help you back up your own argument for ServiceNow.
2. Address your current business problem(s) and do your homework. Talk to your employees and get the data you need to understand why ServiceNow matters for your organization. Be specific, if it’s something you can calculate, calculate it! Check out the ServiceNow ROI calculators for assistance. Never pick more than five (preferably three) business problems.
3. Define your vision for the platform. Aim to inspire and be confident! Nothing helps more than defining a vision. What can the organization gain by leveraging ServiceNow? Spell it out for your audience. Hint: Our CEO loves a good PowerPoint presentation.
4. Promise a small pilot or project to start. In three months, show a quick win (which we’ll talk about more). Always make sure it’s something you can realistically achieve. By showing you are willing to start small, prove as you go, manage expectations, and show results with some licensing, you will get that 6 months to focus on a bigger project.

Build a strategic roadmap to set yourself up for success

Once you’ve defined your vision, you need to build your roadmap. It’s a simple concept but makes the world of a difference when executed correctly – as we said in one of our most recent roadmap strategy webinars “just because it isn’t novel, doesn’t mean it’s not important.”

If you’re working with a ServiceNow partner, it’s helpful to sit down together and conceptualize a checklist of what you can accomplish: in the first month, next few quarters, and ultimately until you at least have a solid two-year (if not three-year) plan.

Building this roadmap will help you with improvements in the organization and, further, get you measurable results – which will stand as proof for your future ServiceNow budget planning.

So, in the end, your roadmap should be a value proposition for every item on your checklist and you should have them in an order of execution, weighing the impact and complexity of each. Here are three steps we suggest:

• Work with a checklist. If you couldn’t tell by now, we’re big fans of the lists and it’s the first rule for your roadmap. It gives your team a clear idea of what you are doing with ServiceNow (i.e. asset implementation, orchestration of IT changes, or Service Watch POV) and when you are doing it.
• Get everyone on the same page. Get adoption and buy in and let your employees and customers have a sense of ownership with the direction your platform is going.
• Prioritize and identify gaps. Once you’ve identified what your checklist is, you’ll want to measure the impact and complexity of each – figure out what can be a quick win versus what might be a longer-term project.

Find quick wins (and boost company morale around ServiceNow)

Looking at your Impact vs. Complexity map, your quick wins (30 to 45-day projects) will exist in that upper-left of the matrix. These will be unique to your company based on the level of effort it requires, its importance, and its overall urgency.

ServiceNow suggests to:

• Focus on capabilities that touch the most consumers to encourage adoption
• Implement incident and request management, service catalog service portal, and knowledge base early to build adoption momentum
• Important for the overall organization change management of your ServiceNow adoption, you need to advertise your wins and find your champions of the platform.

So how do you make this transition easier on your team so you can recognize the true ROI of the platform through more projects?

• Start with a vision. As mentioned early in this post, this is your first step. Before ground breaks, signs go up with pictures and models of what is being built. This helps people see the future by imagining what the world looks like when the old structures are taken down and the new one built up.
• Communicate early and often. Create regular reminders to prepare for the change, provide them with dates when their usual work paths will be interrupted and restored. Help people plan their work in advance and develop an alternative way of getting work done during the interruptions. This will make them more receptive to the changes down the road.
• Expect delays. Make sure you have local coaches to guide people through the expected bumps and hiccups of learning a new system to keep frustration to a minimum.
• Think globally, act locally. Articulate your vision at every level of the organization so you can inspire your staff to help drive the change.
• Monitor the change. Not only should you measure the technology side or a project but also the people – how are your training sessions going? Are you asking for feedback? To find what works best with your team, you need to be asking and watching.

With these tips in your back pocket, you’re ready to take on your first (or next) ServiceNow project.