Over time I've constructed the following general outline for creating executive summary presentations.
- Overview
- Case for change (drivers: business & IT)
- Current State (key observations and issues)
- Future State (alternatives & recommendation)
- Gap Analysis (current, recommended, and future capabilities)
- Roadmap
- Summary (Key... takeaways, recommendations, next steps, measures of success)
Why is this important to our business? How is this different than how we develop today? Why now? What new skills and technologies are required? What devices and standards should we target? Is context-awareness important? Where will applications be deployed? What enterprise capabilities are required to support mobile? What is the roadmap? How is this related or not related to the portal? Are we targeting internal apps, external apps, or both? Who will consume the apps and with what? How does this ......
Here is my general guidance in regards to solutions architecture: Leverage what we have first Gather facts, not opinions when assessing solutions Avoid making early assumptions Prove that issues are real before escalating concerns Present issues or concerns within proper context If prototypes reveal concerns, consider alternative solutions ......