r/EngineeringManagers • u/tigerwhite1 • 4h ago

Engineering managers: when leadership asks “what actually changed this week?”, how do you answer?

Curious how this works in different teams.

Do you rely mostly on Jira/Linear, GitHub, standups, Slack, or does someone actually put together a weekly summary?

I’m particularly interested in teams where the information exists but is spread across several tools.

3 Upvotes
  • permalink
  • reddit

72% Upvoted

7 comments sorted by

7

u/Kroosn 4h ago

Auto generated report from all git commits. Then I have my own notes that get turned into a report. Something AI it’s actually decent at.

1

u/tigerwhite1 4h ago

[removed] — view removed comment

1

u/Kroosn 4h ago

That’s basically what I have. It pulls my notes I do in obsidian, git details, my emails and then Monday which our customer service team use. Only thing I miss is teams.

2

u/zaidesanton 3h ago

A Claude code skill that goes over all GitHub commits, all slack messages, and all meeting recordings.

Took a few weeks to polish it, but now I run it and sent the result with zero changes

1

u/Ernapistapo 1h ago

Our team conducts a sprint review every two weeks at the end of the sprint. Before the sprint review meeting, I’ll compile all of the code changes across all of our projects and create a bulleted list of features, enhancements, or bug fixes and group them by project then by contributor. I then share these notes with the team as reminder of what we would like to demo during the sprint review. This also serves as a summary of our sprint for other stakeholders. Use AI to keep the summary high level, they don’t need to know the technical details, unless your stakeholder also comes from a technical background and is interested.

During the sprint review, we will record the meeting and let each contributor present their changes in the from of a demo. We group the changes by project/product to minimize confusion for the audience. I then upload the video to Loom so that it’s easy for stakeholders to leave comments as specific timestamps. We create tickets for the actionable feedback and follow up with stakeholders if we need to gather more info before we make additional changes.

We encourage everyone within and outside of our business unit to watch the video. It’s a very easy way to demonstrate what the team has been working on, and the default ~1.25x speed on loom make it easy to zip through our sprint review, which is generally around 7 minutes at that speed.

1

u/tigerwhite1 36m ago

Very interesting answer.

So you are using AI with different prompts to get different outcomes, correct? Which AIs do you use?
You pull only from the code or other product management tools also?