Problem Statement
The artifact that names what a hackathon is asking participants to solve, written in advance, owned by a real stakeholder, and pre-tested before publication. Stub.
DraftLast updated 2026-05-03
A problem statement is the artifact that names what a hackathon is asking participants to solve, written in advance, owned by a real stakeholder, and pre-tested before publication. Murby's three-part test requires it to be clear (a participant understands the problem within thirty seconds without prior domain knowledge), actionable (addressable in the event's time window with available resources), and linked to impact (solving it matters to a stakeholder who will still care after the event ends). See problem-statements.