Problem Framing

Turn an approved intake route into a crisp problem statement and a small set of decision-ready options.

Context

Problem framing sits immediately after intake when routing is clear but the work is still underspecified. It absorbs the strongest part of brainstorming-style collaboration without collapsing the entry gate into a full design workshop.

Use it to answer:

• What problem are we actually solving?
• What boundaries must stay fixed?
• What are the viable directions?
• Which direction should the team carry into specification, research, or architecture?

Do not use it when the route is already well-scoped enough for downstream work, or when the user is already in implementation, debugging, or review.

Inputs