Old boss knew. So did the guy who runs the machine and the head or programming (who was also in the brainstorming meeting). We did do the solution last year when we had a similar problem. Which is to say *I* personally did it and then showed everyone involved exactly what I did. Apparently it's not a permanent fix and lasts about a year. There is even an entry on the diagram of the factory floor, showing the solution, which was PRESENTED at the brainstorming, so the guy who presented and the guy who made the diagram presumably also know. I could have stepped up and volunteered more unpaid overtime to do again what apparently our institutional memory has forgotten, but I don't think it's forgotten. I think it's an under appreciated solution and whoever does it, won't even get the private attaboy that old boss used to be so good at using to motivate people. I am confident that if old boss were still here, we wouldn't have even got as far as brainstorming, since we would have talked about at a staff meeting and had volunteers (me, if no one else, but likely several people would have stepped forward) who would go make a fix and it would never have even risen to the level of issue it now is. That's in fact what happened with a similar issue last year.
What I'm not sure I've conveyed sufficiently is that this is NOT my job or even in the assigned area for my group. If we had an accountant on staff who also happens to know how to install a new mouse on his computer, I would be hard pressed to suggest that he should be in trouble if he does not install the mouse for all new employees, or be proactive about volunteering to help all employees who have a problem with their mouse. It is NOT his job, he does have a full time job he needs to do, and there is even a group who is supposed to deal with employee's routine IT problems. Likewise, there is a group who takes care of these machines and I am fortunately on good terms with them, because I can easily see them resenting my dropping in occasionally to solve their problems. If I made a big deal about it or hogged credit, they would certainly resent me, so I do it quietly, key folks like old boss, head of programming, machine operators and head of machine group all know, all knew before and all mutually agreed on the low key approach, and I even have worked some with the machine group to try to teach them how to do this.
I don't think I am in the wrong here, even though I could have volunteered more info at that meeting. I even have a date Monday morning with the machine guy to fix it and my code is almost half done, so I should be ready by then. I appreciate the frank feedback and I am indeed thinking deeply about it (even as I am saying my current thinking is I'm still a good guy, I'm still wondering if I'm fooling myself). But I am also thinking that the behavior of other people in the meeting tells me that there are deep dysfunctional problems at this place and I need to decide what I want to do. Apparently old boss insulated us from a lot of craziness. I do not think I want to volunteer to solve everything and spend huge hours doing so. I'm willing to make some sacrifices to contribute, but want to be hopeful that it will help, or at least be appreciated, and I'm not seeing anything to make me think that yet. Maybe I need to understand how far I'm willing to go on hope alone before I see some hint that things will improve. I hate to think I'm just slow to realize how bad it's going to be and the best people are all either leaving or left already. Which means maybe I am the mediocre old guy who wasn't willing to jump ship quickly enough. Is this a giant ER hint that I'm over-ready to stop working?