What is Documentation Design that I haven't already done?
I'm a contractor who has been working on a project (a developer guide website) for months with another contractor writer. We spent a lot of time:
- Interviewing end users
- Designing the deliverable (creating an outline and defining content, demos, example source code, etc.)
- Establishing styles, standards, and procedures
- Fine-tuning them
- Performing Proof of Concepts
- Running it past our interviewees
- Tweaking our work
- Prioritizing the work
- Creating a first release
They let my co-worker go and replaced her with a full-time employee with an inflated ego. He says the documentation was not "designed," and when I asked him what he meant, he couldn't articulate a coherent answer.
Does anyone have a clue what he might mean by "design"? Maybe a template? I searched the internet, but all I come up with is design documentation, which means something entirely different.