Impact Matrix Reference¶
This matrix defines how different types of incoming information affect design artifacts and which phase to return to.
Primary Impact Matrix¶
| Change Type | Severity | PRD Impact | Prototype Impact | specs Impact | Return Phase |
|---|---|---|---|---|---|
| usability_test | critical | None | HIGH | None | pd-3-prototype |
| usability_test | major | None | MEDIUM | None | pd-3-prototype |
| usability_test | minor | None | LOW | None | Continue pd-4 |
| stakeholder_feedback | scope | HIGH | HIGH | HIGH | pd-2-prd |
| stakeholder_feedback | ui | LOW | HIGH | LOW | pd-3-prototype |
| stakeholder_feedback | flow | MEDIUM | HIGH | MEDIUM | pd-3-prototype |
| stakeholder_feedback | minor | None | LOW | None | Continue |
| user_research | invalidating | HIGH | HIGH | HIGH | pd-1-research |
| user_research | supplementary | MEDIUM | MEDIUM | LOW | pd-2-prd |
| user_research | minor | LOW | LOW | None | Continue |
| tech_constraint | breaking | HIGH | HIGH | HIGH | pd-2-prd |
| tech_constraint | limiting | MEDIUM | MEDIUM | MEDIUM | pd-3-prototype |
| tech_constraint | informational | LOW | LOW | LOW | Continue |
| scope_change | addition | HIGH | MEDIUM | HIGH | pd-2-prd |
| scope_change | removal | HIGH | MEDIUM | HIGH | pd-2-prd |
| scope_change | reprioritization | MEDIUM | LOW | MEDIUM | pd-2-prd |
| market_intel | critical | MEDIUM | LOW | LOW | pd-1-research |
| market_intel | informational | LOW | None | None | Continue |
| bug_report | critical | None | HIGH | None | pd-3-prototype |
| bug_report | major | None | MEDIUM | None | pd-3-prototype |
| bug_report | minor | None | LOW | None | Continue |
| design_update | major | None | HIGH | None | pd-3-prototype |
| design_update | minor | None | MEDIUM | None | pd-3-prototype |
Impact Level Definitions¶
HIGH Impact¶
- Requires significant rework
- Affects core functionality or user experience
- Cannot proceed without addressing
- May invalidate previous work
MEDIUM Impact¶
- Requires noticeable changes
- Affects important but non-critical aspects
- Should be addressed before next phase
- Previous work partially applicable
LOW Impact¶
- Minor adjustments needed
- Polish or refinement level
- Can be addressed alongside other work
- Previous work mostly valid
None¶
- No impact on this artifact
- No changes required
Severity Guidelines¶
Critical¶
- Blocks release or deployment
- Safety, legal, or compliance issue
- Fundamental flaw in approach
- Complete user journey blocked
Major¶
- Significant usability problem
- Important feature missing or broken
- Major scope change required
- Multiple user tasks affected
Minor¶
- Polish or refinement item
- Minor user confusion
- Nice-to-have suggestion
- Single edge case affected
Phase Return Logic¶
Return to pd-1-research¶
When: - User personas found to be incorrect - Target audience changed - Core user needs invalidated - Competitive landscape fundamentally shifted
Return to pd-2-prd¶
When: - Scope changes (features added/removed) - Requirements changed - Technical constraints affect features - Timeline/priority changes
Return to pd-3-prototype¶
When: - UI/UX issues identified - Visual design problems - Interaction patterns need rework - Component-level changes needed
Continue Current Phase¶
When: - Minor issues that don't block progress - Informational inputs (good to know) - Items that can be batched for later - Polish items for future iterations
Aggregation Rules¶
When multiple items have different recommendations:
- Earliest phase wins: pd-1 < pd-2 < pd-3 < pd-4 < continue
- Higher severity takes precedence: critical > major > minor
- Scope changes always require PRD review: Even if UI issues exist, scope changes go to pd-2 first
- Safety/compliance is always critical: Regardless of other factors
Examples¶
Example 1: Usability Test Failure¶
- Input: usability-test-results.pdf
- Type: usability_test
- Finding: Users can't complete checkout (40% completion)
- Severity: critical
- Lookup: usability_test + critical → pd-3-prototype
- Result: Return to pd-3-prototype
Example 2: New Feature Request¶
- Input: stakeholder-feedback-cto.md
- Type: stakeholder_feedback
- Finding: CTO wants bulk upload feature
- Severity: scope (addition)
- Lookup: stakeholder_feedback + scope → pd-2-prd
- Result: Return to pd-2-prd
Example 3: Minor Polish Item¶
- Input: user-feedback-colors.md
- Type: stakeholder_feedback
- Finding: User prefers different button color
- Severity: minor
- Lookup: stakeholder_feedback + minor → Continue
- Result: Continue current phase, log for later
Example 4: Multiple Items (Aggregation)¶
- Item 1: Usability test failure → pd-3-prototype
- Item 2: New feature request → pd-2-prd
- Aggregation: pd-2 < pd-3, so → pd-2-prd (will cascade to pd-3)