Back up to move forward
Submitted by Sheri Albers on August 29, 2018 - 5:26 PM
Conventional wisdom would have told us to not build Phoenix in the first place: "Don't put all your eggs in one basket." and "If it ain't broke, don't fix it." So now they want to try again? Perhaps the answer is not in procurement, but in collaboration. For example, the CRA has a pay system in SAP that has been working well for years. Other departments had their working solutions, whose was best? Why are we trying to re-invent the wheel? If a department needs a pay system, one possible solution would be for them to look for a partner department with a good system that can expand to meet their needs (similar to CRA and CBSA sharing IT resources). As departments who need better pay systems partner with departments with good, solid existing systems, over time, a central "winner" would emerge as the best model, and the rest of the departments can be brought on board as needs arise. The problem with Phoenix was not only that it was implemented poorly, but that it was forced upon departments that did not need to be fixed. Before you try to find a new solution, allow departments to roll back to systems that already work. The benchmark for a new system should be something better than the best old system, not just better than Phoenix. Sometimes you need to back up to move forward.