The Problem
Teams rarely fail from one bad decision. They rot from polite, low-bar questions.
Every time you ask "Was this approved?" or "Did you test this?", you signal that approval and testing are optional extras. You turn basic engineering hygiene into a favor, and you turn yourself into a hall monitor.
Why Phrasing Sets the Ceiling
Language carries an unspoken baseline.
- Compliance questions ("Did you...?") assume the bar might have been skipped. They invite a lazy "Yeah, should be fine" and push people into a defensive yes/no corner.
- Presupposition ("Send me the approved...") treats the best practice as already done. You aren't asking if they met the standard. You're asking for the output that comes after meeting it.
When you ask for the artifact instead of the status, skipping steps gets awkward. People have to admit "Actually, we didn't get sign-off" instead of coasting past a vague check-in.
The Effect on Your Team
| How you ask | What the team hears | What actually happens |
|---|---|---|
| "Did you write tests?" | Tests are nice to have if you have time. | Shortcuts become normal under deadline pressure. |
| "What edge cases did the tests catch?" | Shipping without tests isn't on the table. | Engineers verify edge cases before opening the PR. |
| "Is there a rollback plan?" | Deploys happen without one all the time. | People scramble during incidents. |
| "Where's the rollback linked in the ticket?" | No rollback link, no deploy. | Runbooks become muscle memory. |
10 Swaps That Keep the Bar High
- Design handoff: Wrong: "Was the design approved?" Right: "Send me the approved design so I can see the final states."
- Code reviews: Wrong: "Did you test this locally?" Right: "What broke when you tested this locally?"
- Production deploys: Wrong: "Did you check the logs after deploying?" Right: "What did the error rate look like 10 minutes post-deploy?"
- Incident prep: Wrong: "Do we have a rollback plan?" Right: "Drop the rollback steps in the deploy thread before we push."
- Scope creep: Wrong: "Are we sure this is in scope?" Right: "What are we cutting from this sprint to fit this in?"
- Stakeholder alignment: Wrong: "Did product sign off on this change?" Right: "Loop me into the sign-off thread so I have the context."
- Data migrations: Wrong: "Did you back up the database first?" Right: "Where's the snapshot stored before we run the migration?"
- Meetings: Wrong: "Is there an agenda for this?" Right: "Add the agenda to the invite so I can prep beforehand."
- Client delays: Wrong: "Did you tell the client we're behind?" Right: "How did the client take the updated timeline?"
- Architecture decisions: Wrong: "Did you consider how this scales?" Right: "At what load does this approach start to bottleneck?"
What to Watch Out For
This isn't an excuse to be passive-aggressive. If you say "Send me the approved design" when you already know nobody approved it, you're just playing gotcha. Your team will resent you for it.
Use this in good faith. Assume competence first, ask for the artifact naturally, and when a gap shows up, fix the process instead of shaming the person. Also, don't demand standards you ignore yourself. If you ask for agendas and rollback links, yours better be spotless.
Over to you:
- What's a subtle question on your team that accidentally lowers the bar?
- Have you ever caught yourself asking a "hall monitor" question, and how would you rewrite it?
Top comments (0)