Article · Liz Eversoll
Shift left, hard
Traditional shift left moves work earlier. Shift left hard moves the standard itself, into the tools producing the work.
Inside this article
- Why the principle holdsEarly problems cost less to fix.
- Why work moved rightSix hands, and a translation at each one.
- Shifting the standardThe rules go into the tools.
Every handoff was a translation. Every translation cost time and lost something the original person meant.
This is a summary. Read the full article
Why the principle holds
Shift left means doing something sooner rather than later, because catching a problem early is dramatically cheaper than catching it late. Boehm and Basili quantified it: a defect caught during requirements and design can be up to 100 times cheaper to fix than the same defect caught after release on a large system, closer to five times on a smaller one. Larry Smith named the discipline in 2001. The logic has held for over twenty years because it is true.
Why work has always moved right
Someone who runs the business — a claims manager, a plant supervisor, a sales ops lead — knows exactly how the work should go. They could not say it in a language a designer, an engineer, or a compliance reviewer could act on, so the idea moved right instead: to a business analyst, to a product manager, to a designer, to an engineer, to QA. Every handoff was a translation. Every translation cost time and lost something the original person meant.
The idea moves right
That chain was never incompetence. It existed because turning an idea into something built required skills the person with the idea did not have.
What shifting the standard changes
Moving the work left only helps if the standard moves with it. Governed rules, patterns, accessibility requirements, and business logic go into the tools producing the work, so the output is built correctly from the start instead of corrected at the end. Fewer handoffs, less rework, fewer places for the truth to get lost between one stage and the next.
Moves the work earlier
- Does something sooner rather than later.
- Catching a problem early is cheaper than catching it late.
ResultOnly helps if the standard moves with it.
Moves the standard into the tools
- Governed rules, patterns, accessibility requirements, and business logic.
- Applied by the tools producing the work.
ResultBuilt correctly from the start. Fewer handoffs, less rework.
Read the full article
This page is a summary. The full article has the complete argument and every example.
Related
Code
A coding agent drifts from the standard in a single session, then works from the governed contract instead.
Design
Tokens and component contracts govern the generated screen, so the design system stops being a suggestion.