Many objections arrive disguised as small questions.
A concern about timing may really be a concern about ownership. A question about data may be fear of being blamed later. A request for "more alignment" may mean nobody believes the decision will stick.
Listen for repetition, vagueness, and questions that protect someone from exposure. Then name the possible risk gently enough that the real objection can come out.
Operator artifact: keep a hidden-objection log during a meeting: repeated question, surface topic, protected risk, person exposed, follow-up question.
Field test: When a question repeats, ask what risk the question is trying to protect against.
This is part 4 of 10 in Social Awareness for Operators.
