“The new system just isn’t working the way we hoped…”
It is not unusual for system implementations and upgrades to represent a major investment. Also, when things don’t turn out as planned, costs (and headaches) can quickly multiply.
You can avoid these pains by developing a documented needs analysis and functional requirements listing before signing on the dotted line for an implementation or upgrade.
For all involved, this would help clarify your vision of optimal system functionality or process automation and provide a basis for an even-field RFP process, thus better equipping you to get the most bang for your buck.
Check back next week to find out more reasons why you should use documentation!
- Traci Spratt, Documentation Specialist