moved back to slack. hope to using team soon. reasons;

%3CLINGO-SUB%20id%3D%22lingo-sub-34984%22%20slang%3D%22en-US%22%3Emoved%20back%20to%20slack.%20hope%20to%20using%20team%20soon.%20reasons%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-34984%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20tried%20using%20Teams%20for%20my%20company's%20communication%20channel%2C%20but%20moved%20back%20to%20slack.%3C%2FP%3E%3CP%3EHere%20are%20some%20reasons%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Slow%20and%20buggy%3C%2FP%3E%3CP%3E2.%20Channel%20messages%20are%20non-notification.%20Only%20private%20and%20%40%20message%20has%20notification.%3C%2FP%3E%3CP%3E3.%20Reply%20chain%20makes%20users%20very%20confusing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E1.%20Slow%20and%20buggy%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EI%20know%20it%20is%20because%20of%20preview%20stage.%20I%20believe%20it%20will%20be%20fixed%20soon.%20Anyway%2C%20I%20posted%208%20jpgs%20which%20are%202~3%20Mbytes%20per%20file.%20Total%2030Mbyte%20or%20something.%20And%20then%2C%20whole%20app%20and%20chating%20session%20were%20so%20slow%20and%20not%20usable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E2.%20Notification%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3ECurrently%2C%20there%20are%20no%20way%20to%20get%20notification%20from%20channel%20message%2C%20if%20someone%20type%20something%20in%20channel%20message%20with%20out%20doing%20%40%20thing.%3C%2FP%3E%3CP%3Ewhy%3F%20I%20simply%20don't%20get%20it.%20So%20we%20were%20adding%20%40team(group%20name)%20infront%20of%20every%20message%2C%20and%20it%20was%20so%20annoying.%3C%2FP%3E%3CP%3EWe%20simply%20needed%20notification%20on%20group%20messaging.%3C%2FP%3E%3CP%3EI%20think%20I%20heard%20that%20this%20function%20is%20in%20developement.%20Hope%20to%20see%20this%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E3.User%20confusing%20there%20chat%20room.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EIMHO%2C%20this%20needs%20to%20be%20re-designed%20totally.%3C%2FP%3E%3CP%3ECurrently%20there%20are%20private%20message%2C%20channel%20message%2C%20and%20reply%20chain%20message.%20And%20because%20of%20reply%20chain%20window%2C%20users%20are%20very%20confusing%20and%20having%20a%20hardtime%20figureing%20out%20where%20they%20are%20typing.%3C%2FP%3E%3CP%3EI%20know%20reply%20chain%20can%20be%20very%20useful%2C%20but%20current%20design%20just%20make%20user%20confusing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20moved%20back%20to%20Slack%20as%20of%20now%2C%20everything%20is%20very%20simple%20and%20stable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20to%20move%20back%20to%20Team%2C%20because%20our%20entire%20company%20is%20using%20O365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMessaging%20app%20needs%20to%20be%20simple.%20Functions%20are%20important%20too%2C%20but%20before%20that%2C%20simplicity%20and%20stability%20are%20first%20things%20to%20have.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-34984%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-35845%22%20slang%3D%22en-US%22%3ERe%3A%20moved%20back%20to%20slack.%20hope%20to%20using%20team%20soon.%20reasons%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-35845%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20frustrated%20about%20the%20notifications%20at%20first%2C%20but%20I%20get%20it%20now.%20The%20channels%20could%20include%20a%20hundred%20people%20all%20talking%20and%20getting%20all%20those%20notifications%20would%20be%20insane%2C%20but%20if%20you%20%22point%22%20out%20either%20the%20person%2C%20persons%20or%20channel%20name%2C%20then%20it%20notifies%20them%2C%20and%20you%20can%20keep%20getting%20notification%20as%20long%20as%20each%20reply%20is%20inside%20the%20same%20%22thread%22%20so%20that%20the%20particular%20message%20will%20always%20be%20tracked.%20It%20starts%20to%20make%20sense%20then.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-35089%22%20slang%3D%22en-US%22%3ERe%3A%20moved%20back%20to%20slack.%20hope%20to%20using%20team%20soon.%20reasons%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-35089%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree.%20If%20Microsoft%20wants%20this%20to%20be%20successful%2C%20they%20need%20to%20try%20and%20tailor%20it%20to%20how%20people%20work%2C%20not%20make%20everyone%20re-learn%20how%20to%20chat.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-35027%22%20slang%3D%22en-US%22%3ERe%3A%20moved%20back%20to%20slack.%20hope%20to%20using%20team%20soon.%20reasons%3B%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-35027%22%20slang%3D%22en-US%22%3EThanks%20for%20your%20comments%20and%20experience%20when%20using%20Teams...I%20have%20no%20personally%20suffered%201%2C%20and%20for%20the%20other%20points%20I%20hope%20Microsoft%20will%20take%20them%20into%20account.%20To%20me%20a%20reliable%20notification%20system%20and%20also%20an%20intuitive%20user%20interface%20are%20key%20factors%20for%20Teams%20success%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

We have tried using Teams for my company's communication channel, but moved back to slack.

Here are some reasons;

 

1. Slow and buggy

2. Channel messages are non-notification. Only private and @ message has notification.

3. Reply chain makes users very confusing.

 

 

1. Slow and buggy;

I know it is because of preview stage. I believe it will be fixed soon. Anyway, I posted 8 jpgs which are 2~3 Mbytes per file. Total 30Mbyte or something. And then, whole app and chating session were so slow and not usable.

 

2. Notification;

Currently, there are no way to get notification from channel message, if someone type something in channel message with out doing @ thing.

why? I simply don't get it. So we were adding @team(group name) infront of every message, and it was so annoying.

We simply needed notification on group messaging.

I think I heard that this function is in developement. Hope to see this soon.

 

3.User confusing there chat room.

IMHO, this needs to be re-designed totally.

Currently there are private message, channel message, and reply chain message. And because of reply chain window, users are very confusing and having a hardtime figureing out where they are typing.

I know reply chain can be very useful, but current design just make user confusing.

 

 

 

So we moved back to Slack as of now, everything is very simple and stable.

 

Hope to move back to Team, because our entire company is using O365.

 

Messaging app needs to be simple. Functions are important too, but before that, simplicity and stability are first things to have.

 

 

3 Replies
Highlighted
Thanks for your comments and experience when using Teams...I have no personally suffered 1, and for the other points I hope Microsoft will take them into account. To me a reliable notification system and also an intuitive user interface are key factors for Teams success
Highlighted

I agree. If Microsoft wants this to be successful, they need to try and tailor it to how people work, not make everyone re-learn how to chat.

Highlighted

I was frustrated about the notifications at first, but I get it now. The channels could include a hundred people all talking and getting all those notifications would be insane, but if you "point" out either the person, persons or channel name, then it notifies them, and you can keep getting notification as long as each reply is inside the same "thread" so that the particular message will always be tracked. It starts to make sense then.