A book for hardware builders

The Hardest Hardware Lessons

Everything nobody tells you about building, making, and managing a physical product.

For everyone who has stood in a factory at 2am trying to understand why the product they spent two years building isn't working — and for everyone who would rather not.

Get the Book →

13 copies sold in the first 24 hours. No ads. Just hardware people recognising something true.

About the book

The unpublished version of hardware development — written down.

There is a published version of how hardware products get built, and there is an unpublished one. The published version appears in methodology documents and process frameworks. It describes the phases in clean sequence with the reassuring implication that a team which follows the process correctly will produce a product that works, ships on time, and performs as intended.

The unpublished version is what actually happens. The certification test that failed because a PCB layout decision made six months earlier had never been simulated for EMC. The €80,000 tooling modification because a mechanical design was committed to hard tooling before a thermal problem was resolved. The mass production yield crisis that consumed six months of engineering capacity because a process wasn't properly validated in PVT.

These aren't edge cases. They're the pattern. This book is the unpublished version, written down — with every mistake named, every cost quantified, and every decision framework made explicit.

What's inside

Five parts. Every phase of a product's life.

Part One

Development

From first prototype to validated product — prototyping, EVT, DVT, and PVT. Where the most consequential decisions are made and the most money is spent before a single unit ships.

Part Two

The Factory

How manufacturing actually works — every area of the factory floor from receiving to shipping. How to evaluate and select a manufacturing partner. What experienced operators know that founders don't.

Part Three

Supply Chain

How the component supply chain is built, managed, and how it fails. Single-source risk, the 2020–2023 semiconductor shortage, and a framework for managing supply chain risk at every stage.

Part Four

Mass Production

Production line management, quality systems, engineering changes, field failures, and recalls. The operational disciplines that determine whether mass production is a controlled process or a continuous crisis.

Part Five

Product Lifecycle

Sustaining engineering, cost reduction, versioning, and end-of-life. The disciplines that determine whether your product remains an asset or becomes a liability over its full commercial life.

Throughout

The Lessons

Every major section ends with a lesson — the specific mistake most teams make, the cost of making it, and what to do instead. Blunt, direct, and cheaper to learn from a book than from a product.

From the book

The first lesson is also the last.

"Hardware is hard because it is a discipline of progressive commitment. Every phase of development commits more capital, more time, and more organisational energy than the phase before it — and makes the decisions of every previous phase harder and more expensive to change."

— Introduction: The Lessons Nobody Teaches

"The cost ratio between a bug discovered in prototyping and the same bug discovered in production is not 10:1. It is more often 100:1 or higher. A software bug can be patched overnight. A hardware design flaw requires an engineering change, a production line halt, potentially a tooling modification, potentially a certification re-test, and potentially a field recall."

— Introduction: What Makes Hardware Hard

"The hardest hardware lessons are not the technically complex ones. They are the ones about discipline: the specific moments when the rational decision is to hold the gate, and the pressure to move forward is at its highest. These are the lessons that are not in the textbooks, because they are not technical. They are human."

— Introduction: The Pressure That Defeats Discipline

What readers say

Hardware people recognising something true.

"This is the book I wish I'd had before our first DVT. We made exactly the mistakes described — and paid exactly the costs described. Required reading for any hardware founder."

Early readerHardware startup founder

"Finally someone has written down what we all know but nobody says out loud. The section on manufacturing process validation alone is worth the price."

Early readerOperations lead, consumer electronics

"I've been in hardware for 15 years and still found things in here I hadn't articulated clearly. This is the reference I'll send to every new engineer on my team."

Early readerSenior hardware engineer

* Testimonials from early readers. More reviews coming as the book reaches more hands.

About the author

Johan Philippe (Hans) Stam

Author · Hardware practitioner · Berlin

Johan has spent years working across hardware development, manufacturing, and supply chain — watching the same expensive mistakes repeat across teams, companies, and industries. The pattern was always the same. The costs were always avoidable. The lessons were never written down.

The Hardest Hardware Lessons is his attempt to fix that — to give hardware builders the specific, hard-won knowledge that experienced practitioners carry in their heads, before it has to be learned the expensive way.

Get the book

Learn it from a book.
Not from a product.

Every shortcut you take today is a cost you will pay downstream, at a higher rate, under worse conditions.

Get the Book on Gumroad →

Available now · Instant download · PDF & ebook formats