Accept First, Evaluate Second: Keeping Other People’s Ideas Alive

Acceptance is not approval

This distinction is central in improvisation and equally valuable at work. To accept an offer is to recognise that it has entered the shared conversation. You understand it well enough to respond to the idea that was actually proposed—not to a weaker version of it or to the idea you expected to hear.

Approval comes later. A team can accept that a proposal contains a useful customer need, testable assumption or fresh route and still decide not to implement it. Critical thinking is not removed; it is sequenced more deliberately.

My technology background makes this important to me. Constraints in billing, finance, architecture and operations are real. Applied improvisation should not pretend otherwise. The practice is to let expertise shape an idea before expertise closes it.

You can take an idea seriously without deciding to take it forward.

What blocking sounds like in professional rooms

Blocking is not always a blunt ‘no’. It often arrives as competent, reasonable language. The phrase itself may be true; the pattern becomes unhelpful when it ends exploration before the group understands the value inside the offer.

• ‘We already tried that.’ What was different then, and which part might still be useful now?
• ‘That will not work with our architecture.’ Which outcome is the idea trying to create, and what route could the architecture support?
• ‘We need more data.’ What is the smallest safe test that would produce the data we actually need?
• ‘That is outside scope.’ Is there a useful dependency or future option that should at least be captured?

Separate the opening phase from the judging phase

Teams often try to generate and evaluate at the same time. Every emerging idea is immediately required to prove feasibility, affordability and organisational support. Predictable ideas survive because they already resemble what the system knows how to deliver.

A better rhythm is short and explicit. First, clarify and build: what is the idea, what need does it serve and what becomes possible if it works? Then evaluate: which constraints matter, what evidence is missing and what decision is appropriate?

The separation can be only ten minutes. What matters is that people know which mode the group is in, so a necessary risk question does not accidentally become an early veto.

Accept the intention when the route is impossible

Sometimes the proposal itself genuinely cannot work. The most useful part may be the intention underneath it: faster feedback, less manual work, clearer ownership or a better customer experience.

Instead of ending with the constraint, name the intention you are preserving and invite another route. This respects both the contribution and the reality of the system. It is also a practical form of ‘Yes, And’ that does not require anybody to use theatrical language in a business meeting.

Two ways to extend the practice

After the main exercise, these variations help the group apply the distinction in more realistic conditions:

• Value before risk: before naming a concern, each person must identify one useful element or underlying need in the proposal.
• Keep the intention, change the route: give the group a hard constraint and ask them to preserve the proposal’s purpose while redesigning how it could be achieved.