Git and GitHub for Product Managers
The Four Questions You Currently Ask Someone Else
Every PM working with engineers interrupts them several times a week with the same handful of questions. Each one is answerable in under two minutes if you know where to look.
What You Ask | Who You Ask | Where the Answer Actually Is |
|---|---|---|
Is that shipped yet? | An engineer, in Slack | The releases page, or the PR's merge status |
What's actually in this release? | The tech lead | The release notes, or the list of merged PRs |
Why is this taking so long? | Standup, awkwardly | The PR — usually blocked on a review or a failing check |
Did anyone change the pricing logic? | Three people, none of whom are sure | The file's history |
WITHOUT THIS | WITH THIS |
|---|---|
20 min Finding out whether a feature has actually shipped | 90 sec same team, same repo |
The Real Benefit Isn't Speed
It's that you stop being the person who has to ask. Every time you interrupt an engineer to find out something visible on a screen you have access to, you spend a small amount of credibility. Answering your own questions is the cheapest technical credibility available to a PM.