5.2 Team Dynamics in Acquisition Teams

Team Dynamics Are a Tested Contracting Competency

FAI row 1.6 Team Dynamics is a small slice of Guiding Principles (three questions), but it permeates CON 3990V scenarios. Many items that look like “FAR knowledge” are really who should decide, who should advise, and how the team should work the problem. If you treat contracting as solitary clause application, you will miss answers that hinge on collaboration, conflict management, and authority discipline.

DoD acquisition culture expects an integrated team approach. Integrated Product Teams (IPTs) and broader acquisition teams exist so requirements, contracting, technical, logistics, legal, and financial perspectives collide early — when change is still cheap — rather than after a protest, claim, or fielded failure.

---

The Multidisciplinary Acquisition Team

A functioning DoD contracting team typically includes more than “the 1102 shop.”

Exam lens: When a scenario names three titles, map influence → recommendation → decision authority. The person who cares most about the mission is not automatically the person who can change the contract.

---

Buyer–Seller Common Purpose: Satisfying the Customer Need

Team dynamics are not only internal Government dynamics. FAI’s contracting competency model recognizes a buyer–seller system. The Government buyer and industry seller are not teammates in a warrant sense, but they do share a practical common purpose: satisfy the customer need defined by the requiring activity and the contract.

Healthy external engagement looks like:

• Clear Government points of contact and channels (especially post-award: CO vs COR)
• Early industry communication through proper vehicles (RFI, industry day, draft solicitation)
• Problem-solving on performance issues without informal scope growth
• Honest discussion of risks without leaking source-selection information in competitions

Unhealthy engagement looks like side deals with the COR, preferential access for the incumbent during competition, or adversarial silence until a claim is filed.

Memory hook: Collaborate on the need; compete on the award; contract on the writing.

---

Role Clarity vs. Overlap

If every role were perfectly siloed, acquisition would be slow and stupid. Some overlap is healthy:

• Specialists and COs both think about strategy
• PMs and CORs both care about technical performance
• Legal and contracting both read risk in clauses
• Finance and contracting both care whether a CLIN structure is fundable

Problems start when overlap erases authority boundaries.

Bright lines that CON 3990V expects you to keep

• Only a warranted CO (within authority) binds the Government by contract, modification, or termination
• CORs monitor and recommend; they do not change scope, price, or schedule by email
• PMs prioritize mission and requirements; they do not award or independently rewrite contractual obligations after award
• Legal advises and concurs where required; counsel does not become the source selection authority by force of memo tone
• Finance certifies funds; certification is not a substitute for a contract action

Constructive overlap patterns

• Joint development of evaluation factors (PM/tech + contracting)
• Integrated surveillance planning (COR + CO + PM)
• Early legal/finance touchpoints on high-risk strategies
• Cross-briefings so each function understands constraints

Exam trap: A scenario where “the team agreed” is used to justify an action no one on the team had authority to take. Consensus without authority is still an unauthorized commitment risk.

---

Cohesiveness: What High-Performing Acquisition Teams Do

Cohesiveness means the team shares goals, trusts role competence, and communicates enough to prevent surprise. It is not forced friendliness or suppression of bad news.

Cohesive teams typically:

1. Agree on mission outcomes and constraints early (cost, schedule, performance, compliance)
2. Publish a simple RACI-like clarity for major decisions (who recommends, who decides, who must concur)
3. Maintain a single source of truth for requirements and evaluation factors
4. Surface risks early (technical maturity, vendor base, funding fragility)
5. Protect each other from integrity and authority mistakes — peer correction is loyalty to the mission

Low-cohesion symptoms the exam may narrate:

• Program office runs a parallel negotiation with the contractor
• Contracting learns about a constructive change after costs are sunk
• Evaluators score with private “shadow factors”
• Finance rejects a package at the last hour because nobody shared the CLIN logic
• Legal is invited only after a protest is inevitable

Cohesiveness is built with process, not pizza: kickoff alignments, decision logs, shared calendars for critical milestones, and explicit escalation paths.

---

Constructive Conflict vs. Destructive Conflict

Acquisition teams need conflict — the good kind. Constructive conflict improves requirements quality, evaluation fairness, and risk allocation. Destructive conflict freezes decisions or drives end-runs around contracting.

How leaders (including COs) manage constructive conflict

• Separate people from positions
• Force options into writing: alternatives, risks, authorities
• Time-box debate, then decide with the correct decision owner
• Document minority concerns when risk remains
• Never punish messengers who flag integrity or compliance issues

On CON 3990V, if a specialist challenges a PM’s preferred sole-source path with a competition-feasible alternative, that is often good team dynamics, not disloyalty.

---

When the CO Leads vs. When Consensus Is the Goal

Not every discussion should end in a vote. Authority type determines process type.

CO-led decisions (authority / obligation / formal direction)

Use clear CO leadership when the action:

• Creates or changes a contractual obligation
• Selects a source / makes an award decision (or executes SSA-designated process steps owned by contracting authority)
• Issues a modification, termination, cure notice, or claims decision within CO authority
• Sets formal exchanges with offerors that affect competition fairness
• Determines whether an action is within scope or requires a new procurement

In these moments, the CO should listen widely, decide clearly, and document. Endless consensus-seeking can become an abdication of warrant responsibility.

Consensus-seeking (or structured collaboration) moments

Seek strong team alignment when the issue is primarily:

• Technical tradeoffs among performance parameters
• Operational priority ranking of requirements
• Surveillance approach design and metric selection
• Scheduling of evaluation logistics and SME availability
• Framing of mission risk for leadership decision briefs

Even here, consensus is a method for quality, not a source of legal authority. If the team “agrees” the contractor should start new work Monday, someone still needs a funded, authorized contract action before the Government is properly bound.

---

DoD IPTs and Acquisition Team Culture

Integrated Product Teams are a DoD cultural tool: bring stakeholders together across functions to manage a product or capability end-to-end. For contracting professionals, IPT participation means:

• Translating technical desires into contractable language early
• Warning the team when a preferred path conflicts with competition, fiscal, or ethics rules
• Helping the team pick procedures and contract types that match uncertainty
• Ensuring post-award administration is designed during pre-award, not improvised later
• Carrying team decisions into formal solicitation/award documents accurately

IPT culture fails when contracting is treated as a late paperwork gate or when the IPT believes verbal team agreement substitutes for contract terms. IPT culture succeeds when contracting is an embedded advisor-decider: collaborative on shaping, decisive on obligation.

Practical team-dynamics habits for exam scenarios

1. Name the decision type (technical preference vs. contract action)
2. Invite the missing function early (legal/finance/COR) when risk appears
3. Write the channel for industry communication
4. Escalate authority or integrity issues instead of normalizing them
5. Close the loop so PM/COR/CO share the same understanding of what was directed

---

Integrated Scenario: Dynamics Under Schedule Pressure

Deployment is in 60 days. The PM wants the incumbent to begin “pre-mod work” now. The COR agrees. Finance says funds will arrive “any day.” Legal has not been consulted. The specialist worries about unauthorized commitment and competition issues on a related follow-on.

Team-dynamics diagnosis:

• High mission cohesion impulse, low authority discipline
• Overlap between PM/COR enthusiasm and CO authority is being ignored
• Constructive conflict from the specialist is a feature, not a bug
• Correct path: CO leads on whether any contract vehicle/authority exists; finance confirms funds; if new work is required, use a proper modification or other authorized instrument; do not paper over with team consensus

Memory hook: Many voices, one warrant — conflict on ideas, clarity on authority. That is the CON 3990V team-dynamics standard.