Team Update
Aggregate what your team shipped this week into a clear, stakeholder-ready summary. Pulls from IC weekly updates so you're not starting from scratch.
Overview
The Sapling Manager Team Update turns an engineering manager's connected tools into a finished team performance report and interactive dashboard in one continuous run. It reads real work from the systems a team already uses, then assembles a private, analytical read on how the team is doing, what changed since the last period, which wins are worth celebrating, and where each engineer needs support. The result is a browser-ready dashboard plus the underlying source file, produced without the manager handing off files or repeating themselves between steps.
Inputs
- Pulls automatically from connected tools — GitHub, JIRA, CI/CD, incident/on-call, goals/HR, docs, chat, and meeting notes.
- Confirms your team roster and how each person maps across systems.
- Captures the reporting period, comparison baseline, and context the tools can't see (PTO, parked projects).
Outputs
- A self-contained HTML dashboard with team metrics, wins, feedback, priority areas, and an expandable per-engineer view.
- The source Markdown file to keep, edit, or re-render later.
- Drag an updated file onto the dashboard to regenerate it with no further setup.
Why it matters
Managers get an evidence-backed read on team health in minutes instead of hours of manual collection. Every metric, quote, and link traces back to real captured data, so the report reflects what happened rather than guesswork. The skill compares the team against its own past performance and team averages instead of ranking people against each other, surfacing the hidden work that usually goes unnoticed. It reads from connected tools and writes local files only, never sending, posting, or changing anything in those systems.
Example
A manager of six engineers opens the skill before a leadership review and types “how is my team doing.” It shows which of her tools are connected, confirms her roster and matches each engineer's GitHub, JIRA, and chat identities, and sets the period to the two weeks since her last update. She pastes in the quarter's objectives and notes that one engineer was on leave. The skill pulls the team's pull requests, tickets, and incidents, computes how the period compares to the previous one, and delivers a dashboard. She sees a clear win to highlight, one risk worth getting ahead of, and a per-person view showing that a quieter engineer had been quietly unblocking everyone else's reviews, a contribution she had not seen in any standup.