Why do implementations get stuck?
SOME COMMON CAUSES:
- Remote work environment has stalled existing project cadence
- Project Lost Funding
- Internal staff left, so the project has no true lead or sponsor
- Decision making is bogged down in bureaucracy and meetings
- There is no true person with decision making authority
- External systems or other projects are running behind for integration (e.g. a simultaneous ERP system implementation)
- Data warehouse or interface between other systems stuck
- Internal teams do not want to leave legacy system
How can you get un-stuck?
- Outside project management firms with remote project expetise can establish a cadence and recommend technology that allows for project continuation
- Evaluate new funding sources, calculate benefits of the added efficiancies in completeing implementation
- Hold a new kick-off meeting to clearly define roles, choose new project sponsor. Begin documenting knowledge and status
- Prioritize projects your implementation is dependent on, or shift to a more modular, AGILE implementation style that isn't "all-or-nothing"
- If integration between systems is stuck, consult a firm specializing in these interfaces.
- Establish a "change management" team and training schedule to assure users that new system is not just efficiant, but will streamline their workload
Realistic assessments sometimes present the honest truth, that a project is so far gone has to be considered "sunk cost" and may need to be scrapped, realistically to move forward.
