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
20Comment deleted
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
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
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
Classic PM pattern: 'Ship it fast' until observability proves it's a distributed denial-of-responsibility attack
Classic HiPPO-driven development: bypass change control, crater the SLOs, then run a ‘root cause analysis’ to find a person
HIPPO-driven deploy, no flags, no A/B, and the CAB happens afterwards - rebranded as a postmortem called 'Who authorized this commit?'
Next time ask for a written order. Comment deleted
Exactly Comment deleted
More paper, cleaner ass Comment deleted
Cleaner ass, cleaner paper Comment deleted
don't work for retards, simple as Comment deleted
S Comment deleted
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 Comment deleted
That's reason why these changes always was approved via email or/and task board Comment deleted
Just cleaned from spam Comment deleted
thanks meow whose name I don't remember and I don't see in the sidebar 😛 Comment deleted
probably @Linegel Comment deleted
Mask anonymous indistinguishable personality shit in the entrances Comment deleted
That's why I'm recording on dictophone Comment deleted
https://t.me/sendmegifs/298 Comment deleted