by Steve Endow
How do you create your documentation?
When do you create your documentation?
Who in your organization creates your documentation? Who doesn't?
Does anybody actually read your documentation? How do you know?
Do you specifically budget for documentation in your projects? How much?
Are your customers reluctant to pay for documentation?
Can your documentation keep up with your software releases? Do you maintain detailed release notes?
Do you methodically and consistently update your documentation over time?
Update: (based on a response from Erik Hougaard on Twitter)
Do you create instructional videos or video tutorials as part of your documentation? If so, how do you consistently record, edit, store, publish, and index such videos? Do you have public and private (e.g. customer specific) videos? If so, how do you handle publishing videos for those different audiences?
By now I'm sure you are excited beyond belief, as there are few topics more glamorous than "documentation".
Is it read?
Over the last 20 years, I've worked with over 700 customers. I've documented business processes, business procedures, ERP training guides, user manuals, customization specifications, integration designs, data mappings, installation guides, and software user manuals.
