Call Us: US - +1 845 478 5244 | UK - +44 20 7193 7850 | AUS - +61 2 8005 4826

Data/Process Modeling

There is enough blame to go around in a typical System Implementation scenario. Something gets forgotten, something does not work right, something happens that is not planned for… and a good first step in fixing the problem is acknowledging the responsibility for it. However, sometimes the fault is not yours – even if someone is convinced it is. Take, for example, a Consumer’s reaction to the new system, especially if said Consumer was not directly involved in System Acceptance. It is possible, indeed likely, that some feature of the new system will be at odds with what the Consumer thinks it ought to be. After all, it was requested by somebody else, and somebody else again built it. So a vocal Consumer will complain that the new system is wrong. This situation is dangerous on two fronts: first, if accepted on its face value, it may mean rework, delays or worse; second, if not handled correctly, it may taint the perception of the new system and may lead to more complaints. This is another case where solid, signed documentation really pays off. Prove that the functionality works just as it was requested. Enlist the help of the Project Sponsor, the Customer Decision-Makers, and any other “persuasive peers” (who are most likely just as anxious to have the system well received as you are), to explain the rationale behind design decisions and the process for change. And don’t accept any more blame than is properly yours.