Sometimes clarity of concepts and commitment are improved for the potential client if there are explanations framed in terms of questions and answers.
Why is it so important that I disrupt my whole organization to make my documents “pretty”? Answer: This is a lot more complex than pretty. Yes, they ought to look good, but your organization's operation rides on your documents, and they must be functional according to the many processes required to make a business run well.
My organization has been profitable. So why do I need to fix my documents? Answer: If things have been apparently going well, just leave well enough alone for now. But if your organization is involved in situations that impacts your documents, like a merger with another company for example, the integration of two different documentation systems must be addressed eventually.
What's so unique about your modular based methodology? Answer: It isolates and fixes each self-sustaining organizational process. This allows for maximum focusing and clarity.
Can you guarantee me that my organization will run more smoothly and make more money if the documentation system is improved? Answer: No such promise is possible. But if your organization is a part of a merger or acquisition, is up for an ISO 9000 or Sarbanes-Oxley audit, it will be very apparent how badly your documentation system needs repair.
What are the consequences of just leaving well enough alone? Answer: It's possible that your organization can muddle through every foreseeable situation. Whenever problems arise, somebody will save the day.
I have thousands of legacy documents. What happens to them and the system they were created under? Answer: They must be included in any documentation process change. As little effort as possible will be made to modify them, but they must be accounted for in the transition to the new system.
My organization will be soon buying out another company. Shouldn't we be able to set up an internal employee committee to work out the bugs in the integration of the two documentation systems? Answer: Yes, this is plausible. The problem is that employees have other jobs and priorities, and you need to have one person to drive the change.
How will my organization continue to operate during the transition between documentation systems? Answer: There must be a plan put in place for this transition time.
Can we modify our system one small part at a time? Answer: If possible, this may be the best approach.
My staff is pretty darned busy all day. How much time are they going to have to devote to this project? Answer: Besides making the customer happy, there is probably nothing in a company more important than documentation. Virtually every function, task, process, etc. has a documentation element. It is this continuous paper trail that greases the skids, establishes a record of events, etc. |