Great Questions, Everyone.

Nobody in that room said no.

I have replayed the meeting more times than it deserves, and I am certain of that much.

One person wanted to play devil’s advocate for a minute. Someone else raised a concern about an edge case. A third wondered whether we had tested the assumption underneath the whole thing.

All fair questions.

All asked pleasantly.

At least two of them were genuinely trying to help. I would put money on that. The third probably was too.

I answered every question.

People nodded. Someone said the discussion had been useful. The meeting ended on time.

The thing I had spent six weeks building died on that table without a single person having to be against it.

There was no rejection. No vote. No difficult conversation.

Just a room full of smart people having a thoughtful discussion, followed by absolutely nothing.

The completely reasonable drive home

That was when it landed.

It landed strangely because there was nobody to be angry with.

Nobody dismissed the work. Nobody called the idea bad. There was no sentence I could repeat later as proof that the meeting had gone wrong.

I tried explaining it afterward.

“And then he asked whether we had validated the assumption.”

I could hear how harmless it sounded before I finished the sentence.

He had asked a reasonable question. I had given a reasonable answer. Everyone had behaved professionally.

Never mind. It was hard to explain.

With nobody else to blame, I landed somewhere worse.

Maybe the idea had not been that good.

Maybe I had missed something obvious.

Maybe six weeks of work had seemed convincing only because I was too close to it.

That was what the meeting produced. Not a clean defeat I could disagree with. Doubt about my own work, arriving on the drive home with no evidence attached in either direction.

The room did not reject the idea. It handed the idea back to me as self-doubt.

Questions have excellent public relations

It took me an embarrassing number of meetings like that to understand what was happening.

A question is not a position.

If someone argues against my proposal, they have taken a side. They own the disagreement. If the work later succeeds, they were the person who opposed it.

That carries risk.

A question carries almost none.

“Have we considered the downstream impact?”

“What happens in this edge case?”

“Are we confident in the assumption?”

Every one of those may be worth asking.

None requires the person asking it to say what they believe should happen next.

If the proposal dies, they did not kill it. They raised something important.

If the same idea later succeeds somewhere else, they were never opposed. They were only being thorough.

I had spent six weeks researching, testing, writing, revising and attaching my judgment to a recommendation.

Someone else could stop the decision with a sentence formed while I was presenting it.

Proposing was expensive. Blocking cost one reasonable question.

That difference did most of the work.

Nobody had to arrive intending to kill the proposal. The room only needed to treat every unanswered possibility as a reason not to decide.

There is always another possibility.

They probably were helping

This is the part that makes the whole thing difficult to challenge.

Most of the questions were sincere.

Someone liked the proposal and asked a hard question because they were interested. Another person saw a real risk. A third wanted to make the idea better before the company committed to it.

That is engagement.

It is supposedly what we want in a meeting.

The effect was still the same.

We ran out of time. The decision was deferred until everyone had a chance to think. By the time the next meeting could have happened, there was another priority, another urgent problem and a different agenda.

Nobody opposed the work.

It simply stopped being discussed until, eventually, it was no longer happening.

A meeting that ends without a decision is usually a meeting where the proposal lost.

It just takes longer for anybody to admit it.

I have done it too

Once I noticed the mechanism, I had to admit I had used it.

Not deliberately.

I had raised legitimate concerns about somebody else’s proposal in complete good faith. The concerns were real. They deserved an answer.

They were also what prevented the room from deciding.

I walked out believing I had contributed to a rigorous discussion.

The person who brought the proposal walked out with more work, no answer and the responsibility for returning with something so complete that nobody could think of another question.

I never had to say I opposed the idea.

I am not sure I noticed that at the time.

That was uncomfortable to realize because I had understood myself as helpful. I probably had been helpful.

I had also made blocking free.

Both could be true.

Some people get questions. Some people get postponed.

This part took me longer to see.

When an idea comes from someone the room already trusts, hard questions are part of the path to yes.

People challenge assumptions, raise risks and identify problems. The proposal still leaves with approval because the questions are treated as things to resolve while the work moves forward.

When the idea comes from someone the room has not entirely settled on, the same questions become reasons to wait.

Same words.

Different outcome.

Some people enter the meeting with the room already believing the idea probably works. Everyone else is expected to prove there is no possible way it could fail.

I spent years trying to answer my way out of that difference.

I became very good at anticipating objections. I brought data, edge cases, tradeoffs and answers to questions nobody had asked yet. I could handle forty minutes of scrutiny without becoming defensive or losing the thread.

Then the meeting would end without a decision.

I would walk out pleased with how well I had handled the conversation and realize later that I had achieved nothing.

Forty minutes of excellent answers with nothing decided is still a loss.

I had not been out-argued.

Nobody had argued.

I had been deferred, and the questions were how the deferral happened.

The meeting followed me home

The idea that died was not the largest cost.

The ideas after it were.

Once enough proposals ended this way, I began running the meeting before it existed.

I could hear the questions while I was still building the work.

What about the edge case?

Have we spoken to enough people?

Is the data complete?

Did we consider the failure scenario unlikely enough that nobody else would have been required to plan around it?

Some of this made the work better.

Some of it killed the work before anyone else saw it.

I told myself I was being selective. Choosing my battles. Focusing on the ideas most likely to succeed.

Sometimes that was true.

Sometimes the room had started attending meetings in my head.

At some point, I began pre-killing my own work using other people’s voices, alone in my kitchen on a Sunday.

I had been doing it for a while before I noticed.

The things I stopped bringing were never rejected. Nobody evaluated them, questioned them or decided they were not worth doing.

They never left the house.

The things I stopped bringing were never rejected. They simply never left the house.

There is no record of that kind of loss.

It never appears in a project list, decision log or annual review. Nobody can measure the ideas that disappeared because the person who had them became too good at anticipating the room.

I have no idea what was in there.

That still bothers me.

I stopped trying to win the questions

Eventually, I changed what I brought into the meeting.

Not the work.

The ask.

I stopped presenting an idea and hoping the room would discover a decision somewhere inside the discussion. I brought a recommendation and said what needed to be decided before we left.

When someone raised a concern, I answered it.

Then I asked whether the concern was actually a blocker.

If we could validate it in two weeks, it was a two-week check. If specific evidence was required, we named the evidence, the person responsible and the date when the decision would return.

If someone believed the proposal should not move forward, that was allowed too.

They simply had to say it.

The answer could be yes, no or not yet under clearly defined conditions.

It could not remain thoughtful silence pretending to be progress.

This did not guarantee approval.

It did make the room more honest about what it was doing.

I learned to finish my own questions

The change followed me to the other side of the table.

When I raise a concern about somebody else’s proposal now, I try to finish the sentence.

What would resolve it?

Do I believe the work should stop until it is resolved?

Would I proceed anyway?

The question may be valid. That does not exempt me from having a position.

If I think the risk is significant enough to block the work, I should be willing to say so and own the delay.

If I think the risk can be handled while the work continues, I should say that too.

Otherwise, I have handed the proposer another assignment without giving the room anything useful to decide.

A question with a position attached is a contribution. A question without one may be a delay wearing good manners.

I still get this wrong.

Sometimes I ask the clever question and realize later I never said what I thought should happen. Sometimes the concern is real and I need more time before I know.

That is fine.

The point is not that every question requires certainty.

The point is that uncertainty should not automatically become somebody else’s burden.

The meeting was good

That is the frustrating part.

It was a good meeting.

The questions were thoughtful. The discussion was respectful. I answered well. Nobody behaved badly.

The work still died.

That meeting taught me something I would have preferred not to learn: a room does not have to reject an idea to make sure it never happens.

It can admire the preparation.

Praise the thinking.

Ask excellent questions.

Then leave without deciding anything.

Nobody said no.

Great questions, everyone.