Ship/Sink

Design Review
Checklist

This checklist ensures designs meet user needs, standards, and best practices before implementation. Thorough reviews catch issues early, saving development time.

Designs must solve real user problems and support objectives. This ensures relevance and effectiveness.

Sub-actions:

Pitfalls:

  • Misalignment leads to unusable products.
  • Ignoring goals wastes effort.

Adhering to the design system maintains visual and functional consistency. This speeds development and improves maintainability.

Sub-actions:

Pitfalls:

  • Inconsistencies confuse users.
  • Custom elements increase tech debt.

Designs must work across devices for broad accessibility. This prevents user frustration on different platforms.

Sub-actions:

Pitfalls:

  • Non-responsive designs alienate mobile users.
  • Overlooking breakpoints causes layout issues.

Meeting accessibility standards ensures inclusivity. This avoids legal issues and expands user base.

Sub-actions:

Pitfalls:

  • Poor accessibility excludes users.
  • Non-compliance risks lawsuits.

Testing reveals interaction issues early. This leads to more intuitive designs.

Sub-actions:

Pitfalls:

  • Untested designs lead to rework.
  • Biased testing misses real issues.

Consistency with brand reinforces identity. This builds trust and recognition.

Sub-actions:

Pitfalls:

  • Brand misalignment confuses users.
  • Inconsistencies dilute brand strength.

Complete documentation enables smooth development. This reduces questions and delays.

Sub-actions:

Pitfalls:

  • Incomplete handoffs cause misimplementations.
  • Wrong formats slow development.

Explaining decisions provides context for future reference. This aids maintenance and onboarding.

Sub-actions:

Pitfalls:

  • Undocumented rationale leads to arbitrary changes.
  • No links weaken justifications.

Ongoing testing validates the final product. This ensures the design translates well to implementation.

Sub-actions:

Pitfalls:

  • No plan means missed opportunities for improvement.
  • Poor scripts yield unreliable results.

How to Use

Use in design critique sessions; check each item and note issues for iteration.

Expected Outcomes

Polished, user-friendly designs ready for efficient development.