Favorites and Following in Groups, Teams, and SharePoint

This is a thoughtful post and thanks for the clean writeup.

It's a tough design problem for sure.  Truth be told there are some technical blockers that would make it harder to rationalize that we'd like - and we are working on those blockers.   I don't want to hide behind that as an excuse to not think through the problem.  I can say in previous explorations there were a few constraints that have come up:

 - There are many sites that do not have a Group attached.  This includes Team Sites (this will be solved over time as we work on attaching to existing sites to Groups) as well as publishing sites and portals folks might want to get back to.

 - In hybrid deployments, customers will see on prem sites in this followed list.  On prem the name will be "Followed sites" without an ability for us to easily change or align.

 - In talking with customers, there does seem to be two camps - those that have a set of Groups they work with across all workloads and would like to see a single, consolidated list.  And those that have some Groups where they only use it for mail, for instance, and would find those Groups distracting when looking in SharePoint (and vice versa).  This applies even more with algorithmically-defined list of sites like our Frequent list, which we really want tuned to those sites (groups or not) that folks work with files/content in.

Anyway, I hope that provides and context and food for thought.  Figured I'd share openly in the spirit of this community.  On a broader level, we are always working on various work items to make Groups coherent across the suite.  cfiessinger has the latest I'm sure on public roadmap there, but there is lots of exciting stuff that I believe will make a real difference.