1:1 prep and recording
Load manager conversations with context and keep action items tied to follow-through.
Workflow
Run one weekly review rhythm instead of rebuilding the meeting every Friday.
This page is for the operator who wants the product to become part of a real weekly engineering system, not just another dashboard tab.
- Move from dashboard signal to team discussion without assembling a manual report.
- Use one repeatable rhythm so leadership and managers know what the Friday review is for.
- Branch out of the review into prep, health, or ownership workflows when needed.
Primary job
Operating rhythm
this workflow turns the dashboard into a living weekly system
Best cadence
Weekly
most useful when it is run consistently, not only during crises
Decision type
What changed and what to do next
the weekly review is the bridge between signal and action
What it solves
Teams often have the dashboard but not the operating discipline around it.
This workflow explains how to turn the product into a repeatable weekly habit that actually changes leadership behavior.
No repeatable meeting shape
Without a fixed rhythm, the team spends the meeting reconstructing the week instead of making decisions.
Signals do not branch correctly
Even when a risk is spotted, leaders often do not know which adjacent workflow should pick it up next.
Follow-through stays vague
The review feels useful in the room but does not reliably reshape manager or leadership action afterward.
What the workflow covers
The rhythm is built around one baseline, one review, and explicit branching into follow-up work.
That is what makes the weekly review useful beyond the meeting itself.
Shared baseline
Open the dashboard and trend surfaces that frame the week before the meeting begins.
Structured review
Work through movement, pressure, and anomaly rather than collecting general updates.
Explicit branching
Use related contributor, health, and ownership pages when the weekly signal needs a second layer of interpretation.
How the cadence runs
Prepare, review, branch.
Keep the weekly loop simple enough to sustain and specific enough to matter.
Before Friday
Open the current baseline
Review the dashboard before the meeting so the operator already knows what changed and where the anomalies sit.
The room starts with current context.
During the review
Focus on movement and decision
Use the baseline to discuss what happened, what matters, and whether the signal needs people or repo follow-through next.
The meeting produces action instead of recap.
After the review
Carry the signal forward
Move the relevant threads into manager prep, health review, or ownership work while the context is still fresh.
The weekly review changes the next week too.
Workflow output
The weekly review works when the dashboard is treated as the start of a conversation, not the conversation itself.
That is why the workflow is about cadence and branching as much as the screen itself.
- The dashboard frames the week quickly enough for a regular Friday rhythm.
- Trend and anomaly views help the team focus on movement, not just raw output.
- The workflow assumes some signals will need to move into adjacent pages right away.
- The meeting is most valuable when it produces explicit follow-through, not just discussion.
What changes
The weekly review becomes a dependable operating habit instead of a variable meeting.
That improves both leadership discipline and the quality of downstream action.
Cleaner meeting design
The team knows what the review is for and how it should move from signal to decision.
Stronger manager handoff
Signals move into prep and follow-through more naturally because the workflow expects that branch.
More consistent learning
Week-to-week review becomes a better place to spot patterns, not just isolated incidents.
Go deeper
Use these pages when the weekly review opens a second-order question.
They help you route the signal into executive, people, or ownership follow-up.
Carry it into other rituals
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.
Diagnose the deeper issue
02People 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.
Ownership 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.
Need a weekly review that actually sticks?
Use the dashboard as the shared baseline, then run the weekly rhythm until the team stops having to reinvent the meeting.