08-09-2018 09:21 AM
08-09-2018 09:21 AM
You guys seem to have a bit of ADD when it comes to collaboration applications these days. I kind of thought everything was starting to come together with Teams being new flagship product, but then I see you release Kaizala to Office 365 users. What exactly is the strategy here?
08-09-2018 09:32 AM
If you mean Groups = email, then I think that MS has enumerated how it views Teams vs. Yammer vs. Email, with the Inner/Outer Loops diagrams shown since Ignite 2017.
As for Kaizala, well, yes that's a very good question I too would like an answer on.
08-09-2018 09:42 AM
This works most of the time - but doesn't really cover groups which are about learning - groups which are sort of outer loop - but the people are inner loop. Yammer is good for this.
08-09-2018 09:43 AM
08-09-2018 09:47 AM
Aren't the firstline workers who I'm communicating with using the app my "Inner Loop" contacts? Why not use MS Teams for chatting with my colleagues?
08-09-2018 09:53 AM - edited 10-04-2018 05:48 PM
This is a great point. We believe that there are clear scenarios for each product:
1. Kaizala is recommended in emerging markets in scenarios where you are supporting an open network of people. Users can join Kaizala with just a phone number, with an option to connect their AAD identity
2. Teams is the center of collaboration & communication for Office 365 in the inner loop for your employees.
3. Yammer is best for broad organization wide communities.
We will continue to communicate these scenarios as we build even more connective tissue between the products as appropriate. For instance the Yammer connector enables community managers to collaborate on their community from within Teams. You will see more of this as we head toward Ignite and the end of the calendar year. I hope this helps clarify our design.
08-09-2018 10:24 AM
Bleh...sorry...I just threw up a little bit when I read about a Yammer connector for Teams while reading a response about where Kaizala should be used.
There is a massive ecosystem of products like this that don't come from Microsoft. If I need a secret decoder ring to figure out what massing Microsoft system I need to deploy to communicate in use case A vs use case Z...then why wouldn't I look outside of Microsoft? If I ask the same question of Slack around which tool to use...they have one answer for me. It will be Slack every time. Having multiple products that overlap with 80% functionality (or more) isn't just confusing for system implementers it is confusing for end users. God forbid an implementer actually listen to your marketing noise on this and attempt to implement the wheel of communication for a single client...what would the users think? I also can't help but find the irony that I'm typing this message in yet another proprietary communication persistent chat styled vehicle that isn't on the wheel.
08-09-2018 11:22 AM
>I just threw up a little bit when I read about a Yammer connector for Teams
This connector has a good purpose for many use cases. I have a theater session at Ignite where I'll be discussing how the suite can be used with IT organizations and this connector is something that can be useful.
e.g. use Teams for the "private backchannel" to brainstorm on answers to questions posed in "public" in Yammer.
As for Slack - well it's not hard to understand why a single-product company views it as a good solution for any problem. They only have one answer to give.
09-12-2018 08:40 AM
I just today saw this Kaizala.
You can already give access to outside vendors or collaborators in Teams. Why would I have them use kaizala? Why wouldn't I just create a Team for the project we are collaborating on at the time?
Seems like a lot of redundancy that isn't needed. At least I don't see the need yet.