We all procrastinate sometimes, but waiting until late in the implementation cycle to plan user acceptance will only exacerbate the risks, already cited in our previous posts. Scrambling at the last minute in reaction to user sensitive problems may trigger even more resistance: fear of excessive work pressure and loss of control at the time of “going live.” In this unfortunate circumstance, the possible rewards of the new processes may no longer appear adequate or satisfying.
Action
Work proactively to develop a user acceptance plan.
The approach to avoid this risk starts at the time of gaining management commitment for the project. While stated in this risk category, the project team must accomplish most of the following actions throughout earlier phases of the project:
- Establish an active communications methodology beginning as soon as management has authorized the project
- Create a sense of “ownership” of the configurable product models and the related new processes
- Provide a feedback mechanism to the project team for additional improvements
- Incorporate a mix of motivational methods, both positive (carrot), and as necessary, negative (stick)
Essentially, the project team needs to execute a marketing strategy for creating enthusiastic user acceptance, not foot dragging resistance.
