3 ms·
> He obviously did not understand what his job as a manager is about. > Why on earth would a manager be allowed to set tolerances like how you describe, tool o
by craftinator 5y ago
> He obviously did not understand what his job as a manager is about.
> Why on earth would a manager be allowed to set tolerances like how you describe, tool or no tool?
He's not the expert in the field, I am. Normally, I would have vetted the work orders and fixed it before hand. This is similar to managers in the software world, where the team lead or senior engineer would say," No, we won't do that, it's a bad idea". He never should have been exposed to an option that could screw everything up so badly, but I mistakenly left it on the form. He was just trying to fix what he perceived as a potential problem. He was used to making small changes to work orders to save money or get a more refined product.
The biggest problem with our company's structure is that the operators, for whatever BS org reason, don't have the "pay grade" to tell him to pound sand. Managers need to sit below engineers, in my opinion.
> you must be measured like crazy - set goals based on metrics that will push things in a direction you see effective.
In my sector of manufacturing, margins are king (regardless of locale). If you can cut 10 seconds from an operation, or find a tool that lasts 20% longer, you can save tens of thousands of dollars a year, so we track everything.
- jordanbeiber 5y agoAgain: describe a set of work principles explicitly that all agree on - it's a human communication and collaboration issue you were faced with. A tool is not responsible for this breakdown. Lack of clarity around ownership and responsibilities is, by the look of it. IM humble O.
- galangalalgol 5y agoI'm willing to entertain that the teams using Jira are just making worse choices about the work principles they agree on than our teams using gitlab issues, and that it is coincidental and unrelated to the tool. Surely you agree though, that in general a tool can adversely affect user behavior? The agile manifesto said to value tools and process es less than individuals and interactions, not to discount their impact altogether. Developing software in a single paradigm language when your domain is better suited to a different paradigm is a horrific blunder I have witnessed twice in my career. Developing giant systems using vba macros in excel is a common mistake you hear about. I can however believe that the teams that selected jira over gitlab might have done so because they already bad this use pattern in mind, and not because the tool encouraged it.
- jordanbeiber 5y agoI’ve worked in fantastic settings, truly following the agile principles, using jira as a tracker and board. I’ve been places with many different tools and people. Guess what, it’s ALWAYS about the people. If a team is following principles derived from or resembling the manifesto, the tool will be shaped accordingly. Jira, as an example, sure can be shaped, and I’ve done it myself several times - remove cruft, keep it simple, change if needed.