Article
Reducing Silo-Mentality and Getting Teams to Collaborate
August 24, 2020
Develop A Collaborative Environment
The team leader plays a key role in creating a team culture or climate. If you want to work with a team where there’s an expectation that people will collaborate, and where team members actively look for ways to support one another, it is up to you to consciously build that team.
When assembling a team, whether new hires or from within the organization, look for people who are team players. That means that their competitive spirit is aimed at achieving goals and winning for the team, rather than on raising their own status or trying to one-up their colleagues. Some people view the world as a zero-sum game, where there are limited resources and they must compete to get their fair share. This is the opposite of an attitude of abundance that assumes that we can all win if we work together and there is enough for everyone. Competitiveness is fine when it comes to the organization’s external competitors but has a decidedly negative impact when it is social competitiveness and winning at the expense of other team members.
Our own research at Hagberg Consulting Group makes this abundantly clear. Social competitiveness – people who feel the need to compete with their co-workers – is negatively correlated with openness to input, listening, building partnerships, building relationships, information sharing, and forthrightness. Not the profile of an effective team member!
Stack ranking is a procedure, popularized in the 1980s by GE’s CEO Jack Welch, of ranking employees according to a bell curve. In that system, the top 10% are designated as top performers, while the bottom 10%, seen as a drag on the organization’s effectiveness, are routinely let go. Stack ranking fosters internal competition of employee vs. employee as they strive for high marks, and it stifles innovation. “In a hyper-competitive workplace,” wrote Max Nilson in Business Insider, “where management is essentially asking employees to outperform the people sitting next to them, employees don't have an incentive to share ideas or collaborate.” People focus on their own performance, “rather than working together toward broader goals. And at its most extreme, employees may focus on preventing others from excelling.” After all, you might not want to help a fellow team member because you may be the one who gets fired if he does better than you. [“Why Stack Ranking Is A Terrible Way To Motivate Employees,” Max Nilson, Business Insider Nov. 15, 2013] No wonder people experienced it as a morale killer.
On the other hand, here are some suggestions for building a collaborative, cooperative environment:
- Strengthen relationships. It is important for the leader to continually look for ways to build cohesion and strengthen relationships and bonds between members. Whether it is a meeting whose primary focus is helping team members get to know each other in more depth, a team dinner once a month, or a planning off-site that includes activities that help members get together just for fun and socializing, can go a long way toward increasing team coherence. Also, beware of having such a rigorous and rigid agenda-focus in your meetings that you don’t leave any time for informal discussion and personal sharing. This may not always be possible or desirable, but should be built in whenever feasible.
- Encourage communication between team members. The team leader also needs to encourage communication between team members and avoid relying on the “hub and spoke” style, where communication is primarily one-on-one between the leader and individuals. That style is familiar and comfortable for independent-minded entrepreneurs, but it is not helpful for building teams or evolving solutions to complex problems that require communication and collaboration among various specialties. Encourage team members to develop deeper connections amongst themselves, so that decisions do not always revolve around you. (Why? Because if you are not available at crunch time, how will decisions be made?)
- Beware of silos. In rapidly growing organizations there is always a threat that organizational silos will develop, and teams will focus narrowly on their own agendas and priorities, even to the point of resenting or stereotyping “those people over in sales,” and so on. To counteract this tendency, you need to foster communication between teams, and organize regular meetings between them to coordinate efforts, develop mutual understanding, and learn to collaborate.
- Promote cross-functional teamwork. When silos do develop and people think primarily about their own team or functional agenda, they lose track of what others need and the challenges they may be facing. This mind-set can lead to a reluctance to communicate, coordinate, or cooperate, even to share information or resources with other individuals, departments or teams. As the leader, if you see this happening, let everyone know that you want every team member to be aware of, and sensitive to, not only the projects others are working on, but what they need in order to be most effective. When teams and team members are called upon to cooperate with other teams to work on certain problems and projects, you can make this collaboration more fruitful if you discuss with everyone involved areas where the teams need to work together, what each needs from the other team, and how they can partner most effectively.
- Organize cross-functional meetings . Interdependent teams should meet regularly to clarify mutual goals and roles, sort out ongoing issues and problems, create plans and solutions together, and support each other. Product and Engineering, for example, could meet once a month or even more often, to share what they are working on, what their priorities are, what problems they are facing, and coordinate their efforts. As the leader, help everyone understand what each team needs from the other(s), their problems and priorities, and encourage them to develop empathy rather than looking at the other group as “them”. Be careful to discourage any “us versus them” thinking or negative stereotyping of the other group.
- Encourage active participation in meetings.
Encourage team members to participate and openly share their ideas and perspectives. Do your best to get people involved. Facilitate dialogue between team members. Draw them out. “Maria, we haven’t heard from you on this new initiative. What do you think about it?” Or, “That’s a good idea. How can we build on it?”
- Reduce the fear factor.
Be sure your attitude and demeanor in meetings does not intimidate others, but makes them feel that their presence and their ideas are welcome and appreciated. On the other hand, some people may need to be motivated by the awareness that there will be consequences if they don’t deliver. So this is another area where a balance of leadership styles and approaches may be needed.
- Build a team culture of collaboration.
Starting with your own example, encourage team members to make a strong personal commitment to the success of other members, and not be focused entirely on their own achievements. This requires a spirit and expectation of collaboration and cooperation between team members and fostering a strong common identity, rather than an “us versus them” mentality.
- “How can I help with that?”
As team leader, a major part of your job is to find out what people need, where they are stuck, where they might need more resources, and facilitate the solution. Team members can follow your example, talk to each other about what they are working on, and ask, “How could I help you with that?” Often there is a way to contribute directly to someone else’s part of a project because of the diversity of backgrounds and expertise, but even if there is not, just letting others know you have their back and are available if they need you promotes a spirit of collegiality and mutual support. And don’t forget: on a team, each person’s achievements and successes are not just for the individual, but contribute to the success of the whole.
- Don’t avoid problems. Effective problem-solving and decision-making involves surfacing troublesome issues and bringing up differing views for consideration. When there are problems between the groups, don’t let them fester. Discuss what is and isn’t working and how the communication and collaboration can be improved. The leader needs to actively guide this process, to bring out the best ideas and insights.
- Re-assess your role
. Learn to see yourself not so much as “the boss” or “the decider” but rather as a facilitator of effective problem-solving and communication.
- Model collaborative behavior.
Getting to the core of an issue and making the right decision also requires the leader to model collaborative behavior, not an easy task for those who have largely been individual contributors, but an essential role to learn to play.
share this
Related Articles
Related Articles
Introduction: The Brutal Truth About Change If you’re leading a company, here’s one brutal truth you can’t dodge: resistance to change isn’t just inevitable—it’s a gift. Most leaders don’t see it that way. They treat it like an obstacle to bulldoze, something to out-argue, out-maneuver, or silence. But resistance, if you know how to read it, is a living, breathing diagnostic tool. Every objection, every sideways comment in a hallway, every moment of awkward silence in a meeting—it’s all data. It tells you where the trust gaps are, where the communication breakdowns have happened, and where your people’s unspoken fears live. If you ignore that data, you’re flying blind. The hard numbers back this up: more than 70% of organizational change initiatives fail, not because the strategy was flawed, but because leaders underestimated what it would take to guide people through the emotional turbulence of transformation. If you want your next big initiative to succeed, the shift starts here: stop seeing resistance as the enemy, and start listening to what it’s telling you. When you do, you’ll discover that resistance isn’t a wall to break down—it’s a map showing you exactly where to go next. 1. Rethink Resistance: It’s Data, Not Defiance Let’s flip the lens. When people resist, they’re rarely doing it for sport. They’re sending up flares. They’re telling you something’s unclear, untested, or untrusted. For example, I worked with a CEO rolling out a sweeping technology overhaul. His first instinct when his managers hesitated was frustration—until we sat down and dissected the resistance. It turned out the managers weren’t doubting the technology; they were worried about the gap between the training timeline and the rollout date. They didn’t fear change—they feared being set up to fail. When you stop labeling resistance as “non-compliance” and start treating it like intelligence gathering, you find it points to the very levers you can pull to move the change forward.
Most startup founders are brilliant at innovation, disruption, and blazing new trails. They're visionaries, incredibly driven, and fiercely independent. Unfortunately, those same powerful traits often sabotage their ability to foster genuine collaboration—a critical ingredient in startup success. I've spent decades coaching founders, and one of the biggest blind spots I've observed is the gap between what founders naturally do well and what's required to create truly collaborative cultures. Understanding these tendencies—and knowing how to counter them—can mean the difference between startup stagnation and breakout growth. High Independence, Low Collaboration Founders thrive on independence. They love breaking rules, ignoring boundaries, and pushing limits. But independence can quickly morph into isolation. The very idea of slowing down to seek consensus or accommodate team input feels restrictive, even suffocating. Implications: This independent streak inadvertently sidelines team members, suppresses input, and reduces engagement. Talented people quickly learn their ideas don't matter, and teams become passive or defensive. Actions to Counter: Practice deliberately inclusive decision-making. Clearly define which decisions you'll make alone and where you'll solicit team input. Regularly check in to see if team members feel heard and involved. Dominance Isn’t Always Dominant Many founders naturally take a commanding stance. Their assertiveness, directness, and forcefulness can spark initial progress but, over time, it creates resistance. When team members feel steamrolled or fearful of speaking up, creativity vanishes. Implications: A dominant style shuts down communication, makes feedback difficult, and kills the very collaboration needed for sustained innovation. Actions to Counter: Make intentional space for quieter team members to speak. Foster psychological safety by modeling vulnerability and humility Balance assertiveness with curiosity—actively seek feedback rather than waiting for it. The Curse of Poor Delegation Delegation isn't just handing off tasks—it's handing off trust. But founders notoriously struggle with this, often believing only they can execute properly. Every task not delegated reinforces the message that the team isn’t capable. Implications: Poor delegation creates bottlenecks, slows execution, and demoralizes talented employees who feel undervalued and micromanaged. Actions to Counter: Start small by delegating lower-risk tasks clearly and thoroughly. Regularly check your impulses to micromanage; remind yourself why you hired capable people. Invest in mentoring and coaching rather than controlling. Communication Breakdown Founders are famously impatient. They think fast, act fast, and often communicate quickly or incompletely. What seems obvious to them might be totally unclear to their team. Implications: Poor communication creates ambiguity, confusion, and frustration, grinding collaboration to a halt. Teams waste energy guessing expectations rather than innovating. Actions to Counter: Slow down to clearly articulate the "why" behind your decisions. Confirm understanding by asking team members to reflect back their interpretations. Regularly solicit feedback on your communication style and clarity. Arrogance: The Silent Collaboration Killer Confidence is crucial. But confidence unchecked can veer into arrogance, leading founders to dismiss feedback, overlook critical insights, and alienate key contributors. Implications: Arrogance destroys trust, stifles dialogue, and creates a toxic environment where collaboration is impossible. Actions to Counter: Intentionally invite critique and respond openly and constructively. Regularly acknowledge your mistakes publicly to model humility. Actively seek alternative viewpoints before finalizing decisions. Conflict Avoidance (or Aggression) Many founders fall into two extreme camps: conflict avoiders or conflict initiators. Both extremes are deadly to collaboration. Avoiding conflict leaves critical issues unresolved. Aggressive conflict handling creates resentment and fear. Implications: Poorly managed conflict erodes team cohesion, undermines trust, and can spiral into prolonged dysfunction. Actions to Counter: Establish clear, structured conflict resolution processes. Practice direct yet respectful conflict conversations. Use neutral facilitation for emotionally charged discussions. Systems Thinking vs. Reactive Planning Startups prize agility and adaptability. But too much short-term thinking neglects the processes and structures that sustain collaboration. Without clear systems, teams fall into chaos. Implications: Reactive planning leads to burnout, inefficiency, and frustration as team members constantly fight fires rather than building strategically. Actions to Counter: Balance short-term agility with consistent investment in systems and clear processes. Regularly revisit and improve structures as your company scales. Empower process-oriented thinkers in your organization to build effective systems. Workaholism and Burnout Culture Founders set the pace. But when founders turn workaholic, they unknowingly create an environment of exhaustion, anxiety, and diminished psychological safety. Exhausted teams are seldom collaborative. Implications: Productivity drops, innovation dries up, and talented employees start to leave. Actions to Counter: Actively model sustainable work-life balance. Publicly recognize and reward collaborative, balanced behaviors. Regularly monitor signs of burnout and intervene early. Ambiguity Isn’t Always Your Friend Founders typically tolerate ambiguity better than most. But your team needs clarity and direction. Too much ambiguity creates stress and undermines collaborative execution. Implications: Team paralysis, lack of initiative, and increased frustration. Actions to Counter: Clearly define roles, responsibilities, and expectations. Regularly ask your team what clarity they need to be effective. Balance your tolerance for ambiguity with your team’s genuine need for guidance. The Collaboration Paradox Founders face a paradox. The same traits that fuel their success—independence, assertiveness, rapid execution—also sabotage the collaborative environments crucial for scaling. Acknowledging this paradox is the first step. The second is intentionally adopting behaviors that might feel unnatural at first: fostering inclusive communication, delegating with trust, managing conflict constructively, investing in systems thinking, and balancing your independent streak with genuine empathy. The good news? These skills are learnable. Great founders don’t have to become entirely different people; they simply need to expand their toolkit. Start today by picking just one area and committing to small, consistent improvements. Your team and your startup—will thank you.
The Recognition Paradox:
Why Truly Outstanding Leaders Thrive by Indifference to Personal Glory
