Re: Question concerning product customization and documentation

[Anthony Davey <ant -at- ant-davey -dot- com>]

Wade,

If a customer wants customisation, yes you do make the changes.  But 
they have to be willing to pay the price for that customisation.  Or 
your marketing policy says no, and you don't.

Documentation changes:  list the changes needed, do them, save it with a 
specific title.  In practice, of course, you won't/are unlikely to come 
across 100 different variations for one specific field name, but across 
the whole program you will.  The nightmare comes, if you include screen 
dumps, when customer X calls field A by one name and field B by another; 
customer Y, on the other hand calls field A by the standard name, field 
B by the same name as customer X, and field C is called something else 
non-standard, which customer Z uses, but not terms A & B.  Multiply the 
number of potential different field names customers have by the number 
of screens on the program and you may have some idea of the size of the 
issue.  The decision is someone else's, but you may have some input.

Regards,
Ant

Wade Courtney wrote: