This page is the working picture of how an assessment runs. It pairs with the flagship build & compile analytics audit.
Columns we fill
| Column | What we record | Why it matters |
|---|---|---|
| Clock | Build duration, queue wait, compile stage time | Separates waiting from working |
| Honesty | Cache claims vs. observed reuse | Stops false confidence |
| Decision link | Which release choice the number informs | Retires orphan metrics |
| Owner | Named human, not a team alias | Keeps follow-through real |
| Priority | Ranked change for the next cycle | Turns reading into action |
Sequence
- Intake — you send recent exports and name two releases (one calm, one difficult).
- Interviews — short sessions with build owners and release leads.
- Ledger draft — we mark trustworthy clocks, decorative ones, and gaps.
- Priorities — at most five ranked moves; usually three is healthier.
- Close-out — a briefing where disagreements are written down, not smoothed over.
What you prepare
Anonymised duration samples, compile stage breakdowns, and a sentence on who owns the cut checklist. If exports do not exist yet, say so—we will adjust the first week rather than invent figures.
Natural next action
If this sequence matches the problem you have, request a briefing for the audit, or skim fee guidance first.