Skip to content
DevMeme
2828 of 7590
Management PMs Post #3125 · source on Telegram

Manager overrides warnings then blames engineer when metrics tank a month later

Description

Four-panel Work Chronicles comic in minimalist cartoon style. Panel 1: a developer named Bob (white round head, seated at a laptop behind a purple desk) looks up as a black-haired manager holding a tablet orders, “BOB, MAKE THESE CHANGES.” Panel 2: Bob raises a hand, replying, “BUT IT MIGHT IMPACT OUR METRICS.” The manager, stern, retorts, “JUST DO WHAT I SAY.” Panel 3, captioned with a yellow label “1 MONTH LATER,” shows the irate manager shouting, “OUR METRICS ARE DOWN. WHO AUTHORISED THESE CHANGES?” while Bob sits silently. Panel 4: the manager, arms crossed, says, “NEXT TIME, CONSULT ME BEFORE MAKING ANY CHANGES,” and Bob glares back. Footer text reads: “Comics about work. Made with love & lots of coffee. Work Chronicles. workchronicles.com Join r/workchronicles or follow on Instagram/Twitter/FB.” The strip humorously captures classic blame-shifting and communication breakdown between management and engineering teams, highlighting how disregarding technical risk warnings can hurt product metrics and morale

Comments

20
Anonymous ★ Top Pick Manager-driven development: they smash the “override CI & merge anyway” button, then open a Sev-0 a month later to investigate which engineer dared to follow orders
  1. Anonymous ★ Top Pick

    Manager-driven development: they smash the “override CI & merge anyway” button, then open a Sev-0 a month later to investigate which engineer dared to follow orders

  2. Anonymous

    The only metric that truly matters in enterprise software: how quickly management can pivot from 'ignore the warnings' to 'why didn't anyone warn me?' - typically measured in sprint cycles and inversely proportional to proximity to quarterly reviews

  3. Anonymous

    This comic perfectly captures the 'Schrödinger's Engineer' paradox: you're simultaneously responsible for all decisions and authorized to make none of them. The manager's final demand to 'consult me before making changes' is the cherry on top - a masterclass in rewriting history where the engineer who warned about metrics impact is now blamed for not preventing the very changes they were ordered to implement. It's the corporate equivalent of a rollback without version control - everyone knows what really happened, but the commit history has been force-pushed

  4. Anonymous

    Classic PM pattern: 'Ship it fast' until observability proves it's a distributed denial-of-responsibility attack

  5. Anonymous

    Classic HiPPO-driven development: bypass change control, crater the SLOs, then run a ‘root cause analysis’ to find a person

  6. Anonymous

    HIPPO-driven deploy, no flags, no A/B, and the CAB happens afterwards - rebranded as a postmortem called 'Who authorized this commit?'

  7. Deleted Account 5y

    Next time ask for a written order.

    1. 🌯 🇺🇦 5y

      Exactly

  8. 🌯 🇺🇦 5y

    More paper, cleaner ass

    1. @NiKryukov 5y

      Cleaner ass, cleaner paper

  9. @pixelsex 5y

    don't work for retards, simple as

    1. Deleted Account 5y

      S

  10. @the_cash_network 5y

    We have a lot of customers who request changes non stop, making them confirm the changes by online form (and letting the person who pays the bills approve them) has resulted in a much cleaner relationship with them

  11. @neopulsar 5y

    That's reason why these changes always was approved via email or/and task board

  12. dev_meme 5y

    Just cleaned from spam

    1. @AmindaEU 5y

      thanks meow whose name I don't remember and I don't see in the sidebar 😛

      1. @p4vook 5y

        probably @Linegel

    2. @p4vook 5y

      Mask anonymous indistinguishable personality shit in the entrances

  13. @walkersubterra 5y

    That's why I'm recording on dictophone

  14. @AlexSokolov88 5y

    https://t.me/sendmegifs/298

Use J and K for navigation