A useful brief explains the operating problem, what has already been tried, the constraints, and what should be different when the work is complete.
Many consulting engagements start with the right intention and the wrong brief.
The result is predictable.
Consultants respond with generic proposals, generic approaches, and generic assumptions because the problem itself has not been defined clearly enough.
The quality of the brief often determines the quality of the consultant responses that follow.
Experienced consultants are not looking for a perfect brief.
They are looking for enough context to understand the problem, assess whether they can help, and determine whether their experience is relevant.
A useful consulting brief usually contains four things: the problem, what has already been tried, the constraints, and the definition of success.
1. Describe the Problem, Not the Aspiration
Many briefs begin with broad objectives:
“We want to grow faster.”
“We want to improve operations.”
“We need help with strategy.”
Those statements describe aspirations.
They do not describe problems.
A stronger brief explains what is happening today and why it matters.
For example: Weak: "We need help improving our sales performance." Stronger: "Our sales team is generating meetings consistently, but proposal-to-close conversion has fallen from 28% to 14% over the last two quarters."
The more specific the problem, the more relevant the consultant response is likely to be.
2. Explain What Has Already Been Tried
One of the most useful sections in any brief is often the shortest.
What has already been attempted?
For example:
- Previous consultants
- Technology implementations
- Process changes
- Team restructuring
- Training initiatives
- Pricing changes
Without this context, consultants risk recommending solutions that have already failed.
A brief that explains previous attempts saves time for everyone involved.
3. Share the Constraints
Consultants do better work when they understand the realities of the situation.
Relevant constraints might include:
- Budget limitations
- Timeline requirements
- Regulatory considerations
- Existing technology platforms
- Team capacity
- Geographic requirements
Constraints are not obstacles.
They are part of the problem definition.
The best recommendations are usually shaped by them.
4. Define What Success Looks Like
Many briefs describe deliverables.
Fewer describe outcomes.
There is a difference.
A strategy presentation can be delivered.
That does not automatically mean the engagement succeeded.
Instead, define what should be different when the work is complete.
For example:
“By the end of the engagement, we want a clear market-entry recommendation, a prioritised execution roadmap, and leadership alignment on the next 12 months of investment.”
Or:
“We want a redesigned hiring process that reduces time-to-hire and creates greater consistency across business units.”
The clearer the outcome, the easier it becomes to align scope, expectations, and success criteria.
A Simple Brief Structure
Most effective consulting briefs can be written in one page:
Background
What is happening?
Problem
What specifically needs attention?
Previous Attempts
What has already been tried?
Constraints
What realities must be considered?
Success Criteria
What should be different when the work is complete?
That is usually enough for an experienced consultant to determine whether there is a fit.
Why This Matters
A consulting engagement is easier to scope, price, and deliver when both sides understand the problem in the same way.
The brief becomes the foundation for everything that follows:
- Consultant selection
- Scope definition
- Commercial discussions
- Statements of Work
- Delivery expectations
A vague brief creates ambiguity.
A clear brief creates alignment.
Practical Takeaway
The strongest consulting briefs explain the problem, previous attempts, operating constraints, and the desired outcome. The more clearly the situation is described, the easier it becomes to identify the right expertise and define a successful engagement.
