The most expensive problems on projects rarely announce themselves. They don't show up in a shared document or get flagged in a status update. They show up in a working session where the right people aren't in the room, in a stakeholder interview where the real answer never surfaces, in a recommendation built on insights that are shallower than they should be — not because the client lacks the answers, but because the conditions weren't designed to draw them out.
This is the gap some teams don't talk about because it doesn't look like one. It looks like folks waiting for permission to collaborate, an off-camera meeting, a stakeholder who seems checked out. It looks like normal project friction. But underneath that friction is something structural: the environment wasn't built to get the best out of the people in it.
Conversations require design decisions
Every project has an official process with kickoffs, research sessions, working sessions, and readouts. What gets less attention is the design of the conversations themselves: who's in the room, how the session is structured, what kind of thinking it demands, and what it costs the people being asked to show up fully. These feel like logistics. They're not. They're the mechanism by which real insight surfaces.
When the conditions are right, something different happens in a working session. The quiet stakeholder finally speaks up, the executive collaborates without hierarchy and draws on everyone's expertise, and the person who always sends their thoughts after the meeting jumps in with everyone else. The conversation goes somewhere it wouldn't have gone otherwise, and you come out of it knowing something you couldn't have learned any other way.
When those conditions aren't right, you still get output. People answer the questions. But the insight is surface-level, and everything built on top of it, the analysis, the recommendations, the strategy, is weaker for it. What gets lost is rarely visible until it's too late to go back for it.
Assuming positive intent is a design choice
Early in an engagement, we were working with an extended project team that included a senior client stakeholder. Her calendar had focus time blocked every morning. People scheduled over it anyway. When that time disappeared, her presence in the work shifted. She was harder to reach, less engaged in sessions, and less generative in collaboration. On the surface, it read as disengagement.
The easy interpretation would have been to work around her, reduce her involvement, treat her availability as a constraint to manage. Instead, we protected the time. No explanation required, no questions asked. Something in her calendar mattered enough to block, and that was enough to act on.
Because we had built real trust in the relationship, she eventually shared more. She was going through a divorce. That morning time was time with her kid. But here's the thing: we didn't need to know any of that. The adjustment came first. The context came later.
That's the point. You don't need the full picture to treat someone like a whole person. You just need to assume there's a valid reason and design accordingly. When you get that right, people notice. And sometimes, when the trust is there, they tell you why.
The recommendations we built were better because she was in them fully, not partially.
Where insight actually comes from
Strong recommendations come from strong insight, and strong insight comes from how you design the conditions to surface it. Most project processes skip that link, which is why so much work is technically right, but not nearly as deep or nuanced as it could be.
The format of a conversation is a design decision, and it's one that most project teams make by default rather than intention. When the conditions are right, something different surfaces. When they're not, you still get output, and you might just miss the "so what."
What to design for
None of this happens without psychological safety, and not just the absence of threat. Psychological safety means the whole person is considered: their working style, their context, what they're carrying into the room that has nothing to do with the project. When people feel that, they share more, push back more honestly, and give you the kind of insight that actually moves the work forward. The conditions that create it are more specific than most teams realize.
People. Who is and who isn't in the room shapes everything. Beyond the right roles, consider what each person needs to show up fully, not just professionally, but as a whole person.
Time. When a conversation happens matters as much as what happens in it. The best session at the wrong time, for the wrong people, will still underdeliver.
Place. Smaller, remote conversations can create unexpected intimacy, and people share things on a call they might not say in a conference room. And some sessions just have better outcomes when everyone is physically in the same room. Knowing which is which, and planning for it, is part of the design.
Conversation type. Administrative, light and heavy collaboration, knowledge transfer, deep thought work, each one asks something different of the people in it and surfaces a different kind of insight. Matching the type to the purpose is a design decision, not a default.
Anchor. People engage more honestly when they have something to respond to. An artifact, a provocation, a framework, something in the room that moves the conversation from abstract to specific.
How people participate. Structure participation with psychological safety in mind. Who tends to go quiet? Who dominates? Designing for those dynamics before the session starts is what separates a facilitated conversation from a managed one.
That depth is what allows us to build recommendations that hold up, ones that account for what's stated and what isn't, for the dynamics that don't show up in a brief but determine whether a strategy actually gets implemented. Clients feel the difference in the output. Their customers feel it in the experience.
Designing the conversation and intentionally shaping the room, continuously and with the whole person in mind, is where the best project outcomes begin.
