Start with the situation, not the proposed fix
“We need an app” sounds like a problem, but it is already a solution. The underlying difficulty might be that people cannot find instructions, do not trust the instructions they find, or forget to act at the right time. Each possibility calls for a different response. Framing a problem means describing the gap between what happens now and what people need to happen, without deciding too early how to close it.
Begin with an observation you can explain plainly. For example: “New members often ask staff for help completing the first step of registration.” That is more useful than “Registration is broken,” because it identifies a group, an activity, and a point of friction. It still leaves important questions open. Which step causes trouble? What are people trying to accomplish? Is asking for help itself a problem, or only a problem when help is unavailable?
Separate evidence, assumptions, and interpretations
A good problem frame makes uncertainty visible. Write down what you have directly observed, what others have reported, and what you are inferring. A support team may know that questions about registration are common. It may suspect that the form is confusing. Those statements are related, but they are not interchangeable: people might also ask because they want reassurance before sharing information.
Look for a few concrete examples rather than relying only on a general impression. Walk through the process yourself, review recurring questions, or ask people to describe what they expected at the point where they paused. These steps do not guarantee a complete picture; the people you hear from may differ from those who leave without asking. Note what you cannot yet see, and avoid treating an early explanation as a settled cause.
Define who is affected and what matters to them
“Users” is often too broad to guide a decision. Someone joining for the first time may need clear instructions, while a returning member may care most about speed. Staff answering questions have a different experience again. Describe the people involved by their relationship to the task, not by an imagined average person. This can reveal competing needs before they become surprises during implementation.
Ask what a successful outcome would look like from each perspective. For new members, it might mean knowing what information is required and why. For staff, it might mean spending less time resolving preventable confusion. Also consider who could be inconvenienced by a proposed change. A shorter form, for instance, might feel easier to complete but create extra follow-up if it omits information needed later. Framing the problem well includes these trade-offs rather than hiding them.
Find the right boundary for the problem
A frame that is too narrow can lock you into a fix: “How do we rewrite the button label?” A frame that is too broad can make action impossible: “How do we make every interaction effortless?” Try a question that connects the observed difficulty to a meaningful outcome: “How might we help first-time members understand and complete registration without needing one-to-one guidance?” This permits changes to wording, sequence, support, or the process itself.
Check the boundary by asking what sits inside your ability to change. If the team cannot alter a required policy, it may still be able to explain that policy clearly or ask for fewer details at once. Constraints are useful when they are explicit, but they should not be mistaken for truths about what people need. Revisit the frame if it rules out plausible approaches before you have compared them.
Turn the frame into a testable starting point
Before brainstorming solutions, write a short problem statement: who is affected, what they are trying to do, where the difficulty appears, why it matters, and what remains uncertain. For example: “First-time members trying to register often seek help at the information-entry step. We need to understand whether the instructions, the requests for information, or both are causing hesitation so that members can complete the step with confidence.”
Use that statement as a working draft, not a verdict. Share it with people close to the task and ask whether it reflects their experience. Then choose a small way to learn more, such as comparing two explanations of the step or observing where people pause. If the results challenge the frame, revise it. The purpose of framing is not to delay action until everything is known; it is to make the next action more likely to teach you something useful.
