4 Comments
User's avatar
Alana Brantley's avatar

The hiring section made me think about how easily “we need a technical co-founder” can become a catch-all. Integrating older plant systems and changing who can approve a batch are both hard jobs, and they call for very different experience. I’d be curious how you decide which capability has to live inside the company and which a customer or partner can supply.

Joyce Shah's avatar

The pump example made me think about what a maintenance team does with an alert at 2 a.m. An accurate warning can still be hard to act on if the technician is hours away or the plant has no spare pump. I’d want the field trial to capture the decisions people make after an alert, alongside the quality of the signal itself.

Victor Katz's avatar

I kept wondering what the quality manager already knew. He may have understood perfectly well that sign-off was the bottleneck and asked for help with the paperwork because that was the part he could change. A prototype can surface that distinction, but the founder still has to figure out who inside the plant can change the process.

Jenny Parker's avatar

There’s a tension in building something you expect to throw away. Once a prototype works well enough to impress a customer or an investor, people start asking when they can have it. I wonder if it helps to agree upfront on the one question the prototype is meant to answer, while everyone still remembers why it was built.