Why the brief matters more than the format

Most capstone programmes run into trouble at the brief stage, not the presentation stage. Teams spend weeks investigating a problem that was never precisely defined, then defend their work in front of executives who were not told what decision they were being asked to make. The result is a polished slide deck that nobody acts on.

The brief is the sponsor's job. It cannot be delegated to the programme team or left to emerge from the cohort. A sponsor who defines the challenge clearly, specifies what evidence teams can access, sets out who holds which decision rights and commits to a genuine executive review gives a capstone its practical weight. Without those four elements, the work is an exercise. With them, it is an investigation that could change something.

The four elements a brief must contain

The challenge. A good challenge statement describes a real organisational problem with enough specificity that a team can investigate it and enough openness that they can surprise you. It names the domain, the tension and the reason the problem has not already been solved. It does not prescribe the solution.

Access to evidence. Teams cannot prove a problem or test a solution without access to data, customers, frontline staff or internal processes. The brief should state explicitly what teams may access, who will grant that access and what is off limits. Vague access promises are one of the most common reasons capstone work stays superficial.

Decision rights. The brief should name who can approve a recommendation, who can pilot a solution and who can block progress. This is not about hierarchy for its own sake. It gives teams a realistic picture of the system they are working inside, so they can frame their recommendations accordingly.

The executive review. The review is not a graduation ceremony. It is the moment when a sponsor decides whether the work warrants action. The brief should describe what that review looks like, who attends, what teams are expected to defend and what the sponsor will do with the output. If the review carries no consequence, teams will sense it early and calibrate their effort accordingly.

A blank brief you can use

Capstone sponsor brief

  • Challenge statement: What is the problem, and why does it matter now? (Two to four sentences. Describe the tension, not the solution.)
  • Scope: Which part of the organisation, customer group or process is in scope? What is explicitly out of scope?
  • Evidence access: What data, people or processes may teams access? Who approves access requests? What requires separate clearance?
  • Decision rights: Who can approve a recommendation to proceed? Who can authorise a pilot? Who has the authority to block or redirect?
  • Success measure: What would a useful output look like? What would make the sponsor confident the work is worth acting on?
  • Executive review: When does it take place? Who attends? What are teams expected to present? What decision will the sponsor make at the close of the review?
  • Constraints: Budget, timeline, data sensitivity, regulatory limits or anything else teams need to know before they begin.

Fill this in before the programme launches. Share it with teams on day one.

A hypothetical example

The following is a hypothetical example, constructed to illustrate how the brief works in practice. It does not represent a real programme or client.

Imagine a regional logistics company whose operations director has noticed that customer complaints about delivery windows cluster in a specific corridor, but the relevant data sits across three systems that do not talk to each other. She wants to understand whether the problem is a routing issue, a communication issue or something in the handoff between the warehouse and the last-mile team. She does not yet know which.

A weak brief for this situation would read: Improve customer satisfaction in the delivery network. That is a direction, not a challenge. It tells teams nothing about where to look, what evidence exists or what a useful answer would look like.

A stronger brief would read: Customer complaints about missed or late delivery windows in the northern corridor have increased over the past two quarters. We do not know whether the root cause sits in routing, customer communication or the warehouse-to-carrier handoff. Teams should investigate the problem from the customer's perspective, map the process as it actually runs and identify where the breakdown occurs. The output should be a tested diagnosis and at least one recommendation the operations director can decide to pilot within the current quarter.

The brief then specifies that teams may interview customers who have raised complaints in the past six months, shadow two warehouse shifts and access the complaint log. It names the operations director as the person who can approve a pilot and the regional chief executive as the person who will attend the final review. It states that any recommendation involving a change to the carrier contract requires legal sign-off before it can proceed.

That brief gives teams a real problem, a realistic evidence base, a clear picture of who decides what and a review with a named decision-maker. The teams know what they are being asked to do. The sponsor knows what she will be asked to decide.

What sponsors get wrong

The most common mistake is writing a challenge that is really a solution in disguise. Implement a new customer communication platform is not a challenge; it is a conclusion. Teams handed that brief will spend their time justifying a decision that has already been made, which is neither useful for the organisation nor true to what a capstone is for.

The second mistake is promising access that has not been confirmed. If the brief says teams may interview frontline staff but the relevant manager has not agreed, teams will hit a wall in week two and lose time they cannot recover.

The third mistake is treating the executive review as a formality. When sponsors attend for thirty minutes, check their phones and offer no substantive response, teams notice. The review should be long enough for genuine challenge and short enough to stay focused. A prepared sponsor who is ready to make a decision at the close of the review changes the quality of everything that precedes it.

Before you sign the brief

A sponsor who can answer the following questions is ready to commission the work.

  • Can I describe the problem in two sentences without mentioning a solution?
  • Have I confirmed access with the people who control it?
  • Do I know who will make the decision at the end of the review, and am I prepared to make it?
  • Have I told the programme team what a genuinely useful output looks like?

If any of those answers is uncertain, the brief needs another draft. The time spent clarifying it before the programme starts is returned in the quality of the work that follows.

Written for this site.