Why putting a financial officer in command is a structural problem, not a personnel problem — and what to watch for

I want to be honest with you about something uncomfortable.

If you're reading this in the early morning and you've been tracking the mood in your building — the way certain conversations get quieter, the way the roadmap reviews have shifted from "what are we building next" to "what can we cut" — then you already know what I'm about to say. Your instincts are correct. You're not being paranoid.

What you may not have is the vocabulary to explain why it works the way it does.

I got that vocabulary from a single sentence.

A Sentence That Changes How You See It

A few weeks ago I was fortunate enough to watch to a video with Stephen Wolfram, the physicist and mathematician whose work sits at the intersection of computation and natural law. Almost in passing he made an observation that I haven't been able to stop thinking about.

He said: the reason evolution works is that it operates on an extraordinarily loose fitness function.

The rules of natural selection, stripped to their core, are this: stay alive long enough to reproduce, and repeat. That's it. There is no specification for how you accomplish that. Whether you're a patch of moss on a rock face or a basking shark working a thermal in the Atlantic, the same loose set of rules applies. And within that looseness, nature has produced millions of distinct solutions — ecological niches, body plans, survival strategies — that no central planner could have anticipated or designed.

The looseness is not a bug. The looseness is the entire point.

Now flip it. What happens when you tighten the fitness function?

What Tightening Looks Like in a Company

When a company installs a financial officer in the command position, something very specific happens to the measurement system. Every unit of expenditure gets attached — or is required to attach — to a known unit of incremental revenue. Programs that cannot demonstrate a direct line from cost to return get cut. Variance gets driven out. Predictability becomes the primary virtue.

This is not incompetence. It is a measurement system doing exactly what it was designed to do.

The problem is what it selects against.

Noting that Tim Cook is stepping down, let’s look at his efforts over his leadership term in comparison to Steve Jobs last leadership term.

Apple launched revolutionary products under Steve Jobs that created new markets, while Tim Cook's era focused on ecosystem expansion and services for sustained revenue.

Jobs Era Products (Late Launches)

Jobs oversaw category-defining hardware from 2005-2011, driven by bold innovation to redefine user experiences.

iPod nano (2005): Created portable video/music players; innovation-driven (new form factor).

iPhone (2007): Invented the modern smartphone; innovation-driven (touch interface, app ecosystem).

MacBook Air (2008): Pioneered ultrathin laptops; innovation-driven (design revolution).

iPad (2010): Launched tablet computing mainstream; innovation-driven (new computing category).

iPad 2/iPhone 4S (2011): Refined tablets/phones; innovation-driven (performance leaps).

Cook Era Products (Key Launches)

Cook's recent products since 2011 emphasize wearables, services, and integration, often business-driven for ecosystem lock-in and recurring revenue.

Apple Watch (2015): Wearable health tracker; new category but business-driven (services tie-in).

AirPods (2016): Wireless earbuds standard; business-driven (ecosystem expansion).

Apple Silicon M1 (2020): Custom chips for Macs; innovation-driven (performance shift).

AirTag (2021): Item tracker; business-driven (Find My network growth).

Vision Pro (2024): Spatial computing headset; innovation-driven (new VR/AR paradigm).

Key Differences

Jobs' launches were riskier, innovative, creating standalone categories from a technical vision. Cook's build on the iPhone ecosystem for expanding profitability.

Innovation, by definition, cannot demonstrate a direct line from cost to return before the work is done. The entire value of early-stage research is that it explores territory whose yield is unknown. You are not buying a result. You are buying the possibility of a result — and the landscape of possible results is exactly what gets eliminated when you tighten the fitness function.

With less focus on innovation, you get a company that is very, very good at producing derivative and incremental advancements.

The Accountability Gap Nobody Books

Here is the part that makes this a structural problem rather than a personnel problem.

A financial executive who cuts an innovation program can claim credit on the P&L immediately. The cost savings are legible, auditable, and attributable. The destroyed optionality — the future products that will never be developed, the capability that will atrophy, the engineers who will leave — those costs never appear in any financial statement. There is no line item for "strategic opportunity destroyed." There is no reserve requirement for innovation the way there is for legal liability.

This is an asymmetric accountability structure. You are rewarded for variance reduction and never penalized for eliminating the explore budget.

A famous era of industrial cost discipline proved this at scale. The methodology was sound in manufacturing — tolerance matters, and variation is the enemy on a shop floor. But when the same logic was applied to the innovation pipeline, it produced the same result it always produces when you tighten the fitness function on a complex adaptive system: you eliminate the territory where the next generation of products was supposed

to come from.

The engineers in those companies knew it before management did. They always do.

The Pipeline You Can't See Until It's Empty

Innovation is not a faucet. It is a pipeline. Between the decision to fund early-stage work and the product that reaches a customer, there is a lag — typically measured in years, never in quarters. Which means when you cut the front end of the pipeline, nothing changes at the product end for a long time.

The cuts happen in Q1. The P&L looks better in Q2. By Q4 leadership is taking credit for margin improvement. Three years later, the product pipeline runs dry, the competitors who kept investing are two generations ahead, and the cuts that produced the margin improvement are three organizational structures in the past.

By then, the damage is done and the person who made the decision is long gone or entrenched.

A mature company that understands this builds something equivalent to a governance and reserve function for innovation — a protected, multi-year commitment treated as an obligation, not a discretionary line item. The same way a legal reserve fund exists because nobody asks the CFO to gut it to hit this quarter's number, the innovation budget requires its own protected structure to survive the pressure.

Most companies don't build that structure. They discover they needed it when the pipeline is already empty.

What to Watch For — In Both Directions

If you're in a building where the signals are going the wrong way, here is what I would tell you directly: update your resume now. Not after the announcement. Not after the first round of cuts. Now.

When a financial executive moves into command authority, the first 90 days are almost always a cost rationalization exercise. That is what they know how to do. Being low in the organization does not protect you — it makes you a legible line item. Moving early costs you nothing. Waiting costs you leverage, time, and potentially your severance position.

But here is what you also need to know: not every company in trouble is finished. Some of them figure it out. And when they do, the signals are observable.

• Watch what gets protected when the cuts come. If R&D gets a named carve-out — even a modest one — someone at the top understands the pipeline has a lag. That is the signal.

• Watch who gets promoted. One promotion cycle tells you what the organization is optimizing for. Are the people moving up builders, or are they operators and financial controllers? The org chart is always honest.

• Watch the weird projects. Any advanced concepts group, any small team working on something that won't ship for three years — if that survives the restructuring, somebody is thinking in pipeline terms. If it gets zeroed, the pipeline is being consumed, not refilled.

• Listen to the language. "We're going to out-engineer this problem" and "we're going to optimize our way out of this" are not the same sentence. Engineers hear the difference before anyone else does.

• Look for a funded long-horizon roadmap. Not a vision statement. Not a town hall slide with aspirational language. A named, funded, multi-year technology program with actual resources attached. That is the innovation reserve obligation. That is the company saying: this is not discretionary.

The One Thing That Matters

The story everyone tells about a famous company's comeback gets told as a story about one person. That is the wrong lesson.

The right lesson is that a board made a categorical decision: we are going to put a builder back in command. The specific identity of that builder mattered, yes. But the generalizable truth is the category of the decision, not the name.

Tim Cook's successor is John Ternus, currently Apple's Senior Vice President of Hardware Engineering. He is set to become CEO on September 1, 2026, while Tim Cook transitions to Executive Chairman.

Ternus is called a "brilliant engineer," he is described by Tim Cook as having the "mind of an engineer" and the "soul of an innovator" .

Ternus represents a shift back to product and engineering DNA. His main task will be navigating Apple through the AI era and global supply chain complexities while preserving its design culture .

A company that is serious about coming back from a cost-discipline spiral makes a specific kind of move. It puts someone in command whose hands have built things. It protects the front end of the pipeline even when the pressure is highest. It treats innovation as a core competency, not a gift.

If you see those signals, you have reason to stay.

If you don't, you already have your answer.

Leave a comment

Subscribe now

Herbert Roberts, P.E., is a licensed Professional Engineer with 32 years in aviation R&D and 62 U.S. patents. He writes about engineering, invention, and the systems that make or break both at Inventor's Mind on Substack.

On envy, pride, and what gets built when someone finally trusts the engineers

Herbert Roberts, P.E. | Inventor’s Mind | Wednesday Series

The Honest Confession

I am going to tell you something that took me a long time to say out loud.

When I first saw the SpaceX Raptor Mk3 engine — really looked at it, studied the geometry, understood what they had done with additive manufacturing to produce cooling channel architectures that no conventional process could touch — I felt envy.

Not envy of the credit. Not envy of the press release or the name on the patent or the photograph in the magazine. I have sixty-two patents. I know what a patent feels like. That was not what I wanted.

I wanted to have been in that room. I wanted to have felt what those engineers felt when the budget conversation was not the first conversation. When the question was not how much and how long but how good. When someone in authority looked at a room full of engineers and said three things that I had spent thirty-two years waiting to hear:

We believe in you. We trust you. Yes — with no conditions.

That is the confession. And it took me a while longer to understand what it actually meant.

How Aerospace Actually Works

Let me tell you how the engineering conversation goes in a budget-first organization. Because if you have worked in one, you already know. And if you have not, you need to understand what the alternative was built against.

The idea arrives. It is good — genuinely good, technically sound, with a performance case that the data supports and a development path that experienced engineers believe in. It goes into a review. The review is not about whether the idea is good. The review is about whether the idea is affordable, schedulable, and defensible to a program office that is already watching three other line items bleed.

The idea comes back with conditions. Reduce the scope. Extend the schedule. Cut the test matrix. Prove the concept at lower fidelity before we commit to the full build. Come back when the technology readiness level is higher and the risk is lower and the cost is smaller and the timeline fits the budget cycle.

The engineer learns. Not to stop having good ideas — you cannot train that out of a real engineer. But to pre-filter them. To ask, before the idea is fully formed, whether it will survive the review. To build the cost justification before the technical case. To shape the vision to fit the envelope before the envelope has a chance to expand.

Thirty-two years of that shapes a mind. It shapes the questions you ask first. It shapes what you allow yourself to imagine.

Then you watch someone build the Raptor.

And you realize you had stopped imagining things like that. Not because you could not. Because you had learned not to.

What No Conditions Actually Means

I want to be precise about what I mean by yes with no conditions. Because it is not what it sounds like from the outside.

It does not mean unlimited budget. The Raptor was not built without cost discipline — it was built with a different cost discipline, one that started from the performance target and worked backward to the process, rather than starting from the budget and working forward to whatever performance it could afford.

It does not mean no accountability. The SpaceX test philosophy is more rigorous than almost any program I encountered in thirty-two years of aviation research — because they test to failure, deliberately, systematically, and use the failure data to drive the next design iteration rather than to write a corrective action report that satisfies a program office and changes nothing.

What it means — what it actually means when an organization says yes with no conditions — is this:

We have decided that the engineers are the asset.

Not the asset subject to the budget. Not the asset contingent on the schedule. The asset. The thing the organization exists to deploy. The reason the money is here in the first place.

When that decision is made — genuinely made, not stated in a mission document and then contradicted in every program review — it changes what engineers build. Not because they work harder. Engineers in budget-first organizations work extraordinarily hard. It changes what they allow themselves to attempt.

The Raptor’s additive-manufactured combustion chamber and turbopump components are not the result of engineers working harder than the engineers I worked with. They are the result of engineers being permitted to follow the technical logic all the way to the end — past the point where a budget-first organization would have said: that is too difficult, too expensive, too far from current manufacturing readiness. Stop there. Do the thing we already know how to do.

I have patents on additive manufacturing methods. I was working the problem. The problem was not the technology. The problem was the permission structure.

The Eleven Words

I want to tell you about a specific moment that I have carried for a long time.

Early in my career I was part of a team developing a manufacturing approach that we believed could produce component geometries that conventional machining could not reach. The performance case was clear. The technical path was defined. The team was capable — genuinely capable, the kind of team that forms once in a career if you are fortunate.

The program review came back with the standard response. Reduce scope. The geometry targets are too aggressive for the current budget envelope. Come back at lower ambition and we will talk about the next phase.

We reduced scope. We came back. We got a smaller yes with more conditions. We did the work we were permitted to do, which was good work, careful work, work that added to the knowledge base in ways that mattered.

It was not the work we had come to do.

Years later I watched a video of the Raptor firing on a test stand. I looked at the cooling channel geometry on the combustion chamber — the internal architecture that additive manufacturing had made possible, the thing that could not have been cast or machined, the geometry that existed because someone had looked at the engineers and said: follow the technical logic wherever it goes.

I thought about the program review. About the scope reduction. About the careful, permitted work.

And then I thought: thirty-two years ago, how much and how long. Today, how good.

Eleven words. That is the entire distance between the program review and the Raptor.

How much and how long. Versus. How good.

What This Essay Is Not Saying

I am not saying that budget-first organizations are run by people who do not care about engineering. Most of them care deeply. The program managers and budget reviewers I worked with over thirty-two years were serious professionals doing a genuinely difficult job — managing technical risk against real resource constraints in environments where a cost overrun has consequences that extend well beyond any single program.

I am not saying that yes with no conditions scales to every organization or every program. The conditions that allowed SpaceX to build the way they build — founder-led, private capital, explicit risk tolerance written into the culture from day one — are not conditions that a defense contractor operating on a cost-plus government contract can replicate. The institutional structures are different. The accountability structures are different. Comparing them directly is not fair to either.

And I am not saying that every engineer who worked inside a budget-first culture wasted their career. I did not waste mine. The sixty-two patents are real. The knowledge contributed to things that mattered. The work was worth doing.

What I am saying is simpler and more uncomfortable than any of that.

The permission structure shapes the ambition. Always. In every organization, at every scale. And the engineers who work inside a structure that says yes with no conditions build things that engineers inside a structure that says yes but do not build. Not because of talent. Because of permission.

That is not an excuse. It is a variable. And if you are building an organization — or inheriting one, or trying to change one — it is the most important variable on the board.

Pride Is the Whole Point

I said this was a confession of envy. I need to finish it correctly.

The envy was real. I wanted to have been in that room. I wanted to have felt what those engineers felt on the day that engine first fired at full thrust and performed exactly as the data said it would — because they had been permitted to follow the data all the way to the end without a budget review stopping them halfway.

But underneath the envy, and larger than it, was something else.

I was proud of them.

Profoundly, specifically, technically proud — the way you can only be proud of something when you understand exactly what it cost to build it and exactly how rare the conditions that made it possible were. I knew what they had done. I knew the manufacturing problem they had solved. I knew the thermal management challenge they had cracked. I knew because I had spent thirty-two years working toward the same class of solution from inside a different permission structure.

We were always working toward the same engine. They just got the room to finish it.

That is not a consolation. That is the truth. And the truth, once I sat with it long enough, resolved the envy into something cleaner.

You can only envy what you recognize as worth having. I recognized it because I spent thirty-two years caring about exactly what they cared about — the geometry, the materials, the thermal boundary, the manufacturing method that finally closes the gap between what the physics demands and what the process can deliver.

The envy was just pride with nowhere to go.

It found its place.

They believed in their engineers. They trusted their engineers. They said yes with no conditions. And the engineers — as engineers always do when someone finally says that — built something worth being proud of.

I was proud of them. I am still proud of them. That turns out to be enough.

IF YOU HAVE FELT THIS

Forward this to the engineer in your organization who is still doing rigorous work inside a budget-first culture and has never once stopped caring about the quality. They are carrying something heavy. They should know someone sees it.

Herbert Roberts, PE • Inventor’s Mind • inventorsmindblog.com

The Inventor’s Mind Substack publishes twice weekly — built for engineers who are still paying attention. Free, at inventorsmindblog.com.

A NOTE ON SPECIFICS

Thirty-two years of aviation R&D across two companies means certain programs, employers, and technologies stay inside the work where they belong. The manufacturing methods referenced in this post are documented in my patent portfolio. The program reviews happened. The scope reductions happened. The work was real.

Cloistered decisions take minutes. Their consequences take decades. And between those two time scales lies every great company that did not survive the boardroom that killed it.

Every senior engineer knows the cost of tribal knowledge loss on the shop floor.

The craftsman who retires without a debrief, the materials specialist whose judgment dies with them, the forensic investigator whose pattern recognition was never documented — these losses are the standard vocabulary of modern industrial decline. An entire genre of engineering writing, this column included, exists to name what gets lost when institutions fail to capture the tacit knowledge of their most experienced people.

What the genre does not yet address is that the same loss operates at the executive level, one floor up, and with consequences an order of magnitude larger. The senior executive who retires with no written legacy of what they decided wrongly, and why, is a tribal knowledge evaporation event no less real than the senior machinist who retires without training a replacement. We simply do not name it that way, because we do not expect executive retirement to include an honest accounting of the decisions that did not work.

We should.

We live in a culture drowning in business analysis. The case studies are in every MBA syllabus. The podcasts run three hours long. The business press publishes autopsies within weeks of the event. Every major corporate failure in the last four decades has been dissected, republished, turned into a Harvard Business School case, and absorbed into the general vocabulary of anyone who has sat near a boardroom.

And yet.

The decisions that actually cost great companies their existence — the ones made inside cloistered rooms by small groups of executives insulated from the engineers, insulated from the customer, insulated from the historical record — those are the decisions we remember the least about. The autopsies get written, but they focus on the visible part of the failure, which is the part that happened in the marketplace. The part that happened in the conference room, three years or ten years or fifteen years earlier, is barely described at all. In most cases, we do not know who was in the room, what was said, what was weighed, what was dismissed, or why.

That forgetting is not accidental. It is institutional. It is a feature of how corporations maintain executive continuity. And it is the mechanism by which the next generation of executives walks into the same cloistered room, weighs the same factors, applies the same logic, and kills the next company in exactly the same way.

Why are we so quick to forget?

The Catastrophes We Remember

There are two kinds of corporate catastrophe. The first kind has a customer.

When the customer has a voice, the accountability mechanism works. The press covers the damage. The earnings call becomes a referendum. The CEO takes public ownership, or takes public blame, or takes both. The decision gets reversed or the executive gets replaced. The lesson enters the business vocabulary within the quarter.

Consider the two examples every reader already knows.

In April 1985, Coca-Cola replaced its flagship formula with New Coke. Consumer outrage was immediate, articulate, and visible. Within seventy-seven days the original formula was back on the shelf as Coca-Cola Classic. Business schools made it a case study. The reversal was complete, the accountability was public, and the lesson was absorbed so thoroughly that forty years later a marketing executive who has never touched a soft drink brand can still recite it.

In April 2023, Anheuser-Busch InBev’s flagship beer, Bud Light, ran a partnership campaign that alienated its core drinkers. The sales response was immediate. The brand lost the top-selling-beer-in-America crown it had held for more than two decades. Executives exited. The board commented publicly. Quarterly earnings calls became public accountings of what had been decided and why. Trade publications wrote the long-form retrospectives within months. By the time the dust settled, the broader industry had a new case study and a new set of lessons about how to treat a heritage customer base.

In both cases, the accountability mechanism did its job. The customer voted. The press translated. The market punished. The lesson was preserved. This is what corporate self-correction looks like when the victim is visible.

The Catastrophes We Forget

Now consider two catastrophes of a different kind.

In 1975, a young electrical engineer named Steven Sasson, working at Eastman Kodak in Rochester, New York, assembled the world’s first working digital camera. The device was the size of a toaster, weighed eight pounds, and captured black-and-white images at a resolution of one hundred pixels by one hundred pixels onto a cassette tape. Sasson demonstrated it to Kodak management in 1976. The response, which he has recounted publicly several times since, was curiosity followed by discomfort. Kodak’s business was built on sensitized film. A filmless camera threatened the core of the enterprise. The company filed the patent in 1977, chose not to commercialize the product, and continued to dominate the film market for another two decades. In 2012, Kodak filed for Chapter 11 bankruptcy protection.

No executive was publicly named for that 1976 decision. No podium press conference was held. No earnings call addressed it, because the decision never produced a current-quarter effect that would have appeared on an earnings call. The meeting where digital photography was killed at Kodak happened inside a conference room, by people whose names are not in any index of the subsequent bankruptcy coverage, and whose retirement packages were negotiated and delivered long before the consequence fully arrived.

Around the same time, at Xerox’s Palo Alto Research Center, a team of researchers was building the Alto. The Alto had a mouse. It had a graphical user interface. It had bitmapped displays, what-you-see-is-what-you-get editing, Ethernet networking, and an embedded laser printer. It was, by any honest measure, the personal computer we are still using today. Xerox’s corporate leadership in the East — focused on the copier business that was the company’s profit engine — looked at the Alto and decided it was an expensive curiosity outside the strategy. When Xerox did commercialize the concept as the Star in 1981, it priced the product at sixteen thousand dollars as part of an integrated office system that required further investment in file servers and laser printers. The Star was a commercial failure. The researchers at PARC watched, over the subsequent three years, as Apple built the Lisa and the Macintosh and created the personal computing industry. Steve Jobs said, years later, that if Xerox had understood what it had, it could have been larger than IBM and Microsoft and Xerox combined.

No executive at Xerox was publicly named for the decision to constrain the Alto. No street was renamed. The accountability mechanism that had worked so efficiently for New Coke and Bud Light did not engage, because the victim of the Alto decision was not a customer who could complain. The victim was the future of Xerox itself. And the future of a corporation has no seat on the earnings call.

These are not obscure examples. Every reader of this column has heard them before. The question is not whether we know these stories. The question is what we do with them. And the answer, so far, is almost nothing.

The V / E / F Pattern

Apply the Vision / Execution / Financial Stability matrix to the four cases and something striking appears.

The visible disasters — New Coke and Bud Light — were Vision failures. The company misread the customer. Execution was fine. Financial stability was intact. The vision error produced a product or a campaign the market rejected on sight, and the rejection was loud enough to force a correction. The V-failure was public, visible, and repaired within months.

The invisible killers — Kodak and Xerox — were something else entirely. The Vision was correct. Kodak literally invented the technology that would eventually destroy it. Xerox literally built the personal computer before the term existed. The Financial Stability was intact — both companies had the cash to commercialize what they had. What failed was Execution, and what produced the execution failure was not incompetence but a specific category of institutional decision made inside a specific kind of room.

That is the pattern worth naming. The catastrophes we remember are Vision errors, correctable through market feedback. The catastrophes we forget are Execution errors, uncorrectable because the market does not see the decision that produced them until the company is already gone.

The Cloistered Room

The catastrophes we forget share one structural feature. They were all decided in a cloistered room.

Here is what I mean by cloistered. The room (a) had a small number of executives in it, (b) did not have the engineers who had built the technology in it, (c) did not have the customer who would eventually reject the decision in it, (d) did not have any representative of the organization’s ten-year strategic future in it, and (e) did not have the institutional record of prior similar decisions having failed in it.

I will add a confession here. I have sat in rooms of that shape. On at least one occasion I watched a decision get made that I believed was wrong, and I did not speak as forcefully as I now wish I had, because the language in the room was the language of prudence, and dissent would have read as naïveté. That is not an excuse. It is a description of how the room functions, from the inside, on the afternoon of a decision that a decade later will look very different from how it looked that day.

That room is the incubator of the catastrophes we forget. Not the marketplace. Not the product line. The room.

The room has a predictable composition. The people in it are senior enough to decide, which means they are far enough from the engineering floor that they cannot read the technical evidence directly. They are responsible enough for the current-year budget that they weigh cost in this year’s terms rather than strategic consequence in the next decade’s terms. They are insulated enough from the customer that the customer’s voice enters the room only as a market research summary, filtered through two layers of middle management. They are disciplined enough in their executive posture that the instinct to ask the engineers in the building what they actually think is suppressed as inefficient.

And most consequentially, the people in that room do not have the archive.

They do not have a folder labeled decisions of this type, historically, have destroyed companies of this scale within the following timeframe. They do not have a briefing document titled the executives who killed digital imaging at Kodak used the following reasoning, and here is the 2012 bankruptcy filing that resulted. They do not have a wall in the conference room displaying the archetypes to watch for in their own deliberation.

They do not have it because nobody built it. And nobody built it because we are too polite to point.

Bad Choices Are Tribal Knowledge Too

We speak about tribal knowledge as if it only lives on the shop floor.

The senior machinist who knows which setup fixture to use for the thin-wall casting, who learned it the hard way on a job that scrapped twelve parts in 1994, and who has never written it down. The materials engineer who knows which supplier’s titanium alloy has a heat-treat response that will not produce the hairline crack, and who carries that knowledge out the door the day they retire. The forensic investigator who knows which failure mode the metallurgy textbook does not describe correctly, and whose judgment dies with them.

Those losses are real. I have written about them at length. I have spent eight years of my forensic practice reconstructing tribal knowledge that was supposed to have been captured and was not.

But there is a layer of tribal knowledge we rarely acknowledge, and it lives in the executive suite. It is the knowledge of which decisions were wrong, and why.

The executive who sat in a 1976 conference room at a great film company and listened as the strategy of not commercializing digital imaging was debated, accepted, and approved — that executive knew things about that meeting that no autopsy has ever captured. They knew who spoke and who did not. They knew which arguments landed and which were dismissed. They knew which person in the room pushed back and whose pushback was overruled. They knew what the language of prudence sounded like in that specific room, on that specific afternoon, from those specific voices.

That knowledge is tribal. It is not written down. It lives in the head of the person who was in the room. And when that person retires, when they leave the company, when they die, the tribal knowledge of what went wrong, and how it went wrong, leaves with them.

The Hall of Fame captures the tribal knowledge of what worked. The retirement speech preserves it. The biography extends it. The street named after the executive at the great engine company is an institutional commitment to remember what that person did right.

No comparable mechanism exists for remembering what an executive did wrong. No retirement speech says and here are the three decisions I now believe were mistakes, and here is what the next generation should watch for so they do not repeat them. No biography ends with and the author spent his last ten years documenting the meetings he wished he had interrupted. No street is named after the person who sat silent when they should have spoken.

This is the asymmetry again, but one layer deeper. We preserve the tribal knowledge of success because the person who owned it is proud of it and the institution benefits from the association. We erase the tribal knowledge of failure because the person who owned it is ashamed of it, the institution is legally exposed by any written account of it, and everyone involved has an incentive to let the record evaporate.

The result is an archive that knows everything about how to succeed and almost nothing about how companies actually fail.

An engineering organization that treated craftsman tribal knowledge the way most corporations treat executive tribal knowledge would be malpractice. We would not accept a factory where every senior machinist walked out the door without a debrief. We accept, as a matter of course, a boardroom where every senior executive walks out the door without one.

The Fame of Shame is not a punishment archive. It is a tribal knowledge archive for the executive floor — the record of what the senior people who were in the room actually learned, in hindsight, about what they got wrong and why. That record does not exist today because no one has asked for it. And no one has asked for it because the culture of executive retirement is built around the written legacy of success and the oral evaporation of everything else.

The young executive walking into a 2026 AI decision has the published memoirs of the executives who got it right. They do not have the debriefs of the executives who got it wrong, because those debriefs were never written, because the executives who owed them are retired in comfortable places far from the consequences, and because the institution that could have asked for them decided, implicitly, that it would rather not know.

That is the loss. Not a marketing disaster. Not a product flop. The permanent evaporation of the one form of tribal knowledge the next generation most needs to inherit.

The Planes, the Engines, and the Cars

The Kodak and Xerox cases are the ones most readers know. They are far from the only ones.

There are airplanes that do not fly, engines that do not run, and cars that are not for sale — all because a person high enough in a chain of command said no, in a cloistered room, about a program that could have been a generational gold mine.

The airplanes. In 2001, Boeing announced the Sonic Cruiser, a near-sonic swept-wing commercial airliner intended to carry passengers at Mach 0.98 across the Pacific. The company displayed it at air shows. Airlines expressed interest. The engineering was credible. In 2002, Boeing quietly canceled the program and redirected the engineering effort into what became the 787. The 787 was a commercially successful aircraft. The Sonic Cruiser was a different kind of aircraft altogether, one that might have reset the commercial aviation speed envelope for the first time since the 1960s. We will never know. The decision to cancel was made inside a room. The reasoning was, in retrospect, rational on paper. But the rationality did not address the question of whether the generational aircraft got killed in exchange for an incremental one. That question was never answered publicly. It was answered inside the room, and the room did not write it down. In the early 1990s, McDonnell Douglas was developing the MD-12, a double-decker long-range widebody intended to compete with what became the Airbus A380. The program was canceled before a prototype flew. McDonnell Douglas was later acquired by Boeing in 1997. The A380 program Airbus built in its place dominated the very-large-aircraft segment for two decades.

The engines. In 1988, at the Farnborough Airshow, GE Aviation ran a demonstrator of the GE36 Unducted Fan on a testbed aircraft. The engine produced measured fuel burn savings of roughly thirty percent compared to conventional turbofans of equivalent thrust class. The demonstration worked. The hardware ran. The savings were real. Oil prices then collapsed through the early 1990s, and the airlines who had been evaluating the technology concluded that thirty percent fuel savings no longer justified the development and certification cost. The program was wound down. The engine design went into a storage facility. In 2021, as jet fuel prices and decarbonization mandates converged, GE and CFM announced the RISE program — an open-rotor engine architecture whose public description is nearly indistinguishable from the GE36. The intervening three and a half decades were lost because a cloistered-room decision in the early 1990s shelved a technology that had already flown, already worked, and already proven its economics. Nobody was publicly named. No board accounting was demanded. The hardware went into storage and the institutional memory went with it.

The cars. In 1996, General Motors released the EV1, a fully electric production passenger car leased to customers in California and Arizona. The vehicle was real. The lease holders were enthusiastic. The infrastructure to support it was being built. In 2003, GM recalled every EV1 from its lease holders and had the fleet crushed. Lease holders who attempted to purchase their vehicles outright were refused. Documentary film crews filmed the vehicles being shredded. The public explanation at the time was that the EV1 was not economically viable as a production vehicle. The internal deliberations that produced that conclusion were not published. What is known is that in 2010 Tesla Motors shipped the Roadster. In 2012 the Model S. In 2017 the Model 3. By 2024, Tesla’s market capitalization alone was larger than General Motors, Ford, and Stellantis combined. The question of whether the 2003 decision to crush the EV1 fleet was a strategic error is, by any honest accounting, already answered. No executive was publicly named. No shareholder lawsuit succeeded in compelling a detailed record of the internal deliberations. The EV1 was crushed, the engineering teams were disbanded, and the tribal knowledge of what General Motors actually understood about electric vehicles in 2003 walked out the door with the engineers who had built them.

Three industries. Three kinds of product. Three cloistered-room decisions. Three graveyards of almost.

Every reader can add their own. The reader in semiconductors is thinking about the program their company canceled in 2019. The reader in pharmaceuticals is thinking about the compound their employer shelved. The reader in industrial chemicals, in power generation, in defense systems, in telecommunications — every reader has their own list of airplanes that did not fly and engines that did not run and products that are not for sale, and every reader is carrying the knowledge that someone high enough in the chain of command said no, and that the record of why is not written down anywhere.

The Time-Scale Mismatch

The cloistered room has one more feature that deserves its own naming.

The decision that happens inside it takes minutes. The consequence of that decision takes decades.

This is the structural mismatch at the heart of everything that follows. A boardroom decides in an hour. A market corrects in three months. A product line fails in two years. A company dies in fifteen. The executive who made the decision is retired by year eight. The archive of why the decision was made is overwritten by year three.

This is how institutions forget. It is not that the forgetting is willful, though in some cases it is. It is that the time scale of executive tenure is shorter than the time scale of the consequence. By the time the bill arrives, the person who ordered the meal is not at the table, the menu has been replaced, and nobody in the current restaurant remembers what was served.

That mismatch is the thing no corporate governance structure has figured out how to solve. The board that could hold an executive accountable for a 1976 decision is not the board that existed in 1976. The shareholders who bear the cost of a 1985 product roadmap are not the shareholders who held the stock when the roadmap was approved. The engineers who are staring at a 2026 product gap caused by a 2014 decision are not the engineers who were in the room when the 2014 decision was made.

The cloistered room is not just insulated in space. It is insulated in time. And the forgetting is, in the end, the forgetting that this double insulation produces automatically.

Why Nobody Names Them

Why are we so quick to forget? Three reasons, each of them structural rather than personal.

The first is continuity of power. The executives who make the cloistered-room decisions are almost always still in positions of authority when the first tremors of consequence appear. Naming them at that point is professionally impossible for anyone inside the institution, legally hazardous for anyone outside it, and unhelpful to the board that is trying to steady the ship. By the time the executives are no longer in power, the consequences have become institutional rather than personal — the company is failing because of conditions, not because of a specific meeting that happened fifteen years earlier — and the individual accountability window has closed.

The second is the language of prudence. The cloistered-room decision is rarely framed as let us destroy the future of this company. It is framed as let us not pursue a speculative technology that threatens our core business. That framing is not dishonest. It is how the decision genuinely appears inside the room, at the moment it is made. The problem is that the language of prudence reads identically to the language of wisdom, which means the reviewer looking back a decade later cannot distinguish the Kodak meeting from every other meeting in which Kodak correctly chose not to pursue a distracting technology. Both meetings used the same vocabulary. Only one of them killed the company.

The third is the absence of a corresponding archive. The Hall of Fame preserves the Neumanns, the Kelly Johnsons, the Steve Jobses. It does not preserve the archetypes, the conditions, or the reasoning patterns that destroyed the companies those heroes worked for. As a result, the young engineer walking into their first major corporation in 2026 has been shown one-half of the institutional record. They have been shown what to emulate. They have not been shown what to survive. The archive they would need in order to recognize the cloistered-room pattern, when it forms in front of them, does not exist.

What a Fame of Shame Would Do

The proposal is not to name individuals. It is to preserve the pattern.

A Fame of Shame — a deliberate institutional archive of the archetypes, the conditions, and the decision-language that has historically produced catastrophe — would change three things.

First, it would give the engineer in the organization a vocabulary for the pattern they are watching form. The young engineer in a modern industrial company, sitting in a program review and watching an executive dismiss an emerging technology with a disparaging metaphor, would have a name for what they are watching. That naming is not a small thing. It is the difference between private discomfort and collective recognition.

Second, it would give the board and the shareholder class a checklist. The question is this meeting a Kodak meeting? is answerable, if the archive exists. It is unanswerable if the archive does not.

Third, it would return some of the time-scale asymmetry back to the executive making the decision. The cloistered-room decision works, in part, because the executive knows the consequences will not land in their tenure. If there were a visible record of similar executives, ten years later, having their decisions quoted back to them by the business press and the next generation of students in the engineering and management schools, the posture inside the room might shift, by even a small amount. That small amount, compounded across every major strategic decision in every major institution, is the margin between a Kodak trajectory and a GE Aerospace one.

The Fame of Shame does not name villains. It names the conditions that produce them.

The Credibility of the System

When blatant criminals do not go to jail, the laws we claim to live by lose their credibility.

The analogy is uncomfortable. It is also exact.

A legal system maintains its authority not because it catches every violation, but because violations of a certain magnitude produce a visible consequence in a public record. The murderer who walks free damages more than the victim’s family. The fraud that goes unprosecuted damages more than the defrauded investor. The damage extends outward, into the confidence of every citizen who concludes, correctly, that the rules as written are not the rules as enforced, and who begins to treat the written rules as theater rather than as binding.

Corporate culture operates on the same mechanism, and fails under the same pressure.

An industrial institution maintains its legitimacy by claiming to operate according to certain values. Stewardship of the company’s long-term interest. Fiduciary duty to the shareholder. Commitment to technical excellence. Care for the next generation of the workforce. Responsibility to the customer and the communities the company operates in. These claims are made explicitly, in annual reports, in executive speeches, in onboarding materials, in the plaques in the lobby.

And these claims are credible exactly to the degree that the institution keeps an honest record of when it failed to live by them.

The Kodak 1976 meeting was not an act of stewardship. The Xerox Alto decision was not an act of fiduciary duty. The shelving of the GE36 demonstrator was not an act of technical excellence. The crushing of the EV1 fleet was not an act of responsibility to the customer. These decisions were their opposite. They were stewardship failures and fiduciary failures of a magnitude that, if the institution’s stated values were binding, would produce a visible record, a debrief, an internal case study, a briefing document for the next generation of executives. No such record exists because the institution does not enforce its own claimed values against its own senior people.

Every reader who has worked inside a great industrial corporation for more than ten years eventually learns this. The discovery is quiet and private. The employee notices that the written values and the operational values do not match. The employee notices that the catastrophic decisions of the past are not on the record the same way the celebrated decisions are. The employee notices that the Hall of Fame is real and the Fame of Shame is absent, and that the absence is structural rather than accidental.

The engineer learning this does not lose respect only for the specific executives involved. The engineer loses respect for the institution’s vocabulary of values itself. The stewardship language is perceived as performative. The fiduciary language is perceived as legal boilerplate. The technical excellence language is perceived as marketing copy. And the engineer, who joined the company because they believed the language, begins to operate as if the language is theater, because that is what the absence of an accountability archive reveals it to be.

This is not a minor consequence. It is how great institutions lose their cultural cohesion from the inside.

The laws we claim to live by lose their credibility when the blatant violators of those laws pay no visible price. The values we claim to build companies around lose their credibility when the blatant violators of those values pay no visible price either.

The Fame of Shame is not, at bottom, an exercise in finger-pointing. It is the minimum institutional record required to maintain the credibility of the institution’s own claimed values.

Without it, every value statement every CEO makes from a podium is contradicted, silently, by the absence of the archive that would prove the statement is meant to be binding.

Why This Matters Now

There are thousands of business leaders right now staring down artificial intelligence and asking two questions at the same time.

How do we fund it. And how do we run from it.

Both questions are being asked inside cloistered rooms. The people in those rooms are senior enough to decide and far enough from the engineering floor that they cannot evaluate the technical evidence directly. They are responsible for the current-year budget and therefore weighing cost in this year’s terms rather than strategic consequence in the next decade’s terms. They are insulated from the customer, whose eventual response will arrive in 2032 or 2036 rather than this quarter. They are reading the technology through management-consultant decks and board-packet summaries rather than through direct contact with the people building the systems.

And they are doing all of this with no archive to consult.

There is no wall in any of those conference rooms displaying the 1976 Kodak meeting. There is no briefing document summarizing the Alto decision. There is no named archetype the executive in the chair can consult before saying we are not in the AI business or let us wait until the technology matures or the ROI case does not support aggressive investment at this time. Every one of those sentences has been spoken before, in a different room, about a different technology, and every one of them produced a company that does not exist anymore.

Nobody in the current room knows that. Because we did not write it down.

The decisions being made this year about artificial intelligence will follow the pattern we have seen every time a disruptive technology has forced a cloistered-room decision. Some organizations will choose correctly, and in fifteen years those choices will be hailed as visionary. The executives who made them will have streets named after them and lobby plaques and Collier Trophies and Hall of Fame inductions. Other organizations will choose incorrectly, and in fifteen years those organizations will be gone. The executives who made the wrong choices will have retired comfortably by then, and their names will not appear in the coverage of the resulting collapse, and the lesson will not be preserved, and the next generation of executives facing the next disruptive technology will walk into a room that has no memory of what happened this year.

This is the asymmetry in one sentence.

Good choices are hailed. Bad choices are forgotten.

That is not balance. That is not accountability. That is a ratchet. It selects, over the long run, for the preservation of success stories and the erasure of failure stories, which means the institutional pool of available lessons is systematically half-complete. The executive walking into the 2026 AI decision has the Neumanns and the Kelly Johnsons and the Steve Jobses available to emulate. They do not have the archetypes of the 1976 Kodak meeting available to recognize. The archive is lopsided, and the lopsided archive is what allows the same meeting to happen, over and over, in different conference rooms and different industries, without anyone in the room knowing that they are repeating it.

How can we learn from the bad choices if we never hear about them and study the why?

We cannot. That is the problem.

The Finger Test, Applied Forward

My own editorial standard when writing this column is what I call the Finger Test. Before I publish, I ask: is the finger pointing at a person, or at a decision? If the finger points at a person, I rewrite. If it points at a decision, I publish.

The Finger Test is not a way of letting anyone off the hook. It is a way of making sure the thing I am preserving is the pattern rather than the grudge. Names wash out of the archive within a generation. Patterns do not. The executives who killed digital imaging at Kodak will be forgotten within another decade. The archetype of the executive who kills a future technology because it threatens the current cash cow will still be recognizable to every engineer reading this column in twenty years, and forty years, and eighty years — provided we take the time, now, to write it down.

The test applies backward to Kodak and Xerox. It applies to the Sonic Cruiser and the MD-12 and the GE36 and the EV1. It applies forward to artificial intelligence, to the energy transition, to every materials revolution and manufacturing method and software platform the current generation of executives is deciding about inside cloistered rooms this year.

Somebody in a conference room right now is making a 2026 AI decision that will determine whether their company exists in 2041.

That decision deserves a name. Not the name of the executive making it. The name of the pattern it fits.

If the pattern is we are protecting this year’s cash flow at the expense of a technology that threatens our core business, it has a name, and that name is Kodak 1976.

If the pattern is we are commercializing this innovation as a constrained high-price product because it does not fit our current business model, it has a name, and that name is Xerox Alto.

If the pattern is we had the hardware, we ran the demonstrator, we proved the economics, and we shelved it because the short-term market signal changed, it has a name, and that name is GE36.

If the pattern is we built the product, leased it to enthusiastic customers, and recalled and crushed the fleet because it threatened an adjacent business, it has a name, and that name is EV1.

If the pattern is we will wait until the technology matures and a competitor proves the market, it has a name, and that name is Fast Follower, and every industrial historian can list the companies that died waiting.

The young engineer sitting in the back of the conference room in 2026 does not have the archive that would let them recognize these patterns in real time. The middle manager briefing the executive does not have it either. The board member voting on the budget does not have it.

That is the work. Build the archive. Preserve the pattern. Teach the next generation to recognize the meeting they are sitting in before the meeting kills the company they work for.

The Two Halves of Memory

The Hall of Fame preserves what we aspire to.

The Fame of Shame preserves what we must not forget.

One without the other is institutional amnesia — and institutional amnesia is the condition under which every catastrophic cloistered-room decision has been made, and will continue to be made, until we build the other half of the archive.

The business press will write the autopsy of the next Kodak within weeks of its bankruptcy filing. The autopsy will explain what happened in the marketplace. It will not explain what happened in the room, fifteen years earlier, where the decision was made. Unless we build the record of what happens in those rooms, we will lose the next Kodak, and the one after that, and the one after that, for exactly the same reason we lost the first one.

We were too polite to point.

And too quick to forget.

— Herbert Roberts, P.E. — Inventor’s Mind

Leave a comment

Subscribe now

Facts Build the House. Logic Defends It. The Jury Decides Whether They Believe It.

Act I — Building the House

In the last post we covered chain of custody and why the first photographs taken at a scene control the evidentiary record from that point forward. Today: the deposition — what it demands of the expert giving one, and what it reveals to the expert reading one. Next Thursday: What Are They Saying — reading between the lines of an opposing expert's testimony.

The Deposition as a Discovery Tool

Three people in the room. Three different stories. One of them is yours.

The Friendly Room

The deposition your own counsel takes is conducted under friendly conditions. Your law firm arranged it. They will ask questions that support their case. The atmosphere is professional and calm. Nobody is trying to destroy you.

And none of that means you are safe.

There are three parties to every litigation — the defendant, the plaintiff, and the expert. They never fully share the same story. The defendant has what happened to them. The plaintiff has what happened to them. The expert has what the evidence shows.

Those three stories overlap. They are never identical.

Your job in a deposition is not to reconcile the other two stories. It is to tell yours — the engineering story — cleanly, completely, and without letting either side pull it off its axis. Including your own side.

When Your Own Counsel Asks the Wrong Question

You may see the questions ahead of time. That is standard practice and it serves a legitimate purpose — you are not there to be surprised, you are there to give accurate testimony that supports the case as the engineering evidence supports it.

But sometimes a question tries to bridge a hole.

The attorney has a gap in their case. The forensic data does not fully close it. And the question — carefully worded, professionally delivered in that friendly room — is designed to stretch the engineering truth just far enough to fill the space. And your name gets hung on the bridge.

This is the hardest moment in a forensic engagement. Not the opposing cross-examination. Not the hostile double negative at trial. This moment — in the friendly room, with your own counsel waiting for an answer that helps their case.

Your credibility is not the attorney's asset to spend. It is yours. And it is the only thing that makes your testimony worth anything to anyone in that courtroom.

If the question stretches beyond what the evidence supports, you answer what the evidence supports. Precisely. In the language of the engineering. Nothing more.

What a Correction Costs You

A lawyer does not hear a correction as a clarification.

They hear it as a full rebuttal.

The moment you say — in any deposition, on any question, under any condition — "what I meant was" or "to clarify my earlier answer" — you have just told every person in that room that your prior testimony cannot be fully trusted. Not partially. Fully. Every answer you gave before that moment is now available for challenge.

This is why consistency of framework is not a preference. It is the discipline that protects everything you have said and everything you are about to say. Answer in the same terms. Use the same language. Stay inside the same boundaries every time.

Because the engineer who answers consistently — even under questions designed to stretch the forensic truth — never gives the correction that unravels the whole testimony.

No corrections. No clarifications. No edits.

Answer what was asked. In your framework. Then stop.

Reading the Opposing Deposition

Now you are back at your desk. The opposing expert has given their deposition and you have the transcript.

Most people read a deposition looking for the wrong answer. The answer that is factually incorrect, technically unsupportable, demonstrably at odds with the physical evidence. Those mistakes exist. They are not where the most useful information lives.

The gap never appears in the first sentence.

Watch the third and fourth questions. Watch where the attorney circles back — where they return to something they asked earlier, slightly reframed. That pattern is not accidental. The attorney is working around something. A weakness in the opposing expert's analysis. A finding that doesn't hold under a different line of questioning. A conclusion that required the expert to step outside their own evidence.

The gap shows in the pattern of the questions, not in any single question. The attorney who designed those questions knows exactly where the weakness is. Your job is to find it in the same place they found it — and hand it to your counsel as a fact, not a suspicion.

The Engineering Story Is the Only Story You Tell

Three people. Three stories. One of them is yours.

The defendant's story is about what happened to them. The plaintiff's story is about what happened to them. Your story is about what the evidence shows — what physically occurred, in what sequence, for what reason, to what effect.

Your story does not require the other two to be right or wrong. It requires the evidence to be followed wherever it leads. It requires the language to stay inside the engineering. It requires the framework to hold from the first answer to the last.

That consistency is not stubbornness. It is the thing that makes your testimony worth believing.

And it is the thing that makes the opposing deposition readable — because the expert who drifted from their framework, who answered outside their evidence, who accepted a question's premise when the premise wasn't supported — left a pattern in the transcript that a prepared forensic engineer can find.

Read the pattern. Tell your story. Make no corrections.

Next Thursday: What Are They Saying — reading between the lines of an opposing expert's testimony, and what the questions they chose to ask reveal about the gaps in their analysis.

Subscribe now

Leave a comment

This is Post 5 of 13 in The Forensic Engineer's Field Manual. Read the full series at inventorsmindblog.com.

Herbert Roberts, PE | Licensed Professional Engineer | Six Sigma Black Belt

Forensic Engineering Consultant | 32 Years Aviation R&D | 62 Patents

inventorsmindblog.com

What Every Business Leader and Young Engineer

Needs to Know About Evaluating Innovation

Here is the uncomfortable truth about most business education: it teaches you to evaluate markets but not technology.

You can build a discounted cash flow model in your sleep. You can size a TAM, segment a SAM, and calculate a SOM with your eyes closed. You can pitch a board, negotiate a term sheet, and build a go-to-market strategy that would make your MBA professors weep with pride.

But when someone puts an actual innovation in front of you — a working prototype, a patent portfolio, a sensor that does something no sensor has done before — can you tell whether it is real?

Can you tell whether the technology actually works, whether it will still work outside the lab, whether the claims are protectable, whether the manufacturing path exists, whether the regulatory timeline is realistic? Can you tell the difference between a genuine breakthrough and a polished demo that will evaporate the moment it meets real-world conditions?

Most business leaders cannot. Most young engineers cannot either, because engineering school teaches you to build things, not to evaluate whether someone else’s thing is worth building further.

This gap is expensive.

It leads to investments in technologies that cannot scale. It leads to partnerships with inventors who cannot deliver. It leads to strategic plans built on assumptions that any experienced engineer could falsify in ten minutes. Equally, it leads to the opposite error: dismissing genuinely transformative innovations because the evaluator lacked the vocabulary to understand what they were looking at.

I have been on both sides of this gap. Thirty-two years in aviation R&D taught me to build. Eight years in forensic engineering taught me to diagnose. Both careers taught me the same lesson: the ability to evaluate technology is a skill, and like any skill, it can be learned.

Today I want to give you two tools. Not frameworks. Not theories. Tools. Things you can use the next time someone puts an innovation on your desk and asks for your money, your time, or your championship.

Tool 1: The Megatrend Map

You do not need to understand how these technologies work. That is the engineer’s job. Your job is to understand that they are reshaping every industry simultaneously, and any innovation that ignores them is building on a foundation that is already shifting underneath it.

Eight technology megatrends are rewriting the rules of every market you will ever evaluate. When someone brings you an innovation, check it against this list. Not for how many it uses — but for whether it is aware of the ones that matter in its domain.

Notice what this table does not ask you to do. It does not ask you to understand transformer architectures, consensus algorithms, or CRISPR-Cas9 mechanisms. It asks you to look at the innovation on your desk and ask: is it aware of the forces that are reshaping its industry? Has the inventor thought about how AI changes the data layer? Has the inventor thought about what happens when connectivity fails? Has the inventor mapped the regulatory pathway?

If the answer to these questions is yes, the inventor is thinking systemically. If the answer is no, the inventor is building in a vacuum. Both answers are diagnostic. Neither requires you to be an engineer.

Tool 2: The First-Principles Test

This one is harder and more valuable.

Most innovations are described in terms of features. The sensor has six axes. The algorithm processes ten thousand data points per second. The material withstands twelve hundred degrees. Features are engineering language. They tell you what the thing does. They tell you nothing about whether the thing matters.

First-principles thinking strips the innovation down to its core value proposition. Not what it does. What it is for. The question is deceptively simple: what is the fundamental function this technology performs, and is there a simpler or cheaper way to perform it?

If the inventor cannot answer that question in one sentence without jargon, one of two things is true: the idea is too complex for its target market, or the inventor does not yet understand their own innovation. Both are disqualifying at this stage.

The One-Sentence Test

Every innovation should be expressible in the following structure. I call it the one-sentence test, and I use it on every idea that crosses my desk — including my own.

“This technology enables [specific user] to [specific action]

that they currently cannot do because [specific barrier],

resulting in [quantified benefit].”

Four blanks. If the inventor cannot fill in all four, they are not ready for market. Let me show you why each blank matters.

Here is the part that surprises people: this test is harder for the inventor than it is for the evaluator. The inventor has spent months or years deep inside the technology. They think in specifications. They dream in performance parameters. Asking them to compress all of that into one sentence is asking them to do something profoundly unnatural — to abandon the engineering details they love and speak in the language of the person writing the check.

The inventors who can do this are the ones who close deals. Not because the sentence is magic. Because the discipline required to write it forces the inventor to confront whether they actually know who their customer is, what the customer does with the technology, why the technology does not already exist, and what it is worth. Most inventors, when they sit down to fill in the four blanks, discover they can fill in two of them confidently and are guessing on the other two.

That discovery, made in your office rather than in a failed licensing meeting, is worth more than any financial model.

The Two-Minute Evaluation

You now have two tools. Here is how to use them together, in about two minutes, on any innovation that lands on your desk.

First: ask the inventor for the one sentence. If they cannot produce it on the spot, that is not a rejection. It is a diagnostic. Tell them to go write it and come back. The exercise itself will sharpen their thinking.

Second: scan the megatrend map. Which of the eight forces are relevant to this innovation’s domain? Has the inventor acknowledged them? Not used all of them — acknowledged them. An IoT sensor with no cloud strategy is a red flag. A biotech innovation with no regulatory timeline is a red flag. A data-intensive application with no AI layer is a red flag.

Third: trust what you have learned. If the sentence is clear and the megatrend awareness is present, you are looking at an inventor who thinks systemically. That does not guarantee the technology will succeed. It guarantees you are talking to someone worth spending more time with.

If the sentence is vague and the megatrend awareness is absent, you are looking at an inventor who is still inside their own head. They may have a brilliant technology. But they have not yet translated it into the language of the market, and until they do, no amount of financial modeling on your end will compensate for the lack of clarity on theirs.

The Skill That Pays for Itself

Evaluating innovation is not a talent. It is a skill. Like any skill, it improves with practice. The next ten innovations you see, run the one-sentence test and the megatrend scan. By the fifth one, you will start seeing patterns. By the tenth, you will feel the difference between an innovation that is ready for market and one that needs another six months of development before it deserves your attention.

That instinct — built through practice, not born from talent — is the single most valuable capability a business leader can develop in a technology-driven economy. It is the difference between the executive who says “I don’t understand the technology” and the executive who says “I understand enough to know this one is real.”

The first executive will always depend on someone else’s judgment. The second will make decisions that build companies.

Be the second one.

Not all new technology supports your business’s core mission. Some of it is genuine. Some of it is smoke in a slide deck.

The megatrend map is not a shopping list. It is a filter. The trends that matter are the ones that resolve a contradiction your customers have accepted as permanent. The trends that do not matter — no matter how impressive the demo, no matter how breathless the coverage — are the ones solving problems your customers do not have.

Here is your homework. It takes sixty seconds.

Look at that megatrend table one more time. Pick the one trend that keeps showing up in your inbox, your LinkedIn feed, your vendor pitches — the one everybody seems to be talking about. Now ask yourself: has that trend solved a single problem I actually have? Not a problem I might have someday. A problem I have right now, that costs me money or time or risk today.

If the answer is yes, you are looking at substance. Pay attention.

If the answer is no, you are looking at smoke. And that is fine — not every trend is for every business. The discipline is knowing the difference before you write the check.

Which trends are smoke for you? Tell us. Not to be cynical — to be precise. The best evaluators I have worked with in thirty-two years share one trait: they can articulate exactly why something does not fit as clearly as why something does.

That clarity is the skill. Build it with us.

Leave a comment

Subscribe now

Thanks for reading The Inventor’s Mind Blog’s Substack! Subscribe for free to receive new posts and support my work.

Herbert Roberts, PE, is a Licensed Professional Engineer with 32 years in aviation R&D, 62 patents, and over eight years of forensic engineering consulting for attorneys.

He publishes the Inventor’s Mind at inventorsmindblog.com

Part 3 of 3 | Inventor's Mind | Herbert Roberts, P.E. | Tuesday Engineering Series

In Part 1: Mat Armstrong flew to Miami to save a crashed Bugatti Chiron Pur Sport. Bugatti locked the VIN and declared it beyond repair. Armstrong split the chassis in a Miami shop and proved otherwise. In Part 2: a tool kit at seven years old, the wind-up car with the stamped tin gear, and the Ship of Theseus — repair as the oldest honest relationship between a person and an object. Read Parts 1 and 2 first.

Before the law, there is the culture. And the culture is where the damage is most visible.

A generation that was never handed a tool kit and told the world is knowable is now producing consequences that no legislation has addressed and no manufacturer has been held accountable for. They are not subtle consequences. They are sitting in landfills, on roadsides, in dealer service bays, and in driveways where a car with an ignored yellow warning light is three weeks from a catastrophic failure that a ten-dollar sensor could have predicted.

Consider the four symptoms in sequence. The new iPhone every year is not driven primarily by failure — it is driven by a marketing system sophisticated enough to convince a functional device's owner that adequacy is inadequacy. The AAA flat tire call is the logical outcome of a generation that was never shown that a spare, a jack, and twenty minutes is all a flat tire requires. The ignored dashboard warning light is what happens when an object's attempt to communicate with its owner is received as noise rather than information — because nobody ever explained that the car is telling you something specific and actionable. And the unchallenged service overcharge is the direct result of an information asymmetry so complete that a customer pays $400 for a five-minute cabin air filter replacement because they have no framework for knowing it is a five-minute job.

These are not separate problems. They are the same problem expressed across four different transaction types. The root is identical in every case: an owner with no mechanical literacy is an owner with no negotiating position. The manufacturer and the dealer understand this. They have understood it for decades. And they have made business decisions accordingly.

An owner who cannot read a warning light is an owner who cannot challenge a service quote. The information asymmetry is not a side effect of the system. It is the system.

Planned Obsolescence Has No Countermeasure

This is the hardest truth in the entire series, and it needs to be stated without softening:

Planned obsolescence is a business model that has operated for seventy years without a legal countermeasure, because the costs are diffuse, the beneficiaries are concentrated, and the mechanism is invisible to the person buying the product until the moment it fails.

It operates on three levels simultaneously, and the countermeasures people believe exist only address one of them.

Physical obsolescence is the level most people recognize — engineering a product to fail at a predictable point. The stamped tin gear. The battery calibrated to degrade below useful capacity in eighteen months. The solder joint designed to crack under thermal cycling after three years of normal use. Right to repair has a partial answer here: if you can open it, replace the battery, reflow the joint, swap the gear, you can interrupt the failure cycle. This is what Mat Armstrong demonstrated in Miami. This is what the FTC is fighting for in federal court against John Deere. This is where the legislative wave — Colorado, Minnesota, New York, California, Oregon — is aimed.

Functional obsolescence is the level the law has barely touched. The product still works. The battery still charges. The engine still runs. But the ecosystem around it has been deliberately moved. The iPhone that runs the current operating system but cannot run the current apps because the processor is one generation behind the minimum requirement Apple quietly raised. The printer that accepts only the current cartridge format, which changed the quarter after your warranty expired. The car whose diagnostic port speaks a protocol the aftermarket scanner no longer supports because the manufacturer updated it without publishing the change. You can repair every physical component in the device and it still cannot do what it needs to do, because the software environment was shifted on a schedule the manufacturer controls and the owner never consented to.

Psychological obsolescence is the level with no countermeasure. The product works perfectly. The software runs. The battery holds its charge. The engine starts on the first turn. But the cultural signal has been sent, through advertising budgets larger than the GDP of small nations, that owning last year's model says something inadequate about who you are. The new iPhone every year is not a response to failure. It is a response to a marketing system that has redefined functional as obsolete and current as identity. No law addresses this. No right to repair statute reaches it. The only countermeasure is the one a seven year old discovers on a kitchen floor: that an object which works is an object worth keeping, regardless of what the billboard says.

The three levels operate together as a coordinated system. The manufacturer engineers the physical failure to establish a replacement cycle. They shift the ecosystem to make repair insufficient even when physically successful. They market the replacement as identity to make the cycle feel voluntary. Each mechanism is individually defensible in court. Together they constitute a system that extracts maximum revenue from minimum product life with no legal exposure at any layer.

The landfill is the invoice. Fifty million tons of electronic waste per year globally is what planned obsolescence actually costs — paid not by the manufacturer but by the soil, the water table, and the communities living adjacent to the processing facilities, the majority of which are in the developing world. The manufacturer books the revenue. The world pays the bill.

Where the Law Currently Stands

The legal system is moving. It is moving slowly, unevenly, and with enough carveouts and exemptions to fill a law review journal. But it is moving, and the direction is clear.

Colorado enacted the first agricultural right to repair law in 2023, effective January 1, 2024, requiring farm equipment manufacturers to provide owners and independent repair facilities the same access to parts, tools, and documentation available to authorized dealers. Minnesota, New York, and California followed with electronics right to repair legislation. California's Right to Repair Act — effective July 1, 2024 — requires manufacturers to make documentation, parts, and tools available to any owner or independent repair facility on fair and reasonable terms, covering devices from smartphones to home appliances, with fines up to $5,000 per day for violations. Oregon passed the first law specifically prohibiting parts pairing — the practice of binding components to specific devices through software authentication so that even genuine parts from the same manufacturer will not function unless authorized through the manufacturer's system. More than a dozen additional states introduced right to repair bills in the first two months of 2025 alone.

Apple, which spent years lobbying aggressively against right to repair legislation across multiple states, publicly supported California's SB 244 in 2023. Consumer advocates called it an unexpected about-face. The more precise description is a strategic concession under simultaneous pressure from legislators, regulators, and shareholders — one the company then worked to limit through exemptions and carveouts within the same bill it publicly endorsed. The iPhone released the year Apple publicly supported the California law remained as resistant to independent repair as its predecessors. The support was real. The product design change was not.

The Magnuson-Moss Warranty Act of 1975 — still largely unknown to the American consumers it protects — already bars manufacturers from voiding warranties solely because an owner used a third-party part or an independent repair facility. The manufacturer must demonstrate that the independent repair actually caused the failure before denying warranty coverage. That federal protection exists now, for every consumer product, and has existed for fifty years. Most people have never heard of it. Most dealers act as if it does not exist. Most customers pay the authorized service price because they do not know they have the legal right to choose otherwise.

The FTC vs. John Deere: The Case That Changes Everything

The most significant legal action in the right to repair movement's history is not a state consumer protection statute. It is a federal antitrust lawsuit, and the distinction matters enormously.

On January 15, 2025, the Federal Trade Commission, joined by the Attorneys General of Illinois, Minnesota, Michigan, Wisconsin, and Arizona, filed suit against Deere and Company in the United States District Court for the Northern District of Illinois. The complaint alleges violation of Section 2 of the Sherman Act and Section 5 of the FTC Act — monopolization and unfair methods of competition. Not consumer protection. Antitrust.

The mechanism at issue is Deere's diagnostic tool, Service ADVISOR — the only fully functional software capable of performing all repairs on Deere agricultural equipment. Deere made this tool available exclusively to authorized dealers. A limited version exists for farmers and independent repair facilities, but the FTC alleges it is deliberately inferior — incapable of performing the full range of repairs the complete version handles. The result: as Deere's equipment became increasingly dependent on software for basic mechanical functions, an ever-expanding list of repairs could only be completed through Deere's authorized dealer network. Deere maintained a 100% market share on restricted repairs. Dealers charged accordingly.

Farmers brought the human cost of this structure into sharp focus. Combines sitting idle during harvest windows measured in days, not weeks. The nearest authorized technician two hundred miles away and booked for a week. Crops that cannot wait. Revenue that cannot be recovered. The FTC's complaint quoted Senator Elizabeth Warren's finding that Deere's repair restrictions cost American farmers $4.2 billion per year in downtime and elevated repair costs.

Deere called the complaint meritless and pointed to its ongoing negotiations with the government. The company had previously signed a Memorandum of Understanding with the American Farm Bureau Federation pledging to provide farmers the same tools available to dealers — but that agreement carried no enforcement mechanism and permitted Deere to withdraw with thirty days' notice. It was a promise without a penalty, and the FTC decided that was not enough.

In June 2025, a federal judge denied Deere's motion to dismiss. The case survived. Trial is pending. If the FTC prevails — or reaches a consent decree with structural teeth — the precedent extends well beyond tractors. An antitrust ruling that the withholding of diagnostic tools constitutes illegal monopolization of the repair aftermarket applies to every manufacturer that controls its own diagnostic ecosystem. That is not a narrow class.

The PE License Argument Nobody Has Made in Court

Everything above is documented, litigated, and moving through the legal system on its own momentum. What follows has not been argued publicly in the Armstrong case or in any right to repair proceeding I am aware of. It should be.

A Professional Engineer license is a state-granted credential. Its singular purpose is to authorize the holder to apply engineering knowledge and judgment in service of the public — to certify that a structure, a system, or a repair meets the standards required for safe operation. The PE stamp is a legal instrument. It carries personal liability. It is issued by the state. It supersedes preference.

That credential does not evaporate because a manufacturer locked a VIN.

If a licensed Professional Engineer assesses a repair, applies engineering judgment to the structural and mechanical condition of the vehicle, certifies that the work meets or exceeds the performance and safety standards required for the car's intended operation, and stamps that certification with their license number and their personal professional liability — on what legal basis does the manufacturer claim authority to override that determination?

Bugatti is not a licensing body. Mate Rimac holds no statutory authority over the practice of engineering in the United States, in Florida, or in any other jurisdiction where a PE-certified repair might take place. A PE license is issued by the state. The state's engineering authority does not dissolve at the boundary of a manufacturer's preferred revenue model.

The cost and conditions of that PE liability transfer are not defined by statute. No law specifies what a PE-certified independent repair of an exotic vehicle must cost. No law requires it to be performed in France. No law requires the parts to originate from the manufacturer at the manufacturer's price. Bugatti's $1.7 million quote is a business decision dressed as an engineering necessity. Rimac's decision to lift the parts blacklist under public pressure confirmed the necessity was negotiable — which means it was never a necessity. It was a price.

This argument reframes the entire dispute. Not owner versus brand. Not YouTube mechanic versus hypercar manufacturer. Licensed professional jurisdiction versus corporate revenue preference. A PE stamp certifies the repair is safe. The manufacturer's authorization certifies the repair is profitable for them. Only one of those is a public interest determination. Only one of those is backed by a state-issued credential and personal liability. The law has not been asked to choose between them in this context. It should be.

The Liability Gap They Cannot Close

Bugatti's stated justification for VIN lockdown is liability — the safety risk of structural repairs performed outside factory standards on a vehicle capable of 250 miles per hour. It is their strongest argument and the one that sounds most defensible in public.

Here is the gap in it they cannot close:

If a PE-licensed engineer certifies the repair, assumes the engineering liability, documents the work to a traceable standard, and stakes their professional license on the structural outcome — the manufacturer's liability argument collapses. They are no longer protecting public safety. They are protecting the margin. The liability has transferred to a credentialed professional with statutory authority. The manufacturer's refusal to support the repair at that point is not a safety decision. It is a commercial decision. And commercial decisions dressed as safety determinations are exactly what the FTC's antitrust framework is designed to address.

The Lemon Law Contradiction Nobody Has Named

Lemon laws were written on a foundational assumption so obvious that legislators never examined it: the manufacturer is the ultimate repair authority. If a vehicle cannot be fixed after a reasonable number of attempts through authorized channels, the manufacturer buys it back. The law grants the consumer relief precisely because it treats the manufacturer as the entity with both the obligation and the capability to make the product whole.

The right to repair record has now placed that assumption on federal trial.

The FTC's complaint against John Deere established on federal record that the authorized dealer network — the only legally permitted repair channel for restricted repairs — delivered neither the capability nor the competitive outcome the framework assumed. Farmers exhausted authorized repair attempts. Equipment stayed broken. Harvest windows closed. The monopoly the law implicitly endorsed failed the people it was supposed to serve.

Bugatti made the same failure explicit and public. The manufacturer claimed exclusive global capability over the Chiron chassis split. An independent engineer in Miami proved that claim false on camera in front of millions of viewers. The manufacturer's assertion of irreducible complexity did not survive contact with a determined professional who was willing to look.

The logical inversion is damning. Lemon laws say: if the manufacturer cannot fix it, the consumer gets relief. Right to repair evidence says: the manufacturer is sometimes structurally unwilling to fix it — not for engineering reasons but because their authorized network is optimized for revenue extraction, not repair outcomes. Which means lemon law protection and right to repair protection are not separate consumer issues. They are the same issue viewed from opposite ends of the same failure.

The deeper structural problem: lemon law relief triggers only after multiple failed repair attempts through authorized channels. If the authorized channel is the only legal channel — because the VIN is locked, the diagnostic tool is restricted, the parts are withheld — the consumer is forced to exhaust a remedy path the manufacturer controls before they can access legal relief. The manufacturer sets the pace of failure. They determine what constitutes a reasonable repair attempt. They control whether parts are available to attempt the repair at all. They have positioned themselves to define the conditions of their own accountability. The law handed them that position and has not yet noticed.

Lemon laws gave consumers relief when manufacturers could not fix their own products. Right to repair exposed that manufacturers frequently will not fix their own products. The law meant to protect the consumer assumed the very monopoly that makes the car unfixable.

The Engineering Absolute

Underneath all of it — the antitrust claims, the state statutes, the PE license jurisdiction, the lemon law contradiction, the planned obsolescence indictment — there is a foundational engineering truth that no manufacturer has ever successfully refuted and never will:

Nothing fabricated from parts is beyond disassembly. No part is beyond recreation or replacement — provided engineering integrity is maintained.

That is not opinion. It is the foundational premise of every repair, every overhaul, every failure analysis, every forensic investigation ever conducted in the history of manufacturing. The Chiron Pur Sport is carbon fiber, aluminum, steel, rubber, copper wire, and molded plastic assembled by human hands in a factory in Molsheim, France. It was built from parts. It can be disassembled into parts. Its components can be analyzed, recreated, and replaced by any engineer with the knowledge, tooling, and integrity to perform the work correctly.

The John Deere combine is steel, hydraulics, software, and sensors assembled on a production line in Waterloo, Iowa. The iPhone is glass, aluminum, silicon, and solder assembled by human hands in a factory in Zhengzhou, China. The wind-up car with the stamped tin gears was injection-molded plastic and sheet metal assembled on a line somewhere and sold in a box that implied precision it did not contain.

Every one of them can be opened. Every one of them will tell you the truth about how it was made and why it broke, if you are willing to look. The manufacturer does not own that truth. They assembled the object. They do not own the physics of the materials they used. They do not own the engineering principles governing how those materials behave under load, heat, impact, and fatigue. They own the trademark on the badge. They own the patent on specific innovations within a statutory term. They own the right to compete in the parts and service market through legitimate means.

What they do not own — what no manufacturer owns — is the right to be the sole arbiter of whether a repair is safe, the sole source of the parts that make a repair possible, and the sole authority over what happens to an object after a legal sale. The law is beginning to say so. The engineering record has always said so.

The Only Countermeasure That Has Ever Worked

The right to repair movement is fighting for access to parts, tools, and documentation. Those battles matter and some of them are being won. But the deeper fight — the one the legislative victories only partially address — is for the cultural transmission of mechanical literacy. The knowledge that passes from a person who opens things to a child watching over their shoulder. The permission structure that says the world is knowable and you are allowed to know it.

That transmission was how engineering knowledge moved through civilizations for ten thousand years before a manufacturer figured out how to make a screw that required a proprietary driver. It was interrupted not by a single decision but by a convergence of forces: a liability culture that decided tools were dangerous for children, a school system that eliminated shop class as an industrial-age relic, a consumer culture that reframed disposability as convenience and repair as an imposition, and a technology industry that built deliberate resistance to disassembly into its products and marketed the resistance as elegance.

The result is a generation that owns more technology than any generation in history and understands less of it. A generation that calls AAA for a flat tire. A generation that replaces a functional phone because the billboard said to. A generation that ignores the yellow light until the engine seizes because nobody ever explained that the car is trying to tell them something.

Planned obsolescence does not require a conspiracy. It requires only that the owner never learns to open the object. The stamped tin gear lasts exactly as long as the manufacturer needs it to last — which is until the warranty expires and the replacement cycle begins — because the owner never sees it. The moment you open the case, the business model is exposed. The moment you see how it was made, you see why it broke. And the moment you see why it broke, you understand what it would take to fix it — and whether it was worth fixing in the first place.

That understanding is what VIN lockdown, parts pairing, diagnostic tool restriction, and proprietary screws are designed to prevent. Not for safety. Not for quality. Because an owner who understands the object is an owner who cannot be charged whatever the system decides to charge. Because a customer who can fix the flat tire is a customer who does not need the roadside assistance subscription. Because a farmer who can clear the fault code is a farmer who does not need the authorized dealer two hundred miles away.

Armstrong opened the case. Rimac blinked. The parts blacklist was lifted. The FTC filed its complaint. Twelve states introduced legislation in eight weeks. The EU passed a Right to Repair directive. A federal judge denied the motion to dismiss.

The law is moving toward where the physics always was.

A tool kit at seven years old was a countermeasure against planned obsolescence. It just was not recognized as one at the time. Every child who learns to open something is a market the manufacturer loses permanent control of.

If you found value in this series, forward it to an attorney, a farmer, an independent shop owner, or a parent deciding whether to give a child a tool kit.

They are all fighting the same fight. The engineering record is on their side. The law is catching up. The only question is whether the culture catches up with the law before the next generation loses the instinct to open the case and look.

Leave a comment

Herbert Roberts is a licensed Professional Engineer with 32 years in aviation R&D, 62 U.S. patents, and 8 years of forensic engineering consulting serving attorneys on product liability and failure analysis cases. He publishes the Inventor's Mind series at Substack.

A Forensic Engineer’s Methodology for Reviewing Post-Accident Vehicle Photographs

Drawing Technically Sound Conclusions from Photographic Evidence

A vehicle tells the truth about its own accident. Not in words—in deformation patterns, fracture surfaces, paint transfers, fluid trails, and the geometry of structural collapse. Every crumple zone that absorbed energy, every hinge that yielded, every panel that buckled recorded the direction, magnitude, and sequence of the forces that created it. The physics is embedded in the sheet metal, and it does not change its story between the scene and the courtroom.

The problem is that physics does not photograph itself. Someone else does—an officer, an adjuster, a tow yard attendant, a party to the litigation—and the quality, completeness, and methodology of that photographic record determines what the forensic engineer can and cannot conclude. A technically sound opinion built from vehicle photographs requires more than looking at pictures of damaged cars. It requires a systematic methodology that extracts every available data point, identifies every limitation, and draws conclusions that the physical evidence actually supports.

For attorneys, understanding this process is not optional. It defines what your expert can deliver, what additional evidence you may need to obtain, and where opposing counsel will attack. What follows is the methodology—from first review through final conclusion—that separates defensible forensic analysis from casual observation.

Before the First Photograph: Establishing the Analytical Framework

A forensic engineer does not open a photo set and start looking for damage. That approach invites confirmation bias and guarantees that critical details will be overlooked. The analysis begins with establishing a framework—a structured set of questions that the photographs must answer before any conclusions can be drawn.

The framework starts with the claimed event. What type of collision is alleged? Frontal, rear, side impact, rollover, or a multi-event sequence? How many vehicles were involved? What are the claimed speeds, angles, and points of initial contact? These parameters define what the physical evidence should show if the claimed event actually occurred as described. Equally important, they define what the physical evidence should not show—because inconsistencies between claimed events and physical damage patterns are among the most powerful findings in forensic vehicle analysis.

Beyond the event parameters, the engineer must understand the vehicles themselves before examining damage. Year, make, model, trim level, and optional equipment packages all matter. A vehicle’s structural design—its crumple zone geometry, frame type, body construction method, and safety system architecture—defines how it absorbs and distributes impact energy. The same collision force applied to a body-on-frame truck and a unibody sedan produces fundamentally different deformation patterns, which means the engineer must know what the undamaged baseline looks like before evaluating the damaged condition.

The Systematic Review: Six Passes Through the Photographic Evidence

Experienced forensic engineers do not review photographs once. They review them in structured passes, each with a different analytical objective. This methodology ensures that the full informational content of the photographic record is extracted and that no category of evidence is overlooked because the analyst was focused on another.

Pass 1: Inventory and Chain of Custody

The first pass does not evaluate damage at all. It evaluates the photographs themselves. Who took them? When? Where—at the scene, the tow yard, the repair facility, a subsequent inspection? What camera or device was used? Are the images in their original format, or have they been cropped, resized, filtered, or otherwise altered? Is metadata available?

This matters because photographic evidence is only as reliable as its provenance. Scene photographs taken by responding officers within minutes of the event carry different evidentiary weight than photographs taken by a tow yard attendant three days later, after the vehicle has been moved, handled, and potentially exposed to additional damage. The forensic engineer must establish a timeline for the photographic record itself before relying on it to establish a timeline for the event. Photographs without known provenance do not become useless—but they require the engineer to qualify any conclusions drawn from them, which is a distinction that matters at deposition and trial.

Pass 2: Global Damage Assessment

The second pass establishes the overall damage pattern. The engineer examines the vehicle from all four quadrants—front, rear, left, and right—plus the roof and undercarriage if photographed. The objective is to identify the principal direction of force (PDOF) for each impact event, the extent of structural intrusion, and the general severity of the collision.

This is where the engineer begins testing the claimed event against the physical evidence. A rear-end collision produces a characteristic deformation pattern: rearward crush concentrated at bumper height, progressive engagement of the trunk or cargo area, potential displacement of the rear axle or suspension mounting points forward, and corresponding occupant compartment effects. If the photographic evidence shows a damage pattern inconsistent with the claimed impact direction—lateral deformation on a vehicle alleged to have been struck from behind, for example—the inconsistency must be documented and analyzed.

Global assessment also establishes what the photographs do not show. If only the front of a vehicle was photographed but the claimed event involved a multi-impact sequence, the absence of rear and side photographs creates an analytical gap that the engineer must disclose. The conclusion that “no damage was observed on the right side” is fundamentally different from “the right side was not photographed.” Conflating these two statements is a methodological error.

Pass 3: Localized Deformation Analysis

With the global pattern established, the third pass examines specific damage zones in detail. This is the most technically demanding phase of the photographic review, and it is where the engineer’s mechanical training becomes essential.

Localized analysis examines crush depth and profile. How deep is the deformation at each point across the damage zone? Is the crush uniform, indicating a broad flat-surface impact, or concentrated, indicating a narrow or angled contact? Does the crush profile exhibit the characteristics of an underride, override, or same-height engagement? Are there identifiable contact points—imprints from the striking vehicle’s bumper beam, license plate bracket, tow hook, or structural members—that can be matched geometrically to the opposing vehicle?

The engineer also evaluates the mode of deformation in each zone. Sheet metal can buckle, tear, fold, or stretch, and each mode provides information about the applied load. A panel that exhibits symmetric buckling was loaded in compression. A panel that exhibits tearing was loaded in tension or shear beyond its ultimate strength. A panel that exhibits folding was subjected to bending loads that exceeded its plastic moment capacity. These deformation modes, visible in photographs to a trained eye, constrain the range of forces and directions that could have produced the observed damage.

As with all localized analysis, the quality of the photographs directly limits the quality of the conclusions. Close-up images taken at oblique angles distort the apparent depth and extent of damage. Photographs taken in poor lighting obscure surface details. Images without scale references—a ruler, a known-dimension object, or a measurement notation—prevent the engineer from quantifying crush depth with confidence. Each limitation must be documented and its impact on the analysis assessed.

Pass 4: Contact and Transfer Evidence

The fourth pass searches for evidence of contact between vehicles or between a vehicle and another object. This category includes paint transfers, rubber deposits, fabric impressions, glass fragment distribution, and fluid trails—each of which provides independent data about the collision geometry.

Paint transfer is particularly valuable. The color, location, and height of transferred paint on one vehicle can be compared against the paint color and component geometry of the opposing vehicle to verify or contradict the claimed point of contact. A blue paint deposit at 22 inches above ground on the struck vehicle should correspond to a component on the striking vehicle that is blue and positioned at approximately 22 inches above ground. If it does not, the physical evidence contradicts the claimed collision configuration.

Fluid trails—coolant, oil, transmission fluid, fuel, or brake fluid—serve a different analytical function. Their location and flow direction on the vehicle’s underside and on the ground surface document the vehicle’s post-impact orientation and movement path. A coolant trail originating at the radiator and tracking rearward along the subframe indicates the vehicle was moving forward after radiator breach. The chemical identity of the fluid, its origin point on the vehicle, and its trail geometry all contribute to reconstructing post-impact vehicle dynamics.

Pass 5: Safety System Evidence

Modern vehicles contain multiple safety systems whose post-accident condition provides critical information about crash severity and occupant kinematics. Airbag deployment status, seatbelt pretensioner activation, structural collapse characteristics of energy-absorbing components, and headrest position all leave visible evidence in photographs.

Airbag deployment is a binary threshold indicator. Each airbag module is calibrated to deploy when crash deceleration exceeds a defined severity threshold for a defined duration, which means a deployed airbag confirms that the crash pulse met or exceeded the deployment criteria for that specific module. Equally important, an airbag that did not deploy indicates the crash pulse remained below the deployment threshold—a finding that constrains the maximum severity of the event. When multiple airbag modules are present (frontal, side curtain, knee bolster, seat-mounted), the pattern of deployment versus non-deployment creates a multi-point severity map that the engineer can use to characterize the crash event.

The engineer must also examine seatbelt evidence visible in photographs. Webbing stretch marks, D-ring position, buckle condition, and retractor lockup status all provide data about occupant loading during the event. Pretensioner deployment, visible as a retracted webbing condition with pyrotechnic residue at the retractor housing, confirms that the restraint system detected a qualifying event—another independent severity indicator.

Pass 6: Pre-Existing Conditions and Unrelated Damage

The final pass addresses a question that opposing counsel will inevitably raise: how much of the observed damage was caused by the subject accident, and how much existed before it? Distinguishing accident damage from pre-existing conditions is essential to a credible analysis, and photographs provide several diagnostic criteria.

Rust and oxidation patterns are the most reliable indicators. Fresh deformation exposes bare metal that has not had time to oxidize. Damage with established rust, particularly in deformed areas where paint was removed, predates the recent event. Similarly, paint condition provides temporal information. A scratch with oxidized edges and embedded road grime is older than a scratch with bright, clean edges and fresh paint transfer.

The geometry of damage also distinguishes events. Pre-existing damage from a prior collision will exhibit a different principal direction of force, a different height profile, and potentially a different crush depth distribution than damage from the subject event. Where two damage patterns overlap, the analysis becomes more complex—but the physical principles remain the same. The deformation most recently applied will be superimposed on the earlier deformation, and metallurgical characteristics such as work hardening at fold lines can sometimes establish the relative sequence of events.

Beyond collision damage, the engineer must assess overall vehicle condition. Worn tires, corroded brake lines, deteriorated suspension components, cracked windshields, and inoperative lighting are not collision damage—but they may be relevant to causation. A tire with tread depth below minimum standards, visible in a high-resolution photograph, can support or undermine a loss-of-control theory. A brake line with visible corrosion may be relevant to a claimed brake failure. The engineer must identify these conditions when they appear in the photographic record, even when they fall outside the specific question that counsel has asked.

Multi-Vehicle Analysis: Correlation and Contradiction

When photographs of two or more vehicles are available, the analytical power increases substantially—but so does the complexity. The forensic engineer must now perform a correlation analysis: do the damage patterns on Vehicle A match the damage patterns on Vehicle B in a manner consistent with the claimed collision geometry?

This analysis operates on the principle of geometric compatibility. The crush profile on the front of the striking vehicle should correspond inversely to the crush profile on the side of the struck vehicle. Contact heights should match. Damage widths should be consistent. Paint transfer colors should correspond. If Vehicle A has blue paint transfer at bumper height and Vehicle B is blue with damage at bumper height showing Vehicle A’s paint color, the physical evidence corroborates the claimed contact. If these parameters do not align, the engineer must determine whether the discrepancy results from post-impact vehicle dynamics, photographic limitations, or a fundamentally flawed event narrative.

Multi-vehicle analysis also enables energy-based severity assessment. The total energy absorbed by both vehicles in a collision must be consistent with the closing speed and impact configuration. If Vehicle A shows minor cosmetic damage and Vehicle B shows major structural deformation, the asymmetry must be explainable by the relative structural stiffness of the two vehicles at the point of contact. A compact sedan striking the side of a heavy truck will sustain far more deformation than the truck, and the photographic evidence should reflect that physical reality. Damage distributions that are inconsistent with the known structural properties of the involved vehicles require explanation.

The Pitfalls: Where Photographic Analysis Fails

The Two-Dimensional Trap

Photographs are two-dimensional representations of three-dimensional objects. Crush depth, which is the single most important parameter for energy-based severity analysis, cannot be reliably measured from a standard photograph unless a calibrated reference is present and the camera angle is known. A photograph taken at an oblique angle exaggerates damage that is oriented toward the camera and minimizes damage that is oriented away from it. The forensic engineer must account for perspective distortion in every conclusion drawn from photographic crush measurements and, where possible, corroborate photographic observations with physical measurements, scanner data, or repair estimates that include dimensional documentation.

Insufficient Coverage

The most common photographic deficiency is incomplete coverage. Insurance adjusters typically photograph damage zones relevant to the repair estimate, not to the forensic analysis. Police officers photograph the scene for documentation purposes, often capturing only the most visually dramatic damage. Neither is trained to document the systematic evidence categories that a forensic engineer needs.

A complete forensic photographic record requires all four quadrants at consistent angles, close-ups of all damage zones with scale references, undercarriage documentation, interior photographs showing safety system status and occupant compartment condition, tire condition at all four positions, and—for multi-vehicle accidents—comparative photographs showing the contact geometry between vehicles. When this record does not exist, the engineer must clearly communicate which conclusions are limited by photographic gaps.

Timing and Contamination

Vehicles are dynamic objects in the post-accident environment. They are moved by tow trucks. They are handled by salvage yards. They are disassembled by repair facilities. They are exposed to weather. Each of these interactions can alter, obscure, or destroy physical evidence. Photographs taken after significant handling may show conditions that do not reflect the vehicle’s post-accident state, which means the forensic engineer must consider the chain of custody for the vehicle itself—not just the chain of custody for the photographs.

Resolution and Quality Limitations

A photograph cannot reveal what its resolution cannot capture. Surface textures, fine cracks, paint transfer boundaries, and corrosion patterns that are visible to the naked eye may be invisible in a compressed digital image taken from ten feet away with a smartphone. The engineer must assess whether the available image quality is sufficient to support the intended conclusion. An opinion about microscopic crack propagation based on a low-resolution photograph taken from across a tow yard is not defensible—and an expert who offers one has built the opposing counsel’s cross-examination for them.

Drawing the Conclusion: From Evidence to Opinion

After the six-pass review is complete, the forensic engineer possesses a structured inventory of what the photographs reveal, what they constrain, and what they leave unresolved. Drawing a technically sound conclusion requires navigating each of these categories with precision.

Conclusions that the photographic evidence fully supports can be stated to a reasonable degree of engineering certainty. The principal direction of force, confirmed by deformation patterns across multiple vehicle zones, is a conclusion the photographs can directly support. The relative severity ranking of a multi-event collision, confirmed by the relative crush depths at each damage zone, is a conclusion the photographs can support. The presence or absence of contact between specific vehicles, confirmed by geometric compatibility and transfer evidence, is a conclusion the photographs can support.

Conclusions that the photographs constrain but do not fully determine require careful qualification. A closing speed estimate derived from photographic crush analysis carries wider uncertainty bounds than one derived from calibrated physical measurements, and the engineer must communicate those bounds. A failure mode hypothesis consistent with the visible deformation pattern but not confirmed by metallurgical examination remains a hypothesis, not a conclusion. The discipline of distinguishing between what the evidence proves and what it suggests is not a weakness—it is the foundation of credibility.

Conclusions that the photographs cannot support must be explicitly identified. If the photographic record is insufficient to determine whether a particular component failed before or during the collision, the engineer must say so rather than speculate. If the image resolution cannot support a quantitative crush measurement, the engineer must use qualitative severity descriptors rather than fabricated numbers. The trier of fact is better served by an honest assessment of analytical limitations than by false precision.

The Strategic Imperative

Post-accident vehicle photographs are among the most common—and most commonly misunderstood—forms of evidence in collision litigation. Attorneys who treat them as visual aids for the jury miss their analytical potential. Forensic engineers who treat them as substitutes for physical inspection overstate their conclusions. The photographs occupy a specific position in the evidentiary hierarchy: more informative than witness testimony about damage severity, less precise than calibrated physical measurements, and uniquely valuable when analyzed with the right methodology.

The methodology described here—establishing the analytical framework, conducting structured multi-pass reviews, performing multi-vehicle correlation, documenting limitations, and drawing appropriately qualified conclusions—transforms a stack of photographs from a collection of images into a technical narrative. That narrative, grounded in mechanical engineering principles and constrained by intellectual honesty, is what the trier of fact needs to understand what the vehicles experienced and what the physical evidence actually proves.

Metal does not forget. It records every force applied to it in permanent deformation, and it does not change its testimony under cross-examination. The forensic engineer’s task is to read that record accurately, communicate it clearly, and resist the temptation to say more than the evidence supports. That is the difference between an expert opinion and an informed guess—and it is the difference that determines whether your case stands or falls.

Leave a comment

Subscribe now

This is Post 4 of 13 in The Forensic Engineer’s Field Manual. Read the full series at inventorsmindblog.com.

Herbert Roberts, PE | Licensed Professional Engineer | Six Sigma Black Belt

Forensic Engineering Consultant | 32 Years Aviation R&D | 62 Patents

inventorsmindblog.com

When Engineers Pour Concrete and a Truck Driver Swears Off Flying

Herbert Roberts, P.E. | Inventor’s Mind Blog

Engineers have a reputation for being cheap. Not frugal—cheap. The distinction matters, because frugality implies calculation, which is precisely the problem. An engineer watches a tradesman frame a wall or sweat a copper joint and thinks, “I understand the physics of what that person is doing, which means I can do it myself.” The reasoning feels airtight. The results rarely are.

This is a story about a driveway, a sidewalk, a concrete delivery truck, and a group of jet engine engineers who learned—the hard way—that understanding thermodynamics does not qualify you to finish a four-inch slab.

The Setup

My colleague Joe was building a house. He needed a driveway and sidewalk poured, and rather than hire a concrete contractor—which any homeowner with functioning judgment would do—he invited a group of his fellow engineers to come over and help. Free labor. What could go wrong?

When we arrived, Joe had built wooden forms staked into the ground along the sidewalk pathway and driveway edges. He’d assembled a collection of masonry tools: floats, edgers, brooms, and a few loose eight-foot 2×4s that would serve as screed boards. The crew got to work laying wire mesh and rebar in the open areas of the pour sites.

The concrete truck was running late. So we sat around. We talked about work. We talked about the weather. What we never discussed was (a) what to do when the delivery truck actually arrived, (b) who among us had any experience finishing concrete, or (c) whether any of us had ever touched a masonry float in our lives. The answer to all three, as it turned out, was nobody and nothing.

The Pour

When the truck finally arrived, the driver had limited maneuvering room. He pulled along the edge of the street and swung his chute toward the large open driveway. But the chute could only reach so far—roughly two feet off the street edge—which meant the material had to be hand-shoveled into the back corners of the driveway against the garage, and then shoveled another twenty feet down the sidewalk form to reach the main door of the house.

This is the moment when the gap between theory and practice becomes a physical sensation in your lower back. Wet concrete is extraordinarily heavy. Each shovelful fights you. The delivery driver was falling behind schedule and calling for us to work faster, which is the concrete-truck equivalent of telling someone to calm down—it has never once produced the desired effect.

We struggled. We were in over our heads, and the material did not care.

The Finishing (Such As It Was)

Eventually we got the material roughly in place. Some of the crew began trying to screed water off the top layer of the driveway, only to discover that the 2×4s were eight feet long and the driveway was twenty feet wide. Someone grabbed nails and hammered three boards together end to end. This is not how professional concrete crews operate.

Simultaneously, others moved on to edging with trowels—the wrong trowels—while a few began broom-finishing the driveway surface to add texture. The driver, who had been watching this unfold with increasing alarm, pointed out that the driveway was not firm enough to broom finish yet. He noted that we were using the wrong tool for rounding the edges. And then he asked the question that none of us had considered: why were we not cutting sectioning seams into the thirty-foot-long sidewalk slab?

Silence.

The sidewalk had no expansion gap material. It was going to be a single four-foot-wide, thirty-foot-long monolithic slab. Any first-year concrete worker knows what happens to a slab like that: it cracks wherever it wants, and the results look terrible.

The Rescue

The driver saw that we were hopeless. He climbed down, grabbed the correct edging tool, and began giving the sidewalk and driveway the proper rounded edges. Then he used a groover to divide the sidewalk slab into four-foot sections, sliding the tool across the wet surface in straight lines, each line forming a groove with a rounded edge on both mating faces.

He explained the engineering behind what he was doing: after the mix cures, it will crack along the control joints he cut into the surface. The controlled cracks form their own expansion joints. You are not preventing the crack—you are directing it along a weakened plane so it happens where you choose rather than where random stress concentration dictates. Elegant. Systematic. Precisely the kind of thinking engineers claim to practice.

The Punchline

The driver then asked where we all worked. He could see plainly that we knew nothing about construction and had no discernible skills when it came to pouring or finishing concrete.

We told him we worked at the jet engine company. That we designed and built jet engines for a living.

The look on his face was pure, undiluted horror.

He repeated it slowly: “You guys design jet engines?”

When we reassured him that we did, he climbed back into his truck and said, “I am never getting on an airplane to go anywhere.”

Then he drove off to his next delivery.

The Dunning-Kruger Driveway

The psychologists David Dunning and Justin Kruger documented what most tradespeople already know: people with limited knowledge in a domain tend to dramatically overestimate their competence in that domain. The less you know, the less equipped you are to recognize how much you don’t know. The effect is not about intelligence—it is about the specific blindness that comes from standing outside a field and assuming you can see the whole landscape.

Engineers are particularly susceptible. The analytical training that makes us effective at our jobs creates a metacognitive trap. We learn to break complex systems into constituent parts, model their behavior, and predict outcomes. This works brilliantly for the systems we are trained in. It fails spectacularly when applied to domains where the critical knowledge is embodied—stored not in equations but in the hands, eyes, and accumulated muscle memory of a practitioner.

Consider what the concrete truck driver knew that we did not: (a) how far a chute reaches and how to plan material placement accordingly, (b) when a surface is ready for broom finishing based on visual cues and touch, (c) which tool rounds an edge versus which cuts a control joint, (d) the spacing and depth of relief cuts needed to direct cracking, and (e) the pace at which all of this must happen before the hydration reaction takes the decision out of your hands. None of that knowledge comes from a textbook. It comes from doing hundreds of pours, which is to say it comes from a form of engineering education that happens to be delivered by a truck chute instead of a lecture hall.

Expertise Is Not Transferable. Respect Is.

Every one of us on that crew could calculate thermal stress on a turbine disk, specify the creep life of a nickel superalloy blade, or design a combustion liner to survive thousands of hours at temperatures that would melt the concrete we were struggling to flatten. None of that knowledge told us when mud was ready to finish.

The driver’s logic was perfectly rational from his vantage point. If this crew cannot manage a straightforward residential pour, what are they doing to the engines that keep aircraft at altitude? What he could not see—because the Dunning-Kruger effect works in all directions—was that the skill sets do not transfer. Mastery in one domain confers no advantage in another. As with turbine design, concrete finishing is a discipline, which means it demands its own apprenticeship, its own failures, and its own thousand hours of calibrated repetition.

The lesson is not humility for its own sake. The lesson is that respect for a tradesperson’s expertise is not generosity—it is accuracy. The concrete driver read that slab better than any of us could read a stress plot, and he did it in real time, with the clock running. That is mastery. The fact that it was expressed with a groover instead of a finite element model does not diminish it by a single degree.

Joe’s wife told this story at every company family gathering for years. The engineers laughed. The spouses laughed harder. And somewhere out there, a concrete truck driver is still taking the bus.

Leave a comment

Herbert Roberts, P.E.

Inventor’s Mind | inventorsmindblog.com

Part 2 of 3 | Inventor's Mind | Herbert Roberts, P.E. | Tuesday Engineering Series

Missed Part 1? A man paid $1.9 million for a crashed Bugatti. The manufacturer locked the VIN, cut the parts supply, and told him only they could fix it. An independent mechanic split the chassis and proved otherwise. Read Part 1 first.

The Bugatti story is not about one car. It is about a legal fiction installed quietly across the American consumer economy over the past thirty years — the fiction that purchasing a physical object means owning it.

Nobody signs a contract that reads: you are purchasing a use license. The transaction looks like a sale. Money changes hands. You take possession of a physical object. Title transfers. By every visible measure, you own a thing.

But buried in the warranty conditions, the end-user license agreement, the terms of service — language that effectively says: we retain control over how this object functions, who may service it, and what happens when it breaks. The manufacturer does not say this at the point of sale. They do not have to. They have encoded it in the hardware, the software, and the supply chain. The physical object enforces the contract they never disclosed.

Three Industries. One Playbook.

Apple serialized iPhone components so that a genuine Apple screen pulled from another iPhone will not function in yours without factory authorization through their proprietary diagnostic system. The part is real. The phone is real. The wall is a software decision, not an engineering one.

John Deere locked tractor ECUs so that a sensor fault — the kind a farmer with a multimeter and thirty years of mechanical knowledge could clear in ten minutes — requires a dealer visit, a dealer diagnostic tool, and a dealer schedule. Harvest does not wait for dealer appointments. Crops failed while authorized technicians were booked out.

Bugatti locked a VIN so that no authorized dealer on earth would sell parts for a car a private citizen legally owns. No court order. No regulatory determination. A database entry.

Three industries. Three mechanisms. One operating premise: the sale was never really a sale. You bought access. You purchased the right to operate the product inside the manufacturer's rules. The moment you step outside — repair it yourself, use an independent shop, salvage it — you have violated something they never disclosed at the point of purchase.

The premium is not for the part. The premium is not for the skill. The premium is for the permission — and permission should not be a product.

The Parts Fiction: When a Bugatti Is an Audi

Mate Rimac, to his credit, confirmed something important when he argued against the Chiron rebuild: some Bugatti airbags share part numbers with those used in the Audi A3. His argument was that even identical-looking parts may be calibrated differently for different applications. That is partially correct for safety-critical systems.

What it also confirmed — without intending to — is the supply chain reality the entire luxury automotive industry prefers not to advertise.

The automotive industry sources components from a small set of tier-one suppliers: Bosch, Continental, Denso, ZF, Valeo, Magna. A brake caliper destined for a Porsche 911 and one destined for a Volkswagen Golf may come off the same manufacturing line at the same Continental facility. The casting is identical. The metallurgy is identical. The performance envelope is identical. Porsche charges four times more because the box says Porsche.

Oil filters, alternators, water pumps, sensors, fuel injectors, window regulators, lighting modules — the OEM aftermarket markup over the identical part sold under a generic or supplier label routinely runs 200% to 800%. In luxury and exotic marques it crosses 1,000% routinely. Not because the engineering is different. Because the label is different.

Rimac's argument that safety-critical components require factory-calibrated parts for a specific vehicle's mass and crash geometry is legitimate — and narrow. It applies to airbag deployment thresholds, crash sensors, and structural fasteners. It does not apply to hood panels, coolant hoses, headlight assemblies, or a throttle pedal made of molded plastic. The safety argument covers perhaps ten percent of the parts the lockdown affects. The other ninety percent are protected by the same mechanism for one reason: margin.

The Skills Fiction: When the Dealer Knows Less Than the Independent

A dealer technician is not an engineer. In most cases they are a certified parts replacer — trained to run a manufacturer's diagnostic tool, read the fault code, identify the flagged module, remove it, install the replacement, clear the code, and close the ticket.

That is a legitimate skill. It is not a $300 per hour skill. It is a $75 per hour skill operating inside a manufacturer-controlled pricing structure because the manufacturer decides who is permitted to hold the diagnostic tool.

The independent mechanic with thirty years of experience who diagnoses a fault without a computer, fabricates a solution when the part is unavailable, and warrants his own work — that technician is by any honest engineering measure more skilled than the dealer tech. He is locked out of the authorized repair market not because he cannot perform the work but because he cannot purchase the software license.

The compounding insult is structural. The manufacturer trained the technician. The manufacturer controls the diagnostic tool. The manufacturer supplies the parts at markup. The manufacturer sets the labor rate schedule. The manufacturer determines what qualifies as an authorized repair. Every variable in the transaction is controlled by the same entity that profits from all of it. That is not a market. That is a toll booth with a badge on it.

The Aftermarket Proof: The Physics Do Not Require the Password

The right to repair debate assumed for years that OEM complexity was a genuine barrier — that the sophistication of modern vehicle systems made independent repair genuinely dangerous. The aftermarket engine management industry demolished that assumption with receipts.

MoTeC, Link ECU, MaxxECU, Haltech, AEM — these are not garage projects. MoTeC systems run factory-backed Formula 1 programs, Le Mans prototypes, and World Rally Championship builds. The calibration sophistication in a MoTeC M1 exceeds what ships in most production road car ECUs because the aftermarket has no incentive to dumb it down for liability management or dealer service revenue protection.

The OEM tunes to a compromise position — one that satisfies emissions certification, warranty exposure, dealer serviceability, and liability counsel simultaneously. The aftermarket tunes to the actual application. In specific performance domains the aftermarket has not just matched OEM engine management capability — it has lapped it.

The integration architecture the aftermarket community developed proves the modularity directly: running a stock ECU for body functions — windows, lighting, climate — while the aftermarket ECU manages engine control is now standard practice in high-performance builds. These systems are separable, documentable, and manageable outside the factory environment. The monocoque is not a sealed oracle. The W16 is not irreducible complexity. It is a mechanical and electronic system built from documented physics that any sufficiently trained engineer can interrogate.

Rimac said only a few people in the world have the training to manage a Chiron's systems. MoTeC has trained calibration engineers on six continents managing more complex power systems than a W16 in active racing programs. Complexity is not the barrier. Authorization is the barrier. Those are not the same thing — and the aftermarket proved it.

The manufacturer does not own the physics. They own the password. Those are not the same thing.

The PE License Argument Nobody Has Made

A Professional Engineer license is a state-granted credential. Its purpose is singular: to authorize the holder to apply engineering knowledge and judgment in service of the public — to certify that a structure, a system, a repair meets the standards required for safe operation. The PE stamp is a legal instrument. It carries personal liability. It supersedes preference.

That credential does not evaporate because a manufacturer locked a VIN.

If a licensed Professional Engineer assesses a repair, applies engineering judgment to the structural and mechanical integrity of the vehicle, certifies that the work meets or exceeds the standards required for the car's intended operation, and stamps that certification with their license number and their personal liability — on what legal basis does the manufacturer claim authority to override that determination?

Bugatti is not a licensing body. Rimac holds no statutory authority over the practice of engineering in the United States. A PE license is issued by the state. The state's engineering authority does not dissolve at the boundary of a manufacturer's preferred revenue model.

The cost and conditions of that PE liability transfer are not defined by statute. There is no law specifying what a PE-certified independent repair must cost, where it must occur, or who must perform it. The manufacturer's $1.7 million quote is a preference. It is not a legal standard. It is not the only path to a certifiably safe repair. It is the only path to a repair that preserves their margin — and those are not the same thing.

This argument has not been made publicly in the Armstrong case. It should be. It reframes the entire dispute: not as an owner versus a brand, but as a licensed professional's jurisdiction versus a corporation's preferred business model. A PE stamp says the repair is safe. The manufacturer's authorization says the repair is profitable for them. Only one of those is a public interest determination.

The Liability Gap They Cannot Close

Bugatti's stated justification for VIN lockdown is liability — safety concerns about repairs performed below factory standard on a vehicle capable of extreme speeds. It is their strongest argument and the one that sounds most reasonable in public.

Here is what they cannot answer: if a PE-licensed engineer certifies the repair, assumes the engineering liability, documents the work to a traceable standard, and stakes their professional license on the outcome — the manufacturer's liability argument collapses. They are no longer protecting the public. They are protecting the margin.

Furthermore: the cost and conditions of that liability transfer are not defined by statute. No law specifies what an independent PE-certified repair of an exotic vehicle must cost. No law requires it to occur in France. No law requires the parts to come from the original manufacturer at original manufacturer pricing. The $1.7 million quote is a business decision dressed as an engineering necessity. Rimac's own decision to lift the blacklist under public pressure confirmed that the necessity was negotiable — which means it was never a necessity.

The Lemon Law Contradiction Nobody Has Named

This is where the legal system reveals the internal contradiction it has been carrying for decades without noticing.

Lemon laws were written on a foundational assumption: the manufacturer is the ultimate repair authority. If a car cannot be fixed after a reasonable number of attempts through authorized channels, the manufacturer buys it back. The law grants the consumer relief precisely because it treats the manufacturer as the entity with both the obligation and the capability to make the product whole.

The right to repair record has now put that assumption on federal trial.

The FTC's January 2025 lawsuit against John Deere — survived a motion to dismiss in June 2025, now headed to trial — established on federal record that Deere's authorized dealer network delivered neither the repair capability nor the competitive outcome the framework assumed. Farmers brought equipment to the only legally authorized repair channel. The equipment did not get fixed. Harvest windows closed. The authorized monopoly failed the people it was supposed to serve.

Bugatti made the same failure explicit. The manufacturer claimed exclusive capability over the Chiron chassis split. A determined independent engineer in Miami proved that claim false in public, on camera, in front of millions of viewers.

The logical inversion this creates is damning. Lemon laws say: if the manufacturer cannot fix it, the consumer gets relief. Right to repair evidence says: the manufacturer is sometimes structurally incapable of fixing it — not for engineering reasons but because their authorized network is optimized for revenue, not outcomes. Which means lemon law protection and right to repair protection are not separate consumer issues. They are the same issue viewed from opposite ends of the same failure.

The deeper problem is structural. Lemon law relief triggers only after multiple failed repair attempts through authorized channels. If the authorized channel is the only legal channel — because the VIN is locked, the diagnostic tool is restricted, the parts are withheld — the consumer is forced to exhaust a remedy path the manufacturer controls before they can access legal relief. The manufacturer sets the pace of failure. They determine what constitutes a reasonable repair attempt. They control whether the parts are available to attempt the repair at all.

They have positioned themselves to define the conditions of their own accountability.

Lemon laws gave consumers relief when manufacturers could not fix their own products. Right to repair exposed that manufacturers frequently cannot — or will not — fix their own products. The law meant to protect you assumed the very monopoly that makes the car unfixable.

Where the Law Currently Stands

The legal system is moving — slowly, unevenly, but moving.

Colorado enacted the first agricultural right to repair law in 2023, effective January 1, 2024, requiring farm equipment manufacturers to provide owners and independent shops the same access to parts, tools, and documentation available to authorized dealers. Minnesota, New York, and California followed with electronics right to repair legislation. California's law — effective July 1, 2024 — requires manufacturers to make documentation, parts, and tools available to any owner or independent repair facility on fair and reasonable terms, covering devices from smartphones to home appliances, with fines up to $5,000 per day for violations. Oregon passed the first law specifically prohibiting parts pairing — the Apple practice of binding components to specific devices through software.

Apple, which spent years lobbying against right to repair legislation in California and New York, reversed course in 2023 and publicly supported California's SB 244. Advocates called it an unexpected about-face. The more precise description: a strategic concession under legislative, regulatory, and shareholder pressure — one the company then sought to limit through exemptions and carveouts. The iPhone 15, released the same year Apple publicly supported the California bill, remained as resistant to independent repair as its predecessors.

The John Deere federal lawsuit represents the most significant legal action in the movement's history. The FTC, joined by six state attorneys general, alleges violation of the Sherman Act and the FTC Act — antitrust law, not consumer protection law. That framing matters. Antitrust claims carry the possibility of structural remedies: forced access to tools, mandated parts availability, and ongoing oversight. A consent decree or trial verdict in the FTC's favor would establish a precedent extending well beyond tractors.

The Magnuson-Moss Warranty Act of 1975 — still largely unknown to American consumers — already bars manufacturers from voiding warranties solely because a consumer used third-party parts or an independent repair facility. The manufacturer must demonstrate that the independent repair actually caused the failure before denying warranty coverage. That protection exists now, at the federal level, for every consumer product. Most people have never heard of it.

The Engineering Absolute

Underneath all of it — the legal arguments, the legislative battles, the antitrust claims, the PE license jurisdiction — there is a foundational engineering truth that no manufacturer has ever successfully refuted and never will:

Nothing fabricated from parts is beyond disassembly. No part is beyond recreation or replacement — provided engineering integrity is maintained.

That is not an opinion. It is the foundational premise of every repair, every overhaul, every failure analysis, every forensic engineering investigation ever conducted in the history of manufacturing. The Chiron Pur Sport is carbon fiber, aluminum, steel, rubber, copper wire, and molded plastic, assembled by human hands in a factory in Molsheim, France. It was built from parts. It can be disassembled into parts. Its components can be analyzed, recreated, or replaced by any engineer with the knowledge, tooling, and integrity to do the work correctly.

Rimac's safety concern about the monocoque is real. It is also narrow. It does not extend to the ninety percent of the lockdown that has nothing to do with structural integrity and everything to do with preserving a margin that depends on the consumer never being permitted to find out what the part actually costs.

The manufacturer does not own the physics of the materials they assembled. They do not own the engineering principles that govern how those materials behave under load, heat, impact, or fatigue. They own the trademark on the badge. They own the patent on specific innovations. They own the right to charge a premium for genuine parts through legitimate market competition.

What they do not own — what no manufacturer owns — is the right to be the sole arbiter of whether a repair is safe, the sole source of the parts that make a repair possible, and the sole authority over what happens to an object after a legal sale.

Armstrong proved it with a TIG welder and a section of brake hose. The physics were never Bugatti's to withhold.

If you found value in this series, forward it to an attorney, an independent shop owner, or a farmer.

They are fighting this fight with less information than they deserve. The law is moving in their direction. The engineering record is already on their side.

Leave a comment

Subscribe now

Herbert Roberts is a licensed Professional Engineer with 32 years in aviation R&D, 62 U.S. patents, and 8 years of forensic engineering consulting serving attorneys on product liability and failure analysis cases. He publishes at Inventor's Mind on Substack.

A field guide for attorneys who need to vet, prepare, and protect their expert witnesses

Herbert Roberts, P.E. | forensicfailures.com

The Expert Witness Problem Attorneys Never Discuss Openly

You retained an expert with the right credentials. The CV checked out. The preliminary opinions looked solid. And then something went wrong in deposition — a phrase, a characterization, a moment where the engineer stopped being a technical analyst and became an advocate, a speculator, or a witness the judge had no choice but to limit.

It is not always the opposing expert who damages your case. Sometimes it is yours.

After three decades in engineering — including aviation R&D, failure analysis, and forensic consulting — I can tell you that the gap between a defensible expert and an excludable one is often a single sentence. What follows are the 12 statements that create that gap. Each one is a red flag you can listen for when vetting an opposing expert, and a guardrail you can install before your own expert walks into the deposition room.

The 12 Triggers — Organized by the Failure They Represent

Each entry includes the statement pattern, the legal or procedural red flag it raises, and what it signals about the expert's preparation, methodology, or understanding of their role.

Scope and Disclosure Failures

1. "My opinions extend a bit beyond my written report, but..."

Red Flag: Scope violation. FRCP 26(a)(2) requires complete disclosure of all trial opinions in the expert report. Testimony beyond that scope is excludable.

What It Signals: This expert either did not complete the report properly or is improvising under pressure. Either outcome weakens your case. File the motion in limine if this surfaces at deposition.

2. "The plaintiff is entitled to..." or "The defendant is liable for..."

Red Flag: Ultimate issue testimony. The expert has crossed from engineering analysis into legal conclusion — which is the court's domain, not the engineer's.

What It Signals: Opposing counsel will move to strike this testimony as an improper legal conclusion. Your own expert should know where engineering analysis ends and legal argument begins. If they do not, prepare for a Daubert challenge.

3. "Based on what the client told me, I concluded that..."

Red Flag: No independent investigation. The expert has adopted the retaining party's narrative without examining the physical evidence directly.

What It Signals: Expert opinions must rest on direct investigation, not secondhand accounts. An expert who has not personally examined the failed component, the accident site, or the relevant documentation has a foundation problem that opposing counsel will exploit in cross-examination.

Methodology and Daubert Vulnerabilities

4. "In my experience, this type of failure means..."

Red Flag: Speculation. No testable methodology behind the conclusion. This triggers Daubert's reliability requirement under FRE 702.

What It Signals: Experience alone does not meet the reliability standard. Federal courts have excluded engineers with decades of field experience who could not articulate a reproducible, peer-reviewed methodology underlying their opinions. Ask your expert: what is the method, not just the conclusion.

5. "I used my own proprietary analytical method to reach this conclusion."

Red Flag: Untested methodology. Novel methods that have not been peer-reviewed, lack known error rates, or fall outside generally accepted engineering practice will not survive Daubert.

What It Signals: The methodology must be transparent, reproducible, and grounded in published standards or recognized engineering practice. A method only the expert uses and only the expert validates is an exclusion waiting to happen.

6. "I focused on the most relevant evidence to my conclusion."

Red Flag: Cherry-picking. The expert has selectively presented evidence while ignoring data that contradicts or complicates the primary finding.

What It Signals: A qualified forensic engineer considers all relevant evidence — including evidence that does not support the desired conclusion — and discloses it. An expert who cannot explain the contradictory data is an expert opposing counsel will methodically dismantle.

Advocacy and Role Confusion

7. "What really happened here is that the company decided..."

Red Flag: Advocacy language. The expert has shifted from neutral technical analysis to arguing your case — which is your job, not theirs.

What It Signals: Judges have seen this pattern. An expert who sounds like an advocate loses credibility with the trier of fact. Your expert's job is to educate the jury about engineering principles, not to argue the verdict. If they cannot separate those functions, your case is at risk.

8. "The defendant clearly intended to cut corners to save money."

Red Flag: Intent and motive testimony. State of mind is outside the scope of engineering analysis and is improper expert testimony.

What It Signals: The engineer can testify that a specification was violated, that a lower-grade material was substituted, or that documented procedures were not followed. Why the party made that choice is for the factfinder. An expert who speculates about motive has handed opposing counsel a gift.

9. "I do not believe the witness is being truthful."

Red Flag: Credibility judgment. Assessing witness veracity is exclusively the province of the jury. This testimony will not survive objection.

What It Signals: The engineer can testify that physical evidence contradicts a witness account or that a described sequence of events is mechanically impossible. The conclusion about truthfulness belongs to the jury. An expert who crosses this line invites exclusion and signals to the court that they do not understand their role.

Credential and Boundary Violations

10. "As a structural engineer, I can also speak to the thermal dynamics..."

Red Flag: Out-of-discipline opinion. The expert is offering testimony outside their licensed area of competency.

What It Signals: PE licensure has defined boundaries. An expert who wanders outside their documented discipline — under pressure from counsel, in response to a deposition question, or through simple overconfidence — gives opposing counsel grounds for exclusion on that portion of the testimony.

11. "My CV reflects my extensive experience in this area." (When it does not.)

Red Flag: Credential misrepresentation. Exaggeration, omission, or implication regarding qualifications is grounds for exclusion and professional discipline.

What It Signals: Opposing counsel will verify the CV. Every claim about licensure, publications, prior testimony, and relevant experience will be checked. An expert whose credentials do not match their representations is an expert you cannot put on the stand.

12. "In my dual role as the company's engineer and your retained expert..."

Red Flag: Fact witness and expert witness conflict. Serving in both roles on the same matter creates disclosure and privilege issues that must be managed before they become trial problems.

What It Signals: The roles carry different obligations, different privileges, and different evidentiary standards. An expert who has not disclosed this conflict — or who does not understand why it matters — has created a procedural vulnerability. Identify and resolve this before deposition, not during it.

How to Use This List

Before retaining: Ask your candidate expert to walk through their methodology for a case similar to yours. Listen for the patterns above — experience substituting for method, advocacy language, scope creep beyond their discipline.

Before deposition: Review statements 1, 2, and 11 with your expert directly. Confirm the written report captures every opinion they intend to offer. Confirm credentials are accurately represented. Confirm they understand the line between engineering analysis and legal conclusion.

During opposing expert deposition: Run the 12 triggers as a listening framework. Any of these patterns, properly documented, supports a Daubert motion or a motion to strike specific testimony.

Download the Deposition Red Flag Checklist — the single-page field version of this framework, formatted for deposition prep and courtroom use.

This is Post 3 of 13 in The Forensic Engineer’s Field Manual. Read the full series at inventorsmindblog.com.

Herbert Roberts, PE | Licensed Professional Engineer | Six Sigma Black Belt

Forensic Engineering Consultant | 32 Years Aviation R&D | 62 Patents

inventorsmindblog.com

He Never Worked Here, but He Knew Better Than Us

The John Wooden story that still makes me change the channel

Every March when the tournament bracket drops, I think about a speech.

Not the game. The speech.

—

It was an all-hands meeting. Two thousand engineers in Greenville, South Carolina — gas turbine country, the kind of place where machines the size of a house are built by people who have spent careers learning to make complex things work simply.

The new head of engineering had just arrived from Cincinnati. He had spent his career in aviation, where every fastener is torqued to specification, every assembly is safety-wired, and every analysis is run to exhaustion — because the consequence of failure at 35,000 feet is binary.

He walked the plant for five minutes. He decided what he was looking at.

Then he stood in front of two thousand engineers — men and women from 25 to 55 years old, with decades of combined experience — and he told us about John Wooden.

Wooden, he explained, started every season at UCLA with a lesson on how to tie your shoes. Because the little things matter. Because championships are built on fundamentals. Because you never get too good for the basics.

He told this story every year for three years. In his eyes we were idiots. And because he had to repeat the story each year, we clearly were slow learners too dumb to get better. After all, he spent 20 minutes telling this story last year. How could could that much detailed coaching not fix all the problems he saw.

—

Here is what he got right: John Wooden was a great coach. The shoe-tying lesson is a genuine insight about attention, discipline, and the compounding effect of small habits done correctly.

Here is what he got wrong: Wooden was coaching 18 and 19-year-old men. New players every season. Boys becoming men under direct, daily supervision. He had practice time, film sessions, and the full attention of his athletes for months at a stretch.

The man telling us this story saw the two thousand of us once a year, for at best 40 minutes of one way communication. Leadership at its best. So if he was right, what did he do about it?

There was no remedial training program. No budget for fundamentals instruction. No follow-up. Just the story, a round of applause for the new leadership, and then back to work.

Wow, he really earned his money. Thanks.

—

What the Aviation GM saw when he walked that plant was genuinely different from what he had come from, and he was not wrong about that.

In aviation, a cotter pin is the minimum acceptable anti-rotation device for a critical fastener. You do not hammer a dent in the metal. You do not locally peen a hole to keep a pin from backing out. You design, fabricate, and install the correct engineered solution every time, because a failure at altitude kills people.

In a land-based gas turbine, the machine is three times the size of an aircraft engine. It sits on a foundation. It experiences 1G of load, always in the same direction, which is down. Nothing is going to shake loose due to flight-based twist or strain. So you thermally fit an airfoil into its slot — heat the outer ring, slide in the cold part, let physics lock it in place when the temperatures equalize. No special tools. No engineered snap rings. No $700 torque wrenches. Just an elegant application of material properties you already understand.

This is not laziness. This is engineering optimized for the correct set of constraints.

The engineers in that room had already done the hard work of understanding their problem. They had removed every ounce of unnecessary complexity because unnecessary complexity costs money, extends maintenance time, and introduces failure modes that do not exist when you keep it simple. They had built a discipline around simplicity that took years to develop.

He walked in and saw simple solutions. He mistook them for simple minds.

—

The Wooden story has authority because Wooden had authority — earned through decades of direct coaching, daily contact, and real accountability for outcomes. Borrowing the story without the relationship behind it does not borrow the authority. It just borrows the words.

Two thousand engineers sat politely. We clapped at the right moments. We filed out and went back to the machines.

Three years later, he retired to his executive compensation package. The engines kept running.

—

If you have ever sat in a room and been talked to like you were a problem to be fixed rather than a professional to be trusted — you already know what that afternoon felt like.

You held the line. You kept working. You did not become what the speech implied you were.

That is not a small thing.

P.S. The jokes on him, I wore loafers.

Leave a comment

Subscribe now

Herbert Roberts, P.E. spent 32 years in aviation R&D and has spent the last 8+ years analyzing engineering failures for attorneys. He writes about the decisions — not the people — that determine whether complex systems thrive or fail. Subscribe to The Inventor's Mind at inventorsmindblog.com.

Part 1 of 3 | Inventor's Mind | Herbert Roberts, P.E. | Tuesday Engineering Series

A man bought a car. The car was damaged. He hired a mechanic. The manufacturer told the mechanic to stop.

See the YouTube story at:

https://youtu.be/tz0tO9zt87Y?si=Hz_QtWqaQOqlqb2r

That is the entire story — and in a country built on property rights, it should not be possible.

The car is a Bugatti Chiron Pur Sport, one of sixty ever produced. The mechanic is Mat Armstrong, a British YouTube creator who has built a career resurrecting cars that insurers gave up on. The manufacturer is Bugatti — now led by CEO Mate Rimac, who built his reputation as an engineering visionary. The mechanism Bugatti used to stop the repair was not a court injunction, not a safety recall, not a regulatory action. It was a VIN lockdown — a quiet administrative decision that instructs every authorized dealer on earth to refuse to sell parts for that specific vehicle identification number.

No court order. No statute. No safety determination with legal weight. A database entry. That is all it took to effectively strip a man of the right to repair something he paid $1.9 million to own.

How a Hypercar Becomes a $1.9 Million Paperweight

The crash happened in Miami. The Chiron Pur Sport — valued at $4 to $4.5 million — struck another vehicle hard enough to deploy airbags, crack carbon fiber panels, and heavily damage the transmission. The insurer paid out. Standard process. The original owner, content creator Alex Gonzalez, then did something unusual: he bought his own car back from the Copart salvage auction for approximately $1.9 million.

Bugatti flew a technician from France to inspect it. The verdict: total loss. The car received a salvage title. Bugatti locked the VIN.

Gonzalez contacted Rimac directly. Rimac made two offers: (a) ship the car to the factory in Molsheim, France, for full restoration, or (b) accept a negotiated repair for $600,000 to $700,000. Gonzalez declined both. He wanted the car rebuilt in Miami, on his terms, by people he chose to trust. His concern was direct — in his words, that once the car shipped to France "they start stripping it apart, and then they find more and more issues with it, and the price adds up more." He brought in Armstrong.

What followed is one of the most technically compelling rebuild series on the internet — and one of the clearest illustrations of what right to repair actually means when real money and real engineering meet a manufacturer's wall.

The Damage Was Real. The Obstacles Were Larger.

Armstrong flew from the UK to Miami to see the car in person. The front end had absorbed the full force of the impact — misaligned panels, destroyed headlights at roughly $90,000 each, a cracked carbon fiber fender at the same price, a hood at $60,000, and the signature horseshoe grille surpassing $90,000. Those were the visible numbers.

Underneath, the picture was worse. The gearbox housing had fractured. The monocoque — the carbon fiber structural tub that serves as the Chiron's skeleton — had sustained structural damage. The crash had driven the engine forward, squashing coolant lines and fracturing a cast aluminum engine-mount support.

Rimac addressed this publicly on Instagram. His position was measured and partially correct: "We just don't think it's safe. I'd love to support it, but it's not the right thing to do." He described the Chiron as a "very valuable asset" engineered to remain on the road fifty to one hundred years from now. He stated that "only a few people in the world" have the training to properly separate the rear subframe from the monocoque. He was genuinely concerned about structural repairs performed below factory standard on a car capable of 250 miles per hour.

Armstrong split the car in his Miami shop.

Rimac said only two places in the world could split the Chiron chassis. Armstrong proved there was a third.

Engineering Around the Wall

What followed is a textbook demonstration of what engineers actually do when legitimate supply chains are cut off: they go deeper into the physics than the manufacturer ever had reason to go.

The gearbox mount presented the first "impossible" problem. This component is engineered to fracture deliberately in a crash — its failure mode is the design intent, redirecting crash forces through the body structure rather than into the drivetrain. A replacement was unavailable through the locked VIN and prohibitively expensive through any other channel. Armstrong's team located a specialist who TIG welded it back together. Most engineers would call that weld impossible on a component designed to fail under load. The weld held.

A pinched coolant overflow pipe needed replacement. No Bugatti parts were coming. The team adapted a section of rigid brake hose. The system sealed and held pressure.

Armstrong noted, almost in passing, that the throttle pedal controlling 1,500 horsepower in a $4 million machine is molded plastic. Not billet aluminum. Not aerospace composite. Plastic — the same category of material in a $30,000 family sedan. The mythology of irreducible Bugatti complexity contains multitudes.

At each step the team documented everything on camera. Millions of viewers watched. Rimac watched too — he said so publicly.

The Moment the Manufacturer Blinked

Under sustained public pressure and the documented evidence that the rebuild was progressing without him, Rimac eventually lifted the parts blacklist and reduced Bugatti's repair estimates. He framed it as support. The sequence of events framed it differently: a manufacturer who claimed exclusive capability over a repair backed down when a determined engineer demonstrated otherwise on camera.

Armstrong's response throughout was measured. He was not trying to build a brand conflict. He was trying to exercise the right of an owner — and the judgment of a trained mechanic — over a machine that a customer legally purchased.

"Of course, we're not going to be able to do it to Bugatti's factory standards," Armstrong said. "But again, we're going to give it a go."

That sentence deserves more weight than the internet gave it. It is not bravado. It is the foundational statement of every independent repair professional who has ever faced a manufacturer's wall: I understand the standard. I accept the responsibility. I am going to try.

Bugatti's response to that position was to lock the database entry and wait for the money to run out.

The question Armstrong's story surfaces is not about one car.

It is about a system — a system in which a manufacturer can make a quiet administrative decision after a legal sale and strip the buyer of the practical ability to use, repair, or restore what they purchased. Not through law. Not through safety regulation. Through a database entry and a parts embargo.

Part 2 publishes next Tuesday. In it: the legal architecture behind VIN lockdown, why your $4 million car may share airbag part numbers with an Audi A3, what aftermarket ECU builders know that Bugatti's dealers do not, why a Professional Engineer's license outranks a manufacturer's preference, and the one lemon law contradiction that breaks the entire system open.

Subscribe now

Leave a comment

Herbert Roberts is a licensed Professional Engineer with 32 years in aviation R&D, 62 U.S. patents, and 8 years of forensic engineering consulting serving attorneys on product liability and failure analysis cases. He publishes the Inventor's Mind series at Substack.

You paid $1.9 million for a car. The manufacturer added your VIN to a database and made it unfixable.

No court order. No safety recall. A database entry.

This is not a Bugatti problem. Apple does it with a software flag. John Deere does it with a locked diagnostic tool. The mechanism changes. The result is identical: you hold the title, you bear the cost, you carry the risk — and the manufacturer decides what you are permitted to do with the object you purchased.

That is not ownership. That is a lease you did not know you signed.

Three-part series starts Tuesday. Link in first comment.

The Only Way Out Is Out

Why the escape team saves the company —
and why the CEO always kills it afterward

Herbert Roberts, P.E. | inventorsmindblog.com

The pattern is hiding in plain sight across three industries and six decades.

Every major industrial breakthrough that saved a company, won a war, or remade a market came from a team that first had to escape the organization that needed it most.

This is not coincidence. This is a systems failure that repeats with enough regularity to qualify as a law. And underneath the systems failure is an ego failure that almost nobody in the boardroom will say out loud.

117 Days. No Rules. Best Fighter of the War.

In 1940, the British government asked North American Aviation to produce a new fighter in 120 days. North American had never built a fighter. No fighter program, no fighter culture, no institutional rules about how fighters were supposed to be built.

They had engineers, a deadline, and nobody telling them what they couldn’t do.

The P-51 Mustang flew as a prototype in 117 days. Aviation historians still argue about whether any single aircraft changed a war more. The P-51 gave the Allies the long-range escort fighter that could protect bombers all the way to Berlin and back. Without it, the daylight bombing campaign does not survive.

North American didn’t build the best fighter of World War II because they were the best aviation company. They built it because they were outsiders working outside the rules that governed the insiders.

Twenty years later, Ford tried to buy Ferrari. Enzo Ferrari refused. Henry Ford II did not route the revenge project through Ford’s normal development process — that would have taken years and produced a committee. He handed it to Carroll Shelby, an outsider operating well outside the Ford machine, and gave the team permission to break the rules.

The GT40 won Le Mans in 1966. Then 1967. Then 1968. Then 1969. Four consecutive years. Ferrari didn’t win again until 2023.

Neither story is about genius. Both are about escape.

Boca Raton: The Rules Don’t Apply Here

In 1980, IBM was the largest technology company on earth. Apple, Commodore, and a dozen smaller companies were selling personal computers. IBM had nothing.

Not because they lacked engineers, capital, or market intelligence. IBM had all three. The reason was that their development process took four to five years to produce a new product. The personal computer market was moving in months.

Bill Lowe made the argument: give me a small team, let us work outside the system, and we will build you a PC in one year. IBM’s leadership said yes. That decision alone was more consequential than anything the team subsequently built.

Don Estridge set up in Boca Raton, Florida — deliberately far from IBM headquarters in Armonk, New York. Off-the-shelf components instead of proprietary IBM parts. Open architecture anyone could build on. The operating system outsourced to a small company called Microsoft. Estridge ignored corporate phone calls, skipped review meetings, made decisions without permission.

August 12, 1981. One billion dollars in revenue in year one.

The escape worked. Again.

The Real Reason Escape Teams Exist

Here is what nobody in the boardroom says out loud.

The escape team is not a structural workaround. It is a confession. Every time a company runs a skunkworks — every time a CEO says “small team, outside the system, go” — they are admitting something the organizational chart will never show.

The CEO cannot do the one thing a CEO is supposed to be able to do.

The reason is not incompetence. The reason is that the job of a mature organization’s CEO is fundamentally a maintenance job. Protect the revenue stream. Optimize the processes. Deliver the known output reliably at scale. Legitimate, valuable, extraordinarily difficult — but not an innovation job.

Jack Welch was the greatest maintenance CEO in American industrial history. GE under Welch didn’t invent anything. He optimized, cut, ranked, and financially engineered a conglomerate into a profit machine. The street loved him for it. He called himself an innovator. He wasn’t. He was the best optimizer who ever lived — genuinely remarkable — but he confused optimization for creation, and GE paid for that confusion after he left.

IBM’s leadership made the same error. They greenlit Estridge’s team not because they understood what he was building — but because the mainframe business was threatened and they needed a hedge. The moment the hedge paid off, they absorbed it back into the optimization machine.

I was working near Boca Raton in 1990. At an ASME professional meeting, I sat across from engineers who had been part of the IBM PC team. They were getting laid off.

What I remember is not bitterness — though there may have been some underneath. What I remember is resolve. A quiet professional resolve from people who knew exactly what they had built and exactly why the company they had built it for didn’t understand it. Every one of them had job offers. Dell wanted them. HP wanted them. Compaq wanted them.

IBM built the industry that caught its own people when IBM let them fall.

Michael Dell had weaponized the open architecture into something IBM couldn’t compete with. Dell was Henry Ford applied to computers. Ford didn’t mine his own steel. Dell didn’t fabricate his own chips. Ford standardized the Model T so assembly was ruthlessly repeatable. Dell standardized the order process so fulfillment was ruthlessly efficient. Ford killed the custom coachbuilder industry. Dell killed the IBM proprietary margin forever.

IBM sold its PC business to Lenovo in 2004 for approximately one billion dollars — roughly what the PC did in revenue in its first year alone.

The One in a Million — But Not the First Version

Now consider the one CEO who figured it out. But not the first version of him. The first version of Steve Jobs was as bad as any CEO in this column. Worse, possibly, because he had more talent to waste.

First-era Jobs was a product narcissist with a vendetta. His entire strategic frame was “kill IBM” — not “serve the customer.” The Lisa failed completely. The original Mac nearly failed. Closed architecture, proprietary everything, priced out of the market he needed to win. He was so focused on IBM that he didn’t see Microsoft coming from the side. While he was building the perfect closed weapon to kill the mainframe company, Gates was licensing the OS to everyone with a factory. Apple’s board fired him in 1985. Correctly.

What happened next is the part that matters.

Jobs didn’t spend his exile defending himself. He went to NeXT — essentially a personal escape team with a building — and built something beautiful that almost nobody bought. That is a very specific kind of humiliation. The market is too honest to negotiate with. NeXT was architecturally brilliant and commercially insufficient, and Jobs had to look at that result without a board to blame or a Wozniak to hide behind.

You cannot go through that and come out the other side still believing you are the genius in the room.

He came back to Apple in 1997 transformed. Not because he had better ideas — because he had lost the ego that made his ideas dangerous. He learned that the idea is not enough. The team that executes the idea is everything.

The cigarette pack. All your music. Go.

That is not engineering. That is not product management. That is a single declarative image handed to a pirate team by an admiral who has learned — the hard way — that his job is to hold the image and protect the team from interference while they solve the problem.

And here is what makes him genuinely singular: he was not embarrassed by the pirate flag. He flew one — literally, over the original Mac building. Most CEOs run escape teams in secret because acknowledging them is an admission that the main organization can’t innovate. Jobs announced it. He celebrated it. He understood that the navy exists to maintain order and the pirate exists to find the new world.

He lost some ego and hugged the small team. In the history of American business, that sentence describes exactly one CEO at the top of a company that mattered.

Sculley: The Counter-Proof

The man Jobs recruited with the greatest sales pitch in corporate history — “Do you want to sell sugared water for the rest of your life?” — spent thirty years writing, speaking, and podcasting to prove that firing Jobs was justified.

That is the un-Jobs.

And the brutal irony is that Sculley was not wrong about the vision. The Newton was eleven years early — not eleven years wrong. Handwriting recognition, personal digital assistant, wireless sync, contact and calendar integration. Every concept is in your pocket right now. The silicon wasn’t ready. The wireless infrastructure didn’t exist. The battery technology couldn’t support it. The handwriting recognition was the punchline of a Doonesbury comic strip because the processor wasn’t fast enough to run it reliably.

If the iPhone chip exists in 1992, the Newton ships as a phone and Sculley is the father of the smartphone. Not Jobs. Sculley.

But the chip didn’t exist. And Sculley couldn’t wait — and couldn’t admit the constraint was the supply chain, not the vision — and the ego never left the building. Every board seat he took in the 2000s was framed as proof that the Apple chapter wasn’t his fault.

Same company. Same firing. Completely opposite response to humiliation.

One became one in a million. One became a cautionary footnote.

The iPhone: The Most Elegant Revenge in Business History

Jobs spent a decade waiting for the silicon to catch up. Building the team. Controlling the supply chain. Negotiating the carrier deals. He didn’t write a memoir about being right too early. He didn’t give speeches about being wrongly fired.

He walked onto a stage in January 2007 and introduced three things — a widescreen iPod, a revolutionary phone, and an internet communicator. Then he said they weren’t three separate devices. Then he pulled one object out of his shirt pocket.

Sculley’s Newton was the punchline of a comic strip. Jobs’ iPhone was the cover of every magazine on earth the next morning.

No bitterness. No mention of Sculley. No rehabilitation tour. Just a cigarette pack that made phone calls — built by a pirate team that the one-in-a-million CEO had protected long enough to get it right.

First-era Jobs tried to kill IBM with a closed machine and got fired for his ego. NeXT Jobs got humbled by the market and learned what a pirate team actually needs. Second-era Jobs handed Sculley the most elegant defeat in corporate history — not with a lawsuit, not with a memoir, but with an object that fit in a shirt pocket and did everything the Newton promised and couldn’t deliver.

The Verdict

The escape team saves the company. The CEO takes the credit. Nobody learns the lesson.

The P-51 — the Air Corps didn’t restructure procurement after the war. The GT40 — Ford walked away from racing entirely. The IBM PC — absorbed back into the machine, milked for margin, sold to Lenovo for a billion dollars.

The escape is the confession. Every skunkworks is the organization admitting that the system cannot do what the moment requires. The CEO who runs escape teams and then kills them is the CEO who needed the confession but refused to learn from it.

Jobs is the one CEO who looked at the pirate flag, smiled, and understood that flying it was the job.

Not because he was born that way. Because the market humbled him, the exile taught him, and the second chance — the rarest gift in American business — arrived at the exact moment he had lost enough ego to deserve it.

You cannot build a company around waiting for that. But you can build an escape hatch. You can fly a pirate flag. You can hand a small team a cigarette pack image and get out of the way.

The system can do that even when the CEO can’t.

The best revenge in business is not proving you were right. It’s shipping the product your enemy couldn’t.

Change your ask, change your outcome.

Subscribe now

Leave a comment

Herbert Roberts, P.E.

32 years in aviation R&D | 62 U.S. Patents | Southwest Ohio

Inventor’s Mind | inventorsmindblog.com

What every licensed PE needs to know before stepping into a deposition

Herbert Roberts, P.E. | #ForensicEngineering : inventorsmindblog.com

The Deposition Is Not the Problem. The Engineer Is.

Thirty years of building expertise. Dozens of patents, failure analyses, and design reviews. A PE stamp earned through discipline and time. And then twelve words in a deposition chair reduce it to nothing.

It happens. Not because engineers are dishonest. Because expert witness testimony operates under a legal and ethical framework that engineering school never covered — which means the engineer who walks in confident walks out excluded. I have watched it happen to colleagues with credentials that dwarfed mine. The rules are not forgiving, and opposing counsel is paid to find the gap.

What follows are 12 statements that will compromise your credibility, invite a Daubert challenge, trigger sanctions, or end 9your expert witness practice entirely. Some are obvious. Others are the kind of phrasing that feels reasonable until a federal judge explains why it is not.

The 12 Statements — and Why They End Careers

These are organized by the failure mode they represent: scope violations, methodology failures, advocacy creep, and professional boundary errors. Each one is a real pattern. Each one is avoidable.

Scope Violations — When You Go Beyond What You Were Retained to Do

1. "My opinions on this matter extend beyond my written report."

Federal Rule of Civil Procedure 26(a)(2) is not a suggestion. Every opinion you intend to offer at trial must appear in your expert report before deposition. Testimony that strays outside that written disclosure is subject to exclusion — which means opposing counsel can shut you down mid-sentence with a motion in limine. The engineer who wings it in deposition hands the other side a procedural weapon. Write the report as if the trial depends on it. It does.

2. "The plaintiff is entitled to compensation for..."

The moment you cross from engineering analysis into legal conclusion you have abandoned your role and entered opposing counsel's closing argument. The ultimate issue — who wins, what damages apply, what the legal standard requires — belongs to the court. Your job is to explain what the engineering evidence shows. The jury decides what it means legally. Any engineer who confuses these two functions will be qualified by the court as a witness who does not understand the rules of the room.

3. "I did not personally examine the component, but based on what I was told..."

Every opinion must be grounded in direct investigation. Relying on secondhand accounts, accepting the retaining attorney's narrative without examining the physical evidence, or rendering conclusions on components never inspected violates the foundational principle of forensic engineering practice. If you have not done the work, you cannot offer the opinion. There are no shortcuts in failure analysis, which is why engineers who try to take them get destroyed on cross-examination.

Methodology Failures — When the Engineering Doesn't Hold Up

4. "In my experience, this type of failure usually means..."

Experience is not methodology. Daubert and Federal Rule of Evidence 702 require that expert opinions rest on sufficient facts or data, apply reliable principles and methods, and connect that application to the specific facts of the case. "In my experience" is a signal to opposing counsel that no testable methodology exists behind the conclusion. Courts have excluded engineers with 40 years of experience for exactly this reason. Methodology must precede opinion, always.

5. "I relied on a proprietary analytical method I developed."

Novel or untested methods that have not been subjected to peer review, that lack known error rates, or that fall outside generally accepted engineering practice face Daubert's reliability prong — and rarely survive it. Published standards, recognized testing protocols, and established failure analysis frameworks are defensible. A method only you use, only you have validated, and only you can explain is an invitation to exclusion. If the methodology cannot withstand challenge, the opinion built on it will not survive either.

6. "I focused on the evidence most relevant to my conclusion."

Relevant to your conclusion is not a standard. All relevant evidence — including data that complicates, contradicts, or limits your primary finding — must be considered and disclosed. The forensic engineer who selects only the evidence that supports the desired outcome has not done engineering analysis. They have done advocacy. That distinction matters in deposition, where opposing counsel will ask directly whether you reviewed contradictory data. The answer must be yes, and you must be prepared to explain it.

Advocacy Creep — When the Engineer Becomes the Attorney

7. "What really happened here is that the company decided to save money by..."

You are not an advocate. The moment testimony crosses from objective analysis into argument for a party's position, the expert has left engineering and entered the realm of closing argument — which belongs to counsel. Your obligation is to educate the trier of fact about what the engineering evidence shows and what it means. The expert who argues the case rather than analyzing it loses credibility with judges who have seen this pattern a hundred times.

8. "The defendant clearly intended to cut corners."

State of mind, intent, and motive are outside the scope of engineering testimony. You can testify that a design choice deviated from established practice, that a lower-cost material was substituted where specification required a higher-grade alternative, or that documented maintenance schedules were not followed. What you cannot offer is why a party made a particular decision. The physical record speaks. The interpretation of why belongs to the factfinder, not the engineer.

9. "I do not believe the witness is telling the truth."

Witness credibility is exclusively the province of the jury. As an engineer you can point to physical evidence that contradicts a witness account, identify inconsistencies between testimony and documented facts, or explain why a described sequence of events is mechanically impossible. The evidence does the work. Offering personal judgments about veracity is outside your role, outside your competence, and precisely the kind of overreach that opposing counsel will use to paint you as a hired gun rather than a neutral technical expert.

Professional Boundary Errors — When Credentials Become Liabilities

10. "As a structural engineer, I can speak to the thermal failure mechanism..."

Your PE licensure defines your competency boundary, and that boundary is visible to every attorney in the room. Offering opinions outside your discipline — whether through credential creep, scope expansion under pressure, or genuine misunderstanding of where mechanical ends and civil begins — is grounds for exclusion and professional discipline. Know your lane. Acknowledge its edges. The engineer who stays within documented expertise is the one who gets retained again.

11. "My CV accurately reflects my experience in this area." (When it does not.)

Misrepresenting qualifications — whether through exaggeration, omission, or implication — is grounds for exclusion and professional discipline. Your CV must be accurate. Your licensure must be current and properly described. Your experience must be fairly represented. A PE who overstates credentials risks not only the current case but every future engagement, every licensure renewal, and the professional reputation built across a career. Opposing counsel will verify everything. Assume it.

12. "In my dual role as the company's engineer and your expert witness..."

Serving simultaneously as a fact witness and an expert witness on the same matter creates conflicts that must be disclosed and managed under the applicable rules. The roles carry different obligations, different privileges, and different standards for testimony. Blurring those boundaries without proper disclosure hands opposing counsel a procedural weapon and compromises the integrity of both roles. If you are unsure which role you occupy, that uncertainty belongs in a conversation with retaining counsel before the deposition begins, not after.

The One I Almost Said

I am going to tell you something I have never published. Early in my forensic practice, during a particularly contentious deposition, opposing counsel asked me to characterize why the design team had chosen a thinner cross-section on the failed component. I knew the engineering answer. What I almost gave was the business answer — that the pressure to reduce weight drove a decision that the failure data did not support.

That is intent testimony. That is motive. That is exactly statement #8 on this list.

I caught myself. Retaining counsel did not have to stop me. But it was close. And the reason it was close is that after three hours of technical testimony you start to feel like you own the room. You do not. The court owns the room. Your job is to explain what the evidence shows, not what you believe happened in the boardroom.

The engineer who forgets that distinction is the engineer who does not get called again.

What You Can Do Right Now

Before your next deposition, run this list. Read each statement aloud. If any of them sounds like something you might say under pressure — flag it. Discuss it with retaining counsel. Build the guardrail before you need it.

Expert witness credibility is not rebuilt after it is lost. A Daubert exclusion follows you. An adverse ruling citing methodology failure follows you. The attorney network is smaller than you think, and the reputation you protect in one case is the one that gets you retained in the next.

The 12 statements above are not academic. They are the markers of an expert witness who understands the rules of the room — and the ones who do not.

Download the Deposition Red Flag Checklist — a single-page field tool with all 12 triggers, formatted for deposition prep and leave-behind use.

This is Post 2 of 13 in The Forensic Engineer’s Field Manual. Read the full series at inventorsmindblog.com.

Herbert Roberts, PE | Licensed Professional Engineer | Six Sigma Black Belt

Forensic Engineering Consultant | 32 Years Aviation R&D | 62 Patents

inventorsmindblog.com

A Love Letter to Raspet Flight Research Laboratory

How learning to build drones led to the ugliest airplane Honda ever built. The workshop that had no equal on earth — and the engineers from Japan who knew it.

Subscribe now

This is not a technical post. It is a debt repaid.

I owe the Raspet Flight Research Laboratory at Mississippi State University more than I can document on a resume or quantify in a patent count. For over two years I mixed glues, trimmed plies, built molds, and assembled airplane parts on a daily basis — work that does not appear on a transcript but shaped everything that followed. What I can do is tell the truth about what happened there — truth that is not in their timeline, not in Honda's press materials, and not in any publication I have ever found.

Raspet did not just train me. It trained a generation of students — domestic and international — who arrived with textbooks and left with hands. We were engineers in training, and what we built at Raspet every day could not be taught from a page: the feel of a properly wetted ply, the patience a mold demands, the difference between a part that will hold and one that will not. That culture of hands-on expertise was not incidental to Raspet's reputation. It was the reason Honda came to Mississippi. Honda's engineers had done their homework and found something at Raspet that no other university in the world had built.

They did not stumble into Starkville. They chose it. And they told me exactly why.

What Raspet Actually Built

Dr. August Raspet arrived at Mississippi State College in 1949. His sailplane research and boundary layer discoveries put the United States at world leadership in motorless flight. That is the public story. The deeper story is what those decades of hands-on flight research produced: a culture and a capability that no institution with a bigger name had accumulated in the same form.

In 1965, Raspet flew the Marvel — the world’s first all-composite aircraft equipped with a turboprop. Designed, developed, and built at the Starkville airport. Not at any high-name institution in higher education. In Mississippi, by a team that believed the only way to learn what composite airframes could do was to build one and fly it.

Follow this link: to See the Raspet Flight Research Labortory’s History

That flight happened twenty-one years before Honda arrived. By the time Honda’s engineers walked into Raspet in 1986, they were walking into two decades of composite flight hardware experience that did not exist anywhere else on earth.

The elite institutions were teaching composite theory. Raspet had been flying composite aircraft since before most of their composite programs existed.

There is a difference between a university that studies flight and a laboratory that builds it. Raspet was the second kind. That distinction is everything.

Why Honda Chose Mississippi

I was a graduate student technician at Raspet in the mid-1980s, working on composite demonstration drones in the early days before drones became the future of military technology. I was eighteen months from graduation when Honda Research and Development Corporation arrived in 1986 to build a turbojet-powered all-composite aircraft. I joined the mixed team that began the work — approximately twenty people: Honda engineers, MSU professors, and graduate student technicians.

Honda’s engineers were direct about their decision. They had specifically not chosen the institutions whose names appear at the top of every aerospace ranking — the schools that generate the most publicity, attract the most prestigious faculty, and publish the most celebrated research.

They did not choose those institutions because those institutions teach theory. Raspet built aircraft.

The second reason was the Marvel. Honda’s team had studied the composite leadership record and found it at Raspet — not as a recent development, but as a twenty-year body of work rooted in actual flight hardware. The fabrication knowledge they needed was not in a journal paper. It was in the hands of the people who had been building composite structures at the Starkville airport since 1965.

The third reason was deliberate and strategic. Anti-Japanese import hostility was openly and aggressively present in the United States of the early 1980s. A Japanese company quietly advancing composite aviation technology at a high-profile institution would have been a press story. The same program, run by a small mixed team at a low-key research laboratory in Mississippi, was invisible.

Honda did not hide in Mississippi. They chose Mississippi because it was simultaneously the right place and the quiet place. Those two things were not in conflict. They were the same decision.

The recruiter who interviewed me after graduation looked at my resume and saw Mississippi. I looked back and saw exactly what Honda had seen — because Honda’s engineers had told me what they found there.

The Ugly Duckling and the First Pancake

Here is what the public record does not contain.

Before the Honda MH-02 — the aircraft that flew in 1993 and became the platform for the HondaJet — there was the MH-01. MH stands for Mississippi and Honda. Those initials were chosen deliberately. This was a joint program from the first day, rooted in a specific place and a specific partnership.

The MH-01 (also known as the MH01) was Honda’s first experimental aircraft, built in 1987 to 1988 to test composite materials and innovative aerodynamic concepts that later influenced the HondaJet. It was a modified Beechcraft Bonanza, fitted with a new composite wing and tail section.

The MH-01 was not a new airplane, it was learning platform and demonstrator. It began as an existing aluminum turboprop airframe onto which the mixed team systematically replaced structural components with composite equivalents, one subsystem at a time, working to Honda’s head designer blueprints.

Tail and elevator first. Main wing second. . Each subsystem was built, proof-tested, and flown before the team moved to the next.

I worked on the first phase. My contribution was specific and bounded: composite tail and elevator. We built them, loaded them with sandbags to proof-test the structural design, and when they passed, they went on the hybrid airframe and the hybrid flew. In December 1987 I graduated and left for industry. The team kept building.

Honda does not host photographs of the MH-01. This is understandable. The aircraft was not beautiful. It was an aluminum airplane wearing composite parts it had not been designed for, still carrying its original turboprop because Honda had not yet solved above-wing engine placement. It looked exactly like what it was: a working prototype, a sandbag-tested proof of concept, a first attempt made by twenty people who were inventing the process as they executed it.

Every great program has a first pancake. The first one is always ugly. It is also the one that proves the pan is hot and the batter works. Without it, there is no breakfast. The MH-01 was the first pancake. The MH-02 was the breakfast that fed an industry.

By the time the MH-02 was designed and built from scratch, that mixed team had collectively manufactured and flight-tested every major composite structural element of a jet aircraft. The knowledge was not theoretical. It was in their hands. It was Raspet’s gift to Honda, and Honda’s gift to aviation.

What This Story Is Not

I want to be precise about my role because the precision is the point.

I was a technician, not an engineer. I worked on one subsystem on a twenty-person mixed team that included Honda’s professional engineers and MSU faculty. My contribution was real, early, and specific. It was not central to the program’s success, and overstating it would dishonor the engineers, professors, and fellow graduate students who carried the work forward after December 1987.

What the drone work gave me was preparation I could not have gotten from a classroom. Building real composite airframes — structures that had to hold together under load and in flight — before I ever worked beside Honda’s engineers meant I arrived at the MH-01 program with hands that already knew the material. That preparation was Raspet’s doing. The drone program was where Raspet taught me to build. Honda was where I understood why it mattered.

What I will not leave ambiguous is this: Raspet’s composite capability was not a happy accident. It was built over decades by people who believed that the only way to know if a composite airframe could fly was to build one and find out. That philosophy — the workshop over the whiteboard, the airframe over the abstract — is exactly what Honda came looking for. It is exactly what they found. And it is exactly what produced the world’s first all-composite experimental business jet from a research laboratory in Starkville, Mississippi.

The Love Letter

The American Institute of Aeronautics and Astronautics gave Raspet its Piper General Aviation Award in 1998 for fifty years of outstanding contributions to general aviation. The National Soaring Museum designated it a National Landmark of Soaring in 2003. Today it operates the largest unmanned aircraft fleet at any U.S. academic institution and serves as the FAA’s designated UAS Safety Research Facility.

None of that came from a ranking. None of it came from a marketing budget or an alumni endowment or a famous name above the door. It came from a culture that measured itself by what flew and what held together under load, not by what published and what impressed.

I cannot send Raspet a check. What I can send is this: a public statement, by someone who was there, that what happened in Starkville in the mid-1980s was not a footnote to aviation history. It was a chapter. The Honda MH-01 was the first pancake, ugly and unphotoable and essential. The MH-02 was the proof. The HondaJet, still in production today, is the legacy.

Raspet’s hands are in that airplane. The hands of professors and engineers and graduate student technicians who stacked sandbags on composite tail surfaces and then watched them fly.

To the faculty, staff, students, and researchers of the Raspet Flight Research Laboratory — past and present — you built something the theorists only described. Aviation knows what you did, even when aviation forgets to say so. I am saying so now.

That is the love letter I owe you. Seventy-five years of advancing aviation, and the work was always real.

Today, in 2026, Raspet is still leading. The largest unmanned aircraft fleet at any U.S. academic institution. The FAA’s designated UAS Safety Research Facility. Firsts still accumulating, the same way they always did — not by announcing ambition but by doing the work. The hands-on culture that trained a generation of composite engineers is now training the engineers who will define what aviation becomes next.

Learn more about Raspet: Visit the Raspet Flight Research Labortory

Attached is the summsry of the SAE paper submitted by the RFRL staff and MSU professors on the MH-01 prototype design and fabrication.

Mh01 911015 Composite Prototype Aircraft Development A Method For Design, Fabrication And Test Training Sae International

42.6KB ∙ PDF file

Download

Download

This is not the MH-01 it’s the …

Note: The image shown in this article is the Honda MH-02, it is the second prototype that Honda Produced. Images of the MH-01 are rare, and after much seraching, apparently not available in my internet searches. (I do not own this image and will remove it upon request.)

Learn more about the MH-02 at: https://en.wikipedia.org/wiki/Honda_MH02

Learn more about the production Honda Jet at: https://www.hondajet.com/

I am Herbert Roberts, P.E. — a licensed Professional Engineer with 32 years in aviation research and development, 62 patents, and 8 years translating engineering failures into legal outcomes for attorneys. If you are working in composite structures, patent strategy for materials innovation, or trying to understand where a hands-on capability fits in a commercial landscape, I want to hear from you.

Tell me what you are building.

Leave a comment

inventorsmindblog.com

© Herbert Roberts, P.E. | Inventor’s Mind | All rights reserved

How to Train as a Mechatronics-Focused Mechanical Engineer

for Under $5,000—While Working Full-Time

A Four-Year Self-Directed Curriculum Built from University Benchmarks

The Case for Self-Directed Engineering Education

A four-year mechanical engineering degree at an in-state public university now averages between $100,000 and $160,000 in total cost of attendance. Out-of-state and private institutions push that figure past $250,000. Equally significant is the opportunity cost: four years of foregone wages from full-time employment that, at even a modest entry-level associate position, represents another $120,000 to $160,000 in lost income. The combined economic burden—direct tuition plus lost wages—exceeds a quarter-million dollars for most students before they earn their first engineering paycheck.

The question is no longer whether alternatives exist. The question is whether those alternatives can deliver genuine competence. The answer, increasingly, is yes—provided the self-directed learner follows a structured curriculum, invests in low-cost hands-on laboratory tools, and builds a portfolio that demonstrates measurable capability. The convergence of three developments makes this possible: (a) the proliferation of university-quality open courseware from MIT, Stanford, Georgia Tech, and others; (b) the dramatic cost reduction in microcontroller platforms, sensors, and rapid-prototyping hardware; and (c) the emergence of professional-grade open-source engineering software that rivals commercial packages costing thousands of dollars per license.

This article presents a complete four-year self-directed curriculum modeled on the mechanical engineering programs at Ohio State University, Cal Poly San Luis Obispo, and the University of Florida—three institutions recognized for their respective strengths in research rigor, hands-on pedagogy, and mechatronics integration. The plan is designed for a learner working a full-time entry-level associate position, studying approximately 20 hours per week, and spending less than $5,000 on all equipment, materials, and resources over the full four years.

The Benchmark: What Universities Actually Teach

Before designing a self-directed path, it is essential to understand what the target institutions require. A comparison of OSU, Cal Poly SLO, and UF reveals a common core that transcends institutional branding. All three programs demand the same foundational mathematics sequence (Calculus I through III, Differential Equations, Linear Algebra), the same physics sequence (classical mechanics plus electromagnetism), and the same core mechanical engineering subjects: Statics, Dynamics, Mechanics of Materials, Thermodynamics, Fluid Mechanics, Heat Transfer, Machine Design, and Control Systems. The differences emerge in emphasis and elective structure, not in fundamental content.

Ohio State University

OSU’s BSME program emphasizes research-oriented depth. Its mechatronics pathway includes elective coursework in robotics, embedded systems, and a dedicated Mechatronics Laboratory. The program requires C/C++ or Python programming from the first year and integrates systems-level thinking through its Systems Dynamics sequence. OSU’s strength lies in its analytical rigor—students develop strong theoretical foundations before touching hardware.

Cal Poly San Luis Obispo

Cal Poly’s “Learn by Doing” philosophy inverts the typical sequence. Students engage with physical prototyping and laboratory work from the outset, building intuition before formal theory. The mechatronics focus includes PLCs, microcontrollers, and automation alongside standard ME coursework. Senior projects at Cal Poly are notably ambitious, often involving industry-sponsored builds. This approach produces graduates who can fabricate, assemble, and troubleshoot on day one—a quality that self-directed learners should prioritize.

University of Florida

UF offers a formal Mechatronics Minor alongside its BSME, which provides the most structured integration of mechanical engineering with embedded control and smart systems. The minor adds courses in robotics, smart systems, and embedded control to the standard ME core. UF’s approach is valuable as a curriculum template because it explicitly defines the boundary between core ME and mechatronics specialization.

The Free and Low-Cost Resource Ecosystem

The infrastructure supporting self-directed engineering education has matured far beyond what most people realize. What was once a scattered collection of lecture recordings has evolved into a comprehensive ecosystem of structured courses, interactive simulations, professional-grade software, and community support networks. Understanding this ecosystem is the first step toward building a credible alternative to traditional enrollment.

Open Courseware and Structured Learning Platforms

MIT OpenCourseWare remains the gold standard, offering complete course materials—lectures, problem sets, exams with solutions—for virtually every subject in the proposed curriculum. The 18.01 through 18.06 sequence covers Calculus through Linear Algebra with the same rigor expected at any top-tier institution. The 2.00x series covers the mechanical engineering core. Beyond MIT, Khan Academy provides scaffolded instruction for mathematics and physics that serves as either primary instruction or review. Coursera and edX host university-partnered courses from Georgia Tech, the University of Michigan, and the University of Pennsylvania that include graded assignments and optional certificates. For control systems specifically, Brian Douglas’s YouTube channel and the complementary MATLAB Onramp (free from MathWorks) together constitute one of the most effective learning pathways available anywhere, including inside university classrooms.

Professional-Grade Open-Source Software

The software landscape has shifted decisively in favor of the independent learner. FreeCAD provides parametric 3D modeling with finite element analysis capability built in. Onshape offers browser-based CAD with full parametric modeling at no cost for public projects. OpenFOAM delivers computational fluid dynamics capability that competes with commercial packages costing $20,000 or more per seat. SimScale provides cloud-based FEA and CFD with a free tier sufficient for educational use. GNU Octave replicates most MATLAB functionality, while Python with NumPy, SciPy, and Matplotlib handles everything from signal processing to numerical methods. The Arduino IDE and PlatformIO cover embedded systems development. ROS (Robot Operating System) provides the same robotics middleware framework used in industry and academic research labs worldwide.

Low-Cost Hardware Platforms

The hardware revolution is equally significant. An Arduino Uno costs under $25 and teaches the same microcontroller programming principles as a $3,000 university lab station. A Raspberry Pi at $35–75 provides a complete Linux computer capable of running ROS, processing sensor data, and controlling actuators. Entry-level 3D printers now cost $200–$300 and produce parts adequate for prototyping mechanical assemblies, robotic linkages, and test fixtures. Used oscilloscopes appear on secondary markets for $100–$300. Breadboards, jumper wires, resistors, capacitors, and basic sensors cost pennies per unit. A complete electronics workstation that would have cost $5,000 a decade ago can now be assembled for under $500.

The Four-Year Self-Directed Curriculum

The following curriculum synthesizes the strongest elements of all three benchmark programs into a structured sequence designed for 20 hours per week of study alongside full-time employment. Each semester assumes approximately 16 weeks. The curriculum is organized by year and semester, with specific resources, lab activities, and deliverables for each course. (See the full $5000 Four-Year Self-Directed Curriculum pdf file at the bottom of this article.)

Year 1: Foundations (Mathematics, Physics, and Programming)

Semester 1. The first semester establishes the mathematical and computational foundation upon which everything else rests. Calculus I (Differential Calculus) and Physics I (Classical Mechanics) run in parallel, which is the same sequencing used at all three benchmark institutions. The learner works through MIT OCW 18.01 for calculus and MIT 8.01 or Khan Academy physics for mechanics, completing assigned problem sets on a weekly schedule. Programming begins simultaneously using Python through Automate the Boring Stuff (free online) and MIT’s 6.0001 Introduction to Computer Science. The learner purchases a Raspberry Pi kit ($75–$150) and begins writing small programs that interact with physical sensors—reading temperature, measuring distance with ultrasonic sensors, blinking LEDs in response to input. These exercises are trivial in isolation but establish the habit of connecting code to the physical world, which is the defining characteristic of mechatronics. CAD introduction begins with FreeCAD or Onshape, modeling simple geometric parts and assemblies. The semester’s deliverable is a documented Python project that reads sensor data and produces a formatted output—a weather station, a light-level logger, or a simple alarm system.

Semester 2. Calculus II (Integral Calculus) continues through MIT OCW 18.02, while Physics II (Electromagnetism) introduces the electrical principles that underpin circuit analysis and motor control. Programming advances to MATLAB (or GNU Octave) for engineering computation—plotting functions, solving systems of equations, and basic numerical methods. The learner purchases an Arduino Uno starter kit ($50–$100) and begins building simple circuits: voltage dividers, LED arrays, transistor switches, and basic motor drivers. The critical lab exercise for this semester is building and tuning a line-following robot using the Arduino, two infrared sensors, and two DC motors. This single project integrates programming, circuit design, sensor interfacing, and mechanical assembly—and it costs under $30 in parts. Technical communication practice begins with weekly written summaries of what was learned, formatted as engineering memos. The semester’s deliverable is the line-following robot, documented with a design report that includes circuit schematics, code listings, and performance data.

Year 2: Core Engineering Fundamentals

Semester 3. The second year shifts from pure mathematics and physics into engineering analysis. Calculus III (Multivariable Calculus) and Differential Equations run concurrently, using MIT OCW 18.02 and 18.03. Statics begins through Jeff Hanson’s YouTube lectures or the free Engineering Statics course on Coursera. The learner builds physical beam-loading experiments using 3D-printed fixtures, a bathroom scale (as a force gauge), and aluminum bar stock from a hardware store. Circuits and Electronics begins formally through MIT 6.002 on edX, supplemented by hands-on work with the Arduino and a used oscilloscope ($100–$300 on eBay). The oscilloscope is one of the most important purchases in the entire budget—it transforms abstract waveform concepts into visible, measurable phenomena. Thermodynamics I begins through MIT 2.005 or the equivalent Coursera offering. The semester’s deliverable is a documented circuits project: an Arduino-controlled temperature monitoring system with data logging and display.

Semester 4. Dynamics follows Statics using the same lecture resources. Linear Algebra (MIT 18.06, taught by Gilbert Strang) provides the matrix mathematics essential for robotics kinematics and control theory. Mechanics of Materials begins through a combination of lecture content and physical testing: the learner 3D-prints tensile test specimens in PLA and PETG, loads them to failure using a simple lever-and-weight arrangement, and compares measured yield behavior to published material data. This exercise is crude compared to a university tensile testing machine, but it builds intuition for stress-strain relationships that no simulation can replicate. Basic CAD proficiency deepens through modeling assignments that replicate components from Shigley’s Mechanical Engineering Design. The semester’s deliverable is a structural analysis report on a simple truss or bracket, comparing hand calculations, FreeCAD FEA results, and physical test data from a 3D-printed prototype.

Year 3: Advanced Mechanical Engineering and Mechatronics Core

Semester 5. Fluid Mechanics begins through MIT 2.006 lectures, supplemented by OpenFOAM computational exercises. The learner cannot build a wind tunnel at home, but can simulate flow around basic geometries and validate results against published data—an exercise that develops both physical intuition and computational competence. Heat Transfer follows through the same MIT pathway. Machine Design begins in earnest using Shigley’s textbook, which remains the standard reference across all three benchmark programs. The learner designs, analyzes, and 3D-prints a working gear train or cam mechanism. Control Systems—the keystone of mechatronics—begins through Brian Douglas’s video series and the University of Michigan’s Coursera specialization. The critical lab exercise is implementing PID control on an Arduino-driven DC motor, tuning the controller to achieve specified step-response characteristics. This single exercise—cost under $20 in parts—teaches more about control theory than many semester-long university courses. The semester’s deliverable is a PID-controlled positioning system with documented tuning methodology and performance data.

Semester 6. This semester marks the full transition into mechatronics specialization. Embedded Systems deepens through Raspberry Pi projects using C/C++ and real-time operating system concepts. Robotics Kinematics begins through the University of Pennsylvania’s Coursera Robotics Specialization, which covers forward and inverse kinematics, trajectory planning, and motion control. The learner builds a 3- or 4-DOF robotic arm using 3D-printed links, hobby servos, and Arduino or Raspberry Pi control ($200–$400 total). Sensors and Actuators study formalizes what the learner has been practicing informally: understanding datasheets, selecting appropriate sensors for given applications, interfacing with various communication protocols (I2C, SPI, UART), and driving different actuator types (servo, stepper, DC, brushless). The semester’s deliverable is the functional robotic arm with inverse kinematics control, documented with kinematic diagrams, control architecture, and demonstration video.

Year 4: Specialization and Capstone Integration

Semester 7. Vibrations and Acoustics proceeds through MIT 2.003 lectures and MATLAB simulations. Finite Element Analysis deepens through FreeCAD’s built-in FEA workbench or SimScale’s cloud platform, analyzing increasingly complex geometries and loading conditions. PLCs and Industrial Automation represents the bridge to industry employment: the learner purchases a used PLC trainer from eBay ($300–$500) and works through ladder logic programming, which remains the dominant language in manufacturing automation. This investment directly supports employability in robotics and automation roles. Elective study begins in one of three tracks: (a) AI for Mechanical Systems, using Python-based machine learning applied to sensor data classification and predictive maintenance; (b) Autonomous Vehicles, using ROS-based navigation and SLAM (Simultaneous Localization and Mapping) on the Raspberry Pi; or (c) Biomechanics, studying human movement analysis through sensor-based motion capture. The semester’s deliverable is a PLC-controlled automated sorting or assembly station.

Semester 8. The final semester is dedicated to a capstone project that integrates every discipline studied over the preceding three and a half years. The recommended project is an autonomous mobile robot: a wheeled platform with motor control (Dynamics, Controls), environmental sensing (Sensors, Embedded Systems), path planning (Robotics, Programming), structural integrity (Machine Design, Mechanics of Materials), and industrial communication protocols (PLCs, Automation). The budget allocation for the capstone is $800–$1,000, which is sufficient for a Raspberry Pi 4, Arduino Mega, motor drivers, LIDAR or depth camera, chassis materials, and power system. The capstone deliverable includes complete mechanical drawings, electrical schematics, control architecture documentation, source code repository (GitHub), a demonstration video, and a written design report formatted to professional standards. This portfolio package becomes the learner’s primary credential when seeking engineering employment.

Complete Budget Breakdown

The following table details the full four-year equipment and resource budget. Every item listed serves multiple courses across the curriculum, which is how the total remains under $5,000.

The 20-Hour Weekly Study Plan

Consistency matters more than intensity. The following weekly structure distributes 20 hours across five study days while preserving weekday evenings and one full weekend day for rest. This schedule assumes the learner works a standard weekday job.

The Saturday block is the most important session of the week. It provides the contiguous time needed for laboratory work: soldering circuits, assembling mechanisms, running experiments, debugging code, and documenting results. Projects cannot advance in 30-minute increments. The six-hour Saturday block replicates the university lab session and is non-negotiable for genuine competence development.

What You Cannot Replicate—and What to Do About It

Intellectual honesty demands acknowledgment that approximately 30% of a traditional mechanical engineering education cannot be fully replicated at home. Fluid mechanics experimentation requires wind tunnels and flow visualization equipment. Advanced manufacturing instruction requires CNC mills, lathes, EDM machines, and welding stations. Materials testing at scale requires universal testing machines, hardness testers, and metallographic preparation equipment. Vibrations analysis at professional fidelity requires precision accelerometers and signal analyzers.

The mitigations are real but imperfect. Computational fluid dynamics through OpenFOAM provides simulation experience that is genuinely valuable and increasingly used in industry, but it does not replace the physical intuition developed by watching flow separation over an airfoil in a smoke tunnel. Community college partnerships or makerspace memberships ($200–$500 annually) provide access to CNC equipment and larger machine tools. Some community colleges allow non-enrolled individuals to use lab facilities for a fee. Professional certifications from organizations like the American Society of Mechanical Engineers or the Society of Manufacturing Engineers can partially offset the absence of a degree credential.

The most significant gap, however, is not equipment. It is peer interaction, instructor feedback, and structured assessment. The self-directed learner must actively compensate by participating in online engineering communities (Reddit’s r/engineering, Discord servers, Stack Exchange), joining local maker and robotics groups, entering competitions (RoboSub, Formula SAE if affiliated with a club team, FIRST Robotics as a mentor), and seeking mentorship from practicing engineers. The portfolio of documented projects, published on GitHub and demonstrated through video, serves as the primary credential in the absence of a diploma.

The Portfolio as Credential

A completed degree signals to employers that a candidate endured a structured program and passed a series of assessments. A portfolio of documented engineering projects signals something different and arguably more powerful: that a candidate identified problems, designed solutions, built physical systems, tested them, iterated, and documented the entire process without institutional scaffolding. The self-directed learner’s portfolio should include, at minimum, the following components after four years.

A GitHub repository containing all source code—from early Python scripts through ROS packages and PLC ladder logic—organized by project with clear README files explaining objectives, methods, and results. A technical blog or website documenting major projects with photographs, schematics, performance data, and reflections on design decisions and failure modes. Video demonstrations of working systems, particularly the robotic arm and autonomous mobile robot capstone, uploaded to YouTube or a personal portfolio site. A collection of engineering analysis reports—hand calculations validated against simulation—covering structural, thermal, and dynamic problems. Optional but valuable: Coursera or edX certificates in Control Systems, Robotics, and Embedded Systems, which provide third-party validation of coursework completion. Letters of reference from competition organizers, makerspace supervisors, or professional engineers who have reviewed the work.

This portfolio package, assembled over four years of disciplined work, speaks directly to the capabilities that hiring managers in robotics and automation actually evaluate. It demonstrates not just knowledge but initiative, self-direction, and the ability to deliver functional systems—qualities that distinguish the best engineers regardless of their educational pathway.

The Honest Comparison: $5,000 vs. $200,000

The comparison is not entirely favorable to the self-directed path, nor should it be presented as such. The traditional degree provides a recognized credential, direct access to research facilities, structured peer learning, and a clear pathway to Professional Engineer licensure. What the self-directed path provides is financial freedom, immediate employment, hands-on competence that is often superior to traditionally educated graduates who took minimal lab electives, and a portfolio that demonstrates initiative and capability in tangible form. The right choice depends on the individual’s circumstances, career goals, and capacity for self-discipline.

Conclusion: The Path Is Real

The tools exist. The content exists. The hardware is affordable. The software is free. The only missing ingredient is the sustained discipline to follow through on a four-year self-directed program while holding down a job and building a life. That discipline cannot be purchased at any price—not from a university, not from a MOOC provider, and not from a book. It comes from the learner alone.

What has changed in the last decade is that discipline, when applied consistently, can now produce genuine engineering competence outside the traditional institutional framework. A person who completes this curriculum—who builds the circuits, writes the code, prints the parts, tunes the controllers, assembles the robots, and documents everything with professional rigor—will possess skills that many degreed engineers lack. The $5,000 investment buys not just equipment but proof of capability. The projects speak. The portfolio demonstrates. The work, done properly, is its own credential.

The path is unconventional. It is not easy. But it is real, it is accessible, and for the right person—someone with determination, curiosity, and the willingness to do hard work without external validation—it represents one of the most compelling educational opportunities available today.

What do the Wright Brothers, Thomas Edison, Henry Ford, and Michael Faraday have in common? None held an engineering degree. The Wrights never finished high school. Edison was expelled at twelve. Ford apprenticed in a machine shop. Faraday was a bookbinder who taught himself electricity from the books he was binding. Every one of them learned by building, testing, failing, and building again — which is exactly what this curriculum asks you to do.

Facing the cost of education today, this is how I would approach it: follow a structured university curriculum using free resources, invest in low-cost tools that let me build real systems, work an entry-level associate position that pays the bills and builds discipline, and let four years of documented projects speak louder than a diploma. The path is unconventional. The engineering is not.

Complete 5000 Curriculum

587KB ∙ PDF file

Download

Download

Am I on the right track? Am I missing something?

Leave a comment

Herbert Roberts, P.E., is a licensed professional engineer with 32 years in aviation research and development, 62 U.S. patents, and 8+ years of forensic engineering consulting. He writes at Inventor’s Mind on systematic innovation, engineering judgment, and the structures that make technical organizations succeed or fail.

© 2026 Inventor’s Mind Press | inventorsmindpress.com

Facts Build the House. Logic Defends It. The Jury Decides Whether They Believe It.

Most expert witnesses are retained for what they know.

The ones who change outcomes are retained for what they know how to say — and what they know never to say.

There is a gap between those two things. It is where cases are won and lost. It is where a technically flawless analysis becomes courtroom testimony that holds under the hardest cross-examination opposing counsel can design. And it is where the same analysis — delivered without discipline — hands the other side exactly what they need.

This series exists in that gap.

What This Series Is

The Forensic Engineer’s Field Manual is 13 posts written for attorneys who retain engineering experts and for forensic engineers building a defensible practice.

It follows the actual lifecycle of a forensic litigation engagement in sequence — from the first decision an expert makes that damages their own credibility, through chain of custody, deposition intelligence, timeline reconstruction, root cause analysis, courtroom translation, expert conflict, and cross-examination survival, to the moment the jury goes into deliberation carrying whatever the expert left them with.

Every post is drawn from inside the practice. No theory without a case behind it. No framework without a failure that produced it.

Who This Is Written For

If you are an attorney who retains engineering experts, this series answers the questions you cannot easily ask your own expert — what damages their credibility before the analysis is ever examined, what they cannot say on the stand and why, what a rigorous forensic investigation actually looks like from the inside, and what the cross-examination will do to them if they are not prepared for it.

If you are a forensic engineer, this series names what experience teaches and practice manuals do not — the language boundaries, the deposition discipline, the root cause methodology that holds under challenge, and the dual role the courtroom demands of every expert witness who sits in that chair.

The Three Acts

Act I — Building the House (Posts 2 through 7)

Physical evidence. Chain of custody. Deposition intelligence. Timeline reconstruction. Every post in this act produces a fact — a brick. Without the bricks there is no house.

Act II — Defending the Logic (Posts 8 through 11)

Root cause analysis is where the engineering meets its first real challenge. Opposing counsel, budget pressure, and the complexity of multi-factor failures all test the logic underneath the conclusion. This act covers the methodology, the translation, the expert conflict, and the language discipline required to survive cross-examination.

Act III — The Jury Decides (Posts 12 and 13)

The courtroom is a stage. The engineer is simultaneously the oracle the jury came to hear and the obstacle opposing counsel must discredit before deliberation begins. This act covers what the courtroom actually demands — and the central truth that no engineering school teaches about how cases are decided.

The Series Thesis

Facts build the house. Logic defends it. The jury decides whether they believe it.

The forensic engineer’s credibility is built on emotional neutrality. The moment they show frustration, advocacy, or passion, they become a hired gun in the jury’s eyes. Their value is their precision, their discipline, their willingness to follow the evidence wherever it leads regardless of who retained them.

But that same neutrality, delivered without the attorney’s translation, loses cases.

The attorney is the translator. The engineer hands the attorney the facts. The attorney hands the jury a story. The jury hands back a verdict.

The forensic engineer who understands that chain does not try to be the storyteller. They make sure every fact is clean enough to become one.

The Complete Series

Post 01 | Series Header Document (this post)

Post 02 | 12 Ways to Damage Your Credibility

Post 03 | 12 Statements I Cannot Say as a Forensic Engineer

Post 04 | Chain of Custody & Why Scene Photos Trump Everything

Post 05 | The Deposition as a Discovery Tool

Post 06 | What Are They Saying? — Reading Between the Lines

Post 07 | Reconstructing the Clock — Temporal Sequence

Post 08 | The Work Nobody Sees — Why RCA Takes So Long

Post 09 | If You Can’t Explain It to a 5-Year-Old

Post 10 | You’re Wrong: Same Evidence, Different Conclusions

Post 11 | Pray for a Settlement

Post 12 | The Oracle and the Obstacle

Post 13 | The Jury Decides

New posts every Thursday. All posts free to read.

This is Post 1 of 13 in The Forensic Engineer’s Field Manual. Read the full series at inventorsmindblog.com.

Herbert Roberts, PE | Licensed Professional Engineer | Six Sigma Black Belt

Forensic Engineering Consultant | 32 Years Aviation R&D | 62 Patents

inventorsmindblog.com

Why Thomas Massie Thinks the Way He Does — and Why That Drives Everyone Crazy

Herbert Roberts, P.E. | Inventor's Mind | Everybody Series

434 to 1

This post is not interested in whether Thomas Massie is right or wrong in his thinking. It is interested in why he cannot be anything other than what he is.

The vote is 434 to 1. Again.

His name is always the 1.

Both parties are furious. Leadership on the left calls him obstructionist. Leadership on the right calls him disloyal. The President of the United States has solicited a primary challenge against him. Four hundred and thirty-four people, representing the full ideological spectrum of American politics, have found the one thing they agree on: Thomas Massie is the problem.

Here is what none of them will say out loud.

He is not operating on their system. He never was. And no amount of political pressure will install software onto hardware that was not built to run it.

Thomas Massie is an engineer. Not by title. By formation. And that changes everything about how a person sees a problem, validates a solution, and decides what counts as done.

What MIT Actually Builds

Massachusetts Institute of Technology does not teach you what to think. It teaches you how to validate.

The discipline is this: define the problem before you propose the solution. Establish the objective function before you optimize. Test the load path before you sign the drawing. If the data contradicts the model, the model is wrong — regardless of how many people voted for it.

This is not a philosophy. It is a survival skill. A bridge built by consensus but designed against the load data does not stay up because everyone agreed on it. Physics does not negotiate. Materials do not care about your coalition.

Massie did not just attend MIT. He thrived there. He founded SensAble Technologies, a company built on haptic feedback — the technology that lets your hand feel virtual objects that do not exist. He holds patents. He designed and built the off-grid solar and geothermal systems that power his working farm in Kentucky. These are not resume lines. They are evidence of a mind that runs one consistent operating system: define the problem, gather the data, build the solution, validate against reality.

That system does not have a switch. You do not turn it off when you walk into the Capitol.

Two Objective Functions. One Room.

Every institution runs on an objective function — the thing it is actually optimizing for, beneath the stated mission. Understanding the objective function explains the behavior. It always does.

The engineer's objective function is: Does it work?

The politician's objective function is: Do I survive?

Neither is immoral. Both are rational responses to the incentive structures of their respective environments. An engineer whose bridge falls does not get to blame the vote count. A politician who loses the seat does not get to keep shaping policy. The pressures are real on both sides.

But here is the problem. Those two objective functions are not just different. They are mutually exclusive in the same decision.

"Make it happen — the data says this is the best plan." That is the engineering rearead.l

"We must appeal to a wide populous to protect the positions of elected people." That is the political read.

When Massie looks at a piece of legislation, he runs the engineering read. He identifies the objective function the bill is actually optimizing for — not the stated purpose, the actual one. He checks the load path. He asks what fails first and under what conditions. He votes accordingly.

Four hundred and thirty-four people in that room are running the political read. They are calculating coalition math, estimating electoral risk, and optimizing for survival. When one person in the room is solving a different problem entirely, the outputs look irrational — because they are not answers to the question everyone else is asking.

The 434 are not wrong that Massie is not playing their game. They are wrong that this makes him the problem.

The Hand That Believed the Simulation

In the late 1990s, Thomas Massie and his colleagues at MIT were working on a machine that would let a human hand feel objects that did not exist.

Haptic feedback — force feedback through a mechanical interface — had been a research concept for years. The problem was making it work in real time, with enough fidelity that the hand believed what it was feeling. The nervous system is not easy to fool. It knows the difference between a surface and a simulation.

Massie's thesis work on the PHANToM haptic device became the foundation of SensAble Technologies, which he co-founded before he was twenty-five. The company produced devices used in surgical simulation, product design, and scientific visualization. It was not a concept. It was a product. It shipped. It worked.

Notice what that required. Not consensus. Not coalition building. Not an appeal to the populous. It required a precise definition of the problem, a design that matched the physics of the human hand, and a validation loop that ran until the data said it was ready.

That loop is still running. It never stopped. It just moved from a laboratory in Cambridge to a chamber in Washington, D.C. The inputs changed. The method did not.

Where the Engineering OS Has a Blind Spot

This post has no interest in making Massie a hero. The engineering operating system is a powerful tool. It is not a complete theory of democratic governance, and it is worth being honest about where it breaks.

First: tradeoffs are real. Legislation is almost never an optimization problem with a clean global maximum. It is a negotiation among parties with legitimate but competing interests. A bill that is technically suboptimal by one metric may be the only version that holds a coalition together long enough to move at all. Engineers who refuse imperfect solutions in complex social systems can become a different kind of problem — not because they are wrong about the flaw, but because they have no framework for the cost of inaction.

Second: data in policy is not the same as data in materials science. The load on a beam is measurable. The second-order effects of a tax structure or a foreign policy posture involve variables that resist clean quantification. The engineering confidence that comes from working in physical systems can harden into false certainty when applied to human ones.

Third: the 1-versus-434 position is only sustainable at a specific scale. One dissenting engineer in a design review can force a better outcome. One dissenting vote in a 435-member legislature has almost no mechanism to change the result — only to register the objection. Whether that is a principled stand or an expensive gesture is a question the engineering OS does not answer.

These are real limits. They are worth holding alongside everything else this post has said.

You Have Been the 1

You have been in that room.

Not Congress. Your room. The project review. The budget meeting. The design sign-off. The moment when everyone at the table had already decided, and the data in your hand said something different, and the unspoken rule was clear: fall in line, this is how we get things done, don't be the problem.

You knew the load path. You had run the numbers. You understood what failed first and under what conditions. And you were told — directly or by the pressure in the room — to appeal to the populous anyway. To protect the position. To keep the coalition intintact.

Some of you signed the drawing.

Some of you did not.

Thomas Massie does not sign the drawing when the data says it will fail. That is not stubbornness. That is not disloyalty. That is a formed mind doing the only thing it knows how to do: validate against reality and report the result.

You can agree or disagree with every vote he has ever cast. That is not what this post was about.

This post was about why he casts it the same way every time. And why, if you were honest, you already knew the answer before you started reading.

The engineer does not optimize for survival. The engineer optimizes for the bridge staying up. That is not a political position. It is a different objective function. And once it is installed, it does not uninstall.

Thomas Massie’s official congressional biography and legislative record are available at: https://massie.house.gov/

IF THIS HIT CLOSE TO HOME

Forward it to the engineer in your organization who has been the 1. They will know exactly what it means.

If you found this through LinkedIn, the Inventor's Mind Substack is where the full series lives — free, twice weekly, built for engineers who are still paying attention. Subscribe at inventorsmindblog.com.

EDITORIAL NOTE

This post contains no endorsement of any political party, candidate, or policy position. The subject is engineering epistemology — how a specific kind of technical training shapes a cognitive framework — and nothing beyond that.

Why AI Will Never Replace Physics-Based Engineers

The Irreducible Gap Between Digital Pattern-Matching and Physical Reality

Herbert Roberts, PE | Inventor’s Mind | inventorsmindblog.com

The Question Nobody in Silicon Valley Wants to Answer

There is a narrative gaining momentum in technology circles—one which holds that artificial intelligence will eventually replace all engineers. The claim is seductive in its simplicity, which is precisely why it is wrong. It confuses two fundamentally different activities: (a) writing instructions for machines that operate in constructed digital environments, and (b) designing, analyzing, and certifying hardware that must survive the unforgiving physics of the real world.

The distinction matters because it determines who is actually at risk. Software engineers operate entirely within digital space—their inputs are digital, their processes are digital, their outputs are digital, and their validation is digital. AI lives natively in that space. A coding agent can already write, test, deploy, and iterate code without ever leaving the environment it was born in.

The Stolen Title

I want to make a distinction that I am going to be very careful about — because it is easy to make this argument badly, and making it badly obscures the real point.

The issue is not the people. The people who write software for a living include some of the most technically rigorous and genuinely brilliant minds working in any field today. Software is a collection of logic statements used to define one or more solutions to resolve a set of decisions. The computational problems they solve are real problems. The systems they build are complex systems. This post is not an attack on any of them as individuals or as a profession.

The issue is the word.

Software development does not carry a P.E. license. It does not require one. The consequences of a failed software deployment — as real and as serious as those consequences can be — are generally not measured in structural collapses, aircraft accidents, or the catastrophic failure of life-safety systems. The accountability structure is different. The legal framework is different. The professional standard is different.

When the title engineer detaches from the accountability structure that gives it meaning, the word stops doing the work it was designed to do. The public hears engineer and reasonably infers: licensed, accountable, bound by professional standards to the safety of the people who depend on this work. That inference is correct when the word is used correctly. It is incorrect — and the incorrectness has real consequences — when the word is used as a general descriptor for anyone who solves technical problems on a computer.

The Roman engineers who designed the aqueducts did not get to blame the software. They did not get to issue a patch. They did not get to pivot to a new architecture after the first version failed. They built it right the first time because the alternative was catastrophic and permanent and entirely their fault.

That standard — build it right, own the consequence, no patch available — is what the word engineer carries. When the word travels without the standard, the standard gets lost. And the standard is the part that protects people.

Physics-based engineers—mechanical, aerospace, civil, materials, chemical—work at the boundary between the digital and the physical. They model in the computer but validate against physical testing. They analyze on screen but inspect with their hands and eyes. They calculate in software but certify against regulatory frameworks built on decades of accumulated failure data. That boundary crossing, from digital to physical, is the moat that AI cannot swim.

The Irreducible Gap: Six Pillars AI Cannot Replicate

To prove that physics-based engineering is not at risk of replacement, we need to identify the specific competencies that (a) define the profession, (b) depend on physical-world interaction, and (c) have no viable AI substitute on any foreseeable timeline. There are six such pillars.

Each of these pillars reinforces the others. Embodied judgment informs sensory inspection. Teardown learning feeds embodied judgment with thousands of physical observations that no simulation captures. Legal accountability demands regulatory navigation. Cross-domain synthesis depends on the accumulated experiential base that teardowns and field inspections produce. Remove any one pillar, and the engineering function degrades. Remove all six, and you no longer have engineering—you have computation.

Pillar 1: Embodied Judgment—The Knowledge AI Cannot Train On

Consider a finite element analysis of a turbine component under combined thermal and centrifugal loading. The model produces a stress distribution. A junior analyst reads the numbers. A senior engineer reads the story—and sometimes, the story the numbers are telling is wrong.

That senior engineer has spent twenty or thirty years correlating analytical predictions against physical test data. She has seen cases where the FEA showed acceptable stress but the part failed in service because the model’s boundary conditions didn’t capture a secondary load path. She has seen cases where the stress looked alarming but the material’s actual fatigue behavior, informed by metallurgical condition and surface finish, provided adequate life. This judgment—the ability to look at a computational result and say “something is wrong with this model”—is not pattern matching in the way AI performs pattern matching. It is the integration of thousands of physical observations into an intuitive framework that flags anomalies against lived experience.

AI can only interpolate between its training data. It has never touched a fractured surface. It has never felt the vibration signature of an imbalanced rotor. It has never watched a test specimen neck down before final fracture and noticed that the reduction in area didn’t match what the material certification predicted. These sensory inputs, accumulated over decades, constitute a knowledge base that exists nowhere in digital form and therefore cannot be used to train any model.

Pillar 2: Legal Accountability—The Liability AI Cannot Bear

When a Licensed Professional Engineer stamps a drawing, a report, or an analysis, that stamp carries the weight of personal legal liability. If the bridge collapses, if the pressure vessel ruptures, if the aircraft component fails—the PE who signed off is personally accountable. This is not theoretical. Engineers are deposed. Engineers testify. Engineers lose their licenses and face civil liability when their judgments prove wrong.

AI cannot be licensed. AI cannot be deposed. AI cannot be cross-examined by opposing counsel who wants to know why a particular material was selected, why a specific safety factor was applied, why an alternative design was rejected. The forensic engineering function—analyzing failures, determining root causes, translating complex technical findings into language a jury can understand—requires a human being with credentials, experience, and the ability to defend their conclusions under adversarial questioning.

Beyond the courtroom, regulatory compliance itself demands human accountability. The FAA requires a Designated Engineering Representative—a human—to approve conformity findings. ASME codes require a certified inspector—a human—to witness pressure tests. Nuclear Regulatory Commission protocols require human sign-off at every stage. These are not bureaucratic formalities; they are the mechanisms by which society ensures that someone with skin in the game is vouching for the safety of the design.

Pillar 3: Sensory Inspection—The Physical World Demands Physical Presence

Failure analysis is fundamentally a hands-on discipline. The fractographer sections the failed component, mounts it in epoxy, polishes it through progressively finer grits, etches the microstructure, and examines it under optical and electron microscopy. The fracture surface itself tells a story—beach marks indicate fatigue, intergranular facets suggest environmental attack, dimpled rupture reveals ductile overload, cleavage facets indicate brittle fracture. Reading these surfaces requires years of training and thousands of examinations.

AI can analyze images of fracture surfaces, and it will get better at this over time. But the analysis begins long before the microscope: deciding where to section, how to preserve evidence, what artifacts might be introduced by the cutting process itself, which features to document at low magnification before moving to higher magnification. The physical handling of evidence, the preservation of chain-of-custody for litigation, the judgment about what to examine and in what sequence—these are irreducibly physical activities.

Equally important is field inspection. Assessing corrosion damage on a structure requires physical access, tactile evaluation of material loss, calibrated thickness measurements, and the experiential judgment to distinguish between cosmetic surface oxidation and structurally significant section loss. No remote sensing system or AI image analysis can replicate the information content of a trained inspector’s hands-on evaluation.

Pillar 4: Teardown Learning—The Knowledge That Only Comes from Taking Things Apart

There is a mode of engineering learning so fundamental that it is almost invisible: the teardown. Engineers learn by disassembling hardware—taking apart engines, gearboxes, actuators, structures, and assemblies to understand how design intent translates into manufactured reality. This is not casual curiosity. It is a systematic, hands-on investigation that builds a form of knowledge no textbook, simulation, or AI training set can replicate.

When an engineer tears down a gas turbine, she does not simply catalog parts. She observes wear patterns on bearing races that reveal actual load paths versus predicted ones. She sees fretting damage at interfaces that tells her the clamping loads were insufficient or the surface finish was wrong. She notices discoloration gradients on hot-section components that map the real thermal field—often quite different from the CFD prediction. She finds evidence of maintenance-induced damage, assembly errors, foreign object impacts, and degradation mechanisms that no design analysis ever contemplated. Every teardown is a confrontation between the theoretical and the actual, and the engineer who has performed hundreds of them carries an experiential database that fundamentally shapes how she approaches new designs.

This teardown knowledge is cumulative and cross-pollinating. The engineer who has disassembled a failed hydraulic actuator recognizes the same seal extrusion pattern when she sees it in a pneumatic system. The metallurgist who has sectioned dozens of fatigue-cracked turbine blades immediately recognizes the initiation site morphology when it appears in a completely different alloy system. The manufacturing engineer who has torn down competitor products understands design-for-assembly tradeoffs that no parametric model captures. Each teardown deposits a layer of physical intuition that compounds over a career.

AI cannot perform teardowns. It cannot hold a wrench. It cannot feel the resistance of a press-fit bearing being extracted and correlate that interference with the specification. It cannot smell the distinctive odor of overheated lubricant that indicates a thermal exceedance event. It cannot observe, in three dimensions and real time, how components nest together, how tolerances stack, how wear patterns reveal operational history. The teardown is irreducibly physical, irreducibly hands-on, and irreducibly human.

Beyond the individual component level, teardown learning extends to system-level understanding. Disassembling an entire assembly reveals packaging constraints, routing decisions, maintenance access compromises, and design-for-manufacturing adaptations that are invisible in CAD models and engineering drawings. The engineer learns why a bracket is shaped a particular way—not from the design intent document, but from seeing that it had to clear a wire harness that was routed differently than the drawing showed. This “as-built versus as-designed” knowledge is critical for failure analysis, redesign, and root cause investigation, and it exists only in the minds of engineers who have done the physical work.

The implications for AI displacement are decisive. An AI can analyze a photograph of a disassembled component. It can identify features in a CT scan. It can process dimensional inspection data. But it cannot perform the teardown itself, and more importantly, it cannot accumulate the embodied intuition that thousands of teardowns produce. The teardown is where textbook knowledge transforms into engineering judgment—and that transformation requires hands, eyes, and decades of physical engagement with real hardware.

The Comparison: Why Software Is Vulnerable and Hardware Is Not

The contrast between software and physics-based engineering reveals exactly why one is at risk and the other is not. The following comparison maps the key dimensions:

The pattern is clear. Every dimension that makes software engineering accessible—fast feedback loops, low failure costs, purely digital environment, minimal regulation—is simultaneously the dimension that makes it automatable. Conversely, every dimension that makes physics-based engineering demanding—slow feedback loops, catastrophic failure costs, physical-world interaction, heavy regulation—is simultaneously the dimension that protects it from automation.

AI as Tool, Not Replacement: How Physics-Based Engineers Will Actually Use AI

This argument should not be mistaken for technophobia. AI will transform how physics-based engineers work—it already is. The key distinction is between AI as a tool that amplifies human capability and AI as a replacement that eliminates the human.

Consider the domains where AI is already proving valuable: (a) parametric design exploration, where AI can sweep through thousands of geometry variations and identify promising candidates for detailed analysis; (b) literature and standards search, where AI can rapidly surface relevant specifications, prior failure reports, and material property data; (c) automated mesh generation and FEA preprocessing, which reduces tedious setup time; and (d) TRIZ-based inventive problem solving, where AI can systematically map technical contradictions to inventive principles.

In every one of these applications, AI accelerates the engineering process without replacing the engineer. The parametric sweep still requires a human to define the design space, evaluate the results against manufacturing constraints, and select the final configuration. The literature search still requires a human to assess the relevance and applicability of the findings. The FEA still requires a human to verify boundary conditions, validate the mesh, and interpret the results against physical experience. The TRIZ analysis still requires a human to frame the contradiction correctly and evaluate whether the suggested principle applies to the specific physical system.

This is the pattern: AI handles the computation; the engineer provides the judgment. The computation is fast and getting faster. The judgment is slow and getting deeper. Both are necessary. Neither is sufficient alone.

The Expertise Compression Fallacy

Software culture has popularized the idea that expertise can be compressed into months. “World-class software engineer in six months” is a claim that circulates without irony on platforms like Substack. Read twelve books. Build projects. Ship code. The timeline is aggressive but arguably achievable—not because software people are smarter, but because the domain’s feedback loops are fast and the consequences of error are recoverable.

Physics-based engineering does not compress. You cannot become a competent metallurgist by reading twelve books any more than you can become a competent surgeon by watching twelve videos. The knowledge is embodied: it lives in the correlation between what the textbook predicts and what the test specimen actually does, accumulated over thousands of hours in laboratories, test cells, manufacturing floors, and failure investigations. This embodied knowledge is precisely what AI lacks and cannot acquire from text-based training data.

The implication is significant. If expertise cannot be compressed for humans, it certainly cannot be compressed for machines. The thirty-year expertise curve in physics-based engineering is not a bug—it is a feature. It reflects the genuine complexity of understanding how materials and structures behave under real-world conditions, which is the very complexity that insulates the profession from algorithmic displacement.

The Verdict: Protected by Physics, Secured by Accountability

The case is straightforward. Physics-based engineering is protected from AI replacement by six mutually reinforcing pillars: embodied judgment built over decades of physical-world correlation, legal accountability that demands a licensable human being, sensory inspection that requires physical presence and handling, teardown learning that builds irreplaceable intuition through hands-on disassembly, cross-domain synthesis that spans multiple scientific disciplines, and regulatory navigation that demands experiential interpretation of complex and interacting code frameworks.

AI will make physics-based engineers more productive. It will accelerate analysis, broaden design exploration, streamline documentation, and enhance quality assurance. These are genuine and valuable contributions. But the irreducible core of the profession—the judgment, the accountability, the physical-world interaction—remains firmly and permanently in human hands.

The engineers who should worry are those whose entire workflow exists in digital space, whose mistakes are reversible, and whose expertise can be acquired in months. The engineers who need not worry are those who work at the boundary between computation and physical reality, whose mistakes can be catastrophic, and whose expertise is measured in decades.

Physics doesn’t care about your algorithm. And that is exactly why physics-based engineers will still have jobs when the last line of code writes itself.

Herbert Roberts, PE • Inventor’s Mind • inventorsmindblog.com

Published by Inventor’s Mind | inventorsmindblog.com

The Clock Starts Before You Think It Does

Most inventors believe the patent process begins when they walk into an attorney’s office. That belief costs them money, scope, and sometimes the patent itself. The attorney’s meter runs from the first phone call—and every hour spent reconstructing your invention from memory is an hour that should have been spent building claims. The disclosure document changes that equation entirely.

A patent disclosure document is the structured record you prepare before engaging counsel—which captures conception, operating principles, and prior art awareness in one place, which gives the attorney raw material instead of a mystery to solve, and which positions you as an inventor who understands the process rather than one who needs to be guided through it. Thirty minutes of preparation here routinely saves three to five hours of billable time. That is not an estimate. That is arithmetic.

Why the Document Exists

Patent law in the United States requires that an inventor be able to establish (a) the date of conception, (b) the date of reduction to practice, and (c) continuous, diligent effort between those two points. The disclosure document is the evidentiary foundation for all three requirements.

Beyond the legal scaffolding, the document serves a practical function: it forces the inventor to articulate the invention with engineering precision before emotions, sunk costs, and enthusiasm cloud the picture. An inventor who cannot explain the problem being solved, the mechanism of the solution, and what makes the solution non-obvious is not ready for patent prosecution—regardless of how brilliant the underlying idea may be.

Equally important is what the document is not. It is not a patent application. It does not need legal language. It does not require formal drawings or professional figures. It requires clarity, completeness, and corroboration—the three pillars the attorney will use to do their job.

What Goes in the Disclosure Document

1. Identification Block

Lead with full legal name(s) of all inventors, the date of first conception, the intended filing entity (individual, LLC, or corporate assignee), and contact information. If multiple inventors contributed, identify the specific contribution of each. Joint inventorship creates legal obligations; the disclosure document is the right place to sort that out before it becomes a dispute.

2. Title and Field Statement

Write a plain-language title and a one-paragraph field statement. The title should describe what the invention does, not what it is called internally. The field statement orients the reader to the technology domain—which defines the prior art landscape the examiner will search, which shapes the claims the attorney will draft. One paragraph. No jargon.

3. The Problem Being Solved

This is the most undervalued section. Describe what prior art fails to do, why existing solutions are inadequate, and what specific gap the invention addresses. This becomes the foundation of the Background of the Invention section in the application—and a well-articulated problem statement is the strongest possible argument for non-obviousness. If the problem was not recognized before, the solution cannot have been obvious.

4. Summary of the Invention

Write a concise statement of what the invention is and what it does. Think of it as the elevator pitch for the claims. Two to four sentences. No more. If the summary requires a page to deliver, the invention is not yet understood well enough to be disclosed.

5. Detailed Technical Description

This is the engineering core of the document—which must describe how the invention works, identify key components and their functional relationships, specify materials, dimensions, and operating conditions where relevant, and address alternative configurations the attorney might want to protect. An attorney can only claim what is disclosed. Gaps here become permanent gaps in the patent—which competitors exploit, which licensing negotiations expose, and which litigation reveals at the worst possible moment.

6. Drawings and Sketches

Even rough hand sketches serve the purpose. Label every element. Number every figure. Drawings become formal figures in the application, but their function at the disclosure stage is simply to communicate structure and spatial relationships that text cannot convey efficiently. A sketch that takes ten minutes to produce can save an hour of verbal description.

7. Preferred Embodiment and Alternatives

Describe the best version of the invention as currently understood—which is the preferred embodiment required by 35 U.S.C. § 112—and then identify alternative configurations, materials, and operating modes worth protecting. Each alternative represents a potential dependent claim. Dependent claims are the fence line that keeps competitors from designing around the core.

8. Claims Brainstorm

Your non-attorney attempt to describe the broadest and narrowest versions of what is novel. These will be rewritten. That is not the point. The point is that your engineering intuition about what makes the invention unique directly shapes how the attorney approaches claim construction. Write the broadest statement you believe is defensible, then narrow it three times. The attorney will do the rest.

9. Prior Art You Are Aware Of

List every patent, publication, product, or presentation you know of that relates to the invention—whether it supports or threatens your claims. The duty of candor to the USPTO is not optional, and hiding known prior art creates legal exposure that can invalidate an issued patent years after prosecution. Disclosing it early builds credibility with the examiner and gives the attorney the opportunity to distinguish it strategically.

10. Conception and Reduction to Practice

Record both dates with corroborating evidence: lab notebooks, engineering sketches dated and witnessed, email threads, prototype photographs, test data. The corroboration requirement means that your word alone is insufficient—which is not a commentary on integrity, but a legal standard that applies equally to every inventor. Evidence gathered contemporaneously is worth orders of magnitude more than evidence reconstructed after the fact.

11. Commercialization Notes

Identify who would buy the invention, what market it addresses, and any known competitors or potential licensees. This section is not legally required, but it calibrates the attorney’s claim strategy. Broad claims protect a technology platform. Narrow claims protect a specific product. The commercialization context tells the attorney which fight they are preparing to win.

What Happens When the Document Does Not Exist

Consider the inventor who conceives a novel thermal management solution during a design sprint—which demonstrates clear performance advantages in bench testing, which generates informal documentation scattered across three email threads, two whiteboards photographed on a phone, and a presentation deck with no dates—and then walks into a patent attorney’s office six months later with the story in their head and the evidence on a phone they have already replaced.

The attorney now performs archaeology. Every hour spent reconstructing the conception timeline, locating the original sketches, identifying which version of the design was the “invention” versus the development work that followed—is billable time that produced no claims, no application, and no protection. The inventor pays for the attorney to learn what the inventor already knew.

Beyond the billable hours: the six-month gap introduced prior art risk. A competitor filed a similar application four months after the original conception. The inventor’s undocumented prior conception may be defensible—but the evidentiary burden is now on the inventor, and the corroboration is thin. A disclosure document prepared the week of conception would have resolved all of this before the attorney was ever called.

Three Mistakes That Undermine Disclosure Documents

First mistake: confusing completeness with length. A disclosure document that buries the invention in technical prose, historical narrative, and competitive analysis forces the attorney to extract the invention from the noise. Front-load the critical elements—problem, solution, mechanism—and keep supporting material clearly separated.

Second mistake: omitting embarrassing prior art. Every inventor knows of a reference that threatens their claims. The instinct to omit it is understandable and legally dangerous. The examiner will find it. The question is whether the attorney was prepared to distinguish it or was blindsided by it during prosecution.

Third mistake: treating the document as a one-time event. Inventions evolve during development. Each meaningful modification to the core mechanism is a potential continuation or continuation-in-part application—which requires its own disclosure record, its own corroborated conception date, and its own attorney review. The discipline of maintaining disclosure records throughout development compounds the value of the original document.

The Document Is the Foundation, Not the Paperwork

Patent protection begins not with the filing date but with the conception date—and conception is only legally meaningful if it is documented. The disclosure document is the engineer’s contribution to a process that will eventually require an attorney, a draftsman, and a patent examiner. It is the one element of that process that only the inventor can provide.

Prepare it with the same rigor you would apply to a design review. Front-load the problem statement. Be exhaustive about mechanism. Be honest about prior art. Date and witness every page. Then call the attorney.

You will spend less. You will protect more. And you will walk into that first meeting as an inventor who is ready to build a portfolio, not one who is still trying to remember what they built.

What was your experience filing patents? Were you prepared? How long did it take to get the provisional filed? Please tell us in a comment so we’re compare notes.

Leave a comment

Herbert Roberts, P.E. | Inventor’s Mind | inventorsmindblog.com

FEB (Formen Engpass Barriere) is our proprietary term for systematic innovation.