I bet a large percentage of Slack people _tried super hard_ to stop that cohort of PMs. However, you can only fight upwards so much before you just check out completely, cash the checks, and halfheartedly build whatever nonsense they're forcing through.
It's common for ambitious employees in not-so-ambitious tech companies to lose their jobs over not realizing that the optimal strategy for keeping their job is to just do their work as told, collect a pay cheque, and not innovate.
In these companies, the fastest way to get canned is to believe you are there to help the company succeed by trying to innovate, and in the process of doing so, imply there are flaws with how it's currently being done.
>It's common for ambitious employees in not-so-ambitious tech companies to lose their jobs over not realizing that the optimal strategy for keeping their job is to just do their work as told, collect a pay cheque, and not innovate.
Also known as optimal strategy to get your soul crushed and die inside.
It's really demoralizing to be on a team on which the devs clearly have better design and UX sense than the designer(s) and/or product manager. But not the titles—they're "just" software developers who couldn't possibly understand users or design or common friggin' sense.
Sometimes, the devs can sneak in a hidden fix. For example, remember back when VS 2012 made menus ALL CAPS? Officially, that was the brave new world everybody was supposed to live in (https://devblogs.microsoft.com/visualstudio/a-design-with-al...). Users hated it with a passion.
And then it turned out that there's an undocumented registry key to re-enable the old behavior, that was leaked without much fanfare (https://www.richard-banks.org/2012/06/how-to-prevent-visual-...). It was never mentioned in any official documentation, but word of mouth spread it far and wide, and its existence probably spared the worst in terms of angry user rants.
Ironically, the outcry over the caps was big enough that this setting eventually got an official checkbox in a major release sometime later, and then became the default behavior again.
Maybe they have statistics that indicate that their larges user group by now isn't capable of using markdown? Most non-techies are not aware of markdown.
Maybe they have, maybe they don't. Or maybe they can pull some out of their behinds on the spot when asked (which I suspect is the most likely case).
If non-techies can be taught how threading or bunch of other Slack idiosyncrasies work, they can as easily be taught that surrounding text with characters like *, /, ~, _ and ` changes formatting. It's a trivial concept. Reddit, or countless Internet forums before, never had a problem with teaching that to non-techies.
