Working With Clients · September 2, 2024 · 1 min read
The Question I Should Have Asked Before a Project Slipped
I once treated unclear feedback as something I had to solve alone. The resulting delay taught me that asking a precise question early is a form of responsibility, not a sign of weakness.
As a junior developer, it’s easy to fall into the trap of thinking that asking questions might make you seem less capable or even "stupid." I’ve been there—many of us have. This mindset can be particularly paralyzing when you're eager to prove yourself in a fast-paced environment. But in reality, avoiding questions can sometimes do more harm than good.
In a recent project, I had an important realization. I was assigned a relatively straightforward ticket, but during testing, I received feedback that extended beyond the original scope. Instead of clarifying the additional requests, I decided to handle them on my own. My hesitation to ask questions slowed me down significantly, and the ticket neared its deadline with several issues unresolved. As a result, the CTO had to step in due to the delay, and I found myself stressed, working overtime to correct things that could have been addressed sooner.
“In hindsight, I learned that asking questions doesn’t diminish your capability as a developer—it actually enhances it. It can save time, improve clarity, and prevent unnecessary stress. In development, communication is key, and it's better to ask early than to fall behind later.”
What I learned
I learned that unclear scope does not become clearer through silent effort. A short conversation can protect the schedule, reduce stress, and give everyone the same understanding of what must change.
How it changed my thinking
When feedback appears to extend beyond the original request, I now pause and confirm the expected outcome, priority, and scope. I would rather surface uncertainty early than hide it until a deadline is at risk.
