Steve
Blank

September 21, 1999. The night before E.piphany's IPO, Steve Blank retired. Not "pivoted." Not "stepped back to advise." He walked out. The next morning, E.piphany opened at $8 and closed the day above $100. Blank was already gone - by design, by choice, by a personal philosophy he hadn't quite articulated yet but would spend the next twenty years distilling into one of the most influential ideas in the history of technology business: that a startup is not a smaller version of a big company, and that most founders fail not because they build the wrong product, but because they never bothered to meet the people they were building it for.

The path to that exit began somewhere between Queens, New York and a cargo plane full of racehorses. Blank grew up as a self-described "latchkey kid," finding refuge in public libraries the way other kids found it in playgrounds. He enrolled at the University of Michigan, lasted one semester, hitchhiked to Florida, and got a job converting cargo planes to transport horses. If there is a business school metaphor for "do things that don't scale," this is it.

Then came the Air Force. Four years. Thailand. Electronic warfare systems on F-105G, F-4, and A-7 aircraft. He was nineteen and supervising eleven technicians. He was a member of the Society of Wild Weasels - the Air Force crews whose mission was to fly directly at enemy radar to bait surface-to-air missiles. The ones who draw fire so others can shoot back. It is, in retrospect, the perfect resume line for someone who would later build a career out of running directly at the most dangerous assumption in any business: that you already know what your customers want.

Silicon Valley in 1978 was a different planet. Blank arrived with no degree, a military background in electronics, and an almost preternatural ability to land in rooms where the future was being built. His first job was at Electromagnetic Systems Laboratory, a TRW unit founded by William Perry - the future U.S. Secretary of Defense. From there: Zilog, MIPS Computers, Convergent Technologies, Ardent Computer (supercomputers, failed), SuperMac (peripherals), Rocket Science Games (video games, also failed). He calls these the "craters." He is not embarrassed about them. He turned them into curriculum.

Then E.piphany - CRM software, 1996, co-founded from his living room. It worked. The IPO happened. Blank left. Not at a low point. Not forced out. Not "pursuing other opportunities." He left at the top of the market and walked directly into a classroom.

In 2001, UC Berkeley invited Blank to teach. He didn't have a deck. He had an observation - something he'd noticed across eight startups, two spectacular failures, and one dot-com jackpot. Every founder, himself included, spent months (sometimes years) building products in isolation, then wondered why customers weren't buying. The answer, he argued, was embarrassingly simple: they never asked.

The insight crystallized into Customer Development - four phases that mirror the engineering product development cycle but apply to the business model instead of the code: Customer Discovery, Customer Validation, Customer Creation, Company Building. The premise is almost aggressively obvious: before you build, you must test your assumptions. Before you scale, you must confirm you have something people will pay for. Your business plan is not a strategy document - it is a list of hypotheses. Treat it like one.

In 2004, Eric Ries sat in Blank's Stanford class. Ries took Customer Development and fused it with Agile software development, added "minimum viable product" to the lexicon, and called it the Lean Startup. The book sold millions. The methodology appeared in every business school in the world. Steve Blank's name does not appear on the cover. Eric Ries credits him on the first page. This is not an accident or an oversight - it is, in its own way, the purest expression of Blank's philosophy: get the idea to the people who will use it, as fast as possible, without worrying about who gets the credit.

In 2011, Blank designed Lean LaunchPad at Stanford - an immersive 10-week course in which teams interview 100 customers before writing a single line of code. The National Science Foundation noticed. They adopted it as the I-Corps curriculum, the mandatory entrepreneurship training for federally funded research scientists. As of 2024, I-Corps has put 9,330 scientists through the program, spun out roughly 1,400 startups, and those companies have raised more than $3.166 billion. The Journal of Management dedicated an entire 2024 issue to his work. That is not a small thing.

The pivot everyone missed: around 2016, Steve Blank turned his attention to national security. Not as a pundit. Not as a commentator. As a builder - with the same urgency he'd applied to Silicon Valley, redirected at the most bureaucratically resistant institution in American life: the Department of Defense.

Hacking for Defense, co-created at Stanford with Joe Felter and Raj Shah, applies the Lean LaunchPad framework to real Pentagon problem statements. Student teams don't dream up startup ideas - they're handed actual national security challenges from DoD sponsors and have to interview 100 people in 10 weeks to understand the problem before proposing a solution. In its first year, it was an experiment. A decade later, it runs in 70+ universities worldwide. The 2025 Stanford cohort's student teams collectively interviewed 1,106 beneficiaries in a single semester.

In 2021, Blank co-founded the Gordian Knot Center for National Security Innovation at Stanford's Freeman Spogli Institute, with former Army Ranger and Defense Policy Board member Joe Felter and Raj Shah, former director of the Defense Innovation Unit. The thesis is simple and uncomfortable: the U.S. military moves on acquisition timelines measured in decades; the adversaries it faces move on startup timelines measured in months. Someone needs to bridge that gap.

In 2023, the U.S. Navy agreed. Blank was appointed to the Department of the Navy Science & Technology Advisory Board, where he heads the Innovation Group. The kid who maintained electronic warfare systems on F-105Gs in Thailand at age nineteen now shapes how the Navy thinks about technology adoption. The arc is either deeply ironic or perfectly logical, depending on your philosophy of careers.

He published a new book in 2023: "Hacking for Defense: Innovation Doctrine," co-authored with Peter Newell and Steven Spear, released by Wiley. It is not a textbook. It is a manifesto for a military-industrial complex that has forgotten how to move fast. And in 2025, he published a PEO Directory listing 500 government acquisition organizations - a resource for defense startups trying to navigate the procurement labyrinth. That is the kind of thing that only someone who has spent time on both sides of the table would think to make.