
The Knowledge Your Team Has That Nobody’s Using
You’ve been in this meeting before. Engineering is three months into detailed design when someone from manufacturing finally sees the concept and says, “We tried this two years ago. Here’s why it failed.”
The knowledge existed, but it didn’t have a path into the conversation when it actually mattered. We often treat this as a “people problem” or a failure of a database, but it can actually be a structural problem: when you engage for this information in product development. After all, it’s significantly cheaper to change a piece of paper during concept development than it is to retool a production line later.
In this episode, I share the results of an experiment I ran using AI agents to test two different development approaches across three distinct products: a solar service design, a medical device, and a field harvester. The results were clear: the traditional approach produces “answers,” but the structured concept development approach produces clarity.


Ask a question or send along a comment.
Please login to view and use the contact form.