A Good Question Is Part of the Toolkit

A vague question is a remarkably efficient way to get a vague answer.

“Is this okay?” can mean the finish, the location, the price, the drawing revision, or whether everyone would like to go home. A cheerful “Yep” does not tell you which one was approved.

A useful question names the decision.

Try: “Which of these two locations is approved?” Or: “Does this replace the earlier instruction, or is it an additional task?” Or simply: “What does finished need to look like here?”

Those questions are small enough to answer. They also make it easier to spot when two people are solving different problems.

Give the other person something concrete to work with: the relevant item, the part that is unclear, and the decision needed before the next step. Keep photos and documents inside the approved work channel, with only the information needed for that decision.

There is no prize for attaching the entire history of civilization when one marked-up image will do.

Then close the loop. Repeat the answer in plain language and record it in the normal job notes: what was agreed, who confirmed it, and what happens next. If approval belongs to someone else, keep the task waiting on that person. Silence is still silence, even when the schedule is wearing a very impatient expression.

This does not mean stopping every five minutes to ask permission to think. Routine choices within your scope remain routine. The useful pause comes when the missing answer could change the scope, cost, finish, or someone else’s work.

A good question is a tool. It should fit the problem, be easy to use, and leave less damage than guessing.

Sometimes the most productive thing you can do with both hands is leave them off the tools for a minute.