| Date | Name | Role | Version | Comments |
|---|---|---|---|---|
| @January 23, 2023 | John Doe | Founder | 0.1 | Initial draft |
| Name | Project Role | Contact for |
|---|---|---|
| John Doe | Project lead | Clarifications on user flow, product design & strategy. |
| Isaac Hobb | Tech | Anything front end, back end or data engineering |
| Emma Crosby | Marketing & Admissions | Anything around email drips for admissions |
| Justice Hill | Onboarding & Experience | Anything around email drips for activation |
Why is it important? A condensed version of this very document that provides a high-level overview of the project's goals, scope, and requirements. It usually includes key information about the project's objectives, stakeholders, timeline, budget, and expected outcomes. The purpose of an executive summary in a BRD is to provide a clear and concise summary of the document's content to decision-makers and stakeholders, enabling them to quickly understand the main objectives and requirements of the project. The executive summary should be written in a way that is easily understood by both technical and non-technical readers.
*Few executive summary examples *here**.
<aside> <img src="/icons/light-bulb_gray.svg" alt="/icons/light-bulb_gray.svg" width="40px" /> Get to this section after you have completed this document to summarise everything here.
</aside>
it is best to be clear and concise, highlight key problems and opportunities, define the project scope, provide relevant context, and use visuals if appropriate. The language, formatting, and style should be consistent throughout the document to help stakeholders easily follow the information and understand its relevance.
The objectives of the project should be defined using the SMART criteria, which require them to be specific, measurable, achievable, relevant, and time-bound.