- Home
- Research skills
- Business Problem to Research Question
Business Problem to Research Question
Turn a vague business problem into a decision-led, answerable research question set: objectives, information needs, population, hypotheses and outputs.
Free. Works on Claude, ChatGPT, Gemini or any assistant that accepts a skill file.
What this skill does
The method, encoded.
Most research that disappoints was lost before fieldwork began, at the point where nobody separated the question the business faces from the question a study can actually answer. The two get written as one sentence, the design follows it, and the report lands next to the decision rather than on it.
This skill makes the separation explicit and holds it. It locates the decision behind the request, including the uncomfortable cases: no decision, a decision already taken, or a strategy problem that evidence can inform but not settle. It then applies the test that governs everything downstream: what would you do differently depending on the answer?
From there it builds the ladder: business question, research question, sub-questions, information needs, population and unit of analysis, hypotheses where a prior basis exists, and the outputs that carry the answers. It screens out the four classes of question research cannot answer as posed (forecasts, counterfactuals, hypothetical behaviour, and causes with no comparison group), converts them where conversion is honest, and records what was lost.
The output is a Question Architecture document with a visible kill list, a ranked and scoped question set, and a statement of what the study will not answer. Sometimes the output is that no research is needed, which is a successful result.
Best used for
- Requests for research that arrive as a topic with no decision attached
- Briefs carrying more objectives than the budget or interview length can hold
- Deciding which stakeholder questions to cut, and defending the cut
- Screening out questions research cannot answer before a method is chosen
- Rebuilding an inherited tracker or reverse-engineering an existing study
- Establishing whether research is needed at all
Typical inputs
What you give it.
Original stakeholder request in the requester's own words, Clarified brief output from 01.01 Research Brief Interrogation, The decision the research is meant to serve, and its owner and date, Timing, budget order of magnitude and reporting deadline, Existing research and internal behavioural or operational data, Stakeholder list with what each wants to know
Typical outputs
What you get back.
Decision statement with owner, options and date, Business question and research question, stated separately, Ranked sub-question table (must / should / could), Conversion log for unanswerable questions, with what was lost, Information needs table with named sources, Population and unit of analysis with subgroup base requirements, Hypotheses where a prior basis exists, or an explicit statement that none does, Visible kill list with reasons and requesters named, Objectives and output artefacts, Statement of what the study will not answer
Method coverage
What the skill works through.
- What is the difference between a business question and a research question?
- Finding the decision behind the request
- The "what would you do differently" test
- Breaking a broad question into answerable sub-questions
- Four kinds of question research cannot answer
- From sub-questions to information needs
- Defining the population and the unit of analysis
- When to state a hypothesis, and when not to
- Killing questions that do not earn their place
- What the finished question architecture looks like
- When the honest answer is that no research is needed
Download
Free skill. One file.
Enter your email once. Every skill you download after that takes a single click.
How to install
Add the skill file and the five kernel protocols to a Claude Project, a ChatGPT Project, a Gemini Gem, or paste them at the top of any assistant conversation. Then give it your real research material, not a description of it.
Download skillQuestions
Common questions.
What is the difference between a business question and a research question?
The business question is the choice the organisation faces, and it contains the options: retain, restructure or withdraw. The research question is what a study must establish so that choice can be made, and it contains no decision verbs. If your research question still contains the word "should", the two have not been separated.
How do I write a good research question?
Start from the decision, not the topic. Write the decision in one sentence with at least two options and a date, then write the single question a study would have to answer for the decision owner to choose. Test it three ways: can it be answered by observing, measuring or listening to someone; does it presuppose its own answer; and would a finished report visibly answer it or not.
How many research objectives should a study have?
Fewer than a brief usually arrives with. Three to six sub-questions is a workable range for a single study. The constraint is physical rather than stylistic: interview length, fieldwork budget and analysis time are finite, and every question added takes capacity from another. Rank as must, should and could, and cut from the bottom until the set fits.
What is the difference between research objectives and information needs?
An objective is what the study commits to deliver. An information need is the specific thing that must be measured or understood to deliver it. "Understand price sensitivity" is an objective. "The price at which each user's chosen alternative becomes preferable, by user type" is an information need. Skipping the information needs layer is what produces questionnaires that miss the obvious.
What questions can research not answer?
Four classes. Questions about the future, because research measures the present and the recalled past. Counterfactual questions, which need a comparison that does not exist. Questions about what people would do, because stated intention ranks options well and predicts rates badly. And causal questions with no comparison group, which can only be answered as an account of what people believe caused something. Each can sometimes be converted into an answerable form, provided what was lost in the conversion is written down.
How do I know whether research is needed at all?
Ask what would be done differently depending on the answer. If every plausible answer leads to the same action, no research is needed. The same applies when the answer already exists in the organisation's own data, when a recent study answered it, when the decision must be made before fieldwork could report, or when the cost of the research exceeds the value of the decision.
What if the decision has already been made?
Say so, and do not produce a question set. Research commissioned to ratify a decision cannot change anything, and a polished set of objectives makes that harder to see rather than easier. The correct output is a short statement naming the decision, the evidence already relied on, and the fact that no result would change the course.
Should every research question have a hypothesis?
No. A hypothesis is worth stating where prior evidence or theory gives a genuine direction and a result could refute it. Where there is no prior basis, a hypothesis is a stakeholder hunch encoded into the instrument, and it will bias the design that follows. State that none is warranted rather than filling the section.
How do I decide which stakeholder questions to cut?
Score each on three things: whether the decision changes depending on the answer, whether it can be answered as posed, and whether it is already answered elsewhere. Anything failing one of the three is cut. Publish the cuts with the reason and the requester's name attached. Questions removed silently return at the debrief.
When should the research question be written?
After the brief has been interrogated and before any method, sample or instrument decision. Choosing a method first quietly redefines the population as whoever the method can reach, and that redefinition never appears in the final report.
The skill chain
Works well with.
Research where people already are.
Analyse it where you already work.
Yazi helps researchers conduct surveys, AI interviews and longitudinal research directly through WhatsApp.
%202.png)
