How to Ask
The same question can build credibility or cost it. Here's how to ask so it lands, including with an offshore NOC team.
Use This When
You have the right question but worry how it will land. The same question can build credibility or cost it, depending on when you ask it, how you say it, and what you do with the answer.
The Six Habits
Do This
- Ask about outcomes, not internals. "What do users see?" and "How would we know?" are questions you can always own. "Why did you pick that database?" is a fight you'll lose.
- One question at a time. Stacking three questions lets them answer the easiest one.
- Ask, then go quiet. Count to five in your head. The real answer often comes after the first, safer one.
- Follow the weak answer. "It depends," "the team," and "soon" are invitations. Every question in the bank has a follow-up for exactly this moment.
- Say "I don't know" out loud, then ask something sharp. "I don't know how that works. What happens to users if it fails?" Admitting you don't know and then showing judgment builds more trust than bluffing ever could.
- Close it. End with an owner and a date ("Who's taking that, and by when?"), then send a two-line written recap within the hour.
Tone: Curious, Not Prosecuting
| Lands badly | Lands well |
|---|---|
| "Why didn't anyone catch this?" | "How did we find out, and what would have caught it sooner?" |
| "Is this going to be late again?" | "What's the earliest sign it might slip?" |
| "Who made this change?" | "What made it possible for this change to go out without a canary?" |
| "That doesn't make sense." | "Help me understand the failure case." |
| "Do you understand?" (to the NOC) | "Tell me back what you'll do, so I know I explained it well." |
With an Offshore NOC L1 Team
Do This
- Short sentences, one idea each. Avoid idioms like "ballpark" and "circle back," and avoid sarcasm. Remember, many analysts work in their second language.
- Never accept "yes, understood" as confirmation. Ask for teach-back or a show-me instead.
- Ask about the instruction, not the person. "Which step was confusing?" gets a true answer. "Why did you get it wrong?" gets silence.
- Make it safe to say "I don't know." In many cultures, saying no or admitting confusion to a senior manager feels risky. Thank people who do it, publicly.
- Put it in writing after you say it. A short written summary in the team channel reaches the next shift and helps anyone who missed something on the call.
Example in Practice
The moment: the NOC missed an escalation overnight. The assistant was timing out for 40 minutes before SRE was paged.
The question that gets silence: "Why didn't you escalate?"
The questions that get the truth: "Walk me through what you saw at 02:10. … What did the runbook tell you to do at that point? … Was there a moment you thought about escalating? What stopped you?"
What you learn: the runbook said "escalate if the issue is serious," and last month someone was criticized for paging SRE over nothing. In other words, the process and the culture caused the miss, not the analyst. You fix the runbook ("if timeouts exceed 5% for 10 minutes, page SRE"), and you tell the whole team that early escalation is never wrong.
What Actually Happens
- Someone answers a different, easier question than the one you asked.
- Counter: "That's helpful. And on my question: what do users see?" Calmly asking again is a credibility move.
- The room goes silent and you feel the urge to fill it.
- Counter: don't. Silence after a good question is the question working.
- Someone uses your question to make you look uninformed ("Well, obviously…").
- Counter: "Great, then it should be quick to answer. What's the number?" Stay pleasant and keep the focus on the answer, not on you.
- You ask the right question and nothing happens afterwards.
- Counter: a question without an owner and a date is just conversation. Always close it.
Do It This Week
- Ask one question from When You're Tested or Dismissed in a technical meeting.
- Use teach-back once with the NOC: Instructions That Stick.
- Send a two-line recap after one meeting.