Short answer
Requirements definition turns a validated need into clear constraints and acceptance conditions without prescribing unnecessary solution details.
About Requirements definition
Requirements definition is the ability to translate a validated need into testable conditions, boundaries, and constraints that guide a solution.
Use this competency for
- Roles that clarify what a solution must achieve before or during delivery.
- Work where unclear constraints or acceptance conditions create rework.
Do not use this competency for
- Early discovery where the underlying need has not yet been validated.
Important distinctions
Solution design
Requirements definition states the conditions a solution must satisfy. Solution design determines how the solution will satisfy them.
Expectations by level
IC1
Individual contributor 1
With guidance, defines requirements for a bounded change with known users and constraints. Handles familiar cases and checks that acceptance conditions are testable.
Observable behaviors
- Writes acceptance conditions tied to the stated need.
- Documents known constraints, exclusions, and unresolved questions.
- Reviews requirements with delivery partners before work starts.
Examples
- For a form change, specifies valid outcomes and error conditions without choosing the interface layout.
- When a rule is unclear, records the open question and obtains a decision before refinement.
IC2
Individual contributor 2
Independently defines requirements for ambiguous workflows with multiple constraints. Resolves gaps with relevant partners and keeps requirements aligned as evidence changes.
Observable behaviors
- Maps normal, edge, and failure paths before delivery.
- Separates required outcomes from optional solution preferences.
- Updates acceptance conditions and decision records when scope changes.
Examples
- For a multi-step approval flow, defines permissions, exceptions, and completion conditions across roles.
- When a technical constraint changes, revises the requirement and confirms its effect on the user need.
IC3
Individual contributor 3
Sets requirements practices for a team across connected product areas. Handles conflicting constraints and enables others to define testable boundaries for complex changes.
Observable behaviors
- Defines shared standards for requirement quality and traceability.
- Facilitates decisions when legal, technical, and customer constraints conflict.
- Reviews complex requirements for gaps, contradictions, and unnecessary prescription.
Examples
- For a change spanning several workflows, aligns teams on shared terms and end-to-end acceptance conditions.
- When two constraints cannot both be met, records the decision owner, tradeoff, and revised boundary.