Cardinal Health

What were you previously using?

We had different departments using different tools, some staff were using MS Project, others were using custom Excel spreadsheets. We did have some basic Salesforce object we used for reporting which was fine, but it was just another tool to be across. We also had project notes going through emails and Teams etc.

What challenges were you facing before using Mission Control?

There was a lack of visibility into most of our projects for the leaders of our PMO who didn’t have one place to stay abreast of project status. There was also a lot of verbal communication, so overall visibility cross functionally was difficult.

We also had a lack of reporting and customer facing materials, and if there was any, it was very manual.

There was also a lack of standardization across our projects, due to different functions using different tools.

Why did you choose Aprika’s Mission Control?

We were looking at a few options, as a collective group we really wanted an app partnership that was natively embedded within Salesforce. We also needed something flexible that allowed us to add custom objects, two boxes that Mission Control definitely ticked. It really was the Rolls Royce of Project Management apps based on feature set and relevance.

We looked at building our own solution and we looked at a couple of Mission Control competitors – but once we saw Mission Control’s scale and scope we realized we wouldn’t be able to get close to building something that met the brief, so it was ultimately a very good decision not to build.