Not every problem is a design problem: four questions to ask before your next sprint

Purpose Leaders routinely commit their organizations to a problem-solving logic, most visibly the design sprint, without asking whether the problem rewards it. The paper argues that design thinking’s uneven returns reflect poor fit, not a flawed method, and offers leaders a way to decide, before committing resources, when design-oriented reasoning is more likely to outperform analytical reasoning. Design/methodology/approach This conceptual paper draws on contingency theory and ecosystem research to derive a four-condition diagnostic that locates a challenge by its structural features rather than a firm’s cultural readiness, illustrated through managerial scenarios. Findings Design-oriented reasoning earns its place when four conditions hold: value is experiential, not functional; the problem is still being discovered, not well-defined; the environment is volatile, not stable; and delivery requires aligning independent actors outside the firm’s authority. The conditions are cumulative; the fewer that hold, the stronger the case for analytical reasoning. Practical implications The diagnostic gives leaders a structured pre-deployment judgment aid applicable in minutes, and a discipline for handing off from design-oriented to analytical reasoning as problems mature. Originality/value The paper shifts the unit of analysis from firm-level readiness to the problem’s structural conditions, reframing the deployment of design thinking as a matter of leadership judgment. The framework is offered as an actionable synthesis of established contingency insights, structured for managerial judgment, rather than as a validated predictive test.