Collaboration is often positioned as a capability. Something teams need to do more of. Something leaders need to encourage. 

But in my experience, collaboration doesn’t fail because people don’t want to work together. 

It fails because they don’t feel safe enough to think out loud and that’s a very different problem to solve. 

The silence we don’t talk about

If you’ve ever sat in a meeting where: 

  • everyone nods, but no one challenges  
  • decisions are made quickly, but feel incomplete  
  • concerns surface after the meeting, not during  

You’ve already seen the gap. 

On the surface, it looks like alignment.
Underneath, it’s silence. 

Not because people don’t have ideas but because they’re holding them back. 

Thinking out loud requires a level of vulnerability that many environments don’t actively support. 

It means sharing: 

  • an idea that’s not fully formed  
  • a concern that might be unpopular  
  • a perspective that challenges the group  

When the perceived risk of speaking up is higher than the value of contributing, people stay quiet. 

Collaboration is not about participation

We often measure collaboration by participation: 

  • Who spoke?  
  • Who contributed?  
  • Who attended?  

But participation is an outcome. 

The real question is: Did people feel safe enough to contribute before they even opened their mouth? 

Because without that sense of permission: 

  • people self-filter  
  • they wait for certainty  
  • they defer to hierarchy  
  • they protect themselves instead of the outcome  

What you end up with is not collaboration, it’s compliance. 

The impact on decision-making and accountability

This is where the ripple effect becomes clear. 

When people don’t think out loud: 

  • decisions are made with incomplete information  
  • risks remain hidden  
  • alternative options are never explored  

Which means decision-making quality drops and when decisions are made without full visibility, accountability becomes blurred: 

  • “I didn’t know that was a risk.”  
  • “I assumed someone else had considered it.”  
  • “We agreed in the meeting…”  

But did you really agree?
Or did no one feel safe enough to disagree? 

This is where your ecosystem comes together. 

Collaboration enables shared thinking.
Decision-making reflects the quality of that thinking.
Accountability depends on both. 

When safety is missing at the collaboration layer, everything downstream is impacted. 

What psychological safety looks like

Psychological safety is often misunderstood as being “nice” or avoiding conflict. 

It’s not. 

It’s about creating an environment where people can: 

  • challenge ideas  
  • raise concerns  
  • admit uncertainty  
  • offer perspectives  

without fear of judgement, embarrassment, or negative consequences. 

As Amy Edmondson defines it, it’s the belief that you won’t be punished or humiliated for speaking up. 

That belief changes behaviour. 

Teams with high psychological safety: 

  • share ideas earlier  
  • challenge thinking constructively  
  • surface risks before they escalate  

Which leads to better decisions and stronger outcomes. 

Designing for thinking out loud

If collaboration is struggling in a team, the answer isn’t simply “encourage more input.” 

It’s to design environments were thinking out loud feels safe. 

That starts with how leaders show up. 

  1. Shift the purpose of conversations

Move from reporting to exploration. 

Instead of: “Any updates?”  

Ask: 

  • “What are we still working through?”  
  • “What doesn’t feel right yet?”  

This signals that incomplete thinking is welcome. 

  1. Model vulnerability

People take their cues from the leader. 

If the leader always presents certainty, others will do the same. 

But when a leader says: 

  • “I’m not sure yet…”  
  • “Here’s where I’d value your thinking…”  

it creates permission for others to contribute. 

  1. Create space, not pressure

Inviting input is not the same as putting people on the spot. 

Instead of: “John, what do you think?”  

Try: “Let’s pause, what perspectives haven’t we heard yet?”  

This opens the conversation without singling people out. 

  1. Respond in a way that reinforces safety

What happens after someone speaks matters just as much as whether they spoke. 

If ideas are dismissed, ignored, or criticised harshly, safety disappears quickly. 

But when contributions are: 

  • acknowledged  
  • explored  
  • built upon  

people learn that their voice matters. 

The real test of collaboration

The real test of collaboration is not how well a team works when things are clear. 

It’s how they show up when things are uncertain. 

When: 

  • the path isn’t fully defined  
  • the risks aren’t fully known  
  • the answers aren’t obvious  

That’s when thinking out loud matters most and that’s when safety becomes the differentiator. 

Think about your last few team conversations. 

  • Who spoke easily?  
  • Who stayed quiet?  
  • What might have been left unsaid?  

The most important question: What would need to change for people to feel safe enough to think out loud? 

Because collaboration doesn’t start with tools or frameworks, it starts with safety.