Skunk Works and the XP-80: speed from clarity

What happened

Kelly Johnson's unit at Lockheed built the XP-80 in 143 days. The team worked to a set of 14 rules that shaped how it was organised and how it worked with its customer.

Those rules described a small, empowered team, requirements agreed with the customer up front, simple records, and close contact between engineers and the customer.

What was found

The published history of the unit presents its pace as a product of how the work was set up. Decisions sat with a small team, the customer agreed what was needed at the start, and records were kept simple enough to stay current.

Nothing in that account suggests rigour was traded for speed. The rules removed friction around the engineering, rather than removing the engineering.

Engineering lesson

Schedule pressure is often treated as a reason to compress verification or defer documentation. The Skunk Works account points the other way: time is saved when the requirement is agreed early and the people who own it can talk to the people who need it.

Simple records are not the same as no records. A record that is light enough to keep up to date is more useful than a complete one that lags the design.

The practice this points to

Agree requirements with the customer before design work scales, and keep the customer close enough to resolve questions quickly.

Keep the team that owns a requirement small and accountable, and keep the record of decisions simple enough that it stays true.

Where Kelvora fits

Kelvora is a requirements and assurance platform that keeps requirements, decisions and their rationale in one lightweight, current record. It is designed to help a small team keep agreement with the customer visible as the design moves, with engineers in control of every change.

Sources

1. Lockheed Martin, Skunk Works history.
2. Ben Rich & Leo Janos, “Skunk Works” (1994).

Last reviewed 12 October 2026