After conducting a diagnostic process, we need to get all of our findings, thoughts, and ideas into writing. The Diagnostic Report is the main deliverable of our Diagnostic process. It represents the final shared understanding between us and the client, and our full vision for the project. The Diagnostic report must include enough information for the project organizer to create a clear SOW for the next phase (typically UX)
Over time we’ve experimented with many different methodologies for this deliverable. This procedure represents a baseline approach which you can modify to meet the particular needs of the client.
Here are some example diagnostic reports. Note that they represent a variety of different diagnostic scopes, so you may not be able to achieve the same level of detail in the hours you have for your particular diagnostic. In recent times, we have shifted some information architecture/UX work out of the diagnostic and into the initial UX scope. That is to prevent premature decision-making that ultimately affects the project.
A diagnostic report should generally be 20-30 pages. There is no template yet, so for now, start with an existing report as your base. Over time we will create a template to start from. The format is generally something like:
We add different sections and sub-sections on a case-by-case basis. It all depends on what our plan actually is, and what the client is focused on or challenged by.
A good plan satisfies the client’s: