3.4 Conflict Resolution & Teamwork

Conflict Resolution & Teamwork

Procurement sits at the intersection of various internal business functions and dynamic external markets. Because it is constantly required to balance competing demands—such as the finance department's drive for cost reduction versus engineering's demand for high-quality specifications, or the business's need for speed versus legal's requirement for strict compliance—conflict is an inevitable part of a procurement professional's daily life.

Managing this conflict constructively, rather than letting it derail projects, and fostering effective teamwork are essential skills for driving value, innovating, and maintaining healthy, productive stakeholder relationships.

Sources of Conflict in Procurement

Conflict in procurement can arise internally (between different departments within the buying organization) or externally (with suppliers and vendors). Common sources include:

• Divergent Goals and Objectives: This is the most frequent source of internal conflict. For example, procurement's primary KPI might be to reduce costs by standardizing a component across all product lines. Meanwhile, the engineering department's goal is to maximize product performance by using a highly customized, expensive, non-standard component. These opposing goals naturally create friction.
• Resource Constraints: Limited budgets, personnel shortages, or aggressive timelines can cause conflict. Departments may fight over the allocation of the procurement team's time, demanding that their specific sourcing projects be prioritized over others.
• Misaligned Expectations: If a supplier misunderstands a technical specification, or if internal users expect a delivery timeline that the supplier simply cannot meet due to logistical realities, conflict will inevitably ensue when these expectations clash with reality.
• Power Struggles and Authority Issues: Conflict frequently arises over who has the final authority to select a supplier, sign off on a budget, or approve a contract variation.
• Communication Failures: Poorly drafted contracts full of ambiguity, a lack of regular feedback, or cultural misunderstandings in global supply chains can quickly escalate from minor annoyances into serious, legally fraught disputes.

Conflict Resolution Models: The Thomas-Kilmann Instrument

To manage conflict effectively, professionals must not react emotionally; instead, they must consciously choose an appropriate resolution strategy based on the specific situation. The Thomas-Kilmann Conflict Mode Instrument (TKI) is a widely recognized framework that categorizes conflict resolution styles based on two behavioral dimensions:

1. Assertiveness: The degree to which a person attempts to satisfy their own concerns and achieve their own goals.
2. Cooperativeness: The degree to which a person attempts to satisfy the other party's concerns and maintain the relationship.

By intersecting these two dimensions, the model creates five distinct conflict resolution modes:

1. Competing (High Assertiveness, Low Cooperativeness)

This is a power-oriented, "win-lose" approach where one pursues their own goals at the expense of the other party. It involves using hierarchical authority, economic power, or hard negotiation tactics to force a decision.

• When to use: In emergencies where quick, decisive action is vital, or when enforcing critical rules (like health and safety compliance, ethical sourcing policies, or regulatory requirements) where there is zero room for debate or negotiation.

2. Accommodating (Low Assertiveness, High Cooperativeness)

This is a "lose-win" approach where one yields to the other party's demands, essentially sacrificing their own goals to satisfy the other person.

• When to use: When you realize you are wrong or have weak data, when the issue is far more important to the other party than to you, or when preserving harmony in the relationship is more critical than the immediate commercial outcome of the dispute.

3. Avoiding (Low Assertiveness, Low Cooperativeness)

This is an unassertive and uncooperative "lose-lose" approach where a person simply ignores the conflict, withdraws from the situation, or delays dealing with it.

• When to use: When the issue is trivial, when emotions are too high and a cooling-off period is needed to regain perspective, or when you have absolutely no chance of satisfying your concerns. However, chronic avoidance is dangerous, leading to unresolved issues, festering resentment, and eventual supply chain failure.

4. Compromising (Moderate Assertiveness, Moderate Cooperativeness)

This approach seeks a fast, middle-ground where both parties give up something to reach a mutually acceptable, though imperfect, solution. It is a "partial win-partial lose" scenario.

• When to use: When goals are moderately important but not worth the intense effort of a fully collaborative approach, when time is short, or when two parties with equal power are firmly committed to mutually exclusive goals (e.g., a buyer wanting to pay $10, a supplier wanting $12, and compromising at $11).

5. Collaborating (High Assertiveness, High Cooperativeness)

This is the ultimate "win-win" approach. It involves digging deep into the underlying concerns, constraints, and interests of both parties to find a creative, synergistic solution that fully satisfies everyone's needs. It requires high trust and open information sharing.

• When to use: When the objective is to learn, when merging insights from people with different perspectives, and when the relationship with the stakeholder (internal or external) is highly strategic and long-term. While it requires the most time and effort of any mode, it yields the best, most sustainable long-term results.

Team Dynamics in Procurement

Procurement is rarely a solo endeavor. Strategic sourcing projects, capital expenditures, and major contract implementations almost always require the formation of teams.

Cross-Functional Teamwork

A cross-functional team brings together individuals from various departments—such as procurement, engineering, finance, legal, marketing, and quality control—to work collaboratively toward a common goal.

• Benefits: It breaks down organizational silos and "turf wars." It ensures that all departmental perspectives are considered before a supplier is selected, drastically reducing the risk of post-contract disputes or product failures. It leverages diverse expertise to find innovative solutions. For instance, a cross-functional team evaluating a new software system ensures it meets IT security standards, user functionality requirements, legal data protection laws, and procurement budget constraints simultaneously.

Stages of Team Development (Tuckman's Model)

When a cross-functional procurement team is newly formed, it does not immediately operate at peak efficiency. In 1965, psychologist Bruce Tuckman identified five distinct stages of team development that groups must navigate to achieve success:

1. Forming: The team comes together for the first time. Members are polite, cautious, and somewhat anxious. They are focused on understanding the project's broad objectives and defining their individual roles. There is a high dependence on the team leader or project manager for direction and instruction.
2. Storming: Conflict inevitably emerges as team members start to feel comfortable enough to assert their opinions and push their departmental agendas. The engineering rep may clash loudly with the finance rep over budget constraints. This is a critical, volatile stage; avoiding the conflict here prevents the team from growing. The team leader must actively facilitate constructive conflict resolution to keep the project on track.
3. Norming: The team successfully resolves its differences, establishes accepted ground rules, and aligns firmly on shared goals. Members begin to genuinely respect each other's expertise, communication improves, and they work collaboratively. A strong sense of team cohesion builds.
4. Performing: The team now functions at a highly efficient, synergetic level. They are autonomous, highly motivated, and capable of solving complex problems without constant oversight from management. This is the stage where the team successfully executes the complex sourcing strategy and delivers maximum value.
5. Adjourning: The project is completed, the contract is signed and implemented, and the team prepares to disband. It involves recognizing the team's achievements, formally closing out the project, and capturing "lessons learned" to improve future cross-functional projects.

Understanding these stages is vital for procurement professionals leading cross-functional teams. Recognizing that the "storming" phase is a normal, healthy, and necessary part of team evolution prevents panic when inter-departmental conflicts arise early in a project. By applying the right conflict resolution strategies and patiently guiding teams through Tuckman's stages, procurement can turn diverse, conflicting groups of stakeholders into high-performing units that deliver exceptional value to the organization.