Regardless of the communication form-whether it is verbal, written, or in a presentation-the story and the resulting documentation will naturally inherit 3-circle analysis characteristics. For example, upon analysis completion, it takes very little effort to create a short email message summarizing your work. Or for the operating system-focused audience, you could simply provide the Performance Summary Analysis and the Operating System Performance Analysis sections (described next). You can scale and customize your communications very quickly, without sacrificing technical integrity or performing needless rewrites.

Let's look at the story components, how they relate to each other to build the story, and how you might go through this process to develop your story.

Every story has a beginning, an ending, and something in between. In essence, your performance story is no different. Figure 1-2 shows the components I include and their relationship to one another.