Connect your data
Authorize sources, scope the repos, and start the nightly sync.
Workflow library
See the operating loops, not just the screens.
Forgemaster is most useful when it becomes part of a weekly or monthly rhythm. These pages show the practical setup, review, and follow-through loops the product is built to support.
- Connect the right data sources without over-scoping the rollout.
- Run one repeatable weekly review instead of inventing a ritual from scratch.
- Turn team and contributor signals into tracked follow-through.
Setup burden
Low
the pages explain the minimal practical path to first value
Cadences
3 core loops
setup, weekly review, and manager follow-through
Audience
Operators
people responsible for running the workflow, not just approving it
Start the system
These pages explain how the product comes online and becomes part of the weekly rhythm.
They are written for the person who has to operationalize the tool, not just buy it.
Run the weekly review
Turn Friday review prep into one repeatable operating cadence for the whole team.
Prepare 1:1s and follow through
Run a weekly manager rhythm that starts with evidence and ends with tracked actions.
Keep the loop moving
After setup, the value comes from turning signals into conversations and tracked actions.
Use this section to understand what the team actually does with Forgemaster once the data is flowing.
Weekly review pain
Weekly engineering review
When leadership spends the meeting reconstructing the week, use one shared baseline for delivery, incidents, and risk.
Outcome
Review prep drops from 90 minutes to under 20.
1:1 prep and recording
Load manager conversations with context and keep action items tied to follow-through.
Shared baseline
Team metrics dashboard
When weekly reviews start with stitched-together updates, use one screen for delivery, incidents, and contribution movement.
How to use this section
Browse in the same order your team will adopt the product.
Start with data connection, then move into the weekly team loop, then into manager follow-through.
1
Connect just enough data
Bring in the systems that create the signals you want to review first. Do not boil the ocean.
First value arrives faster.
2
Run the shared review rhythm
Use one repeatable weekly review so leadership, managers, and the team start from the same baseline.
The product becomes part of the operating system.
3
Carry signals into follow-through
Use contributor and manager workflows to turn weekly signals into coaching, ownership, and retention action.
Signals convert into change.
Need the shortest path to first value?
Start with the setup workflow, then run one weekly review. That is enough to make the rest of the system legible.