1:1 prep and recording
Load manager conversations with context and keep action items tied to follow-through.
Use case
Run the weekly engineering review from one shared baseline.
This page is for the leader who is tired of assembling Friday updates from half a dozen tools. Forgemaster turns the review into one repeatable decision-making loop.
- Start the meeting from the same delivery facts every week.
- Spot stalls, incident pressure, and contributor load before they surprise the team.
- Carry the signals directly into manager follow-through.
Best cadence
Weekly
best used as a fixed review rhythm rather than an occasional report
Primary audience
CTO + managers
shared review surface for leadership and team leads
Primary outcome
Fewer blind spots
less scrambling for updates and more time on real decisions
Problem framing
Why this review is harder than it should be.
Most weekly reviews fail because the team spends the first half collecting facts instead of acting on them.
Too many sources
Metrics live in one place, incidents in another, and contributor context in someone’s memory.
No shared baseline
Leaders walk into the review with different versions of what happened and why it matters.
Action gets lost
Even when the review is useful, the follow-through often breaks outside the meeting itself.
What Forgemaster surfaces
The weekly review pulls delivery, incident, and contributor context into one view.
It gives the meeting a practical operating baseline instead of another slide deck.
Delivery movement
See cycle time, review flow, and contribution patterns that explain whether the team actually moved this week.
Operational pressure
Add incident load, downtime, and response context so weekly output is read with real operating conditions attached.
People signal
Use contributor and manager context to see when the delivery pattern points to overload, concentration, or coaching follow-up.
How the cadence runs
One review, three moves.
The value comes from making the weekly loop predictable.
Thursday
Let the baseline settle
Open the dashboard after the week’s data has landed so the team starts from the current operating picture.
The facts are assembled before the meeting.
Friday
Review what moved and why
Work through delivery movement, incident pressure, and contribution context together instead of collecting updates live.
The meeting produces decisions instead of recap.
After the review
Hand off follow-through
Move contributor-specific signals into manager prep, ownership work, or executive reporting instead of letting them disappear.
The weekly review changes actual behavior.
Screen spotlight
The team metrics dashboard gives the weekly review its baseline.
It is designed to answer the first question in the room: what happened this week that actually matters?
- Incident context sits next to delivery movement instead of in a separate report.
- Trend views make weekly movement readable without digging through raw tools.
- Contribution context helps the team spot when output depends on a narrow set of people.
- The same view can anchor leadership review and team discussion.
What changes
The review becomes an operating loop instead of a reporting ritual.
That matters because leadership quality is mostly about what happens after the signal appears.
Faster prioritization
The team can decide what to fix, defer, or escalate without first debating what happened.
Earlier escalation
Ownership gaps, review drag, or people strain surface while there is still time to respond.
Better manager follow-through
The weekly review produces concrete threads to carry into 1:1 prep and coaching work.
Go deeper
Use these pages to break the weekly review into its parts.
Start from the meeting, then branch into the feature or adjacent use case that explains the signal.
Break down the signal
02Leadership reporting
Executive engineering briefing
When leadership updates feel vague, use team and repo signals to explain what changed and what needs support.
Outcome
Deliver engineering updates that hold up to follow-up questions.
Carry it into action
02Ownership fragility
Ownership and knowledge risk
When critical systems depend on too few people, use repo ownership and depth data to expose the risk early.
Outcome
Know which critical system would break if one person left today.
People strain
Team health and burnout signals
When overload or burnout shows up too late, use work-pattern and retention signals to surface strain earlier.
Outcome
Spot burnout and overload 4–6 weeks before it becomes attrition.
Want the weekly review to run on rails?
Start with the team metrics dashboard, then wire the review rhythm into the manager and executive workflows around it.