Thread by @mipsytipsy

YES. Great section. The edges of tool adoption create silos.

Also: ultra relevant to the thread on software to sabotage your org, and the ~50% of responders who replied, "Jira."

https://twitter.com/1tss4r/status/1438442702434185216

Communication pathways are sooo hard to get right, and inspire such frothing, unreasonable rage when they get it wrong.

The last time I used jira was well over a decade ago, and I thought it was impenetrable spaghetti at the time. I can't imagine it's gotten any simpler...

But it's kind of an impossible problem, of course it's going to turn into feature soup when you've been making bank on enterprise for this long.

Every team starts out trying to replicate and "improve" on how a squintillion people and teams interoperate,

but each of the teams they connect have evolved their own communication pathways.

What could be more fascist and enraging than being forced to fit your communication into foreign pathways that don't fit how you actually interact or work? ¯\_(ツ)_/¯

Naturally, there are knobs and options to force jira to do your bidding. (There are probably at least ten people in the world who know them, too.)

That may buy you a respite. But these pathways are always shifting and adapting to changes in the system, so it won't last long 🙃