SCIE90011: Crafting Strong Problem Statements

These flashcards cover the definition, characteristics, templates, and frameworks associated with crafting strong problem statements for product development.

Problem Statement

A concise, structured description of who has a problem, what the problem is, where/when it occurs, and why it matters, without specifying a solution.

Brief for Ideation and Concept Generation

A role of the problem statement where it frames the challenge to spark creativity and sets boundaries to fuel exploration without locking into a specific solution.

Reference Point for Evaluating Ideas

A function where the problem statement acts as the benchmark for judging whether an idea is actually relevant during brainstorming and concept evaluation.

Alignment Tool for Teams and Stakeholders

A resource that ensures researchers, designers, and decision-makers share the same understanding of a challenge and prevents solving different versions of the same problem.

User-centred

A characteristic of a strong problem statement that explicitly names the primary user or stakeholder and frames the problem from their perspective.

Contextualised

A characteristic that specifies where and when a problem occurs, including the setting, workflow step, and constraints, while avoiding overly general or global problems.

Solution-agnostic

A characteristic where the problem describes a need without embedding specific technologies like an "app", "AI", "sensor", or "platform".

Evidence-informed / plausibly grounded

A quality of a problem statement that reflects actual insights from needs finding and problem mapping rather than pure speculation.

Testable / discussable

A quality that allows a problem statement to be interrogated with users to see if it is an accurate description and contains assumptions that can be challenged.

User–need–impact template

A problem statement structure following the format: [User] in [context] struggles to [do X / achieve Y], resulting in [negative outcomes/impact].

"How might we…?" (HMW) framing

A template used to help [user] in [context] to [achieve desired outcome], given [key constraints].

Engineering style with metrics

A template stating: In [context], [user] currently experiences [problem], characterised by [quantitative or qualitative evidence], which leads to [impact], aiming to enable [desired change].

Scientific Method

A hypothesis-driven problem-solving framework involving observation, hypothesis, experiment, analysis, and revising theory.

Double Diamond

A framework focused on divergence–convergence cycles consisting of the steps: Discover, Define, Develop, and Deliver.

PDCA Cycle (Plan–Do–Check–Act)

A framework for continuous improvement involving planning a change, testing on a small scale, measuring outcomes, and implementing or iterating.

Lean Startup

An innovation framework for uncertainty that focuses on building a minimum viable product (MVP), measuring response, and learning from data to cycle rapidly.