AlignChangesToFindings [rule] v1.0.0

Proposed design changes must be cross-referenced against documented pain points, validated patterns, and known success metrics before finalizing direction. Any conflict between the proposal and existing research must be surfaced explicitly.

Severity

warning

Applies When

Project has research documents such as usability study findings, experiment outcomes, or analytics reports.

Verify By

Cross-reference the proposed change against documented pain points and validated patterns. Note any conflicts in the design rationale. A proposal that ignores available research must be sent back.

AlignChangesToFindings [rule] v1.0.0

Proposed design changes must be cross-referenced against documented pain points, validated patterns, and known success metrics before finalizing direction. Any conflict between the proposal and existing research must be surfaced explicitly.

Severity

warning

Applies When

Project has research documents such as usability study findings, experiment outcomes, or analytics reports.

Verify By

Cross-reference the proposed change against documented pain points and validated patterns. Note any conflicts in the design rationale. A proposal that ignores available research must be sent back.

Rationale

Ignoring prior research wastes its investment and reintroduces solved problems. A design change that contradicts a validated finding is riskier than one that extends it — that risk must be named and accepted deliberately.

Severity

warning

Applies When

Project has research documents such as usability study findings, experiment outcomes, or analytics reports.

Verify By

Cross-reference the proposed change against documented pain points and validated patterns. Note any conflicts in the design rationale. A proposal that ignores available research must be sent back.