Team Focus
Use when asked to apply McKinsey's TEAM FOCUS framework — the interpersonal TEAM half (Talk, Evaluate, Assist, Motivate) and the analytical FOCUS half (Frame, Organize, Collect, Understand, Synthesize) — for structuring both team dynamics and a problem-solving process together.
TEAM FOCUS is a framework developed by McKinsey & Company combining two complementary halves: TEAM addresses interpersonal team effectiveness; FOCUS addresses the analytical structure of the problem-solving process itself. Applying only one half addresses just part of what makes a team's work actually succeed.
TEAM (interpersonal)
- Talk — establish genuinely effective communication channels; this is foundational, not a nice-to-have, since every other element depends on information actually flowing.
- Evaluate — assess performance and adapt accordingly, rather than running on assumption about how things are going.
- Assist — help each other; strategically leveraging each person's unique capabilities is a defining trait of genuinely high-performing ("special forces") teams.
- Motivate — pay close attention to what actually drives individual team members — generic motivation tactics matter less than understanding each person's real drivers.
FOCUS (analytical)
- Frame — before starting, identify the key question being studied, draw issue trees exploring potential lines of investigation, and develop hypotheses to test — framing well up front prevents wasted effort investigating the wrong question.
- Organize — a necessary, if unglamorous, step preparing the team for efficient problem-solving, organized around the content hypotheses with the end goal in mind.
- Collect — gather relevant data, deliberately avoiding over-collection of data that won't actually contribute to answering the key question.
- Understand — evaluate collected data for what it actually contributes to proving or disproving the hypotheses — the discipline of repeatedly asking "so what?" rather than just accumulating findings.
- Synthesize — turn analyzed data into a compelling narrative; this is where the well-known "pyramid principle" (leading with the conclusion, then supporting detail) shapes how a report or presentation is structured.
Why both halves matter together
A team with excellent interpersonal dynamics (TEAM) but no analytical discipline (FOCUS) can collaborate wonderfully while solving the wrong problem, or drowning in irrelevant data. A team with rigorous analytical process but poor interpersonal dynamics burns out or fractures before the analysis can be completed well. TEAM FOCUS treats both as necessary, not as a choice between them.
Common pitfalls
- Skipping Frame and jumping straight to Collect — gathering data before the key question and hypotheses are actually defined risks collecting the wrong data, or far more than actually needed.
- Treating Understand as just "presenting the data" — the "so what?" discipline is what turns raw analysis into an actual answer to the framed question; skipping it leaves conclusions implicit rather than stated.
- Ignoring the TEAM half entirely — a purely analytical approach to FOCUS without attention to Talk/Evaluate/Assist/Motivate risks a technically sound analysis delivered by a team that's burned out or miscommunicating along the way.
- Synthesizing without the pyramid principle — burying the actual conclusion under supporting detail, rather than leading with it, makes even well-supported findings harder for an audience to act on.
Learn more
- Ways of Working for related team-communication and collaboration principles.
- Decision Tree, Mental Model for structuring the Frame stage's hypothesis development.