Digital Requirement Refinement

Problem

Business requirements often start as vague statements such as “too slow,” “hard to use,” or “we need a new system.” Without a clear role, scenario, constraint, and measurable impact, discussions can jump straight to product shape or vendor selection before the business effect, reproduction path, and acceptance evidence are established.

How It Works

The skill turns vague asks into a pain-point statement built on who encounters what problem in which scenario, with what negative business impact. The workflow includes:
- Collect information: fill in role, scenario, issue, impact, plus job duty, timing, environment, and constraints
- Identify gaps: detect missing or ambiguous elements, and separate minor inconvenience from business disruption
- Guide refinement: ask targeted questions such as error rate, time cost, network conditions, and manual workarounds
- Generate description: produce an objective, verifiable statement that does not preset a solution
- Validate effectiveness: check verifiability, severity, and problem focus, rather than jumping to “replace the system”

Boundaries

It is useful for requirement clarification, pain-point definition, project review, and pre-solution discussion; it does not replace architecture design, ERP selection, development scheduling, or implementation planning, and it cannot invent missing quantitative data.