| name | hypothesis-operationalization |
| description | Strategy: refine a working hypothesis into a precise, testable form |
| version | 1.0.0 |
| category | hypothesis-formation |
| type | strategy |
| campaign | hypothesis-formulation |
| tactics | ["falsifiability-audit"] |
| sops | ["operationalization","falsifiability-check","boundary-condition-specification","variable-identification"] |
| dependencies | {"tactics":["falsifiability-audit"],"sops":["hypothesis-formation-variable-identification"]} |
Hypothesis Operationalization
Refine a working hypothesis into a testable form: transform a vague directional idea or conceptual hypothesis into a precise, testable proposition in which every term has an operational definition and every variable has a measurement method.
When to Use
- A directional hypothesis already exists ("I think X may influence Y"), but it has not been made precise
- The hypothesis contains abstract constructs that need to be concretized into observable indicators
- Preparing to enter the research-design stage and needing a directly operationalizable version of the hypothesis
- A reviewer or collaborator gives feedback that "the hypothesis is too vague"
Not applicable: there is not yet any hypothesis direction → first use one of the other three strategies to generate a hypothesis, then return to this strategy to refine it.
Thinking Framework
Abstract → Concrete
Every term gets an operational definition, every variable gets a measurement method.
The five levels of operationalization:
- Construct clarification: what does each term in the hypothesis mean? (conceptual level)
- Variable identification: which are the operationalizable variables? (analytical level)
- Operational definition: how is each variable measured/manipulated? (methodological level)
- Boundary conditions: within what scope does the hypothesis hold? (applicability level)
- Falsifiability criteria: what observation would refute this hypothesis? (judgment level)
Common operationalization failure modes:
- Circular definition (defining X in terms of X) → an operational definition must reference observable behavior or measurement
- Mismatch between measurement and construct (operationalism gap) → must argue that the measurement instrument actually captures the construct
- Overly broad boundary conditions ("in all contexts") → must be specific about sample, context, and time range
Budget Gate
| Tier | Operationalization completeness | Variable measurement | Boundary conditions | Falsifiability |
|---|
| S | All abstract terms have operational definitions | All variables have draft measurement methods | Main boundary conditions specified | 1 falsification scenario |
| M |