- It requires a special skill
- Strategy documents are superior to check lists
- Results don't need to be in context
- Execution only needs to be outlined
- Data should be someone else's problem
No contextualization of the results? Kidding... surely? A summary may be sufficient but then a summary contains a "summary" of the explicitly rendered results. Wait though. There are more graphs than text. That must count right? I mean each has a useful description like "the transactions per second graph shows the number of transactions per second"... epic.
Baseline, load and soak will be run. That is an execution plan? Sure. Short and to the point. What though will happen as time gets shorter and problems refuse to get resolved? Contingencies? Eerie.
Data obviously can't belong to someone else. Surreal.
Skills. My current view is... that I need more input here although its probably QED.