Ensure that the help design will fit in with what the programmers intend to do. A writer or editor should also be involved with the design of the software interface. If the developers make changes in the design phase, instead of leaving the writers to explain confusing things at length in the help, everyone's job will be easier, and the result will be much better for the user. Benefits of this step With a plan for the online help, everyone on the project knows what's expected, and doesn't have to take time later in the project figuring out what to do. The help should then end up very consistent, so the users know where to expect help, what sort of help to expect, and where they can navigate from any type of help topic.
Help is easier for testers to test and for technical reviewers to review.
The online help development process is perceived by others on the project as much more rigorous and disciplined, and the technical writers' professional standing increases accordingly. The main role for an editor at this step is to ensure that help design specifications include all necessary decisions. The editor might be responsible for compiling the specifications, or advising the responsible person. Another role for the editor is to examine the software interface design and recommend changes. Later in the project, the editor's work will be greater and will probably include many more consistency changes and negotiations over terminology and other issues.