LaFasto–Larsen Five Dynamics of Teamwork and Collaboration

1. What Is LaFasto–Larsen Five Dynamics of Teamwork and Collaboration?

The LaFasto–Larsen Five Dynamics of Teamwork and Collaboration is a research-based framework that explains why some teams excel while others stall—even with smart, well-intentioned people. It organizes team effectiveness into five interlocking dynamics that build from the inside out:

• Team Member (the individual behaviors and capabilities people bring)
• Team Relationships (the quality of trust, respect, and communication between members)
• Team Problem Solving (how the team defines problems, makes decisions, and executes)
• Team Leadership (how leaders enable focus, standards, and momentum)
• Organizational Environment (the surrounding systems, culture, and senior support)

Within Team Effectiveness & Collaboration frameworks, it is both a diagnostic and a design guide. It helps you pinpoint where a team is strong or stuck (e.g., capable individuals but low trust; spirited debate but poor decision hygiene), and it provides targeted interventions to move performance. The model’s central insight: start with the human foundation (members and relationships), and then tune the team’s operating mechanics, leadership, and context to reinforce the behaviors you need.

In plain terms: get the right people behaving the right way, build trusting relationships, adopt disciplined problem-solving, enable the team with effective leadership, and align the organization around them—do these five well, and results follow.

2. Origin and Background

The model stems from decades of work by Frank M. LaFasto and Carl E. Larson. Their 1989 book, “TeamWork: What Must Go Right/What Can Go Wrong,” synthesized field research on effective teams. They expanded the evidence base in “When Teams Work Best” (2001), drawing on input from more than 6,000 team members and leaders across industries to distill the critical dynamics that consistently predicted success. The Five Dynamics of Teamwork and Collaboration is the practitioners’ formulation of those findings, widely used in organizational development, leadership programs, and consulting engagements.

Why it was created: to translate diffuse ideas about teamwork into an actionable, sequenced model leaders and teams can use to improve performance without mystique or jargon.

3. How the Five Dynamics Work

The dynamics are nested. Strong individual behaviors make constructive relationships possible; healthy relationships enable rigorous problem-solving; leadership amplifies and aligns effort; and the organizational environment either accelerates or stifles the team. Each dynamic has specific behavior standards and practical levers.

1) Team Member: “What do I bring?”

• Core behaviors: Credible competence; results orientation; collaborative mindset; open communication; reliability (keeps commitments); adaptability.
• What good looks like: Members prepare, contribute constructively, ask for and offer help, give and receive feedback, and take ownership for team outcomes—not just functional ones.
• Common gaps: Passive participation; silo-first thinking; defensiveness; missed commitments; poor follow-through.
• Levers: Role clarity, clear expectations (behavioral standards), development plans, coaching, and visible recognition for collaborative behaviors.

2) Team Relationships: “How do we work together?”

• Core behaviors: Trust, respect, psychological safety, constructive conflict, empathy, and balanced airtime.
• What good looks like: Issues are raised early; debate is about ideas, not people; commitments are public; peers hold peers accountable; feedback is timely and specific.
• Common gaps: Artificial harmony; triangulation (“meetings after the meeting”); dominance by a few; unresolved tension.
• Levers: “Working with me” exchanges; explicit norms for conflict and feedback; facilitation practices (rotating facilitators; check-ins/out); tracking psychological safety.

3) Team Problem Solving: “How do we decide and execute?”

• Core mechanics: Clear goals and criteria; shared fact base; decision rights and rules; disciplined debate; closure and documentation; follow-through and learning.
• What good looks like: Problems are defined crisply; alternatives are generated and evaluated against explicit criteria; decisions are recorded with rationale; responsibilities and timelines are clear; progress is visible on a shared board or dashboard; retrospectives improve the system.
• Common gaps: Vague problem statements; solution-jumping; re-litigation; unclear owners; missing data; weak handoffs.
• Levers: Charter and OKRs; RACI/RAPID for top decisions; decision logs; standard operating cadences (stand-ups, reviews, retros); access to data; root cause tools.

4) Team Leadership: “How are we enabled and held to standards?”

• Core responsibilities: Set and protect purpose; ensure role/goal clarity; model norms; manage boundaries and stakeholders; secure resources; reinforce peer accountability; recognize wins.
• What good looks like: Leader balances challenge and support; invites dissent then insists on closure (“disagree and commit”); clears obstacles; shields the team from churn; coaches individuals and the collective.
• Common gaps: Overdirecting (micromanagement); underleading (abdication); unclear priorities; tolerance of norm violations; stakeholder whiplash.
• Levers: Leader coaching; explicit decision criteria; published priorities; escalation paths; rituals for recognition; succession or deputy roles to distribute leadership.

5) Organizational Environment: “Do systems help or hinder?”

• Core elements: Incentives and performance management; decision rights and governance; tools and data access; capacity and budget; cultural signals from the top.
• What good looks like: Team outcomes are reflected in scorecards and rewards; approvals are right-sized; cross-functional work is supported by SLAs; leadership communicates consistent priorities.
• Common gaps: Misaligned KPIs; slow or opaque approvals; tool fragmentation; conflicting sponsorship; overload.
• Levers: Team-level OKRs in performance reviews; decision-right thresholds; shared dashboards; SLAs across seams; portfolio management to reduce WIP; sponsor agreements.

Linkages and sequence: LaFasto–Larsen emphasize an “inside-out” approach. Start by elevating the expectations and behaviors of members, then establish trust-based relationships that can carry constructive conflict, then formalize problem-solving mechanics, then enable and coach through leadership, and finally tune the environment. Skipping early work raises the cost of later fixes.

4. When to Use the LaFasto–Larsen Model

Most helpful when:

• Standing up or rebooting cross-functional teams where friction and handoffs derail outcomes.
• Diagnosing recurring team issues that aren’t solved by more meetings (missed commitments, re-litigation, low engagement).
• Developing team leaders who must balance challenge, support, and system navigation.
• Scaling agile/product operating models—aligning human dynamics with cadences and decision rights.

Especially powerful: As a shared language for executive teams and program squads to identify the one or two dynamics holding them back right now and apply targeted fixes.

Less suitable or potentially misleading: If treated as a personality typology (it isn’t), or used as “team-building” without adjusting decision rights, incentives, or cadences. For independent working groups with minimal interdependence, simpler coordination tools may suffice.

Contemporary use: Often paired with GRPI/Hackman for design, Lencioni for interpersonal norms, and operating tools (OKRs, RACI, decision logs) to translate dynamics into daily practice.

5. How to Apply the LaFasto–Larsen Model: Step-by-Step

1. Clarify outcomes and interdependence.

   Write a one-page mandate: purpose (why now), 3–5 measurable outcomes (with baselines/targets), scope in/out, constraints, and horizon. Confirm you truly need a team (shared products) vs. a working group.

2. Baseline the five dynamics.

   Use a short pulse (Likert items per dynamic) plus artifact review and observation. Examples:

   • Member: “We keep commitments; we ask for/offers of help are common.”
   • Relationships: “It’s safe to raise risks; conflict stays on issues.”
   • Problem-solving: “Decisions are documented with owners and dates.”
   • Leadership: “Our leader invites dissent and closes with clarity.”
   • Environment: “Incentives and approvals support our outcomes.”

   Triangulate with data: decision lead time, rework, escalations, engagement.

3. Start inside-out: elevate Team Member expectations.

   Co-create behavior standards (e.g., prepare; be concise; deliver or renegotiate; give/ask for feedback each sprint). Make commitments public; recognize exemplars. Address individual gaps with coaching.

4. Codify Team Relationships (norms) and practice them.

   Run “working with me” exchanges; agree conflict/feedback norms (time-box debates; decision criteria; “say it in the room”; “disagree and commit”). Rotate facilitation to balance airtime and inclusion.

5. Install Team Problem-Solving mechanics.

   Adopt a cadence (weekly stand-up, biweekly review/demo, monthly retro). Define top 5–10 decisions with RACI/RAPID; use decision logs (what/why/owner/date/what would change our minds). Ensure data access and shared dashboards.

6. Coach Team Leadership behaviors.

   Leader (and deputies) model the norms; clarify priorities; remove obstacles; manage stakeholders; protect focus; provide specific recognition. Use peer feedback on leader habits (“what helped/what to try next”).

7. Align the Organizational Environment.

   Secure sponsor agreements on priorities and escalation paths. Adjust incentives to include team outcomes. Right-size approvals and SLAs across seams. Provide tools/data the team needs; reduce WIP via portfolio decisions.

8. Deliver early shared wins and iterate.

   Target a meaningful joint deliverable in 4–8 weeks. Review outcomes and the five dynamics monthly; pick one dynamic to improve each cycle. Refresh norms and artifacts as membership or scope changes.

6. Example: The Five Dynamics in Action

Context: A $800M regional bank forms a cross-functional “Digital Onboarding” team (Product, Engineering, Risk, Compliance, Marketing, Operations) to cut account-opening time from 3 days to under 30 minutes and raise completion rates by 15 points. Prior efforts bogged down in risk/compliance approvals and inconsistent handoffs.

Application:

• Team Member: The lead sets expectations: prepare; surface risks early; deliver or renegotiate; feedback each sprint. Individuals write “working with me” profiles with strengths and triggers.
• Team Relationships: Norms agreed: challenge ideas, not people; time-boxed debates with decision criteria; “say it in the room”; rotate facilitation; include remote members deliberately (airtime tracking).
• Team Problem Solving: OKRs set (median onboarding time to 20 minutes; completion +15 pts; abandonment −40%). RACI/RAPID mapped for risk exceptions, UI changes, vendor choices. Decision log adopted; shared funnel dashboard created; weekly stand-up and biweekly review/demo established.
• Team Leadership: Product lead invites dissent, then closes with “disagree and commit.” The lead negotiates an SLA with Compliance: low-risk changes reviewed in 48 hours; higher-risk in 5 days with criteria pre-agreed. Leader recognizes cross-functional help publicly.
• Organizational Environment: Sponsors (CIO, CRO) align incentives to include time-to-open and completion rates; approve exception thresholds; dedicate a risk analyst to the team; reduce approval layers for low-risk experiments.

Outcomes (10 weeks): Median time-to-open cut to 34 minutes; completion rate +11 points; abandonment −29%. Decision lead time dropped 55%; escalations down 40%. Team pulse improved 17 points on “conflict is constructive,” 15 points on “decisions are clear,” and 14 points on “leaders remove obstacles.”

7. Strengths and Limitations

Strengths

• Sequenced and holistic: Integrates individual behavior, relationships, mechanics, leadership, and environment in a practical order.
• Actionable: Provides specific norms and operating mechanisms to install; easy to combine with OKRs, RACI, and agile cadences.
• Leader-friendly: Clarifies what leaders must do (and stop doing) to enable teams.
• Diagnostic clarity: Helps teams pick the one or two dynamics to fix now for outsized impact.

Limitations

• Not a silver bullet: If incentives, capacity, or decision rights are misaligned, dynamic work helps but won’t overcome systemic blockers without organizational change.
• Behavior change load: Requires consistent modeling and reinforcement; one-off workshops fade without operating changes.
• Evidence nuance: Strong practice-based support; like most team models, causal proof in complex settings is probabilistic, not deterministic.
• Risk of generic application: Teams differ—diagnose before prescribing; don’t apply all interventions at once.

8. Common Pitfalls (and How to Avoid Them)

• Starting with process, skipping people.
  What goes wrong: Great cadences, low trust; conflict goes underground.
  Avoid by: Setting member expectations and relationship norms first; then add mechanics.
• Norms on paper, not in meetings.
  What goes wrong: “Say it in the room” becomes a poster; triangulation persists.
  Avoid by: Rotating facilitation, airtime tracking, and closing meetings with explicit decisions and owners.
• Leader overreach or abdication.
  What goes wrong: Micromanagement kills ownership; hands-off leadership lets drift and ambiguity grow.
  Avoid by: Inviting dissent, setting standards, closing decisions, and removing blockers—then getting out of the way.
• Re-litigating decisions.
  What goes wrong: Momentum stalls; accountability blurs.
  Avoid by: Logging decisions with rationale; using “disagree and commit”; defining what new evidence reopens a call.
• Ignoring the environment.
  What goes wrong: Approvals and KPIs contradict team goals.
  Avoid by: Aligning incentives and thresholds; securing sponsor SLAs; reducing WIP.
• One-time push.
  What goes wrong: Gains decay as membership/scope shifts.
  Avoid by: Monthly check-ins on the five dynamics; mini-resets when context changes.

9. How LaFasto–Larsen Relates to Other Frameworks

• Hackman Five Conditions: Hackman sets preconditions (real team, direction, structure, context, coaching). LaFasto–Larsen is the inside-out behavior and operating guide within those conditions. Use Hackman for design/context; LaFasto–Larsen for ongoing team practice.
• GRPI (Goals, Roles, Processes, Interpersonal): GRPI provides a design checklist. LaFasto–Larsen adds leadership and environment explicitly and sequences improvement from member → relationships → problem-solving → leadership → environment.
• Lencioni Five Dysfunctions: Lencioni focuses on trust, conflict, commitment, accountability, results—mapping to the relationships and problem-solving layers. Pair with LaFasto–Larsen for leadership and context levers.
• Tuckman Stages / Drexler–Sibbet: These describe the team journey and key questions by stage. LaFasto–Larsen prescribes the behaviors and mechanisms to progress at each stage.
• Katzenbach–Smith: Defines “real team” basics (small, complementary skills, purpose, goals, approach, mutual accountability). LaFasto–Larsen shows how to enact those basics day-to-day and extend to leadership/environment.
• Belbin Team Roles: Useful for the Team Member layer (behavioral contributions). Use Belbin to balance preferences; LaFasto–Larsen to set norms, mechanics, and leadership that leverage those contributions.
• Operating tools (OKRs, RACI/RAPID, decision logs, agile): These instantiate the Team Problem-Solving and Leadership layers so behaviors stick.

10. Key Takeaways

• The LaFasto–Larsen model organizes team effectiveness into five dynamics: member behavior, relationships, problem-solving mechanics, leadership, and environment.
• Improve teams inside-out: set clear behavior standards for members, codify trust-based norms, install decision/ execution discipline, coach leadership, and align systems.
• Use it as a targeted diagnostic—fix the one or two dynamics holding you back; don’t boil the ocean.
• Pair with design frameworks (Hackman, GRPI) and operating tools (OKRs, RACI, decision logs) to convert behavior change into performance.
• Sustain gains with early wins, monthly check-ins, and environment alignment; revisit as scope or membership changes.

11. FAQs About LaFasto–Larsen Five Dynamics

Is this model the same as Lencioni’s Five Dysfunctions?
No. There’s overlap (both stress trust and productive conflict), but LaFasto–Larsen adds explicit layers for problem-solving mechanics, team leadership, and organizational environment, and it sequences improvement from individuals outward.

Do we have to work through the dynamics in order?
Use the “inside-out” sequence as a default. If member behavior and relationships are weak, process fixes won’t stick. That said, diagnose first—sometimes a clear process change (e.g., decision logging) quickly improves relationships by reducing ambiguity.

How do we measure progress?
Track a small basket: outcome metrics (e.g., cycle time, NPS, defect rates), decision lead time and re-litigation, escalations, on-time delivery, plus pulses on clarity, psychological safety, and perceived leadership support. Review monthly.

Can small teams or leadership teams use this?
Yes. The dynamics scale from two-pizza squads to executive teams. For exec teams, pay special attention to the environment layer (incentives and governance) and to mutual accountability in the relationships layer.

How long does it take to see impact?
With disciplined application, you can see early shifts (decision clarity, fewer escalations, more candid debate) in 4–8 weeks. Hard results typically move over one to two quarters as behaviors are reinforced by leadership and system changes.

What’s the quickest way to start?
In 30–60 days: set member behavior standards, agree conflict/feedback norms, adopt a decision log with owners and dates, establish a basic cadence (stand-up/review/retro), and secure sponsor SLAs for approvals. Deliver one shared win to build momentum.