A business can spend weeks discussing a problem without agreeing on what needs to change. One person sees slow delivery, another sees insufficient staffing, and a third proposes new software. Each may be responding to a real frustration, yet the group is already comparing solutions to different questions. This Sean Bassik Consulting article explains how to write a short problem brief before choosing an intervention. A useful brief describes the current situation, its consequences, the evidence available, and the decision ahead. It gives a team a shared starting point without pretending that the cause is already known.
Describe the problem as an observable condition
Begin with what is happening in the business. Orders require repeated clarification, approvals wait in an inbox, or customers receive inconsistent updates. Avoid putting the proposed solution inside the problem statement. Saying that the company needs a new platform skips the question of why the current process fails. Specify where the issue occurs and who experiences it. Include a recent example that people can examine together. A statement grounded in observable work is easier to investigate because it invites evidence, while a broad claim about poor efficiency can mean almost anything to different members of the team.
Explain the consequence in operational terms
Show why the condition matters. A delayed approval may prevent a team from scheduling work. Repeated clarification may require employees to contact customers several times before beginning. Describe those consequences without exaggerating their scale. If the financial impact is unknown, identify the information needed to estimate it rather than inserting a confident number. Readers of Sean Bassik Consulting can use this step to distinguish an inconvenience from a priority that deserves concentrated attention. The consequence connects the problem to the business, making it easier to compare with other work competing for the same time and resources.
Define the boundary of the investigation
A problem brief should make clear what is included and what is outside the current review. You might examine one service line, one location, or one stage of the customer process. That boundary does not deny the existence of related issues. It creates a manageable area in which the team can learn something useful. Explain why the chosen scope is appropriate and note any important dependencies. If the issue changes substantially across locations, avoid combining them into one average description. A focused investigation can later expand, but an undefined one is difficult to complete or evaluate.
Gather a small set of representative examples
Choose examples that show how the problem appears in actual work. Include both difficult cases and cases that moved smoothly when possible. The contrast may reveal conditions worth investigating. Record what happened, when it happened, and which information is directly available. Keep opinions separate from records. A colleague’s explanation can be useful without becoming established fact. This Sean Bassik article recommends a practical evidence packet: enough detail to support discussion, with clear notes about limitations. Avoid overwhelming the brief with every available document when a few well chosen examples can identify the next question more clearly.
List possible causes as hypotheses
Invite the team to propose explanations, then label them as possibilities to examine. Delays could come from unclear ownership, missing information, uneven workload, or a dependency outside the team. Several causes may interact. Ask what evidence would support or weaken each explanation. This helps prevent the most confident voice from turning an early opinion into the official diagnosis. It also makes followup work purposeful. Instead of asking someone to investigate everything, assign a question that distinguishes between plausible causes. The brief should preserve uncertainty where uncertainty exists, because that is exactly what the investigation needs to resolve.
State the outcome you want to improve
Describe the future condition in terms of the work. You may want requests to arrive with complete information, approvals to have a clear owner, or customers to receive consistent status updates. Keep the outcome separate from a specific product or organizational change. Add a measure when you have a reliable way to observe it, and define how it will be collected. A target without a baseline may need refinement. Sean Bassik Consulting readers can begin with a clear direction and a plan to establish the current state before deciding what level of change is realistic.
Identify the people needed for the next decision
The people who experience a problem are not always the people who can change the process. Name the person responsible for the investigation, the people who can provide evidence, and the person who will decide what happens afterward. Explain what each needs to contribute. A frontline employee may clarify how exceptions are handled, while a manager may explain a constraint that is not visible in the workflow. Include those perspectives early. A brief becomes much more useful when it points toward a decision with an owner instead of ending with a general request for everyone to think about the issue.
Make the next step limited and reviewable
End the brief with a specific next action. That might be reviewing a sample of recent requests, observing a handoff, or comparing two versions of an intake form. Define what the action should reveal and when the team will review it. Avoid treating the first brief as permission for a large implementation project. Its purpose is to improve the quality of the next decision. If the investigation reveals that the original problem statement was incomplete, revise it. Learning that the issue is different from what you first believed is useful progress when it prevents a poorly matched solution.
Use the brief to keep discussion focused
Bring the document into planning conversations and update it as evidence changes. When someone proposes a solution, ask which part of the problem it addresses and what assumption it depends on. This keeps creativity connected to the actual task. Explore Sean Bassik Consulting for more business planning topics, and begin with one issue that repeatedly consumes attention. A clear brief does not need impressive language or a large presentation. It needs an observable problem, an honest account of its consequences, and a next step that moves the team from competing impressions toward a decision grounded in the work.