5 ms·
When you think about this more deeply, a well working status system is an existential threat to several layers of management. If all you do is collect metrics
by fleddr 4y ago
When you think about this more deeply, a well working status system is an existential threat to several layers of management.
If all you do is collect metrics and reports to aggregate them upwards, the value added is minimal.
Maybe there remains some value in exception management (risks, roadblocks)? Barely so in my experience. Because managers in tech have no clue what they're managing. So this is again just a report which next the team should resolve on their own.
- steveBK123 4y agoYes, but to be fair to managers in tech - no one else around them knows what they are doing either. Tech managers tend to have to wear too many hats filling in gaps in the product/project/program management layers and do some random assortment of people management & technical leadership.. depending on which firm/team and day of week. For non-tech companies, you'll often see a lot of non-technical stuff happening in the technical management hierarchy. At a high level all they care about is process, and at a low level all they care about is if a stakeholder is screaming right now. Nowhere in between do they care about what is actually being delivered. And by process I mean things like firm-wide cookie cutter agile mandates, all-hands calls, OGSM, OKR, etc. The last two shops I worked, the CTO spent a lots of time talking to investors about Cybersecurity/Resiliency/Cloud strategies, which are more attributes of a well engineered system, rather than a deliverable product. You wouldn't believe how many annual/quarterly CTO hosted events I've attended where either a Navy SEAL or Astronaut was the keynote speaker, lol.