problemdriven

Problemdriven refers to an approach in which understanding and framing a real-world problem guides the planning, design, and evaluation of a project or intervention. The emphasis is on solving a genuine user or stakeholder problem rather than pursuing predefined features or activities. The term is used across fields such as software development, product management, design thinking, education, and public policy.

At its core, problemdriven practice starts with a clear problem statement and success criteria, typically derived from stakeholder interviews, user research, or field observations. Requirements are elicited from the user’s perspective, and potential solutions are evaluated by how effectively they address the problem and the outcomes they produce. The approach is iterative and evidence-based, with prototypes, experiments, or pilots used to learn and adapt. Prioritization and decision-making are tied to impact on the identified problem rather than to internal agendas or technology pushes.

Applications vary by field. In software and product development, problem-driven discovery informs backlog prioritization and feature selection. In public policy and governance, it emphasizes diagnosing root causes before implementing interventions. In education, problem-based learning centers on solving authentic problems to develop domain understanding and transferable skills.

Advantages include greater relevance to users, improved alignment of effort with measurable impact, and increased adaptability to changing conditions. Challenges involve accurately framing the problem, avoiding scope creep, and measuring outcomes. Successful execution often requires cross-functional collaboration, clear governance, and ongoing stakeholder engagement. See also: problem-based learning, design thinking, requirements engineering, user-centered design.