zlacker

>>ZacnyL+(OP)
Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement.

Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof.

I can of course not say whether the people currently working at Twitter did warn that the recent measures could have such major side effects, but I would not be surprised in the slightest, considering their leadership's mode of operation.

Even as someone who very much detests what Twitter has become over the last few months and in fact did not like Twitter before the acquisition, partly due to short format making nuance impossible, but mostly for the effect Tweets easy embeddability had on reporting (3 Tweets from random people should not serve as the main basis for an article in my opinion), I must say, I feel very sorry for the people forced to work at that company under that management.

>>Topfi+Ew
At least once have I done a CC blast as a form of insurance when being asked to do something absolutely boneheaded.

>>Waterl+7A
You gotta get executives in writing sometimes or they'll throw you under the bus later.

>>7thacc+OE
If executives are throwing you under a bus, make an exit. There’s no coming back from a clown show like that.

>>Waterl+TF
I have a general rule that I make proactive, diligent efforts to inform and correct, and I do it 3 times to 3 different groups in leadership, and if that doesn't work, I'm out.

I'm about 2 for 8 but you gotta try sometimes.

>>jagged+cM
Yeah more often than not people just really really want to touch the hot stove.

Being the bearer of bad “stoves are hot to the touch” news makes you a downer.

>>steveB+3O
And in some absolutely bizarre anti-logic, I’ve seen some decide that the person trying to warn is somehow responsible for the inevitable outcome.

Not enough of you believed and now this balloon is adrift and will never make it to Imaginationland.

>>Waterl+tO
> I’ve seen some decide that the person trying to warn is somehow responsible for the inevitable outcome.

All. the. time...

Pervasive cognitive glitch: inability to distinguish between _problems_ and _people_.

Identifying the problem ==> causing the problem.

>>waters+cZ
I got tasked with essentially project managing a doomed project that the boss had already made all the tech decisions & promises on. Nothing was built but we had customers with firm dates for go-live. It was clearly not going to work, and not be on time. I pointed some of this out.

He then asked me to do weekly RAG status for stakeholders. So I did and it all slowly turned red with no easy remediation.

He did two things that made me realize it was time to go:

First, when I suggested that "if I report red status all year and then it doesn't complete on time, but I kept everyone well informed - am I going to be rewarded end of year".. to which I got nervous laughter response.

Second, he started talking about "what if we change the definition of done", such that we just start marking things amber/green because like.. well some of it is running in QA or hey its like 70% done, so why not mark it done?

Just seemed like he handed me the keys to a sinking boat as he stepped off in the last life boat.