The Secret of Warren Buffett’s Business Writing Style

‘The business schools reward difficult complex behavior more than simple behavior, but simple behavior is more effective.’ Warren Buffett.


15 White Paper Templates for only $19.99

Download Template

How to Write an Executive Summary that Generates Interest

Your Executive Summary should excite the reader and help them understand the key results and conclusions in your business document, whether it’s your business proposal, business plan, annual report, case study or white paper.

Looking for inspiration?

Read the Annual Reports written by Warren Buffett and you’ll see how he does it. You know he has confidence in his company. He highlights the goods news in a nice understated way and delivers the less pleasant results with the same even tone.

Executive Summary Definition

Here’s one definition from The Handbook of Technical Writing, “An executive summary is to consolidate the principal points of a report in one place. It must cover the information in the report in enough detail to reflect accurately its content but concisely enough to permit an executive to digest the significance of the report without having to read it in full….”

Learn More: 21 Executive Summary Writing Tips

Characteristics of a Well-Written Executive Summary

While this is a business document in the tradition sense, you must still find ways to stimulate the reader’s interest, make them want to turn the page and take some action.

  • Executive summaries must be original.
  • Executive summaries must not be cut-and-pastes extracts from the main document.
  • Executive Summary should provide unique information not contained anywhere else.
  • Executive summaries are standalone documents. The reader, for example, an investor, should be able to grasp your over-arching aims without having to read the entire document.

Documents That Require Executive Summaries

Some business documents require summaries, others don’t. Write an executive summary for the following types of documents:

  • Grant Applications
  • Standards
  • System Design Documents
  • Technical Reports
  • Training Plans
  • White Papers

Documents That Do Not Require Executive Summaries

You do NOT need to write an Executive Summary for shorter documents or certain technical publications, such as:

  • Functional Specifications
  • Meeting minutes
  • Release Notes
  • Status Reports
  • User Manuals
  • Workshop reports

Learn MoreHow to Write the Executive Summary for Business Plans

Executive Summary Format & Guidelines

These are guidelines for your Executive Summary. They’re not set in stone, so adjust where necessary. The summary should cover the:

  • Purpose
  • Scope
  • Methodology
  • Results
  • Conclusions

In general, you can write it as follows:

  • First paragraph answers: “What is this document about?”
  • Summary answers “How did you get the information?”
  • Expand on the Software Development process (if applicable)
  • Facts
  • Results
  • Conclusions
  • Findings Note: present facts in tabular format.
  • Recommendations

Learn More: How to Write the Conclusion Section of your Business Plan

What doesn’t go in the Executive Summary?

Other information that doesn’t go in the Executive Summary includes:

  • Acknowledgments
  • Background data
  • Cross-references
  • Footnotes
  • Industry updates
  • Justifications
  • Objectives
  • Project history
  • References

Remember to close your executive summary will a strong summary statement. This must persuade the reader that your business is a winner and the only way to do this is to turn the page and learn more about your company.

Learn More: How to Write Your First Executive Summary

Final Tips for Writing the Business Plan’s Executive Summary

Provide a summary. The business plan itself gives the financial details.

  • Use strong and positive language.
  • No more two pages long. Don’t pad your business plan’s executive summary with fluff.
  • Generate interest by enticing your reader to read the rest of the business plan, not tell him everything.
  • Read it aloud. Does it read well or sound artificial? Is it clear and succinct?
  • Adjust the executive summary for your respective audience. For example, if you want to attract investors, focus on the opportunity your business provides investors and why this opportunity is so special.
  • Put yourself in your readers’ shoes. Does the executive summary really make you feel excited? If not, why?

First impressions count, right?

Learn More: Long v Short Executive Summaries for Business Plans

The Executive Summary of any business document is the first impression you make on the reader. If your business plan’s executive summary is poorly written, dull, or cut/pasted together it will hardly get noticed and the effort you put into the rest of the document won’t be seen.

Instead, set aside two or three hours and write the best Executive Summary you can. Challenge yourself to write three hundred words that excite you, generate interest, and paint a picture of your company. People want to read about other people. Don’t forget the power of human interest.

In the end, they’re going to do business with you – not your product.

The final word goes to Warren. Here’s his take on gold, “It gets dug out of the ground in Africa, or someplace. Then we melt it down, dig another hole, bury it again and pay people to stand around guarding it. It has no utility. Anyone watching from Mars would be scratching their head.”

Make sense?

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan