Running a requirements call
Ask the right questions, play it back, and confirm before you build.
Case study: The report nobody wanted
Kiran, a developer in Bengaluru, joined a call with a Melbourne logistics client who said, "We need a dashboard for deliveries." Kiran nodded, said, "Yes, yes, understood," and spent three weeks building a beautiful chart-heavy dashboard. The client's ops manager looked at it and said, "We just need to know which trucks are late, right now." Kiran's lead, Farah, redid the call. She asked, "Who looks at this, and what decision do they make?" then played it back: "So you need a list of late trucks, refreshed every five minutes, for dispatchers on mobile. Right?" The rebuild took four days.
Takeaway: "Understood" is not understanding. Ask open questions, play it back, and get a yes before you build.
We often say "understood" to avoid seeming slow, and save doubts for later. Global clients expect questions; a good playback makes you look sharp, not uncertain.
Running the call
Goal: Leave the call with the real problem, the users, a definition of done, and a confirmed summary.
Step by step
- Start with the problem. Ask what's going wrong today, not what to build.
- Ask open questions. Who uses it, when, and what decision they make.
- Dig into examples. Ask for the last time this problem happened.
- Play it back. Summarize in your words and ask if it's right.
- Confirm in writing. Send the summary and the open questions.
Say this, not that
| Before we talk about the dashboard, what problem are you trying to solve? | The request is a guess at the solution. Find the problem. | |
| Who will use this, and what decision will they make with it? | ||
| Could you walk me through the last time this went wrong? | Any other requirements? | Stories reveal details that lists never do. |
| Let me play that back to make sure I've got it right. | Yes yes, understood. | A playback catches misunderstandings in minutes, not weeks. |
| I'll send a one-page summary today. Could you confirm it by Friday? |
Model conversation
- Emma
- So basically we need a dashboard for deliveries.
- You
- Happy to help. Before we get into the dashboard, what problem are you trying to solve?
- Emma
- Our dispatchers keep finding out about late trucks only when customers call to complain.
- You
- That's useful. Could you walk me through the last time that happened?
- Emma
- Yesterday a truck was stuck on the freeway for two hours. Nobody knew until the store rang.
- You
- Let me play that back. You need dispatchers to see late trucks within minutes, ideally on their phones, so they can call stores first. Is that right?
- Emma
- Exactly. Honestly, the charts don't matter much.
- You
- Great. I'll send a one-page summary today. Could you confirm it by Friday before we start?
Explaining your needs
Goal: Explain your problem clearly in plain words, so the team builds what your business actually needs.
Step by step
- Describe the pain. What goes wrong today, and how often.
- Give an example. One real story beats a list of features.
- Say what success looks like. How will you know it's working?
- Ask when unclear. It's fine to ask the engineer to explain jargon.
Say this, not that
| I'm not technical, so I'll explain the problem and you tell me the best way to solve it. | You own the problem. Let them own the solution. | |
| Right now, our sales team spends about two hours a day copying data between spreadsheets. | ||
| Here's a real example from last week. | You know, the usual issues. | Specific stories give engineers something to design around. |
| Success for me is that the team stops doing this by hand. | ||
| Sorry, could you explain what an API means in this context? | Yes, yes, that's fine. | Agreeing to what you don't understand creates surprises later. |
Model conversation
- Yuki
- Thank you for your time. Could you tell me what you need?
- You
- Sure. I'm not technical, so I'll explain the problem, and you can tell me the best way to solve it.
- Yuki
- That's perfect, actually.
- You
- Our sales team spends about two hours a day copying orders from email into three spreadsheets. Mistakes happen every week.
- Yuki
- I see. We could connect your email system to your CRM through an API.
- You
- Sorry, could you explain what that means for my team, day to day?
- Yuki
- Orders would appear in one place automatically. Nobody would copy anything.
- You
- That's exactly it. Success for me is zero copying and no mistakes in the monthly report.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.