Shorter timelines usually trade away sample size or coverage
Aliases: timeline compression · scope-time trade-off · research constraint
What it is
A scope–time trade-off occurs when a deadline moves forward without more resources, requiring fewer participants, segments, tasks, contexts, rounds, or analytic depth. The cost is not generic lower quality; particular claims lose precision, coverage, or explanatory support.
Why it happens
Recruitment and sessions have dependencies that cannot all be parallelized, and synthesis requires accumulated evidence. A request to go faster hides cuts in overtime, convenience sampling, or skipped review. Each cut produces a different bias, so reductions should target what matters least to the decision rather than thinning every stage equally.
Studying it
Compare original and compressed designs on sample, segments, tasks, settings, review, and supported claims. Track cycle time, missed issues, rework, and decision changes to test whether compression saves total time. Sensitivity analysis can show how removing a segment or task changes conclusions.
Where it stops holding
Coverage is not the only route to speed: established panels, parallel teams, automated cleaning, and narrower questions can improve efficiency. Tools cannot remove waiting, interpretation, or ethics review. A narrow study can remain rigorous if its claim narrows too; the error is preserving a broad conclusion while hiding the cut.
Applying it
- Name every removed coverage dimension and its inferential consequence.
- Narrow the question and decision before cutting critical segments or review.
- Retain tasks and comparisons most likely to change the decision; queue the rest.
- Narrow report claims accordingly and evaluate compression through downstream rework.