Thinking With People, Not At Them

We've built an industry of tools for transmitting ideas to each other. Almost none of it helps us think together — which is where the actual value is.

We have built an enormous apparatus around communication: messaging platforms, slide decks, collaboration software, coaching frameworks, presentation training. Nearly all of it is designed to help one person transmit an idea to another more efficiently.

Almost none of it helps two people think together.

That distinction — thinking at people versus thinking with them — is easy to miss and expensive to get wrong. It's the difference between a room that produces better ideas than any single person brought into it, and a room where the most senior person's idea is received, lightly questioned, and adopted.

What thinking at looks like

When we think at people, we present, persuade, and perform. We arrive with a conclusion and a narrative built to move it forward, and the other person's role is to receive it — to affirm it, or question it at the margins, but rarely to help build it.

It's everywhere. In leadership development that hands out frameworks instead of developing original judgment. In meetings where people are asked to respond to conclusions rather than help shape them. In coaching and clinical work that reduces a particular human being to a standard sequence of steps. These aren't conversations. They're broadcasts with a feedback channel.

And it's the default for an understandable reason: thinking at people is efficient, and every system we operate inside rewards efficiency, speed, and standardization. Thinking with someone is none of those things. It's slower, it's live, and it means giving up control of where the conversation ends up.

Why "more debate" isn't the fix

The obvious correction is to invite more disagreement — more friction, more challenge, on the theory that conflict sharpens ideas. The evidence doesn't support that as stated, and it's worth knowing why.

The largest meta-analysis on the question found that conflict in teams — including task conflict, the disagreement-about-the-work kind usually assumed to be productive — was on average negatively related to performance and satisfaction, not positively (De Dreu & Weingart, 2003). Friction by itself doesn't reliably improve anything. Often it degrades it.

So the problem with thinking at people isn't a shortage of disagreement, and the solution isn't manufacturing more of it. The variable that determines whether disagreement helps or harms is how it happens — whether people are, underneath the disagreement, thinking with each other or at each other. The same challenging comment can sharpen a decision or blow up a room depending entirely on that.

What thinking with actually requires

Two conditions turn disagreement from a threat into a resource, and both are well established.

The first is psychological safety — the shared sense that the room is safe for interpersonal risk, so people will surface a doubt or a half-formed objection instead of holding it (Edmondson, 1999). Without it, the useful disagreement never gets voiced; people default to receiving. With it, the friction that would otherwise stay silent or turn personal becomes available as material.

The second is subtler and more demanding: the capacity to hold in mind that the other person has a mind of their own — separate, differently informed, working from premises you can't see. Psychologists call this mentalizing, and Peter Fonagy, who developed the concept, describes reflective functioning as the uniquely human capacity to make sense of one another (Fonagy et al., 2002). Thinking with someone requires it continuously: you're not just tracking your own argument, you're tracking theirs — what they're seeing that you aren't, why a reasonable person would land where they've landed.

This is the capacity that most communication tools bypass entirely. A slide deck doesn't mentalize. A framework doesn't. They move content in one direction. Thinking with someone is the opposite motion — staying in the other person's frame long enough to be changed by it.

Why it's worth the cost

Thinking with people is slower, less controllable, and more demanding of the person leading it. It asks for patience, a tolerance for not knowing where you'll end up, and enough security to let someone else's read reshape your own.

What it returns is the thing every organization claims to want and few actually produce: decisions that have been stress-tested through more than one mind before they're committed to. A conclusion you reached alone has been checked against exactly one set of blind spots — yours. A conclusion genuinely thought through with others has survived contact with the things you couldn't see. That's not a softer way to work. It's a more rigorous one.

In practice

The shift from at to with is mostly a shift in what the person holding the room is trying to do.

Invite the thinking before you anchor the conclusion. Once you've stated where you've landed, you've changed the task from building to reacting. Put the real question in front of people before you put your answer on it.

Track how people see it, not just whether they comply. The useful information in a disagreement is the model underneath it — what the other person is seeing that leads them somewhere different. Getting to that requires asking, and then staying in their frame long enough to actually follow it.

Make it safe to bring the half-formed objection. The doubt someone won't voice is the one you most needed to hear. That depends less on inviting input and more on how the last person who raised something inconvenient was treated.

Value the insight over the performance. A room optimized for looking sharp will produce polish. A room optimized for thinking together will produce better decisions, and they rarely look as tidy on the way there.

The reframe

We keep trying to solve collaboration with better tools for transmission — clearer decks, tighter frameworks, faster platforms. But the thing we say we want from working together, better and more resilient thinking, doesn't come from transmitting ideas more efficiently. It comes from actually thinking with other people: holding their mind alongside our own, making it safe for them to bring what they really see, and letting it change where we land.

Until we build for that, we'll keep thinking at each other — clearly, efficiently, and alone.

References

De Dreu, C. K. W., & Weingart, L. R. (2003). Task versus relationship conflict, team performance, and team member satisfaction: A meta-analysis. Journal of Applied Psychology, 88(4), 741–749.

Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.

Fonagy, P., Gergely, G., Jurist, E. L., & Target, M. (2002). Affect regulation, mentalization, and the development of the self. Other Press.