Co-Intelligence: Why Learning Together Beats Knowing Together

Here is a question worth sitting with for a moment.

Your organization has spent years hiring smart people, building knowledge repositories, documenting processes, and training staff. You have accumulated a lot. So why does it feel like the moment something genuinely new shows up, the whole machine slows down?

Diana Larsen has an answer. And it is not a comfortable one.

The problem is not that your people don't know enough. The problem is that knowing and learning are two different things. And most organizations have spent decades optimizing for the wrong one.

That's what this episode is about.

Diana has been in this world longer than most. Over thirty years working at the intersection of teams, learning, and leadership. She came to Agile before there was an Agile Manifesto, through a discipline called socio-technical systems design, which is a fancy way of saying she was already thinking about how people collaborate to get hard things done. She co-authored Agile Retrospectives, one of the most dog-eared books in the field. She co-wrote Liftoff, which is still the go-to guide for getting teams started well. Her most recent book, Lead Without Blame, written with Tricia Broderick, tackles the culture problem that sits underneath almost every team failure.

She also co-originated the Agile Fluency® Model, which is worth knowing about if you have ever felt like the Agile frameworks your organization adopted were designed for someone else's problems.

She is sharp, candid, and genuinely funny. This was a good conversation.

The Knowledge Work Trap

Peter Drucker gave us the term "knowledge worker." It was a useful frame. Lawyers, accountants, analysts: people whose value comes from what they know and how they apply it. That model worked for a long time.

It is not enough anymore.

Diana makes a distinction that I have not been able to stop thinking about since our prep call. Knowledge work is about applying what you already know. Learning work is about noticing when the world has shifted and figuring out what that means before your competitors do. Barry O'Reilly wrote a whole book about this called Unlearn, and the core idea is the same: the knowledge that got you here may be the thing slowing you down now.

AI is accelerating this problem. The things AI does well, retrieval, synthesis, pattern matching across large datasets, those are the core skills of knowledge work. So if your people are mostly doing knowledge work, you have a real problem on your hands. Not someday. Now.

Learning Together Is Harder Than It Sounds

Learning as an individual is one thing. You can figure out your own gaps, seek out new information, adjust your approach. Most reasonably self-aware professionals can do that.

Learning as a team is a completely different skill set. Diana calls it co-intelligence, and it is one of the central ideas in Lead Without Blame. It is the shared body of understanding that a team builds together through working, failing, reflecting, and adjusting. You cannot build it by aggregating individual expertise. You cannot buy it. You have to grow it deliberately.

Most organizations have no idea how to do this. They run retrospectives that produce action items nobody follows through on. They hold all-hands meetings that feel more like announcements than conversations. They promote their best individual performers into leadership and then wonder why the team dynamic shifts.

Why Blame Is the Real Enemy

You cannot build a learning culture inside a blame culture. Full stop.

When people are protecting themselves from consequences, they are not taking risks. When they are not taking risks, they are not learning anything new. When they are not learning anything new, the organization stagnates while the market keeps moving.

Diana and Tricia Broderick designed the Lead Without Blame framework around this reality. The shift they are asking for is not soft. It is moving from "I hold you accountable" to "we take responsibility together." That changes who shows up to work and how.

Valiant Leaders

Diana has a concept she calls valiant leaders, and it is worth understanding clearly. Valiant does not mean fearless or visionary or any of the other adjectives that get attached to executive leadership. It means courageous enough to try things that might not work. Caring enough about the people doing the work to create the conditions for them to succeed. Willing to get out of the way when the team knows more than you do.

That last part is where most leaders struggle. And it is exactly where the learning work has to start at the top.

The Agile Fluency Model: A Framework That Asks a Question First

Most Agile frameworks tell you what to do. The Agile Fluency® Model starts by asking what you actually need. That is a different posture entirely.

Diana co-created it with James Shore because the "one right way" conversation about Agile was not matching their experience on the ground. Different organizations need different things from their teams. A team supporting internal tooling has different requirements than a team building a continuously deployed software product. The model helps you get clear on what you actually need before you decide how to get there.

Free white paper at agilefluency.org. Worth the read.

One Thing She Changed Her Mind On

Diana spent years going to the mat for co-located teams. Teams had to be together. That was the position.

She changed her mind.

In-person time still matters. If you want a high-performing team, you should plan for it intentionally. But it is no longer the prerequisite she once believed it to be. With the right tools and practices, distributed teams can be genuinely high-performing. The fundamentals still apply. They just have to be applied more deliberately.

What's Coming Next for Diana

She is building a new program called Thrive in Turbulent Times. Small groups, a mix of in-person immersions and virtual sessions, designed for middle managers and senior leaders who are responsible for creating work environments for their teams. Because the quality of that environment determines everything that happens downstream. If you are feeling the weight of that responsibility right now, this is worth knowing about.

BOOKS AND RESOURCES MENTIONED

• Lead Without Blame: Building Resilient Learning Teams — Diana Larsen and Tricia Broderick

• Agile Retrospectives: Making Good Teams Great (2nd Edition) — Diana Larsen and Esther Derby

• Liftoff: Start and Sustain Successful Agile Teams — Diana Larsen and Ainsley Nies

• Unlearn: Let Go of Past Success to Achieve Extraordinary Results — Barry O'Reilly

• StrengthsFinder 2.0 — Tom Rath

• Agile Fluency® Model white paper (free): https://www.agilefluency.org

Website: https://www.dianalarsen.com Go to the top of her website and hit Subscribe. You can choose to receive her newsletter, workshop announcements, or both. Details about Thrive in Turbulent Times will land there first.

LinkedIn: https://www.linkedin.com/in/dianalarsenagileswd/

If this conversation sparked something for you, let's talk about what it means for your organization.

Book a call: https://tidycal.com/coachkumar/30-minute-meeting

Take the Disruptor Method assessment: https://www.thedisruptormethod.com/quiz

LinkedIn: https://www.linkedin.com/in/kumardattatreyan/

Website: https://www.agilemeridian.com

The Meridian Point goes live every Tuesday at 12:30 PM Eastern on LinkedIn, YouTube, and Facebook. If you are not subscribed yet, now is a good time.

The Meridian Point Podcast | Agile Meridian