Want More?
Sign Up to Be Notified About OneSource Virtual Updates and Communications.
Jun 18, 2019Consulting & Deployment

Do You Need a Third-Party Project Manager for Your Workday Launch Implementation?

Do You Need a Third-Party Project Manager?

Selecting a new HCM and financial management solution is not something any organization should rush into. You have to evaluate your software options and do your research, and then you have to build support for the solution you’ve chosen. But while all of these steps are crucial for a successful ERP implementation, they’re the first of many that you’ll be taking on your road to going live.

Workday has the potential to transform your business processes in amazing ways. But transformation doesn’t happen overnight. Deploying Workday takes a team. And while some of those team members will belong to an outside implementation service provider, you don’t need another project manager in the mix in order to have a successful deployment.

The Expertise You Need Is Right in Front of You

Projects are hard. It makes sense, then, that when you’re beginning a Workday Launch implementation, you want to feel confident about your deployment partner’s expertise. But you also need to pay attention to the expertise of the internal resources that are already around you.

Why would you contract with a third-party project manager to coordinate with your deployment partner when you already have experts on your team who thoroughly understand your business processes and strategic objectives?

The people you choose for your internal team should be regarded as thought leaders within your organization. They should deeply understand your business and be empowered to make key decisions. They should also be able to influence decision makers within your organization.

The Best Reasons for Not Hiring a Third-Party Project Management Contractor

Since existing employees already have full time roles, it’s understandable that some organizations would consider hiring a third-party project manager.

But there are at least two reasons this might be a mistake:

  • First, while coordinating internal efforts with your deployment team does take time, it’s not a full-time job in itself. Do you really want the expense of hiring a full-time third-party contractor for part-time work? Through creative and critical thinking, you and your internal team can brainstorm ways of balancing the requirements of your Workday Launch implementation with the requirements of their normal roles, minimizing disruptions to normal business operations as much as possible.
  • Second, the work your internal resources will do is too important to outsource, as the key knowledge transfer that takes place during your deployment should stay within your team well after you go live. From this standpoint, hiring a third-party contractor is counterproductive in the long run.

Transform Your Business Processes With the Right Experts in Your Corner

Workday has proven to be transformative for the organizations that use it. But going live involves more than just installing new cloud software. It’s a process. And that’s why it’s so important for you to have the best possible deployment team in place.

Does that mean you need to hire a third-party project management contractor? Ultimately, that’s up to each organization to decide. But when you consider the expense of hiring a full-time contractor, and the fact that you’re already surrounded by people who thoroughly understand your organization, the costs—both literal and figurative—quickly start to outweigh the benefits.