Earlier quoted context omitted.
Bad sign. If the rank and file are afraid to give honest internal feedback, they have a management problem. At least for me, that's a time-to-leave signal.
*Slack, not signal.
Slack’s new WYSIWYG input box is terrible
501–510 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#502This is funny because I work across the street of Slack’s office in Vancouver, Canada and two Slack engineers who I frequently chat with during our daily commute already told me they —and a handful of other employees— hate the WYSIWYG input box too, but were afraid to express their feelings because their role is irrelevant compared to the people who made the decision to ship it.
Bad sign. If the rank and file are afraid to give honest internal feedback, they have a management problem. At least for me, that's a time-to-leave signal.
Re: Slack’s new WYSIWYG input box is terrible
#503This is not one of those "oh, that's annoying, i'll have to remember that and learn to work around it" issues. It's more like "I want to immediately stop using this software but have no choice". Its driving me crazy - Slack is all text input. Don't break text input dummy!
Personally, I recommend switching to Ripcord as a Slack client. That's what I did some time ago, and I couldn't be happier.
Re: Slack’s new WYSIWYG input box is terrible
#504Earlier quoted context omitted.
Was super skeptical about all those Jira replacement SaaS’s out there. But Clubhouse is actually pretty good. For people on the fence, give it a try.
I for one am still waiting for usable task management SaaS - one that doesn't limit me to "epic/project/task" split, but instead recognizes that the work is being decomposed recursively , and has dependencies. All I really want is a system that lets me arrange my tasks into a DAG. B is a subtask of A. C and D are subtasks or B. E is a subtask of D. F is a subtask of A, but depends on D being complete. It's simple and…
Perhaps a weekend project/"show HN" to gauge interest would be warranted.
Re: Slack’s new WYSIWYG input box is terrible
#505In their defence (not the defence of the WYSIWYG box itself) - they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability, etc etc. You have to remember Slack's target persona is probably no longer the Engineer (If it ever was) - it's more likely a much less tech-savvy employee who finds WYSIWYG editors very handy to create rich text inputs. I guess…
> they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability I have never worked at a company that did user testing or if they did it was always done in a way or interpreted in a way to back up the designer's opinion. I don't think I've once in my entire 40 yr career seen a designer test with users, find out something was bad, and change their design…
Re: Slack’s new WYSIWYG input box is terrible
#506Earlier quoted context omitted.
Concerning Clubhouse.io, it looks great, is there a download version? I know “Cloud is the way to go”, but I work in Men’s Rights (DV abuses, etc) and it is usually something that cloud companies don’t want on their platform, so we’re constantly at risk of being revoked.
No modern software works locally, it's always all in the cloud. That's why most large companies (and some cases like yours) stick with the big guys like Atlassian and Microsoft; the new competition doesn't support their data requirements.
Re: Slack’s new WYSIWYG input box is terrible
#507Earlier quoted context omitted.
> they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability I have never worked at a company that did user testing or if they did it was always done in a way or interpreted in a way to back up the designer's opinion. I don't think I've once in my entire 40 yr career seen a designer test with users, find out something was bad, and change their design…
Most of the established large tech companies do User experience research sessions while doing several iterations of mocks during the process. This is prior to AB testing. My current and last company both followed this practice.
Re: Slack’s new WYSIWYG input box is terrible
#508Earlier quoted context omitted.
I would bet a lot of money I already know the pitch. It's the same one that the Confluence PM I'm sure made. "We have done very well selling to technical programmers and hip startups, but the market is so much bigger. shows Office 365 revenue numbers vs Slack revenue numbers . We have an opportunity to take this to the next level. We need to make this the goto office communication platform. cheers . Markdown may seem…
>I would bet a lot of money I already know the pitch. It's the same one that the Confluence PM I'm sure made. "We have done very well selling to technical programmers and hip startups, but the market is so much bigger. shows Office 365 revenue numbers vs Slack revenue numbers. We have an opportunity to take this to the next level. We need to make this the goto office communication platform. cheers. You're probably ri…
Integrating with AD (or Azure AD) does not require Microsoft's blessing. Source: the product I'm working on (which is in the same market as Slack and Skype for business) is currently doing that.
Re: Slack’s new WYSIWYG input box is terrible
#509I had a quick glance at the API. It does look possible. What's the catch? Am I missing something?
Re: Slack’s new WYSIWYG input box is terrible
#510It's a bit annoying that there is no way to toggle the WYSIWYG rendering, but for me personally there have been countless times when I was missing some kind of preview while editing. For instance to align stuff in preformatted blocks...