This is a common scenario for technical writers: there is existing content, let's say for V1 of a product, and the same content needs to be provided for V2. Do you limit your work to making changes to the existing content for technical accuracy with V2? Or do you start with a blank slate and design a new doc, generously copying content from the old where applicable?
Here are some of the issues I consider when making that call. The first two are fairly cut-and-dried, but after that it's more subjective.
Even when (1) the product isn't changing that much, and (2) you have plenty of time, and (3) there's really no feedback or data, and (4) you have definite ideas for improvement -- you still want to consider whether reworking this doc (rather than just updating) is the most important thing you could be doing with the time you have.
I won't be writing any more about System Center 2012 - Operations Manager. After several years on the Operations Manager content team, and Data Protection Manager before that, I've moved to a new (to me) product team: Windows Embedded. Specifically, Device Manager (which extends Configuration Manager, so I guess I didn't really move too far away from System Center, eh?)
The job description for my new position included a link to a video that interested me. It had never occurred to me that all the gadgets I take for granted had an operating system - I was so desktop/server-centric. "World of Windows Embedded" really piqued my interest and I'm excited to start learning a new product.