Convince Your Boss

How to Get Executive Buy-In for Project Management Software


You’ve found the perfect project management tool. Now you just need the boss to say yes. Learn how to build a compelling business case that leaves them with one question: Where do I sign?


Intro

Getting to Yes

In many organizations, the role of project management software is often misunderstood.

Some executives may see project management tools as an added, unnecessary cost. But, in a world where companies waste $122 million for every $1 billion invested due to poor project performance, that couldn’t be further from the truth.

In fact, a study by PwC found that “use of commercially available PM software drives higher levels of portfolio performance and greater satisfaction with an organization’s PM practices.”

Yet, many teams still find themselves using outdated or inadequate tools. As a result, project managers and their teams waste time and resources on tasks that can be simplified, streamlined, or even eliminated if the right tool was in place.

So, how do you convince your executive team that you need a modern project management solution? How do you overcome common objections around budget, timing, and implementation?

By demonstrating how a new project management tool will help executives meet their goals, make a positive impact on the business, and, ultimately, boost the bottom line.

In this guide, we’ll walk through how to do just that. We’ve also created a bundle of useful tools to help you through the process (click here to download them all now). By the end, you’ll have built a solid business case for gaining executive buy-in for a new project management tool.

Free Resource Kit

Acquire Your Business Case Toolkit

Use these six resources to build a compelling business case for a new project management tool.

Get the Resource Kit

Chapter One

A Successful Pitch Requires a Change in Mindset

Before we go any further, let’s make one thing clear: this is not about you.

When you’re asking your company to invest in new technology, it’s not about the ways a new tool will save time and make your life easier. It’s not about the hours you spend searching for attachments in email threads. Nor is it about how you had to stay late every night this week because you’re overscheduled.

Gaining approval for a new project management tool isn’t about you at all. Gaining buy-in will require a shift in mindset. It’s time to go bigger. Start thinking about your boss. Your boss’s boss. The business as a whole.

This is about rising to the top of management’s priorities and the land of ROI, stack rank, and Internal Rate of Return.

It’s about how your current tool prevents your team from running efficiently. How it steals money from the bottom line. How every minute spent digging through emails is a minute of productivity lost.

When you shift your focus, building a business case will be become much easier and effective. Alright, let’s do this.

Determine who has the power to approve or deny.

First, determine who will need to approve this before you can move forward. Do you need to convince just your manager? Or do you need to take this to upper management? Do other departments (e.g., IT, accounting) have a seat at the approval table, as well?

Next, make a list of your stakeholders—the people who may influence (but not necessarily vote yes or no) the decision to adopt your proposal. Start by listing your natural supporters: the managers and teams who are most likely to benefit from a new tool.

You also need to determine who could be a stumbling block. How do finance, purchasing, and IT decide to purchase and support new software packages? What are their criteria? Do your homework and understand their concerns and motivations before you meet with them. Then, help them see how the efficiency you seek sits right at the top of their agenda.

Align with the priorities of the key decision makers.

Once you’ve identified your stakeholders, put your pitch aside for a moment. Pretend you’ve Vulcan mind-melded with the people you are pitching to. You can now experience the world from their perspectives.

What do they care about? What keeps them up at night? How many unsolicited pitches do they see every day? What interests them? What bores them? What concerns them? Consider your stakeholders’ personalities and worldviews, and keep these in mind as you develop your case.

Before you walk into that pitch meeting, you must be able to answer the question:

“How will this new project management tool help my stakeholders achieve their goals?”

Define your supporters and skeptics.

It’s likely that some stakeholders will immediately be onboard, asking, “When can we start?” Others might be much more hesitant. They’ll have questions. And that’s okay because you’ll be prepared to answer them.

When proposing a new tool, stakeholders are likely to fall into three camps: the supporters, the neutral, and the healthy skeptics. The key is to try to see things from their perspective, anticipate their concerns and questions, and then formulate talking points that will appeal to their wants and needs.

Likely Supporters

  • Your Boss. Is your manager the only decision-maker? If so, you can proceed to Chapter 2. If not, partner with your manager to schedule a meeting with the decision-makers you outlined earlier and formulate a gameplan for gaining approval.
  • Marketing. If you can demonstrate how this new tool will improve customer satisfaction, you’ll have a trusted ally.
  • Sales. The magic words any sales team wants to hear are “improved accuracy of our delivery schedules.”
  • Product Development. Fewer missed deadlines, reductions in risk and randomness, more accurate timelines…the list of benefits goes on and on.

Neutral

Executive Management. Initially, this group may seem disinterested. If appropriate, you may tease the benefits in the form of a question. Ask them, “Would you like to know the status of every project without having to ask for a report? What if you could be one-click away from current information on every project in the company?” They’re going to be excited. They’ll probably say yes. So be ready to show them a dashboard designed for their most common requests.

Remember, you all work for the same company. Nobody on this list is your “opponent.”

Healthy Skeptics

(Remember, you all work for the same company. Nobody on this list is your “opponent.” The questions they ask are legitimate. Your responsibility is to get them the information they request.)

  • Purchasing. It’s their job to question proposals. Purchasing is responsible for getting the most out of what the company already owns. For best results, approach this team with a list of business needs that are not being met with the tool your company uses today. (You’ll learn how to assemble this list in Chapter 2.)
  • Finance. Take a similar approach here. Share why the software you currently license cannot create the efficiency that your new tool brings to the equation.
  • IT. It’s their job to keep things running securely and efficiently. They will ask questions about “footprint”, rollout costs, security, “attack surface areas,” and international standards. Prepare yourself by reviewing the tool’s security policy. Check out LiquidPlanner’s Security Overview for an example.

Find an influential ally.

While this step is not necessary, it may lend extra credibility to your proposal. (“Well, if Allison from accounting thinks this is a good idea, I’m in.”)

To find your ally, look for another department in your company that would benefit from the tool. For example, a project management tool that also tracks billable hours and costs would be helpful for the accounting team. An entire engineering or product design team could use the tool as a bug-tracking system.

Find someone with different job functionalities than you. For example, if you’re the project manager for the IT team, look for a non-PM ally from the engineering team who would be open to vouching for your request.

While it’s not necessary that your ally attend the pitch meeting, he or she can help by endorsing your choice. Ask how this tool would benefit your ally’s team and include the answers in your pitch. You can also ask for advice on best practices for approaching key decision makers. Find out what has helped or hindered approvals in the past.


Chapter Two

Three Methods for Demonstrating the Value of a New Solution

Building a business case requires connecting your proposal to larger business objectives.

You’ve named your key stakeholders. You’ve thought about their needs. Now it’s time to demonstrate how your proposal will help meet their goals and the business’s objectives.

To do this effectively, you must justify the costs and illustrate the potential benefits. Again, this isn’t about you and your team. Telling your stakeholders how much easier your life would be won’t cut it.

Instead, focus on framing your investment request around key business objectives, like improving customer satisfaction, moving products to market faster, and increasing efficiencies that result in increased revenue and lowered costs.

In this chapter, we’ve outlined three methods to help you demonstrate the business value of your request.

1. Connect the new project management tool to business or unit objectives.

Most companies have similar goals: increase revenue, cut costs, and keep employees happy and productive. Your challenge is to make the connection between your proposal for a new project management tool and these broader business goals.

First, choose three of your company’s objectives to target. If you’re unsure, work with your manager to determine these. For each objective, list two to three ways your current project management tool is impeding progress in this area. Finally, explain how a new tool will help overcome these challenges and drive results.

The following are typical business objectives you can use to build your case:

Business Objective 1:

Improve time-to-market for new product or service releases.

Current Situation: Three things have inhibited product launches in the past:

  • Poor estimates and inaccurate timelines created false expectations and inefficient use of resources as people poured on the gas to clear bottlenecks.
  • As timelines were perceived as ambiguous, the amount of time the launch team spent briefing their management and peer organizations on “status” created a new bottleneck, further impeding progress.
  • As work slipped, accelerated, or was re-prioritized, the impact of those changes was unforeseen, unaddressed, and brought progress to a standstill.

Expected Outcome: With a new project management solution in-place, we can improve forecasts; identify and react to changes quickly; and produce automated, self-serve status reporting for management and/or clients. Plans to launch new products would be accelerated, bringing earlier than expected revenue to the company.

Business Objective 2:

Reduce delays and customer disappointments from supply-chain changes, resource constraints, or re-prioritization by management.

Current Situation: Three things have caused delays in the past:

  • Decisions were made outside our project team without regard to the downstream impact those changes would create.
  • Time spent collecting information to merely assess the status of the individual tasks across the two-dozen projects was an impediment to completing actual work.
  • We had no ability to see the how to optimize the deployment and workload of our resources, so they were underutilized and improperly scheduled.

Expected Outcome: Project management software will allow the team to understand how changes in scope, project length, budget, etc. impact projects and delivery dates. The team can then anticipate and react to downstream risks much earlier, leading to fewer delays and disappointments.

Business Objective 3:

Improve employee engagement and reduce turnover.

Current Situation: Three things have played a role in lowering employee morale:

  • Open communication is currently limited because the entire team does not have access to our project plans. Relevant files and information is scattered.
  • Without a holistic view of what is happening, our team does not know who is working on what and when.
  • Because of this decreased visibility, team members feel they lack ownership and autonomy in their day-to-day work. This leads to decreased engagement.

Expected Outcome: A new project management solution will give the entire team access to project plans, files, and statuses. This transparency will remove our team’s stress and anxiety around doing the right work at the right time. A new tool will also improve employee engagement, as our team will have more control and visibility over priorities, timelines, and the work being done.

These are just three examples to illustrate how your proposal for a new project management system can be connected to larger business objectives. By formatting it this way, your stakeholders can have a clearer idea of the current situation and what improvements a new tool would bring.

2. Quantify the Costs and Show Reductions

Another way to demonstrate business value is to quantify the costs of your current tool and show how the new tool will save the business time and money. To get the complete picture, you must consider the Total Cost of Ownership (TCO) over a three to five year span. Your vendor can provide costs for the proposed tool.

If you need help calculating the TCO of your current tool, befriend someone in Accounting who can help you calculate the following:

  • Software licenses
  • Hardware and OS purchases
  • Maintenance costs and upgrades
  • Salary costs of any staff needed to maintain the system
  • Contract resources whose sole job is maintaining or supporting your tool

“Time is money. Every minute spent on redundant or unnecessary PM work is money lost.”

Hidden Costs

While the more visible and direct costs are well known and easily documented, it’s often the hidden costs that companies neglect to consider. These can be harder to quantify but should be taken into consideration, especially if your team isn’t currently using any project management system

Your time: Time is money. Every minute spent on redundant or unnecessary PM work is money lost. To illustrate this, calculate how much time is spent on manual processes, such as updating spreadsheets and writing and sending status reports, as well as gathering updates, whether that’s through email, meetings, or water cooler conversations. Then, calculate how often those tasks are performed over a week/month/year. Multiple those numbers by the hourly equivalent of the person doing the work. If more than one person is involved, you can use a blended FTE rate to represent the team.

Cost of delay: Even the smallest delay has the potential to set off an avalanche, costing thousands of dollars. While a new tool won’t be a cure-all, it can help anticipate, avoid, and mitigate issues that could lead to project delays. If your projects have been running behind schedule, calculate the economic impact of deferred income and lost sales, as well as additional project costs. If you had a tool that helped you better identify and analyze risks, how much would you save? If you continue on your current path, how much do you stand to lose?

Opportunity cost: Many organizations continue to push on with a “that’s how we’ve always done it” attitude. While manually updating a spreadsheet several times a day is doable, it’s also incredibly inefficient. If repetitive tasks could be made more efficient or even eliminated, those team members could spend their time on more valuable work.

Cost of inefficiency: Inefficiency is a common symptom of a subpar project management tool. For example, the most common way to share spreadsheet updates is through emails. Sometimes this happens immediately; sometimes it takes a few hours or days to get passed along. This leads to delays and wasted time.

Other tools limit access to one person at a time. Because that person is wholly responsible for updating the plan, they spend a majority of the day tracking down updates and entering the data. This might be okay if their entire job was dedicated solely to updating the PM tool, but that’s usually not the case. If this situation sounds familiar, spend a week adding up the hours spent on tracking down statuses and updating the plan. The number might be a surprise for both you and your stakeholders.

Customer Satisfaction: If you’re delivering late or going over budget, your customers aren’t going to be happy. Of course, a project management tool cannot be wholly blamed for customer dissatisfaction, but if you see trends, it may be worth investigating further. To measure this, you could look at measures like repeat and lost customers, revenue from existing customers, and customer surveys.

To showcase these numbers, create a spreadsheet calculation that shows the summation of each item. You can use the example in our download kit to build yours. You may want to partner with someone from the finance team to ensure you have the most accurate information.

To put these costs in clearer terms, we created a cost calculation worksheet to help quantify the true costs of using an ineffective project management tool. Just plug in a few numbers, and you’ll have solid data for your proposal.

Free Resource Kit

Calculate the Costs of Inefficiency

Calculate the value of a new tool in terms that your boss or executive team will understand.

Get the Resource Kit

3. Calculate the Value of a New Tool’s Benefits

Successful project management has a direct impact on the bottom line. Projects that are delivered on time and on budget lead to revenue and satisfied, repeat customers. Improvements in process and efficiency reduce time spent on routine tasks, which equates to more time spent on valuable work. With improved cost tracking, management can easily find which activities, processes, or errors are driving up costs and then make adjustments.

Your challenge is to find your own real world scenarios that demonstrate the value a new project management tool would bring.

Some areas to explore:

Time Saved: A new project management tool has the potential to cut hours of administrative time. For example, let’s say that you could go from a weekly status meeting to a monthly meeting. That saves you three hours per month. Over a year, you would have saved 36 hours. Multiply that by the number of people on your team, let’s say 5, and you’re now saving 180 hours every year.

If you multiply that by the blended rate of your team, we’ll say $33 an hour for this example, that comes out to $5,940. That’s nearly six grand of your company’s money and 180 hours of your team’s time going toward meetings.

Now, what will your team do with those extra hours? If your team bills hourly, you can multiply your hourly rate to show how much potential extra income your team could bring in.

If your new tool offers collaboration features, you can also calculate at the number of hours you spend on sending and reading emails and manually updating project plans.

For example, a LiquidPlanner customer drastically reduced the amount of time his team spent on emails. He estimates that his team now saves the equivalent of 480 days per year. That’s about $73,000, the salary of one employee. His team also wins back that time, which further boosts productivity.

Increased Capacity: Any project management tool worth its salt will help you maximize your team’s productivity. For example, one of our customers was able to reduce project durations from six months to six weeks. Instead of two projects every year, they can now ship eight. That’s a significant increase to the bottom line.

To calculate this, look at the number of units (e.g., physical items, billable hours, projects) that your team currently produces over a certain period of time (e.g., hours, weeks, months). If you were able to increase capacity by 10 percent, how many more units could your team produce? What about 20? 30?

Value of Intangible Benefits: Some benefits are harder to quantify. While you may be tempted to ignore these, the intangible benefits may have just as much of a business impact as the more tangible assets of your benefits calculations.

These could include:

  • Improved customer satisfaction and loyalty
  • Improved engagement and lowered stress for employees
  • Better management and data
  • Less time performing repetitive tasks
  • Increase in billable services

Whether you use one or all three of these methods is up to you. The most important thing is to present enough of a justification to secure an approval without overwhelming your audience. Also, be mindful of not getting carried away with dubious savings estimates and tying hard-costs to intangible ROIs. Give yourself some wiggle room in the ROI department to prevent executives from immediately dismissing your calculations.


Chapter Three

Build Out Your Implementation Plan

You can bet that one of the first questions your stakeholders will ask is, “How long will it take to transition to this new tool?”

 

It’s time to get a game plan together for implementing your proposed solution.

Think of adopting a new tool like running a project. If you’ve got a plan in place, you’ll have a higher chance of success. This chapter will walk you through how to create a rollout plan and timeline that will ease executive fears.

1. Form an implementation team.

The Champion:

Every project needs a project manager and your rollout is no exception. The first step is to identify a strong champion to drive the implementation and act as a mobilizer for the team. Now and in the future, they will be the point-of-contact for all things related to the new solution. Having an appointed champion is key to adoption. If you’re reading this guide, that person is probably going to be you!

The Implementation Leads:

Depending on the size of your team, you may also want to designate a few other implementation leads to facilitate buy-in and assist with training and communication. These people might be department heads or other project managers.

The Executive Sponsor:

Finally, you’ll want to partner with an executive sponsor to help communicate the benefits of using a project management solution and support its continued usage. Once you get buy-in from your executives, pay attention to who seems most excited and enlist them to motivate the rest of the team by saying, “This is important for our business, and here’s why.”

Having this implementation team established before you pitch the solution will go a long way in convincing stakeholders that the transition will be well-managed.

2. Set goals.

Getting the team to learn how to use a new system is important, but be sure to place just as much emphasis on goals and processes during the transition. Start by asking the question, “What is our goal in using this new tool?”

Common responses are:

  • “We want to track progress.”
  • “Project management.”
  • “Uhhh, to keep all of our project information in one place?”

These answers are a good start, but they won’t help you get results. Make sure to identify specific areas in which you’d like the project management tool to improve the way your team works.

Some examples are:

  • “Help PMs identify at-risk projects and tasks sooner so they can proactively mitigate the risk, rather than putting out fires after the project is late.”
  • “We want to show the impact of new and changing priorities on our schedule.”
  • “Get a better understanding for how resources are being utilized to make the business case for expanding the team.”

Once you’ve identified one or two specific goals, write them down and be prepared to include them in your pitch and throughout the implementation.

3. Explore training options.

There could be a lot that goes into training your team, depending on the complexity of the solution you select, the formal training your chosen solution provides (or doesn’t), and your team’s previous experience with software.

The very first thing you should do is find out what training programs are offered for the solution you’re considering. After that, you’ll be in a better position to create an onboarding plan that your management team will be confident in. The very first thing you should do is find out what training programs are offered for the solution you’re considering. After that, you’ll be in a better position to create an onboarding plan that your management team will be confident in.

Review Documentation

Most project management systems will offer documentation in the form of guides, manuals, or videos. Spend time looking through these resources to assess the depth and breadth of the information. Think of questions your team may ask and see how long it takes for you to find the answer on your own.

Research Support Offerings

You’ll also want to find out what type of customer support comes with your subscription and whether or not training is included. For example, LiquidPlanner includes 4 hours of one-on-one onboarding assistance and training as part of our premium subscription packages. Many SaaS (Software as a Service) providers will only offer fee-based training, so make sure to factor in these costs as they can quickly add up.

Establish Training Groups

Various people within your organization will use the project management system in different ways. For example, team members that need to see their assigned work will use completely different features than project managers. You may wish to set up separate training sessions based on roles. Starting with three groups is oftentimes sufficient: executives (data consumers), project managers or department managers (schedule and resource editors), and team members (task editors).

4. Outline the logistics.

In addition to training the people that will be using the software on a daily basis, you should also consider other implementation logistics. This includes things like IT involvement and adjustments to existing workflows. Here are some questions to ask yourself:

Technical logistics:

  • How much involvement from IT will we need to implement this new system?
  • Will we need to configure single sign-on before the rollout?
  • Do we need to set up integrations between this new system and our other tools?

Process logistics:

  • How does this new software impact our existing workflow?
  • Who is responsible for establishing and communicating adjustments to workflow?
  • What is the transition plan between the previous project management method and this new tool?

Once you’ve identified areas of impact, contact the people at your company who will help with these logistics and get rough estimates for the amount of effort each item will require. They also might be able to suggest implementation steps or requirements you didn’t think of. Meeting with the right people will ensure that you have answers to your stakeholders’ questions.

5. Establish a timeline.

When it comes to implementation, your executive stakeholders are probably going to care a little more about the when, instead of the how. It’s important to remind them that any change in process or tool requires time.

There are a lot of factors that influence how long a rollout will take: team size, existing workload, company culture, buy-in, training schedules, the list goes on.

That’s why many implementations can take up to three months to get full adoption. However, a lot of the time-intensive work happens upfront in the first month or two of the rollout. Here’s what a typical timeline looks like in more detail:

Week 1: Preparation

  • Implementation team gets acquainted with the tool
  • Introductory memo is sent to the entire team
  • Training sessions are scheduled

Week 2: Configuration

  • Customize the interface to align with your team’s workflow
  • Map out user permissions and access levels

Week 3: Setup

  • Import existing work into the system
  • Create project templates for repeatable business functions
  • Establish business rules for software usage

Week 4: Training

  • Hold kickoff meeting and communicate rollout plan
  • Facilitate and/or conduct training sessions
  • Invite team members into the system

Week 5: Go Live

  • Switch over from old project management system to the new system
  • Check in with all groups to address areas of concern

Week 6: Monitor

  • Begin building reports to share with stakeholders
  • Monitor adoption and integrate the new system in all processes and meetings

Week 7: Adjust

  • Make adjustments to workflow in the system based on feedback
  • Revoke access from old project management system and archive

Weeks 8 to 12: Iterate

  • Share initial reports with stakeholders and clients
  • Provide an update to evaluation stakeholders with initial ROI analysis

When you give your stakeholders a concrete timeline up front, you’ll be setting expectations for the reality of implementing a new project management solution. Be sure to sprinkle in the benefits that the business will start to realize as you walk through this timeline.

Read on to learn how to put together a proposal and deliver a pitch your boss can’t refute.


Chapter Four

Assemble Your Research in a Written Proposal

The hard work is over. Now you need to package it. Your last step is to create a short document that summarizes your research, proposal, and plan.

Use this document during your meeting to ensure you cover your key points. It can also double as a nice leave-behind for stakeholders.

We recommend breaking the proposal document into four sections:

The Vision:

First, offer a taste of what life could be like with this new project management tool.

“A chicken in every pot.”

“A computer on every desk.”

“A world where projects are delivered on time and on budget and redundant, unnecessary meetings are a thing of the past.”

You get the picture.

“A world where projects are delivered on time and on budget and redundant, unnecessary meetings are a thing of the past.”

Then, state your proposal for purchasing a new project management solution upfront in one to two sentences. Or, instead of proposing to purchase, you may suggest running a pilot of the software for a month. It may be easier to get buy-in for a test run, rather than a full adoption.

The Background:

In this section of your proposal, you’ll use your research from Chapter 1. Begin by demonstrating that you understand the needs of your stakeholders and the business. For example: “This quarter, our company has been focused on reducing the time-to-market for new products.”

Then, briefly explain how your current project management tool is preventing your team from meeting these objectives. Be thorough enough that you paint an accurate picture of the current situation, but don’t spend more than two paragraphs on this section.

The Initiative:

Now you need to demonstrate why your proposal will bring the company closer to the vision you’ve outlined.

List three reasons why your boss should approve your proposal. Use the work you did in Chapter 2 to show how a new tool would contribute to this greater vision. Don’t make the mistake of just listing features here. Remember to frame it from your stakeholders’ perspective: “What’s in it for me?”

You should also list consequences of not approving your proposal for a new tool. Look at your calculations from Chapter 2 to determine how much time, money, and productivity is currently being lost. If you continue to do things the way you’ve always done, what do your stakeholders and the company stand to lose?

The Architecture:

Outline your plan for making the switch, if your proposal is approved. Use your plan from Chapter 3 to briefly outline the steps to successfully implementing a new tool.

Remember, this document should only be a page or two long. Any additional information can be discussed during your pitch meeting.

We created a checklist to use when reviewing your written proposal. This should help you ensure the important details are covered.

Free Resource Kit

Proposal Checklist

Ensure you’re ready for the pitch with this handy checklist.

Get the Resource Kit

Chapter Five

Anticipate Objections and Compose Rebuttals

There will be questions. There will be objections. Don’t let them derail your entire proposal.

Imagine that you’re in the room with the executive team. You’re getting closer to The Ask, and you’re feeling good. They’re smiling, nodding, asking the right questions. You’ve hit your key points. You can tell your business case is resonating.

Then, out of nowhere, one of them drops a bomb on your presentation. You stutter out an answer and try to quickly move on. But no one is listening anymore. They’re thinking about the question. They’re having doubts. They’re making their decision before you even finish your pitch.

When you discuss your idea, there are going to be questions and objections. These can be stumbling blocks that trip you up over and over again or steps that take you in the right direction. It all comes down to how you prepare.

Address Their Questions

First, take 30 minutes to write down every question your stakeholders could possibly ask. To get the creative juices flowing, divide your document into six sections: who, what, when, where, why, and how. Then, start writing.

Here are some ideas to get you going:

  • Who is going to run the rollout?
  • What will be the benefits of this new tool versus our current?
  • When would we implement this?
  • Where will our data be hosted?
  • Why do we need a project management tool?
  • How long will it take to train your team?

Make sure every question is answered somewhere in your presentation. You don’t want to hear “No” just because you didn’t take the time to anticipate and answer your stakeholders’ questions.

We’ve created a guide to the most common executives ask about LiquidPlanner. It should help you better anticipate possible questions and formulate smart responses.

Free Resource Kit

Executive FAQ Cheatsheet

Be ready to answer executives’ most commonly asked questions about PM software.

Get the Resource Kit

Play Devil’s Advocate

Now grab a second sheet of paper. Write down every objection you can think of and then ask your team to do the same. Narrow your lists down to four to six objections. Now script talking points for every objection. Bring this document to your meeting and reference if needed.

Should you proactively address these objections within your presentation? There’s a fine line. You don’t want to plant objections in an executive’s head, but you also don’t want to look unprepared. If an obvious objection is listed by both you and your peers, then consider mentioning it in your pitch.

The 6 Most Common Objections to Investing in a Project Management Tool

Drawing upon our customers’ experiences of pitching to executives, we’ve come up with the six most common objections to investing in a new project management tool.

1. The Budget Objection

We can’t afford a new tool right now. Our budget is spoken for.

2. The “We already have…” Objection

We already use spreadsheets for project management. Why do we need to pay for a tool?

3. The Security Objection

Cloud-based software is not secure.

4. The Customization Objection

I want to be able to control and customize the functionality of the software.

5. The Cost Objection

I’ve heard Software as a Service (SaaS) is more expensive than on-premise solutions.

6. The Adoption Objection

Learning a new tool will be a challenge for our team. We don’t have the time or resources to adopt a new tool.

Want to see our recommended responses and the rationale behind each? We thought you might ask. Download the Objections Cheatsheet below:

Free Resource Kit

Objections Cheatsheet

Learn the 6 most common objections to PM software and how to respond.

Get the Resource Kit

Chapter Six

Making the Pitch

If you’ve done all of your homework in Chapters 1 through 6, you should feel very comfortable approaching stakeholders with your findings and proposal.

Bring your boss (unless you’re pitching him or her, of course) and the executive sponsor to the meeting. If you think this will be a hard sell, consider bringing the influential ally you identified in Chapter 1, as well. Be sure to thoroughly brief them before the meeting, so that you’re all on the same page.

Schedule the meeting at a time when your stakeholders are going to be most receptive. Then, bring your proposal, pitch presentation deck if you’re using one, and FAQ and objection cheatsheets.

Demonstrate the tool during the meeting.

If you’re pitching software, you better be ready to demonstrate it. Before the meeting, take advantage of the vendor’s free trial to build out a workspace and learn the tool.

During the meeting, use a projector to display the tool live so stakeholders can better picture their teams using it. As you walk through your proposal, demonstrate the features and functionalities and explain how they are an improvement from your current system.

If you’d rather not have the added pressure of demonstrating live, use screenshots or a recorded demo to assist your presentation.

Whatever format you decide, make sure you’re experienced enough with the tool to competently explain features and benefits to your stakeholders.

Seal the deal with an attractive presentation.

You’ve put a lot of work into this pitch. Don’t derail it with a sloppy slideshow.

We’re not suggesting you spend hours adding fancy animations and choosing the just right stock images. Instead, focus on making it easy to quickly consume (no walls of text) and visually appealing (embed graphs, images, video and branded colors, if possible).

We’ve created a presentation template that you can use to guide the conversation. Get your copy here:

Free Resource Kit

Pitch Deck Template

Use the slides and talking points in this customizable template to format your executive pitch.

Get the Resource Kit

Know when to stop.

When you reach the end of your pitch, restate your proposal for adopting or piloting a new tool. Then, stop talking.

It may feel uncomfortable. You will probably feel tempted to fill the silence. But, don’t do it. Instead, take a deep breath. Count to three, and wait for your stakeholders to respond. You don’t want to risk unselling the idea by babbling on and on.

Considering all of the hard work you’ve put into this proposal, we hope you get the green light right there! If you do, tell them thank you, leave the room, and do a victory dance in the hallway. Details can be hashed out later.

If they need time to deliberate, thank them for their time and leave them with copies of your proposal.

If your proposal is not accepted, just remember every salesperson’s motto: “No only means not right now.”

If your proposal is not accepted, just remember every salesperson’s motto: “No only means not right now.” Go back to your desk and do a little post-pitch analysis.

  • What went wrong?
  • How could you improve?
  • Were there any questions or objections that tripped you up?

If you truly believe this new project management tool will have a positive impact on the lives of you, your team, and your stakeholders, be patient and continue to work with your team to show the need and quantify the potential benefits and impact. Be patient; a more opportune time may present itself in the future.

Conclusion

In today’s competitive marketplace, companies are being pressured to deliver more while cutting costs. To accomplish this, teams need solid project management tools that help them stay ahead of the competition–not fall behind.

We hope this guide will help you demonstrate this need to your executive team. Remember, it’s not only about the features. It’s about how the right project management software will positively impact the business’s bottom line.

Free Resource Kit

Building a Business Case for Project Management Tools

You’ve found a new tool. Your team’s itching to roll it out. But first, you need to win that final executive sign-off. These six resources will help you build a compelling business case that will have executives asking, “Where do I sign?”

Get My Free Resources
Introduction
Chapter One: A Successful Pitch Requires a Change in Mindset
Chapter Two: Three Methods for Demonstrating the Value of a New Solution
Chapter Three: Build Out Your Implementation Plan
Chapter Four: Assemble Your Research in a Written Proposal
Chapter Five: Anticipate Objections and Compose Rebuttals
Chapter Six: Making the Pitch
Conclusion
Convince Your Boss was last modified: October 19th, 2017 by Chris Straehla