I like the idea of, and use the structure of projects with clearly defined goals. Once a project is complete, if the output/result of it has any kind of ongoing use and maintenance, I'm curious how people handle the transition from project documentation to procedural documentation.

Currently I state a goal, and sometime objectives of a project, then create actions, and use notes when necessary to supplement the actions (which becomes partially a diary). Procedural documentation—for example: how to maintain a web site with technologies x, y, and z—tends to get posted to a wiki (the organization I'm working with has a number of changing people responsible for various areas of operation).

Perhaps I could revise the way I document projects so that the information, if not automatically self-documenting, would require less re-write for a wiki, or what have you.

Bob