---
id: "prereq-traditional-design-workflows"
type: "prereq"
source_timestamps: ["00:07:55", "00:11:26"]
tags: ["design", "industry-knowledge"]
related: ["concept-specification-vs-execution", "entity-product-figma", "entity-product-claude-design"]
reason: "Required to understand why the AI's ability to skip wireframing and output HTML/UI mockups is a structural shift in the industry."
sources: ["s07-chatgpt-images"]
sourceVaultSlug: "s07-chatgpt-images"
originDay: 7
---
# Traditional UI/UX Design Workflows

## Why this is a prerequisite

To grasp the magnitude of [[concept-specification-vs-execution]] and the threat embodied by [[entity-product-claude-design]], a reader needs baseline familiarity with how UI/UX design is *traditionally* done.

## What you should know going in

- The role of tools like [[entity-product-figma]] as the central canvas for UI design.
- The handoff process from design → engineering (design specs, redlines, dev mode export).
- The iterative nature of wireframing → mockup → prototype → handoff.
- The cost structure of design teams (junior designers doing variations, senior designers owning systems).

Without this context, the magnitude of '**Claude Design** outputting editable HTML' or '**GPT Image 2** rendering a perfect UI mockup in one shot' cannot be fully appreciated — it sounds like a marginal speedup rather than a structural collapse of the industry's labor pyramid.
