The best pilot project might be the one you kill

If you’re programming a robot to pick parts and report progress to a central warehouse system, you might only need four to six weeks to confirm whether the proof of concept is viable.

In both cases, you must define in advance very specific metrics and outcome expectations that the pilot must produce to be considered viable. You must also set the timeframe in which results (good or bad) are expected. And you must communicate the project, timelines, and expectations to the pilot project team, the board, and management stakeholders. You’re your timeframe expires, results can be reviewed, and a decision to move forward or terminate can be made.

Avoiding pilot project ‘sand traps’

Estimating the timeline and metrics for a pilot project is key — and can often be more art than science. It’s understandable as well that emotional stakes may be involved in a pilot project, whether from the IT leader, board, or CEO, that could influence objectivity when it comes to deciding when to pull the plug.