And revisit this statement throughout the project. The problem you’re trying to solve or correct is as important as the technology you select. Interview stakeholders who will interact with the new technology to avoid under-delivering or over-delivering and, in either case, the potential for introducing new problems.

Whether it’s customer retention, network uptime, ROI, or other criteria, know what success looks like. Identify and calculate risks against the benefits of a successful rollout.

Understand dependencies on other events or projects to create milestones and a realistic deployment schedule. This will inform the rollout approach, from procurement to staffing to change management.

Build the team, develop the specific plan, and create repeatable processes that will enable all aspects of the rollout. A proof of concept is key.

Don’t just collect and report the data. Use it to tell the story of what’s working and where adjustments are necessary.