Problem Framing Guide: turning a curiosity into a testable research scope
Problem framing is the skill of turning a vague curiosity or operational pain into a bounded question that can be investigated. Good framing saves time, improves experiment design, and makes results easier to interpret.
Core elements of a strong problem frame
- Context: What is the environment, product, or process where the problem appears? Who is affected?
- Observed outcome: What specifically are you trying to change, measure, or understand?
- Scope and boundaries: Where does the question apply, and where does it not? Be explicit about constraints such as population, equipment, and timeline.
- Assumptions: List what you are taking for granted. These become the first things to test.
- Success criteria: How will you know the research found something useful? Define measurable signals or decisions enabled by the outcome.
Common problem-frame patterns (with examples)
Exploratory: find hidden opportunities
Example: "Our lab assays are inconsistent week-to-week. Where is most variability coming from, and can we reduce it by changing a simple step?"
Comparative: choose between options
Example: "Does automated sample prep give similar precision to manual prep for this assay within acceptable cost?"
Impact-driven: link research to a decision
Example: "If we can reduce false positives by X%, will that cut follow-up testing costs enough to justify automation?"
Practical framing workflow
- Write a one-sentence problem statement (context + observed outcome).
- List at most three assumptions you rely on.
- Define up to two measurable success criteria tied to decisions or impact.
- Identify who cares and who decides (use the Stakeholder Mapping tool in this resource).
- Do a rapid evidence scan to find existing answers or gaps.
- Produce two candidate scoped questions you could test in a pilot.
How to avoid typical framing mistakes
- Vagueness: Avoid broad aims like "improve performance" without a metric and boundary.
- Hidden assumptions: Surface them as testable statements rather than treating them as facts.
- No decision in mind: If the research won’t change a decision or action, it’s often low priority.
- Overly ambitious scope: Prefer a small, defensible slice you can test quickly.
Questions to guide a team discussion
- What will we stop doing if this research shows X?
- Who will use the results, and what decisions will they make?
- What evidence would convince a skeptical stakeholder?
Next practical step
Use the Stakeholder Mapping form to capture key people and the Prioritization Worksheet to score candidate questions. Then draft a one-page brief using the template in this resource to request time and resources.
Discussion
Comments and conversation will live here.