#781 1943 · Lockheed (Kelly Johnson) · Aerospace / R&D organizational design
Lockheed built America's first jet fighter in a rented circus tent, on a handshake, months before the contract existed
the problem
Normal defense-contractor process couldn't move fast enough for a wartime jet threat
background
In June 1943, the US Army's Air Tactical Service Command told Lockheed it urgently needed a jet fighter to counter Germany's new Me-262, a threat serious enough that the normal defense-contracting timeline — committee reviews, formal specifications, sequential sign-offs across engineering, procurement and manufacturing — could not plausibly deliver a working prototype before it mattered. Lockheed's ordinary organization was built for exactly the kind of coordinated, checked, multi-department process that made fast, one-off engineering nearly impossible.
The standard wartime response to an urgent request was to push the existing organization harder: add staff, prioritize the project on paper, ask departments to move faster within the same approval structure. That approach didn't change the actual bottleneck — a jet fighter designed and built by committee, however urgently prioritized, still had to pass through every one of the same sequential checkpoints a routine peacetime aircraft did.
what everyone would do
The standard wartime response to an urgent deadline was to escalate priority within the existing structure: add more engineers, demand faster sign-offs, pressure every department in the normal sequential chain to move quicker — treating the timeline as a speed problem to push through rather than a structural problem in how the work was organized.
what they saw
Johnson saw that the delay wasn't coming from any single department working too slowly — it was coming from the number of handoffs and approvals a project had to survive before work could even begin. A small team empowered to make its own engineering decisions and answer directly to one customer contact didn't need to move faster through the normal process; it needed to skip the parts of the process that existed to coordinate people who, in this case, didn't need coordinating.
the move
Engineer Kelly Johnson assembled a small, hand-picked team of engineers and mechanics, physically separated them from Lockheed's main operations — working out of a rented circus tent next to a foul-smelling plastics plant, since no other space was available — and began designing the XP-80 jet fighter on a verbal agreement with the Army before a formal contract existed. The actual paperwork didn't arrive until four months after the team had already started building.
why it works
Physically and organizationally isolating the team removed the two things that consumed the most time in ordinary defense contracting: waiting for cross-department sign-off on decisions the team could make itself, and waiting for a formal contract to authorize work both sides had already verbally agreed needed to happen. Starting on a handshake meant engineering began the moment the need was clear rather than the moment paperwork caught up to it, and a small, hand-picked team meant nearly everyone in the room could make a real decision, so almost no time was spent relaying context up a chain of command.
the payoff
Johnson's team delivered the XP-80 Shooting Star prototype in 143 days, seven days ahead of the deadline, becoming the first American jet fighter. The organizational approach that made it possible — small teams, direct customer access, minimal bureaucratic overhead — was later codified as Kelly's '14 Rules and Practices' and became the founding template for what Lockheed formally named Skunk Works, which went on to build the U-2, the SR-71 Blackbird and the F-117 stealth fighter.
where it breaks
The model depends on a customer relationship with enough trust to authorize real work before a formal contract exists, which is unusual outside urgent, high-stakes situations with a decision-maker who genuinely has authority to commit resources informally. It also scales only to a small number of concurrent projects — the entire point is a small team with minimal coordination overhead, so running many such units at once inside one company reproduces the coordination problem the model was built to escape. And it requires exceptional individual engineers, since the model removes the checks and reviews that would normally catch a mediocre engineer's mistakes.
what came after
Kelly Johnson's 14 Rules became the reference template for the modern corporate 'skunkworks' unit — a small, insulated, high-autonomy team charged with moving faster than a parent organization's normal process allows — and the term itself, taken from the improvised tent Johnson's team first worked in, entered general business vocabulary as shorthand for exactly that kind of unit, used across industries far beyond aerospace.
references
- [1]The Skunk Works Legacy — Origin StoryLockheed Martin, 2018lockheedmartin.com
- [2]Managing Lockheed's Skunk WorksGood Science Project, 2024goodscienceproject.org