---
id: "prereq-traditional-sdlc"
type: "prerequisite"
source_timestamps: ["00:08:16"]
tags: ["sdlc", "context"]
related: ["concept-the-translation-layer", "claim-mockup-extinction"]
reason: "Understanding the baseline inefficiency of the PM → Designer → Engineer handoff is necessary to appreciate why Claude Design is disruptive."
sources: ["s05-claude-design-30min"]
sourceVaultSlug: "s05-claude-design-30min"
originDay: 5
---
# Prerequisite — The Traditional Software Development Lifecycle

## What You Need to Know
The speaker assumes the audience understands how software is traditionally built:

1. A **Product Manager** writes a spec (PRD).
2. A **Designer** interprets that spec into a static visual mockup in [[entity-product-figma-d5]].
3. An **Engineer** translates that visual mockup into front-end code (HTML/CSS/React).

Each handoff introduces translation losses and coordination overhead.

## Why This Matters
Without this baseline understanding, the significance of *collapsing the translation layer* — see [[concept-the-translation-layer]] — and generating code directly from a prompt is lost. The disruption story in [[claim-mockup-extinction]] presupposes that you know what is being disrupted.