The executive summary should provide a snapshop of the key features of the business case, but most importantly it should present a short and compelling argument for the business case, addressing briefly the What?, Why?, and How? of the business case.
- It may be easier to write the Executive summary after completing the rest of the business case
- Developing an elevator pitch might help you to identify the the main messages you want to convey. See these example pitches from digital preservation practitioners at SPRUCE mashup events.
SCAPE Project Case Studies
Example text from SCAPE Project case studies with explanatory discussion notes.
Use this to see how the key aspects of a business case can be articulated within a particular use case.
Jpylyzer executive summary
An example executive summary.
Mass digitisation projects generate millions of master images that must be stored in multiple locations to ensure their longevity. At this scale, storage costs (even in the short term) are considerable. JPEG2000 technology offers the potential to significantly reduce the size of digitised masters for a negligible loss of quality. Using the JP2 file format to store digitised masters therefore provides an attractive alternative to the conventional choice of TIFF. There are however considerable digital preservation concerns about JP2, which could put the longevity of digitised collections at risk. This business activity will put in place a quality assurance process that will validate JP2 masters, mitigate preservation risks associated with their usage, and as a result enable considerable storage cost savings. By reducing initial storage costs by around 60%, resources will be freed up for the digitisation of one million additional pages.
Discussion notes explaining the approach in developing the Executive Summary example, above.
The summary above explains the context and current situation before describing the change to business processes that will be implemented. It focuses on the key elements for a business case of this kind: benefits, costs and risks. The text uses some technical language (mention of JP2 and TIFF) and this may be deemed too technical for the audience, in which case it may be better to refer to the technologies in general terms without specifically naming them.
See the full case study for more information: A business case for Jpylyzer