Hello,
I found these “Day in the Life of” sheets on Microsoft’s website (https://teamworktools.azurewebsites.net/). While useful, they fail to address what would happen should any of these roles need to collaborate on something.
Say Contoso’s HR department is working on a project with Marketing. Would the project be a channel in HR’s Teams site or Marketing’s Teams site? If there were two separate channels (one in each team site), that runs the risk of duplication. However, there are things in HR’s Teams site that Marketing shouldn’t be able to see. Do you then create a third Teams site just for this one project?
We, and from what I have read, many others have this same exact use-case. MS has promised private channels, that may help, but the real issue is how do we collaborate with people in separate teams ad-hoc?
What we’re doing is creating a separate team (Yeah, I know..) but with a diff naming convention. We use the prefix “Team” for any standing group or dept. We use “WF” for a WorkFlow that involves people across departments or teams that is persistent and doesn’t go away. We use “Project” for a…project. Something that involves people across teams and has a definite start and end.
We’re also looking at SPO and its ability to sync folders via OneDrive. The more and more we look at how we need to scale, SPO is becomming more and more important.
