Oftentimes it can be tempting to say ‘yes’ just simply to be polite or to keep the conversation moving, but this can cause a serious break in communication.
Watch Adam give this tip to Hark during his first week at SSW!
Imagine a client asks you to change how users log in to their application, but the requirements are unclear.
Instead of asking questions, you reply:
“Yep, sounds good to me!”
❌ Figure: Bad example - Miscommunication between the client and developer
Now you have an unhappy client, wasted development time, and additional costs caused by a misunderstanding.
Let's try a better approach…
You: “Could you clarify why we're changing the login process?”
Client: “We want users to log in with their email address instead of their username because customers keep forgetting their usernames.”
✅ Figure: Good example - Asking clarifying questions bridges the gap between you and the client
As a consultant or developer, always ask follow-up questions when something is unclear. For example, if a client requests a search feature, ask whether they want to search by name, category, or both. Similarly, if your manager asks you to prepare a report, clarify what information they want included.
Taking a few extra minutes to clarify expectations can save hours of rework and help you deliver the right solution the first time.