iteration-design-vs-development

What problem does it solve?

It prevents teams from discovering major UX or product issues only after engineering has started building, when fixes become dramatically more expensive and slower.

Core Features & Use Cases

• Clarifies the split between design iteration and development iteration so stakeholders know which cycle is “healthy” and which signals late rework.
• Diagnoses the causes of excess development iteration (e.g., skipped prototyping, isolation between design and engineering, untested assumptions, premature high fidelity, spec-and-throw).
• Provides concrete reduction strategies like bringing engineering in earlier, prototyping with production primitives, testing with users at low fidelity, and defining “done with design” criteria.

Quick Start

Use this skill to review where your project is currently finding issues and recommend the cheapest next iteration step that will reduce likely rebuild during development.