Teamwork

You will not ship great products without a team that works well together. The actual job of teamwork is to create synergy — where the whole is greater than the sum of the parts. But that requires more than just technical skills. It demands communication, political savvy, and conflict management.

Most teams fail not because of lack of expertise but because people struggle with interpersonal dynamics. If you cannot build trust and open communication across functions, your product will suffer.

The trap of functional silos

Many organizations still organize people into functional silos: engineering, design, marketing, sales, and so on. Each team optimizes for its own goals, KPIs, and incentives. The result? The product becomes a handoff game — engineers wait on specs from product, product waits on customer feedback from sales, design waits on requirements from product, and nobody owns the end-to-end outcome.

Breaking silos is not just a nice-to-have. It is essential for speed and innovation.

Cross-functional teams that are outcome-driven outperform functional groups. The difference is accountability — the team shares a common goal and metrics, not just individual KPIs.

How silos hurt product teams in India

In many Indian companies, traditional hierarchy and strict role definitions reinforce silos. Engineers focus on technical delivery, sales focus on targets, and product managers become middlemen passing tickets. The communication tends to be formal and limited to status updates, not real problem-solving.

This creates delays, missed dependencies, and frustration. The startup subsidiary case study from the late 1990s shows this clearly: the parent company had work groups organized by function with little socialization and a strict hierarchy. The startup’s teams, in contrast, were permanent cross-functional units with joint planning, continuous learning, and shared accountability. The startup’s teams achieved higher morale, client satisfaction, and performance.

The pattern is consistent: technical skills alone don’t make a team great

Katz (1997) and Thompson (2004) found that effective teams require not just technical skills but interpersonal, decision-making, and problem-solving skills. Strozniak (2000) reports that people skills — communication, trust, conflict resolution — are where teams struggle most.

If your team only focuses on technical delivery, you will hit a ceiling on performance.

Building synergy across functions

The key to teamwork is synergy. This means people willingly share ideas, criticism, and information openly. It means creating an environment where the team’s output is greater than what each member could produce alone.

What does synergy look like in product teams?

• Engineers understand the customer context — not just specs.
• Designers collaborate early with product and engineering.
• Sales shares real user feedback continuously.
• Product managers facilitate, unblock, and align the team around outcomes.

All of this requires effective communication — not just status updates, but open dialogue, feedback loops, and radical candor.

Cross-functional structures and rituals that force collaboration

To create synergy, you must redesign processes and introduce rituals that break down barriers:

• Organize teams around user journeys or outcomes, not functions. Embed product, design, engineering, QA, and data in each squad.
• Set shared goals and metrics. Tie incentives and recognition to team performance, not just individual functions. For example, a shared OKR on "New User Activation Rate" encourages marketing and product to collaborate.
• Use intentional collaboration rituals: daily cross-functional huddles focused on dependencies, regular co-creation sessions like design studios or journey mapping, and pairing practices such as engineer-QA or PM-designer co-working.
• Create shared communication channels and documentation. Dedicated Slack channels and collaborative docs in Notion or Confluence ensure transparency and reduce siloed private messaging.

Atlassian’s ShipIt Days are a famous example: 24-hour hackathons where employees from any function form ad-hoc teams to build anything they want. This breaks silos and fosters bottom-up innovation.

Political skills: the invisible work of product teams

Technical and communication skills are necessary but not sufficient. Political skills are often the difference between a team that stalls and one that delivers.

Political skills include:

• Gaining support from stakeholders outside the team.
• Securing resources necessary for your team’s work.
• Protecting the team from external distractions and threats.
• Managing internal conflicts constructively.

The startup case study illustrates this. The COO of the subsidiary, a lawyer with computer skills, was responsible not only for building teams but also for ensuring acceptance of the team’s output and overcoming obstacles.

You must be a political operator as well as a product expert.

Internal political skills: managing conflict within the team

Conflict is inevitable. High-performing teams have agreed-upon processes to surface and resolve conflicts before they fester.

Avoiding conflict leads to resentment and dysfunction.

Suppressing conflict leads to passive-aggressive behavior.

Good conflict resolution:

• Creates psychological safety to speak up.
• Uses structured methods like facilitated discussions or retrospectives.
• Focuses on the problem, not the person.
• Seeks consensus or clear decisions.

The anatomy of a high-performing team

High-performing teams combine:

• Technical expertise in their respective domains.
• Interpersonal skills to communicate openly and build trust.
• Political savvy to navigate organizational dynamics.
• Shared accountability for outcomes, not just outputs.

The startup subsidiary’s success was built on permanent, cross-functional teams with ongoing social interaction, high morale, and commitment to team processes. The parent company’s work groups, by contrast, were temporary, hierarchical, and strictly task-focused, leading to lower cohesion.

Your role as a product leader is to cultivate these conditions for your team.

Test yourself: The team conflict dilemma

Alumni callout

PL alumni now work at Flipkart, Google, Razorpay, PhonePe, Swiggy, Amazon, Microsoft, and 30+ other companies.

Where to go next

• Build your product leadership skills: Leading Product Teams
• Master stakeholder management: Stakeholder Management
• Improve your communication: Effective Communication for PMs
• Learn conflict resolution techniques: Conflict Management
• Develop cross-functional collaboration rituals: Team Rituals and Processes