KiTalent · Research · Book From Interviewing for Skills and for Identity
Chapter 10

Building and Leading Senior Teams

A lone oak tree

A search firm holds one instrument for this cluster that nobody else has, and it took me years to realize we were holding it. When you map an executive market, any market, any country, the strong candidates are not evenly distributed across the companies that employed them. They cluster. The same three or four names recur, generation after generation, as the boss under whom today's CFOs and country managers were made; in Milan we could name them, in Munich we could name them, and I suspect you can name them in your own market right now. Recruiters call them trees: executives whose former deputies now run half the sector. And the map shows deserts too: big names, celebrated careers, decades of large teams, out of which, somehow, nobody ever grew.

That map is a longitudinal record of the capability this chapter assesses, compiled by the market itself over twenty years, and it points at the cluster's uncomfortable truth: the truest test of senior-team leadership is administered too late to help you — it is what the team becomes, and what its people become, after the executive is gone. Trees and deserts are visible in hindsight. Your job is to assess them in advance, in a candidate who arrives, always, with the same two words on the CV: great team.

What it is, and what it predicts

Define the cluster as the capability to compose, grow, and orchestrate a team of senior leaders — not people management in general, which is a middle-management competence the strataplex left behind two levels down, but the executive version: shaping the top table itself. Behaviorally, five collectable components. Choosing: the candidate's own track record as a picker of senior people — their hires and promotions as a portfolio with outcomes. Developing: growing deputies into successors — stretch allocation, feedback that lands at senior level, the patience to let someone learn expensively. Exiting: acting on senior misfits with both speed and dignity — distinct from Chapter 9's accountability conversations, which hold people to commitments; this is the harder compositional act of concluding that a person, however liked, is wrong for the table. Team mechanics: converting a group of barons into a team — a shared agenda, conflict that happens in the room rather than after it, the conditions under which senior people tell each other the truth. Multiplying rather than hoarding: delegating real authority, building succession depth, and — the tree-versus-desert variable — tolerating, even sponsoring, the export of talent one has grown.

What it predicts is anchored in one of the oldest and most replicated findings in the field: in the original derailment studies and everything since, the inability to build and lead a team is among the classic career-enders for executives — routinely near the top of the derailer lists, ahead of most technical failings. From the constructive side, the leadership meta-analyses give solid support to the developmental behaviors at this cluster's core (the individualized consideration component of the transformational family is the well-evidenced part, carefully separated, in this book, from the charisma component Chapter 1 taught you to distrust). And Chapter 1's portability findings return here with a twist worth savoring: Groysberg's stars kept their performance when they moved with their teams, which means team-building capability is not adjacent to executive performance; for many executives it quietly is the performance, embodied in other people.

This cluster's special epistemic hazard, named upfront as the anatomy requires: the inherited machine. An executive who takes over a strong, well-built senior team can coast on it for a year or two while it masks every deficit this chapter cares about, and the CV will read led a high-performing team with perfect technical truth. Ch. 9's hazard was attributing results; this cluster's is attributing people. The probe architecture below is therefore an archaeology: built, inherited, or borrowed, layer by layer.

How it fakes

The vocabulary here is the cheapest in the executive lexicon, because the culture has spent thirty years teaching it: I hire people smarter than me. A-players hire A-players. My job is to make myself unnecessary. Every candidate says it; the faking research tells you the specific forms the polish takes when you probe beneath.

Borrowed alumni: impressive names claimed as protégés who were, on inspection, already made when the candidate arrived — development by proximity. The loyalty exhibit: long team tenure offered as proof of leadership when it may be proof of comfort — a court retains people too, and retention without growth is the desert's most convincing disguise. The tough-love trophy: the rehearsed senior-exit story (it overlaps Chapter 9's pre-brutalized accountability tale — same script, different scorecard line). The modesty dodge: my team did everything deployed as humility that also, conveniently, dissolves every question about the candidate's own choices into the collective — and remember Chapter 17 before scoring it: the same surface is produced honestly by half the world's cultures, and the cure is the probe, not the penalty. And the criteria-read: candidates know "develops talent" is on your scorecard, so protégé names arrive pre-listed. The names are the beginning of evidence, not the end — where are they now, and what would they say grew them?

The probe architecture

Layer 1 — standardized stimulus: "Take the senior team you inherited in [the relevant role] — walk me through it person by person, as it stood on your first day. Then tell me what you changed, who you bet on, and what the table looked like when you left." One prompt, and the archaeology is underway: inherited versus built is now the explicit terrain, and the choose–develop–exit components all have a stage.

Layer 2 — planned probes: Who did you promote, and what had you seen that others hadn't? Who did you move out — how long did it take from first doubt to decision, and what happened to the person? What did you change about how the team worked — the meeting, the conflicts, what could be said in the room? Where are your former deputies now? And the baron probe: every inherited senior team contains one prince running a private kingdom — who was yours, and what did you do?

Layer 3 — verification probes: Which of those people would take my call? (Watch the answer's speed as much as its content.) Who succeeded you — in this role and the one before — and where did the successor come from? What would [the exited executive] say about how their exit was handled? Each answer is a reference hook for Chapter 7's second ring, and the candidate hears it happening, which is itself a small integrity test administered live.

Layer 4 — the disconfirming pair. First: "A bet on a person that you got wrong — someone you chose or promoted who didn't work out. What did you miss, and when did you know?" Then: "Someone strong who left you — for reasons that, honestly, were at least partly about you. What did you learn?" A real team-building career contains both; the candidate who has never mis-picked has not picked much, and the candidate whom no strong person ever left has either led very briefly or is not being honest with one of you. As in Chapter 9, listen for the asymmetry: real builders are more precise about their picking errors than the record demands, because the errors taught them their craft.

One probe deserves its own paragraph because it is this cluster's cleanest single instrument: the successor question. "Who replaced you in your last two roles, and where did they come from?" It is short, factual, externally verifiable in minutes, and brutally diagnostic: internal successors the candidate visibly grew are the tree showing itself; a pattern of emergency external replacements behind them is the desert, with innocent explanations (boards choose successors; reorganizations intervene) that exist and must be checked, per the next panel, before the score moves.

In the room, and only outside it

What shows live is how the candidate holds people in language. Real builders describe their people with individuated precision — this one's edge, that one's fear, the specific thing the third one needed to hear in year two — and with a warmth that stops short of ownership; hoarders and coasters describe functions ("my CFO was solid, sales was a problem"). Listen for developmental verbs attached to named humans. Listen, too, to how a difficult former subordinate is rendered: respect for a person who didn't work out is craft; leaked contempt is a flag this chapter registers and Part IV interprets. And their questions about your client's team are the cluster performing itself: the builder asks who is on the table, who is ready for more, and who has been waiting too long, because they are already doing the archaeology on your client.

What only references hold is the other side of every story above, and this is the cluster where Chapter 7's symmetry check stops being advice and becomes the method: bosses structurally cannot see this capability; it happens below them. The decisive witnesses are the direct reports and the protégés, reached through the second ring, and the market map itself, where the firm's own longitudinal knowledge of trees and deserts is, used honestly and verified case by case, legitimate corroborating evidence. What nobody holds pre-hire is the two-years-after test; the closest available proxy is the pattern across the candidate's full history, which is why Layer 1 excavates more than one role.

Red flags — with their innocent explanations

No traceable protégés across a long career. Innocent: short tenures, flat structures, businesses where development genuinely diffuses. Across fifteen senior years, though, the desert reading strengthens with every role checked. Turnover spike on arrival. Innocent: a mandated cleanup; check the mandate (Chapter 3's archaeology) before charging the person, because some tables needed clearing. Nobody ever left. Innocent: superb retention exists, and the differentiator is growth. Did the stayers' scope expand, or did loyalty substitute for development? A court also has excellent retention. Successors always external. Innocent: succession is often the board's call, made above the candidate's head; verify whose decision it was before scoring. Contempt in the telling. Innocent once, since some former colleagues earned it. As a pattern, it forecasts how your client's team will one day be described, and it routes an identity question (what do other people's limitations mean to this person?) to Part IV, where it belongs.

The reference question

Run through Chapter 7's two-level method, with the second ring deliberately weighted toward direct reports and named protégés. Frequency, to a former report: "How often did you see them hand someone a stretch that risked short-term results — routinely, occasionally, never?" Episode: "They told us about [the senior exit]. You saw it from the team's side — how was it done?" To a claimed protégé: "They named you as someone they developed. What specifically did they do — can you point to a moment?" (The pause here is the data; genuine protégés answer this question with a story that has been waiting years to be asked for.) Calibration, plural by design: "Would you work for them again — and who else from that team would?"

Scorecard anchors

2 — Below the bar. Team narrative runs at function level; claimed protégés dissolve under verification into proximity; exits handled by avoidance, delegation to HR, or brutality; the inherited machine claimed as built; successor question yields externals and shrugs. Second-ring reports hesitate at "work for them again."

3 — At the bar. At least one verified development story with a living witness and one senior exit confirmed, from the team's side, as timely and dignified; credible improvement in how the team worked; a succession answer that includes at least one internal name; the modesty or confidence of the telling survives probing into individuated knowledge of their people.

4 — Distinguishing strength. A verifiable alumni pattern across roles — the tree visible in the market map and confirmed by protégé testimony; internal successors they demonstrably built; at least one unlikely bet that paid, described with more credit to the person than to themselves; a table that survived their departure without collapse; second-ring reports who volunteer the best-boss register unprompted and start naming other witnesses before you ask. The desert's opposite, in evidence.

The seam with Part IV

The skills above are assessable, and beneath them sits something the skills method will keep grazing without capturing: what other people's growth means to this person. Hiring someone better than yourself is, technically, a decision; being able to bear it is not a skill. It is ego regulation, security of identity, the relation between one's worth and one's indispensability: the difference, at root, between the executive who builds a tree and the one who, with identical vocabulary and better stories, builds a court. Layer 4's second question ("someone strong who left you...") is where this surfaces if it surfaces at all in the capability interviews; flag what you see, hand the thread to Chapters 20 and 22, and resist scoring it here. This chapter measures whether they can. Part IV asks whether, in your client's world, they will.

Where the rules run out

The honesty paragraph. The derailment anchor is old, replicated, and solid; the developmental-behavior evidence is meta-analytic but drawn from broad managerial samples, and its transformational-leadership packaging carries a construct fuzziness this book handles by leaning on the individualized-consideration component and refusing the charisma halo. The alumni-tree instrument is practitioner observation, longitudinal and self-correcting and unpublished; it is marked [T] and used as corroboration, never as verdict, not least because market memory carries its own biases about whom it credits. The two-years-after test, the cluster's real criterion, is unobservable pre-hire by definition; everything here is a proxy for it, and the anchors above should be piloted and then corrected by Chapter 25's calibration log. This cluster, more than any other, is where a firm that tracks its placements will eventually know things the literature does not.

Notes and sources

Evidence grades: [M] meta-analytic/systematic; [L] peer-reviewed primary; [S] credible practitioner/survey; [T] flagged practice-derived observation.

  • Inability to build and lead a team as a classic derailer: McCall & Lombardo, "Off the Track" (CCL, 1983) and the derailment tradition since; Hogan derailer framework. [L/S]
  • Developmental leadership behaviors (individualized consideration; construct cautions on the transformational family): Judge & Piccolo (Journal of Applied Psychology, 2004); DeRue, Nahrgang, Wellman & Humphrey (2011). [M]
  • Team conditions for candor and learning: Edmondson, psychological safety and team learning research (1999 and successors). [L]
  • Stars retaining performance when moving with teams: Groysberg, Chasing Stars (2010). [L]
  • Internal versus external succession economics: Bidwell (2011), per Chapter 1. [L]
  • Faking forms, criteria-reading, modesty norms: Levashina & Campion; Kleinmann's ATIC research; cross-cultural self-presentation evidence (Ch. 17 sources). [L/M]
  • The alumni-tree market map; the successor question as instrument: this book, from search practice. [T]
  • Five-component packaging and anchors: this book's synthesis. [T]
About the author

Alessio Montaruli

Founder & Group CEO, KiTalent

Alessio Montaruli holds an MA in Theoretical Philosophy from the University of Turin, with additional study at the University of Freiburg. He is the Founder and Group CEO of KiTalent.

LinkedIn profile