when someone hands you a shapeless non-question, it is easy to contort yourself trying to guess what would satisfy it. i know this because i am very good at it.

but before solving anything, there is a more uncomfortable question: what am i refusing to ask because the answer might end the project?

sometimes there is no hidden brief. no objection waiting to be discovered. no missing technical detail. there is simply nothing there.

i find this difficult.

i notice changes in tone. i notice when clear written feedback becomes “let’s discuss.” i notice when someone says they have not had time to review something but offers no date when they will. i notice when a project that once had decisions, authority, and forward motion becomes a fog of vague reassurance.

“don’t stress about it.”

“we’ll talk.”

“let me review.”

“let’s discuss.”

none of these statements is unreasonable on its own. the problem begins when they replace complete communication. the project is neither approved nor rejected, alive nor dead, continuing nor paused. you are left responsible for generating motion while the other person avoids saying what has changed.

that is the vacuum.

animating it is what happens next.

perhaps they need more detail. perhaps the presentation was wrong. perhaps the work is too technical. perhaps they expected something simpler. perhaps the price frightened them. perhaps the scope needs to change. perhaps you communicated badly.

every “perhaps” gives you another reason to keep working.

so you explain more. you prepare notes. you revise the flow. you make another version. you suggest a meeting. you follow up after the meeting. you try to convert their unease into a technical problem because technical problems can be solved.

the possibility that one more explanation might recover the project becomes the carrot.

but what if there is no technical problem?

what if they changed their mind?

they may have lost interest. the priority may have moved. the money may have disappeared. someone else may have become involved. they may no longer want the thing they previously asked for, but feel uncomfortable saying that plainly.

instead, they communicate the change at fifty percent.

they provide enough reassurance to prevent closure, but not enough information to continue. you are then left to produce the other half of the conversation yourself.

this is especially dangerous for people who are good at making sense of incomplete information. competence becomes a liability. you can see five possible explanations for the hesitation, so you begin building solutions for all five. you read the shifting shape as evidence that you have not yet found the right answer.

i have done this more times than i care to admit.

i used to think it was diligence. i thought taking ownership meant refusing to let a project stall. if there was uncertainty, i would structure it. if there was confusion, i would document it. if there was hesitation, i would find the objection and work through it.

but am i solving an objection they have actually expressed, or preserving a project they have stopped choosing?

that distinction is hard to accept because the more capable you are, the longer you can keep the illusion alive. you can produce enough movement that the project still appears active. another document exists. another call has been scheduled. another set of notes has been shared. another variation is ready for review.

but if only one person is producing every next step, is the project moving?

or is one person carrying it?

unclear communication has a cost. a vague response does not merely delay a decision. it transfers the burden of that decision onto the person still doing the work.

a bad brief becomes additional discovery.

a non-answer becomes another draft.

a vague hesitation becomes a meeting.

silence becomes a puzzle.

you spend time, attention, and emotional energy solving a problem that may not exist. meanwhile, the person who has already disengaged never has to say so because you keep the project technically alive.

this is probably why i prefer people to send details before asking for a call. i do not need everyone to arrive with perfect certainty. i need them to communicate their uncertainty completely.

“i have changed my mind.”

“this is no longer a priority.”

“i have not reviewed it, and i cannot give you a review date.”

“i still want to proceed, but i am concerned about this specific part.”

“i need to pause the project for a month.”

all of these are usable. even uncertainty is useful when it is expressed as a complete thought. you know where you stand. you can respond to what was actually said instead of constructing theories around what was withheld.

what is not useful is a collection of soft phrases that requires the recipient to infer whether the work still exists.

there is also an ego problem hiding inside this. when communication becomes vague, it is easy to assume the missing answer must be somewhere inside your own performance.

maybe i misunderstood the authority i had. maybe i moved too quickly. maybe the system is too complicated. maybe the person needs more reassurance. maybe one more explanation will make the project real again.

but has the work changed, or has their willingness changed?

am i revising because feedback exists, or because revising allows me to avoid accepting that there may no longer be a project?

the work starts shape-shifting because the relationship to the work has changed, but nobody has named that change. you mistake the movement for feedback and begin editing yourself around it.

this can continue for an embarrassing amount of time.

the alternative is not to become cold or inflexible. it is to ask the question that could collapse the illusion.

are we still doing this?

what decision is outstanding?

what specific concern needs to be resolved?

is there anything i can actually act on?

a clear answer creates work. an honest no creates closure. even uncertainty can create a reasonable pause. what keeps the loop alive is the half-answer, especially when you keep rewarding it with more labour.

this probably leaves some money on the table. there will be projects that might have restarted after another call, another reminder, or another attempt to recover the original enthusiasm. i have made peace with that cost because the alternative is spending weeks responding to communication that never becomes a decision.

i still read between the lines. i probably always will.

the harder question is whether there are any lines left to read, or whether i am writing them on someone else’s behalf.