Back to Blog
Blog

How do you avoid tying pilot milestones to integrations the vendor cannot control?

How do you avoid tying pilot milestones to integrations the vendor cannot control?

Integrations often depend on the customer’s IT team, a third party system or an approval process that can take months, so a pilot that depends on them…

Integrations often depend on the customer’s IT team, a third party system or an approval process that can take months, so a pilot that depends on them can stall for reasons nobody in the pilot can fix. The pilot then gets judged on delays rather than on whether the tool works, and the people who championed it end up defending a timeline they never controlled.

This pattern is common because integrations look like simple technical tasks during planning, when in practice they involve security reviews, access requests, firewall changes, test environments and sign off from the teams who own the systems on the other side. Each of those teams has its own queue and priorities, and a pilot is rarely at the top of the list, so a milestone that reads as connecting to the maintenance system in month two can easily slip to month six.

The better approach is to set milestones around what the pilot team can control, like converting procedures, running jobs and gathering feedback, and to treat integrations as a parallel track with its own timeline. Milestones such as converting an agreed set of procedures, running a target number of real jobs with a named crew and reviewing feedback with supervisors at set points can all be met by the people in the pilot, which keeps the evaluation focused on whether the tool solves the problem.

Manual imports or file transfers can fill the gap until the integration is approved, such as a daily export of work orders or a periodic upload of the asset list, and someone in the pilot team should own that routine so the data stays current. Running this way for a while also clarifies exactly which data the integration needs to carry, which can make the eventual request to IT smaller and easier to approve.

It helps to write this structure into the pilot plan from the start and share it with the sponsors, so everyone understands which milestones decide the outcome of the pilot and which depend on other teams. If the integration track slips, the pilot can still reach a clear decision on its own merits, and the integration simply joins the rollout plan when it is ready.