The Project Brief: What to Write Before the Charter
The moment someone says "we should do a project," organisations often reach for the most comprehensive tool they know: the business case or the project charter. Both are valuable documents, but both assume a level of definition that usually does not exist at the start of an initiative. The result is hours or days of analysis invested in projects that could have been evaluated -- and in some cases stopped -- in under an hour with a much simpler document.
The project brief sits between the initial idea and the formal project structure. It is short, deliberately incomplete, and designed to answer one question: is this initiative worth investing in further definition? When used well, it saves significant effort by surfacing poor project ideas early, before teams have built attachment to them, and before governance processes have created momentum that is hard to stop.
What Belongs in a Brief
A project brief has six components. The first is a problem statement: a clear, specific description of the problem being solved or the opportunity being pursued, written in terms of its impact on the organisation or its stakeholders. A good problem statement does not assume the solution -- it describes what is broken or missing, without prescribing the fix.
The second component is a proposed solution in one paragraph. This is not a detailed design -- it is a directional statement about the approach the team intends to explore. Keeping it to one paragraph forces the initiator to be clear about what they are actually proposing, rather than deferring the hard thinking to the business case.
The third is rough scope: what is in and what is out. Even a brief description of boundaries -- which business units, which systems, which geographies, which time period -- prevents scope conversations from starting from scratch every time the initiative is discussed. It also makes gaps visible early, before scope grows by default rather than by decision.
The fourth component is key assumptions. Every project initiation rests on assumptions that, if false, would change the analysis materially. Surfacing them in the brief allows reviewers to challenge them early, when changing course is inexpensive. Hidden assumptions that survive into the charter or business case tend to become embedded in the plan, making them harder to surface and more costly to correct.
The fifth is a rough order-of-magnitude cost and time estimate. Not a detailed estimate -- that requires definition that does not yet exist -- but a range that allows decision-makers to compare the initiative against competing priorities and available budget. A project that will likely cost between $500,000 and $2 million and take 12 to 18 months to deliver is a fundamentally different investment decision than one that will cost $50,000 and be done in a quarter.
The sixth and final component is who is asking and who will approve. Documenting the initiator and the decision authority closes the accountability gap that often opens in the space between an idea and a funded project. It also ensures the brief reaches the right audience -- someone with the authority and context to make a real go/no-go decision.
When a Brief Is Enough vs. When You Need More
A brief is sufficient when the initiative is small enough that its scope can be defined in days, when the problem is clear and the solution approach is not contentious, or when the primary purpose of the document is to get a go/no-go decision before any further investment is made. Internal improvement projects, small system enhancements, and limited-scope process changes often belong in this category.
A full business case is warranted when the investment is large enough to require formal capital approval, when there are multiple competing solution options that need rigorous comparison, when the benefits case requires detailed financial modelling, or when the organisation's governance processes require it. The brief does not replace the business case for complex initiatives -- it precedes it, ensuring that effort is only invested in business cases for initiatives that have survived basic scrutiny.
How a Brief Reduces Wasted Effort
The most expensive projects are the ones that are stopped after significant effort has been invested. A detailed business case for a project that ultimately fails the gate review represents weeks of analytical work that produced no value. The brief is designed to surface the most common reasons projects fail early review -- unclear problem, implausible solution, unaffordable cost, unavailable sponsorship -- at minimal cost. A brief that takes two hours to write and results in a project being stopped has paid for itself many times over.
Organisations that use the brief well find that it also improves the quality of initiatives that do proceed. The discipline of writing a clear problem statement and articulating key assumptions early tends to produce better-scoped projects, with more realistic expectations and more clearly defined governance. The brief is not just a gate document -- it is the first act of project thinking, and it sets the tone for what follows.
XNM Consulting helps organisations build project initiation frameworks, from brief templates through to governance structures that reduce wasted effort and improve delivery success rates. Learn more about our program and project delivery services.