Welcome to February's edition of Plumtree Perspectives, and whether you're new here or returning, thank you for being part of the Plumtree community!
Each month we share new ideas, practical tools, and simple frameworks focused on how R&D teams can collaborate more effectively, thrive in complexity, and deliver faster for patients.
In today's fast-paced and complex environment, teams that can sense what is new and changing have a real advantage. They notice what is emerging. They name what is unclear. They share what they are seeing. Then they adapt. Together.
When teams work this way, the work flows. Decisions are made closer to the work. Information is shared without boundaries. Teams adjust in real time. The path forward becomes clearer because the team can openly name what is undefined, uncertain, or unknown.
That shared awareness is not accidental. It is collective intelligence in action.
What we're noticing
Many teams struggle to work with collective intelligence to achieve shared outcomes.
We often hear language like:
"Stay in your lane."
"I don't really understand what that role does."
"That's your job, not mine."
Over time, that language becomes the team's default operating system. People show up as functional experts. They speak only to the work they believe they own. Ideas are shared narrowly. Thinking rarely builds across roles.
The team is doing the work, but it is not truly thinking together.
The insight
When teams teams operate this way, the work gets harder. Interdependencies are missed. Small gaps turn into big problems. Opportunities go unnoticed.
Then come the symptoms. Rework. Delays. Fragmented execution. Hard functional boundaries.
Frustration grows on all sides. Team members feel stuck. Leaders feel like they have to step in too often. The cost is not just efficiency. It is lost learning, slower decisions, and a team that never fully uses its collective capability.
The Plumtree Perspective
Teams move faster when they identify the outcomes they own collectively and organize around those outcomes. Problems surface earlier. Questions get sharper. Solutions are more creative.
Clarity comes faster because conversations are anchored to the outcome and what is getting in the way. There is no function on the hot seat. Everyone feels the responsibility. Everyone is actively engaged.
We recently saw this with a team facing a data review challenge ahead of a critical readout. They noticed the issue early. They mobilized a small, empowered, cross-functional group. They clarified roles and decision authority quickly.
Then they got to work. The result. The final readout was delivered weeks ahead of plan.
They were solving problems in the moment, not waiting for management direction. That is collective ownership at work.
What you can try
Two simple practices can help teams build this muscle.
First. Run a retrospective on a recent collective outcome or deliverable.
Bring together the people who were directly involved in the outcome. Ask three questions.
"What worked well?"
"What got in our way or held us back?"
"What should we do differently next time?"
The goal is not to critique. It is shared learning and shared ownership of how the team works together. See below for the link to the retrospective guide on our website.
Second. Run a pre-mortem for an upcoming deliverable. Again, bring together the directly involved team members and do the following:
Ask "What will cause us to miss this outcome or fail to deliver? Name everything."
Then ask "How will we prevent it?"
Let the team decide how they will work together to succeed
In both cases, have someone facilitate. Make sure all voices are heard. Invite different perspectives. End with clear commitments on what the team will try next.
Dan Coyle explores what creates meaning, connection, and sustained performance inside teams. Three ideas stood out for us.
The quality of attention we give each other matters as much as the work itself.
Trust is built over time through small, repeated moments. How a meeting opens. How a team responds to a setback.
The most innovative teams explore broadly together before they converge on answers.
Flourishing is not accidental. It is built through everyday habits that shape how people show up for one another.
Want to learn more? Click the image for the Amazon link.
Until next time!
If your R&D team is navigating complexity and you want support getting aligned and moving faster, we’re happy to start with a conversation. Plumtree is here to help teams and organizations work at the speed of science.
P.S. If you know someone who’d find this useful, please forward it and invite them to subscribe HERE.