Which stage areyou really on?
Same six stages, two ways in. Pick the one you can answer honestly. Then send the other to a colleague: the gap between what leadership believes and what engineering can prove is usually the most useful number on the page.
For CTOs and engineering leads
You’ll need to know how your repository, CI and review actually work.
- Evidence checks, from branch protection to scheduled routines
- Your stage, and the gap between what you’d claim and what you can prove
- Your next step as a GitHub issue
For CEOs, founders and non-technical leaders
No technical knowledge needed. Each question says who to ask or what to look at.
- Questions about money, time, people and risk you can check yourself
- Your stage, and what it means for the business
- The questions to take to your engineering lead, as an email
Taken both, or received a link from a colleague? See the comparison. Answers travel in the link itself; nothing is stored on a server.