Collaboration Encouragement

For two decades, I’ve seen engineering teams attempt “collaboration.” Often, it manifests as mandated daily stand-ups, endless Slack threads, and meetings that feel like performance reviews disguised as brainstorming sessions. We talk about collaboration, we put “collaboration” on performance reviews, but are we actually encouraging genuine collaboration?

It's easy to confuse activity with actual collaboration. Activity looks like everyone being present in a meeting. Collaboration is about people feeling safe enough to share half-baked ideas, challenge assumptions, and build on each other's work – even when it’s messy. I recently witnessed a team struggle for weeks with a complex bug, only to have a junior engineer, hesitant to speak up initially, suggest a surprisingly simple solution during a retrospective. That’s the power of genuine collaboration.

Here’s what I’ve learned about fostering genuine collaboration, moving beyond the buzzword and creating a team where people want to work together.

The Problem with "Forced" Collaboration

Let’s be honest: much of what passes for collaboration is simply task assignment wrapped in feel-good language. “Let’s collaborate on this feature!” often translates to “I need you to build this part, and you that part.” That's division of labor, not collaboration. For example, asking an engineer to simply ‘implement’ a design without understanding the ‘why’ behind it stifles ownership and genuine contribution.

This “forced” collaboration breeds resentment and stifles creativity. People start viewing collaboration as extra work, a check-box exercise, or a way for management to micromanage. I've seen engineers actively avoid asking for help, fearing judgment or being seen as incapable.

The key isn’t more meetings or communication channels. It's about building a culture of psychological safety.

Building Psychological Safety: The Foundation of Collaboration

Psychological safety, a term coined by Harvard Business School professor Amy Edmondson, is the belief that you won't be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. It's not about being nice; it's about creating a space where vulnerability is seen as a strength, not a weakness. Edmondson's research demonstrates that teams with high psychological safety are more likely to innovate and perform effectively.

Here's how to build it:

• Lead with Vulnerability: As a leader, you have to go first. Admit your own mistakes. Ask for help. Show that it’s okay to not have all the answers. This isn’t about appearing weak; it's about demonstrating that learning and growth are valued more than perfection.
• Normalize Failure: Celebrate learning from mistakes, not just successes. Conduct post-mortems that focus on what went wrong, not who is to blame. Frame failures as opportunities for improvement, not grounds for punishment.
• Active Listening & Curiosity: When someone shares an idea, resist the urge to immediately critique it. Ask clarifying questions. Seek to understand their perspective. Show genuine curiosity. A simple “Tell me more about that…” can go a long way.
• Create Safe Spaces for Feedback: Implement mechanisms for anonymous feedback or one-on-one check-ins where people can share concerns without fear of retribution. And act on the feedback you receive.

Tools & Practices to Enable (Not Dictate) Collaboration

Once you've established a foundation of psychological safety, these tools and practices can help facilitate genuine collaboration. We can think of fostering collaboration like building a pyramid – psychological safety is the broad base, tools and practices form the middle, and intrinsic motivation is the peak.

• Knowledge Sharing Platforms: Tools like Confluence are invaluable for documenting knowledge, sharing learnings, and creating a central repository of information. Encourage teams to contribute and actively maintain these resources. This fosters a shared understanding and reduces knowledge silos.
• Collaborative Project Management: While tools like teamwork.com can be useful, remember they're tools, not solutions. Focus on transparency – everyone should be able to see what everyone else is working on. Kitemaker.co, which integrates with existing tools like Slack and GitHub, can be particularly effective for visualizing the development process, improving alignment, and surfacing dependencies.
• Asynchronous Communication: Not every discussion needs to happen in real-time. Encourage teams to use asynchronous communication channels (like dedicated Slack channels or project management comments) for non-urgent discussions. This maximizes individual focus and minimizes disruption.
• “Open Office Hours” (Virtual or Physical): Encourage senior engineers to dedicate specific times for open office hours where junior engineers can ask questions and seek guidance. This fosters mentorship and knowledge sharing.
• Regular “Tech Talks”: Encourage engineers to share their learnings and expertise with the team through regular tech talks or presentations. This builds community and fosters a culture of continuous learning.
• Dev.to and Internal Forums: Support engineers in sharing their work and knowledge publicly on platforms like Dev.to, or create internal forums for discussion and knowledge exchange.

By implementing these tools with a focus on psychological safety, teams can move beyond simply being ‘connected’ to truly collaborating.

Beyond Tools: Fostering Intrinsic Motivation

Ultimately, the most effective way to encourage collaboration is to foster intrinsic motivation. People collaborate best when they're passionate about the problem they're solving and feel a sense of ownership over the solution.

Don’t focus on “fixing” boredom, but on giving engineers the agency to solve meaningful problems. Provide opportunities for them to explore new technologies, experiment with different approaches, and contribute to projects that align with their interests.

Conclusion

Collaboration isn't about forcing people to work together; it’s about creating an environment where they want to. By focusing on psychological safety, providing the right tools, and fostering intrinsic motivation, you can build a team that thrives on collaboration, innovation, and shared success. It takes effort, consistency, and a genuine commitment to creating a culture of trust and respect.