When Your Leader Gives an Unreliable Request, Don't Refute Immediately—Start with This Step

There is a saying: act first, talk later. Sometimes a CTO asks for something that seems of little value, yet the author still proceeds to execute it.

From a professional standpoint, the author immediately explains the execution difficulty and cost, presenting the current situation in full.

If the leader insists on proceeding, the author carries out the task without hesitation. When unable to give an immediate professional conclusion, the author says, “I’ll research and provide my conclusion by tomorrow,” which he calls “timely feedback.”

The superior’s information pool is far larger than the subordinate’s.

The author notes that his own judgment may be limited by the information he has, and it may lack context. He suggests asking the leader to clarify critical context; once the context is clear, the task may become feasible or even urgent.

It is a career taboo to wait a long time before providing feedback on a leader‑assigned task. Throughout execution, regardless of smoothness, the author stresses the need for continuous updates. If difficulties arise, reporting them allows the leader to give advice or halt the work. Sharing results promptly, along with personal post‑mortem insights, demonstrates reflective habits and builds trust.

Key Takeaway

Pre‑assessment (your professional judgment), mid‑process progress updates (transparent execution), and post‑result reporting (including your own review).

Mistakes in pre‑assessment are acceptable—they often stem from information gaps; slower progress is understandable due to unforeseen challenges. The biggest risk is working in silence and responding “almost done” when asked, which erodes confidence.

Finally, avoid being the person who only nods or immediately says “no.” Follow the outlined method to become the trusted person a leader feels comfortable delegating to.