It sounds really interesting to work in a manufacturing plant for a year or two in order to empathize with the industry and learn how to blend in software in a way that actually solves problems like you describe. Or, generally, to penetrate areas where technology solutions don't apply obviously. I wonder how you'd set that kind of arrangement up. If you could design a company around displacing a few cofounders for a few years where the product research is hands on, on the ground, doing the job, I bet there are many people who would be interested in this type of setup. I agree the software industry does way too much "solve for ourselves first" type of product development and it's really discouraging.
I think a key point that people fail to remember or marketing just oversells, is that there is no silver bullet for all the problems, especially for an industry that has so much history, precedent and inertia. People want to try and solve (and from the other side, want perfect full solutions) all problems at once, whilst in reality small improvements in key areas are probably the 80/20 that is needed to bring business value. I think continuous feedback and good "translators" would be key for any product in those industries. Manufacturing people are busy and will tell you what the surface level pain point is, but they don't have the time or maybe don't have the idea fully thought out on what the underlying problem/goal is.
After typing up all that, I realise that most of this is applicable to every industry.
