Part 3 of the Asking Questions Series: The Hidden Dynamic That Shapes Every Collaboration
There is a dynamic in collaborative work that most leaders feel but rarely name.
You are in a brainstorm or a design review or a planning session. Someone puts an idea on the table. The next few minutes determine whether that idea gets developed into something useful, or gets picked apart before it ever had a chance. And it is almost never the idea itself that determines the outcome. It is the questions that follow it.
Some questions build. Some questions tear down. Both have a place. But most people never consciously choose which one they are using, and that unconscious choice shapes the quality of every collaboration they are part of.
What Build-Up Questions Do
A build-up question accepts the premise of what has been offered and extends it. It says, implicitly: I am treating this as real, and I want to see where it goes.
Build-up questions sound like:
- "If we did this, what would it unlock for us that we don't have now?"
- "How would a customer describe this if it worked exactly the way you are imagining?"
- "What is the version of this that would make us proud in two years?"
- "Who is the specific person this would help most, and what does their day look like?"
- "What would we need to believe for this to be a great idea?"
Notice what these questions have in common: they push the idea forward. They invite the person who raised the idea to develop their thinking further rather than defend it. They create more material to work with.
This matters more than most leaders realize. Ideas in early stages are fragile. They are often half-formed, messily expressed, and built on intuitions the person holding them has not fully articulated yet. A build-up question gives those intuitions room to become something. A tear-down question, applied too early, kills them before you know what they were.
What Tear-Down Questions Do
A tear-down question challenges the premise. It introduces friction, tests the idea's logic, looks for the places where it might fail.
Tear-down questions sound like:
- "What is the evidence that customers actually want this?"
- "How is this different from what we already tried in 2022?"
- "Who is going to build it, and where does this fit in the current roadmap?"
- "What is the risk if this does not work?"
- "Why would a customer switch from their current solution for this?"
These are not bad questions. They are necessary. The problem is not tear-down questions. It is tear-down questions applied at the wrong moment, in the wrong proportion, by the wrong person in the room.
When tear-down questions arrive before an idea has been developed, they function as idea killers, regardless of intent. The person who raised the idea stops building and starts defending. The room contracts. Other people who were about to offer something similar decide not to. The collaboration narrows exactly when you need it to expand.
The Sequencing Problem
The most common mistake in collaborative settings is not that people ask tear-down questions. It is that they ask them too early.
Think about the typical flow of a product brainstorm. Someone proposes an idea. Within sixty seconds, someone else (often the most senior person in the room, or the most analytically minded) asks about evidence, feasibility, or precedent. The person who raised the idea shifts from building to justifying. Other ideas that were about to surface don't. The session produces one idea that got partially stress-tested rather than five ideas that could have been evaluated against each other.
The discipline is to separate the phases explicitly.
Phase 1: Build up. For a defined period (it does not have to be long, even ten or fifteen minutes), the only questions allowed are build-up questions. You are not evaluating. You are expanding. The goal is to get the idea as fully developed as possible before you stress-test it, because you can only stress-test what has been articulated.
Phase 2: Tear down. Now the critical questions are welcome. What is the evidence? What is the risk? What are we not accounting for? Does this contradict something we already know? This phase has teeth and should. But it works better when there is something to evaluate.
This sequencing is not just about protecting ideas. It is about getting better answers to your critical questions. A half-developed idea cannot absorb rigorous scrutiny well. A fully developed idea can, and the answers you get are more informative.
Reading the Room: When to Use Which
Not every situation calls for the same balance. Here is how I think about it:
Use build-up questions when:
- The idea is new or early-stage
- You are in a brainstorm, ideation, or discovery phase
- The person sharing is junior, newer to the team, or showing early signs of hesitation
- The previous few minutes have been critical and the energy in the room has contracted
- You don't yet fully understand what is being proposed
Use tear-down questions when:
- An idea is mature and has already been built up enough to evaluate
- You are in a review, a decision gate, or a planning session where critical evaluation is the explicit purpose
- You are protecting the team from a bad investment of time or resources
- The group consensus is moving too fast toward something untested
- You are the one responsible for quality control on the output
There is also a third category worth naming: questions that appear to tear down but are building up. These are the most sophisticated: the "yes, and" of the questioning world.
"What is the version of this that would survive the harshest scrutiny?" looks like a critical question. But it is inviting the person to build a more robust version of their idea rather than defending the current one. Same with: "What would make this ten times more valuable than it currently is?" or "What is the objection you would most want to pre-empt?" These questions apply productive pressure without collapsing the exploration.
The Power Dynamic Nobody Talks About
Here is something that does not get said enough: in most rooms, the senior person's questions are heard as directives.
If you are the most senior product person in a brainstorm and you ask a tear-down question, the room does not hear "here is a thing to think about." It hears "the director does not think this is viable." The idea's momentum, and often the idea itself, is over.
This means senior leaders carry asymmetric responsibility for the questions they ask and when they ask them. Your build-up questions have outsized power to draw out the room. Your tear-down questions have outsized power to shut it down. Neither of those is inherently bad, but you should be choosing consciously.
The practical implication: in collaborative sessions, consider holding your tear-down questions until others have had a chance to build. You can always ask them later. The damage of asking them too early is often irreversible.
The Question That Bridges Both
There is one question I have found that does both things: it builds up an idea while surfacing the thinking you would need to tear it down fairly.
It is this: "What would have to be true for this to work?"
This question accepts the idea as a premise (build-up) and immediately asks for the underlying assumptions (tear-down setup). It is not adversarial; it does not say "prove it." It is collaborative; it says "let us figure out what we would need to believe together."
The answer to this question is enormously useful. It surfaces the assumptions the idea depends on. Some of those assumptions you will believe immediately. Some you will want to test. Some you will know are false. And now you are having a productive, grounded conversation about the idea's viability, not a debate about whether the person who raised it is smart enough to be taken seriously.
What This Looks Like in Practice
A few patterns I have developed:
Before I ask a critical question, I ask: have I built this up enough? If I don't fully understand the idea yet, my critical question is probably premature. I build first. The tear-down gets better when I understand what I am tearing down.
I name the mode I am in. In collaborative sessions, I will sometimes say out loud: "I want to build on this for a few minutes before we ask hard questions. Is everyone okay with that?" Naming it gives the room permission to do the same. It also signals to the person whose idea it is that critique is coming, which is kinder than blindsiding them.
I watch the energy, not the clock. The right time to shift from build-up to tear-down is not after a fixed number of minutes. It is when the idea has been developed enough to evaluate. You can usually feel when that is: when the conversation starts circling rather than building, or when people start reaching for critical questions naturally.
I pay attention to who has not spoken. In most group sessions, the people who have not spoken yet have build-up in them. They are waiting for a build-up question that makes it safe to contribute. A well-timed "what does this make you think of?" or "how does this connect to something you have seen before?" can unlock the person who has been quiet.
The Bottom Line
Every question you ask in a collaboration is doing one of two things: expanding the space or contracting it. Build-up questions expand. Tear-down questions contract. Both are necessary. Neither is sufficient on its own.
The skill is knowing which one to reach for at which moment, and having the discipline to sequence them in the order that produces the best work, rather than the order that feels most natural to a critical mind.
The best collaborative environments I have been part of have this in common: people build generously before they critique rigorously. Ideas get room to develop before they get tested. And when critical questions arrive, they land on something substantial enough to be worth the scrutiny.
This does not happen by accident. It happens because someone in the room is choosing their questions consciously.
The Full Series
- Part 1: The Art of Asking Questions. Why most questions miss, the mindset shift, the anatomy of a good question
- Part 2: Questions in the Field. What to ask in discovery, stakeholder conversations, strategy sessions, and 1:1s
- Part 3: Build-Up vs. Tear-Down Questions (you are here)