Likewise here. IMO, Teams is a good place for information to go to die. I can file emails that I may want to refer to in my own filing system, and in some cas

Likewise here. IMO, Teams is a good place for information to go to die. I can file emails that I may want to refer to in my own filing system, and in some cases I've gone back to emails I filed ten years ago to discover the answer to some company question. With Teams, I can find on Monday posts that were sent on Friday. They're probably still there, I just can't find them. Similarly for files that are stored on Teams/Sharepoint; it's hard to create a useable link (at least there's no obvious way to do it), and everyone is forced to use one person's directory structure, which as often as not doesn't make any sense to the rest of us. What's the right way to store files? Store a single copy in some database-like structure, and let me create my personal "directory structure" to point to it. Then I can find it, and if anyone else uses their own personal directory structure, they can find it too. This could be a Linux file system where I'm allowed to create simlinks, but not copy a file, or it could be my Outlook folder structure. (I'm assuming that when Outlook sends an email to multiple recipients on the same email server, there's really only one copy of the email, and everyone has links to it, at least until they reply to it.)