How Research-Based Reading Strengthens Connection and Develops Collaborative Intelligence 

A Story About Discovering the Invisible Signals That Either Build or Break Workplace Connection

How Research-Based Reading Strengthens Connection and Develops Collaborative Intelligence 
A Story About Discovering the Invisible Signals That Either Build or Break Workplace Connection. A woman sitting in a car reading The Culture Code by Daniel Coyle

Discovering how research-based reading strengthens connection and develops collaborative intelligence is rarely what leaders expect — but for many, it becomes the insight that changes everything about how they understand the people they work with.

Phoebe had been head of digital transformation for several years. 

Projects delivered on time. 

Expectations communicated clearly. 

Performance reviews that used words like efficient and dependable. 

And yet — something wasn’t working. 

The same problems kept surfacing. 

Team meetings dissolved into awkward silence. 

Cross-departmental collaboration felt transactional rather than generative. 

The innovation she’d been hired to foster wasn’t materialising — despite her having removed every procedural barrier she could identify. 

Phoebe was delivering results well. But she was beginning to suspect she wasn’t always creating the conditions that made meaningful results possible.

The Morning She Sat in Her Car

The shift began on an ordinary morning. 

Phoebe sat in her car in the office car park, twenty minutes early as always — but this time she wasn’t reviewing presentation notes or checking emails. 

She was finishing the final chapter of The Culture Code by Daniel Coyle. 

She’d picked it up three weeks earlier after yet another team meeting had dissolved into awkward silence. 

That morning she closed the book and sat with something unexpected. 

What struck her wasn’t just the research on high-performing teams. 

It was Coyle’s analysis of belonging cues, vulnerability loops, and purpose narratives. 

For the first time, Phoebe understood that the silence in her team meetings wasn’t about lack of ideas. 

It was about lack of psychological safety. 

Something her efficiency-focused approach had inadvertently undermined. 

She had been optimising for task completion whilst neglecting the relational foundations that made meaningful collaboration possible.

The First Experiment

That morning’s team stand-up became Phoebe’s first deliberate experiment with what she’d read. 

Instead of diving straight into project updates, she opened with a question. 

“What’s one thing I do that makes it harder for you to share ideas or concerns?” 

The silence that followed felt interminable. 

Then Raj, one of her senior developers, spoke carefully. “Sometimes when we raise potential issues with a project approach, it feels like you’ve already decided the path forward. We’re not sure if you want our input or just our compliance.” 

Phoebe’s first instinct was defensive. 

But she caught herself. 

“That’s really helpful, Raj. Can you give me a specific example so I can understand better?” 

What followed was a conversation unlike any her team had experienced. 

People began sharing — tentatively at first, then with increasing candour. 

Her habit of immediately problem-solving made them feel unheard. 

Her focus on deadlines over process left them feeling like interchangeable resources rather than valued collaborators. 

It was uncomfortable. It was also the beginning of something different.

What Phoebe Realised Afterwards

The more Phoebe thought about The Culture Code, the more clearly she saw what the research had shown her. 

Coyle’s analysis of belonging cues gave her a framework for understanding why small moments mattered so much. 

When a new team member proposed an idea and Phoebe immediately pointed out its limitations, she wasn’t just critiquing the idea. 

She was sending a signal about whether that person’s contributions were valued. 

When she held planning meetings without the developers who would implement the plans, she wasn’t just being efficient. 

She was communicating who did and didn’t belong to the core decision-making group. 

Phoebe began recognising the same patterns everywhere. 

People weren’t withholding ideas because they lacked them. 

They were withholding them because the signals they were receiving said it wasn’t safe to share.

What Happened Next

A few weeks later Phoebe faced a different challenge that revealed another dimension of what she’d read. 

The broader technology leadership group — eight directors across different functions — had devolved into a dysfunctional pattern. 

Performative meetings. 

Polished updates. 

Private competition for resources and recognition. 

Phoebe had always participated in this dynamic, viewing it as inevitable organisational politics. 

But she recognised it now as something else. 

Status management overtaking genuine collaboration. 

At the next leadership meeting, when her turn came to present, she deviated from the standard format.

 “I’m going to try something different today. Rather than giving you a polished update, I want to share where I’m genuinely struggling and see if anyone has insights.” 

The room went quiet. Then Martin — the infrastructure director who typically used these meetings to showcase his accomplishments — spoke up. 

“We’re dealing with something similar. I’ve been reluctant to talk about it because it feels like admitting we built things wrong initially, but the reality is we’re at a crossroads.” 

Phoebe had initiated what Coyle called a vulnerability loop. By taking the social risk of admitting struggle, she’d created permission for others to drop their defensive posturing.

The Shift

One insight changed how Phoebe approached leadership. 

From

 Optimising for task completion 

To 

Creating the conditions that made meaningful collaboration possible 

Instead of asking: 

“What’s the most efficient way to structure this?” 

She started asking: “What signals am I sending — and what are they communicating to the people around me?” 

And the conversations changed almost immediately.

When the Culture Pushed Back

Once Phoebe began working this way, she encountered something she hadn’t anticipated. 

One vulnerability loop wasn’t enough.

 She came to the next leadership meeting expecting something different. 

What she got was almost identical to what had come before. 

The culture had simply absorbed it and returned to its previous shape. 

She went back to The Culture Code that evening, looking for what she’d missed.

She found it in a passage she’d previously highlighted without fully understanding: Coyle’s observation that culture isn’t created through single interventions — it forms through thousands of small signals sent consistently over time. 

One honest moment didn’t rewire months of accumulated distance. 

It planted something. 

But planting wasn’t the same as growing.

That distinction changed what she did next.

She started small, and she started the next morning. 

When a team member raised a problem she didn’t know how to solve, she said so. 

When a cross-departmental meeting stalled, she named the stall. 

When she opened her weekly check-in with the leadership group, she brought a genuine question rather than a resolved update. 

None of it was dramatic. 

That, she was beginning to understand, was precisely the point. 

And when she finally applied the same practice upward — to her own manager — she discovered the risk ran in every direction. 

And that she’d been willing to take it everywhere except the place it most frightened her.

The Teaching Insight

Phoebe discovered that leadership wasn’t about creating the right structures. 

It was about sending the right signals — consistently, in every direction. 

When she stopped asking “How do I make this more efficient?” 

And started asking “What does this moment communicate to the people around me?” Two things changed. 

Her team stopped complying and started collaborating.

 And the people she worked with finally felt safe enough to bring their best thinking.

Why This Matters

Professional training often focuses on processes, strategy, and decision-making. 

But leadership also requires something harder to teach. 

The ability to create the conditions where people feel safe enough to contribute, challenge, and connect. 

When we read research-based non-fiction, we gain access to something that experience alone rarely provides: the specific mechanisms by which trust either forms or erodes. 

Phoebe’s story shows what happens when those mechanisms move from the page into practice. 

And that practice keeps revealing new things the longer you stay with it.

This is an extract from How Research-Based Reading Strengthens Connection and Develops Collaborative Intelligence — a School of WorkLife Story Lesson.

The complete lesson follows Phoebe’s full journey — including how insights from The Culture Code changed how she approached her team, her peers, and her own manager — and what she discovered when she returned to the book several months later. It shows how you can apply the same perspective in your own work — learning to recognise the signals that either build or break psychological safety, and respond with the connection intelligence that many leadership challenges quietly require.

Experience the complete lesson: 

How Research-Based Reading Strengthens Connection and Develops Collaborative Intelligence Learn how research-based non-fiction that explores the science of high-performing teams can develop collaborative intelligence and change how you understand the people you lead.

Deepen the practice with the WorkLife Compass Guided Programme: 

The Power of Non-Fiction: Developing Connection Through Reading — Discover how research-based reading strengthens belonging, trust, and the collaborative intelligence that shapes a working life.

This story was inspired by my book, WorkLife Book Club Volume One Shoreditch by Carmel O’ Reilly — following members of a London book club as they navigate WorkLife challenges through the wisdom found in the books they read together.

Work With Me: Individual WorkLife Coaching, Commissioned Learning Resources, Speaking Engagements and Organisational Partnerships.

Support This Work: Your support makes a difference and helps me to continue creating resources that are accessible to everyone. Thank you. Carmel

Listen to the audio version here: 

Share These Learning Resources:

These resources are designed as short, effective learning experiences—for individuals managing their own development and companies supporting their people’s growth.

If you think this learning resource story would be helpful to others, share it forward.


Discover more from schoolofworklife.com

Subscribe to get the latest posts sent to your email.

Published by Carmel O' Reilly

I'm Carmel O'Reilly, founder of School of WorkLife. I use story-based learning — characters in real WorkLife scenarios — to help people develop their working lives, through Story Lessons, Guided Programmes, and Professional Self-Coaching resources, and the WorkLife Stories podcast. Irish, London-based, and endlessly drawn to a good story.