No? You solved the symptom not the issue?
No? You solved the symptom not the issue?
I sometimes suggest timeboxing investigations for this reason. Spend 4h on this - if root cause is not found, just throw more hardware at it. Although I expect a writeup of what was investigated and ruled out, so that it can be used when someone returns to it.
This is rarely if ever done in a sensible way. Instead you find Managers, Engineers or PMs avoiding troublesome stakeholders, hallway convos or Slack DMs that are never properly written into public record in a searchable/readable way, last minute overrides from higher ups based on limited context of the problem space or their own unaligned career goals, poor recordkeeping, panic mode bandaid fixes when systems break, etc...
IMO a lot of the “meat proxy” and “loop obsession” behavior we’re seeing is simply people using the sense of short term productivity gains as self-soothing against anxiety from corporate dysfunction that they have no control over.
Oldschool periodic reports and memoranda weren't perfect, but they did encourage taking time to curate one's message. And gave others somewhere to go for a properly curated message.