Define a data strategy for homepage team updates

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

As part of the personalized homepage project, we're looking at how to smartly surface a team summary for each individual user. Team summaries are useful for team leads and managers to keep an eye on their projects, and on their direct reports, and to see what items they might need to follow up on.

For a first pass, we'll utilize the existing "followed user" feature, and surface the followed user activity feed. However, that approach doesn't make it obvious that the feature can be used for "teams." It also requires users to actively follow everyone on their team. Longer-term, we'll want a better way of generating a summary of team activity, so we can provide a quick overview of what a person's actual team has been up to, that minimizes the need for user input.

Possible approaches

We initially discussed using AI/ML to summarize followed user activity in numbered list items. This will take some work, and is a step in the right direction. However, perhaps there's a better way to define a "team" for people, so we can surface relevant team updates in an easier/clearer way?

  • We could, potentially, create an experience that's completely separate from the existing "followed user" feature. That might involve introducing the concept of a team, and allowing people to manually define who is in their team, and who they want updates from.
  • Can we, for example, use AI/ML to determine who someone often interacts with, and use those individuals for the user's team summary? Or maybe there's another way to more intelligently define a user's team without them needing to manually do so?

To-do

  1. If we want to programmatically define what other users are on someone's "team" we'll need to define what will constitute as a relevant interaction between two people.
  2. For the team summary piece: We'll need to define what should count as "work" so we know what activity is meaningful/relevant to summarize in a team summary.
Edited by 🤖 GitLab Bot 🤖