3 ms·

> Teams seems to be the only one to avoid the fate of becoming the communication platform where knowledge goes to die. I wonder how many people actually find a

> Teams seems to be the only one to avoid the fate of becoming the communication platform where knowledge goes to die. I wonder how many people actually find any kind of information in teams logs that are older than, say, a few days. Even leaving aside the fact that it's a horrendous experience because of the lag and messages jumping all over the place as they're loaded, the search function is an absolute joke. Half the time it doesn't find anything, and the other half it'll just give you give the message that exactly matches your query, without any kind of context.

TeMPOraL 3y ago
I agree - search in Teams absolutely sucks. Fortunately, a basic threading capability that's separate from chat helps a bit - but more importantly, search in Outlook and SharePoint sucks much less (though still some), so in an integrated system, there are other ways to browse chat history, more suitable for building up a knowledge base.
- vladvasiliu 3y ago
  Yeah, search in Outlook has a hope of finding stuff. Am I to understand you can use Outlook to browse Teams chats? How would one go about doing that?
  - TeMPOraL 3y ago
    I'd have to ask my corporate IT, but I understand that if you perform enough unholy rituals to bind Exchange and SharePoint and AD together, everything somehow becomes smoothly accessible from everything else. Like, e.g., hovering over someone's profile on Teams is the quickest way for me to check if they're on a leave and have auto-responder set for their e-mail. Or, calendars staying in sync, and Teams automatically applying a "Busy/DND" status based on your "busy" blocks. Or, from the more annoying side, how Yammer (Microsoft's pseudo-Facebook for Work) updates pop up in both Teams and Outlook. Or how the same files you exchange inside teams in Teams can also be found via SharePoint, and even pop up in Outlook. Etc. There's a lot of those tiny things.

TeMPOraL 3y ago

I agree - search in Teams absolutely sucks. Fortunately, a basic threading capability that's separate from chat helps a bit - but more importantly, search in Outlook and SharePoint sucks much less (though still some), so in an integrated system, there are other ways to browse chat history, more suitable for building up a knowledge base.

vladvasiliu 3y ago
Yeah, search in Outlook has a hope of finding stuff. Am I to understand you can use Outlook to browse Teams chats? How would one go about doing that?
- TeMPOraL 3y ago
  I'd have to ask my corporate IT, but I understand that if you perform enough unholy rituals to bind Exchange and SharePoint and AD together, everything somehow becomes smoothly accessible from everything else. Like, e.g., hovering over someone's profile on Teams is the quickest way for me to check if they're on a leave and have auto-responder set for their e-mail. Or, calendars staying in sync, and Teams automatically applying a "Busy/DND" status based on your "busy" blocks. Or, from the more annoying side, how Yammer (Microsoft's pseudo-Facebook for Work) updates pop up in both Teams and Outlook. Or how the same files you exchange inside teams in Teams can also be found via SharePoint, and even pop up in Outlook. Etc. There's a lot of those tiny things.