IX. Why This Matters — The Question HR, Headhunters, and Boards Almost Never Ask Out Loud

Given that a real, documented diversity of effective leadership styles exists, and given that Implicit Leadership Theory shows that most evaluators do so against a fixed mental prototype of the leader — a mental image, a set of already-formed impressions — without knowing they're doing it, the question rarely asked — and that should be the first one in any senior hiring process — is:

Is the leadership actually being hired, or is it the image of leadership already fixed in our heads before the first interview even opens?

The Formula Almost Always Left Out

The KSAO model — Knowledge, Skills, Abilities, Other characteristics —, standard in industrial-organizational psychology for decades, already contains the answer to what should be measured. Knowledge and skills are the two letters almost every process evaluates with reasonable rigor. Abilities — underlying capacity, not just trained skill — already starts to dilute. And the "O" — traits, values, motivation, congruence — is systematically the one left out, precisely because it's the hardest to verify quickly.

Kristof-Brown, Zimmerman, and Johnson, in a 2005 meta-analysis, formalized a distinction almost no process separates: Person-Job fit (can they do the work?) versus Person-Organization fit (are their values congruent with the culture?). Most processes evaluate the first and take the second for granted, unverified.

One more honesty is worth adding before moving on, because it concerns the real limit of everything this article has proposed so far. KSAO, Person-Organization fit, the twenty-five-cell matrix from Part VIII — these are frameworks, not closed equations. They give evaluation a common structure, comparable across people and across different organizations: that's what makes them useful, and it's real. But no framework, however rigorous, resolves on its own the particular case in front of you. It's, allowing for the analogy, like solving an integral: the general formula predicts the shape of the curve — and then there's the constant, the +C, that no formula can fix in advance because it depends entirely on the specific initial condition it's given. The values any healthy ecosystem needs — integrity, congruence, psychological safety — are, in that sense, the universal part of the equation. But how those values show up in this particular person, at this particular moment in their career, within this particular culture, is the constant no framework calculates ahead of time. The formula guides judgment. It doesn't replace it.

When Not Even the Job Itself Is Clearly Named

There's a layer to this problem that happens before evaluation even begins, and it deserves its own name because it isn't evaluator bias — it's a design failure in the job posting itself. Robert Kahn, Donald Wolfe, Robert Quinn, Diedrick Snoek, and Robert Rosenthal, in their foundational work on organizational stress (1964, still one of the most cited in all of organizational psychology), formalized the concept of role ambiguity: the lack of clarity about a job's expectations, scope, and success criteria, documented as one of the most consistent and best-studied sources of work-related stress that exist.

In architecture and engineering, this ambiguity takes a very concrete, very recognizable form: posting a vacancy for "Principal" — a role of technical and business leadership, often on a partnership track, oriented toward client development and strategic project direction — when what the organization actually needs, and what it effectively interviews and evaluates for, is a "Job Captain" — a role focused on coordinating and technically reviewing construction documents, centered on drawing consistency and quality control, without the strategic or business dimension the title "Principal" implies anywhere in the world. In industry practice, these are two roles with almost opposite responsibilities, authority expectations, and career trajectories, and confusing them in the posting isn't a semantic nuance — it's exactly the role ambiguity Kahn and colleagues documented as a measurable source of harm, now transferred from the already-hired employee to the candidate who doesn't even know yet what real position they're being evaluated for.

And that ambiguity rarely runs along a single axis. It often compounds across several at once: not just seniority (Principal vs. Job Captain), but also function (Project Manager, oriented toward scope, budget, and client relationship, confused with a shop or office head, oriented toward internal operations and production). When both axes go misaligned at the same time, the candidate isn't calibrating their preparation against a single poorly defined role — they're calibrating against two distinct, overlapping definitions of success, without anyone in the process having noticed the overlap. It's the same role ambiguity from Kahn and colleagues, just compounded: not one axis of uncertainty, but two crossing inside the same job posting.

And when a third layer gets added on top of that — the language the process is conducted in doesn't match the language the posting was written in, or the required proficiency level was never precisely specified — the candidate ends up absorbing three simultaneous sources of role ambiguity in a single process: they don't know for certain what the job is, they don't know for certain what function is expected of them, and they don't know for certain what language they'll be evaluated in or by what standard. None of these three ambiguities is the candidate's fault. All three are, exactly as Kahn's literature predicted back in 1964, the responsibility of a system that never precisely defined what it was asking for before it started asking.

When the Guessing Game Wears the Costume of Rigor: Cultural Fit

Lauren Rivera (Pedigree: How Elite Students Get Elite Jobs, 2015) documented that "cultural fit" at elite firms functions as a proxy for social class, school, and shared cultural capital — not for genuinely shared values. The correction: from cultural fit to cultural add — not "do they resemble us?" but "what do they add to the ecosystem, and what would the ecosystem need to change for their real capability to deliver?"

An image is worth using here that sums up the cost of not asking that question: a profile of the highest capability — epistemic authority, say — placed in the wrong ecosystem isn't lost to incompetence. It sits unused, like a Ferrari covered in dust in a parking lot, engine intact, with no road designed for it to run on. The question that falls to whoever's hiring isn't just "is this person competent?" — it's "am I willing to invest in building the ecosystem where that capability actually delivers?" That turns cultural add from an evaluation question into an investment question.

And here a distinction is worth making that avoids falling into the same trap this article has been flagging all along: there is no legitimate fit of origin — resembling the group already, before joining, is exactly the class bias Rivera documented, and nothing that follows contradicts that. But there can exist, and it's worth actively pursuing, a fit of destination: genuine social integration into a group, deliberately built after the person is already inside, not demanded as a condition of entry. Gregory Walton and Geoffrey Cohen, in a randomized experiment published in Science (2011), demonstrated this with a precision rare in psychological interventions: a brief intervention, designed to reduce first-year college students' uncertainty about whether they belonged in their new environment — framing social adversity as common and temporary, not as a sign they didn't fit — raised African American students' GPA in a sustained way over three years, cut the achievement gap with white students in half, and improved their reported health and well-being. None of the participants, by the end of the study, was aware they'd received the intervention.

The difference from fit of origin couldn't be clearer: no one was filtered for already resembling the rest of the campus — they were, in fact, the ones who least matched the institution's dominant social profile. What the intervention deliberately and measurably built was belonging itself, as a destination earned through real investment, not as an entry requirement verified in an interview. That's the fit worth pursuing inside any organizational ecosystem: not the kind that decides who gets through the door, but the kind an organization actively builds, with real resources and real time, once the person is already inside — the exact same investment logic the dust-covered Ferrari called for a paragraph back.

And the image has a flip side worth naming with the same clarity: that same Ferrari, once given the right road, doesn't just stop sitting idle — it improves the road itself. An exemplar with epistemic authority, placed in the generative crossing described in Part VIII's matrix, doesn't just deliver their own capability: they raise the standard of rigor and judgment for the entire team around them, because their way of leading — showing the reasoning, not just the conclusion — builds transferable capacity in the people around them, not dependence on them. Investing in the right ecosystem for this profile isn't just avoiding wasted talent. It's one of the few investments documented in this article that grows the whole pie, not just divides it better.

The Uncomfortable Fact About How We Actually Predict Performance

Frank Schmidt and John Hunter, in Psychological Bulletin, 1998, synthesized the most complete meta-analysis ever conducted on the predictive validity of selection methods. The unstructured interview — the one that dominates the vast majority of real hiring processes — has a predictive validity of barely ~0.38 with subsequent performance. The method with the highest validity of all those evaluated is an actual work sample, ~0.54: evaluating what the person actually produced, not how they carried themselves socially for half an hour under artificial pressure.

And That Error Hits Unevenly

Prioritizing work evidence over interview performance turns out, almost as a side effect, to be the most inclusive way to evaluate talent — it doesn't penalize unconventional communication styles or different ways of processing a question under pressure. Holly White and Priti Shah found, across two studies (2006, 2011), a specific, non-uniform pattern: adults with ADHD-associated traits outperformed adults without ADHD on divergent thinking — generating more original ideas — and, in the 2011 study, on real, world-verifiable creative achievement, though the 2006 study also found that same group performed worse on convergent thinking tasks — arriving at a single correct answer. It's not that neurodivergence guarantees more creativity across the board; it's that it excels specifically at divergent idea generation, precisely the kind of thinking a structured interview built to evaluate "the correct answer" tends not to know how to read.

This isn't limited to ADHD, or to architecture. Simon Baron-Cohen, along with Sally Wheelwright, Carol Stott, Patrick Bolton, and Ian Goodyer, documented in 1997 that parents and grandparents of children with autism showed up, in the sample studied, more than twice as often in the engineering profession as those of other children — evidence of a real cognitive link between autism-spectrum traits and the capacity to systematize complex patterns, the same capacity underlying engineering, data science, and related technical disciplines. In architecture, industrial design, engineering, data science, academic research, and other high-systemic-demand disciplines, multiple studies report a prevalence of ADHD, autism, and giftedness traits above the general population — often, the same cognitive profile that sustains complex systems thinking and genuine tolerance for multivariable ambiguity, the natural terrain of epistemic authority.

And it's worth naming something almost never mentioned together: these three conditions — ADHD, autism, and giftedness — aren't mutually exclusive categories. James Webb and colleagues, in their reference work on dual diagnosis in gifted populations (2005), documented that these three conditions overlap and get confused with each other with enormous frequency — a gifted child or adult can show the same pattern of motor restlessness, intense hyperfocus, or social difficulty that an evaluator without specific training automatically labels ADHD or autism, when in reality they're manifestations of an intellectual capacity the environment failed to accommodate — to the point that misdiagnosis, in either direction, is, according to their research, more the rule than the exception. A selection process that evaluates through social interview instead of work evidence doesn't just fail to distinguish ADHD from epistemic authority: it fails to distinguish any of these three conditions, frequently overlapping in the same person, from the social noise a traditional interview format is designed to reward.

The Adjustment Period Almost No One Considers Anymore

There's one more piece rarely part of this conversation, and it directly worsens the problem of misreading short tenure: the practical disappearance, in many current processes, of a genuine probationary period — understood not as a legal formality, but as an honest window of mutual adjustment between person and ecosystem. John Van Maanen and Edgar Schein, in their foundational work on organizational socialization (1979), documented that integrating into a new culture — understanding its real underlying assumptions, not just its stated values — follows a predictable curve that takes time, almost never less than several months in a genuinely responsible role. Michael Watkins formalized that same curve in more operational terms in The First 90 Days (2003): a new executive needs, almost universally, a period of learning the system before their performance reflects their real capability, not their initial unfamiliarity with the terrain.

When that period is shortened or disappears — when performance on unfamiliar terrain is expected from week one, or when a tenure of a few months gets read as failure without first asking whether there was even a real opportunity to complete the adjustment curve — the system is, once again, measuring wrong: it's evaluating the orientation phase as if it were the stable-performance phase, and penalizing the person for a curve the organization itself never gave them time to travel. It's the same root error Schmidt and Hunter document on the interview side — judging with the wrong instrument — now applied to time instead of method.

Short Tenure, Read the Opposite of How It's Usually Read

Michael Arthur and Denise Rousseau documented the concept of the boundaryless career: frequent movement between organizations isn't, in itself, evidence of instability. It's often the signal of someone who reads, faster than average, when an ecosystem is incompatible with what they need to deliver — and acts accordingly, instead of spending years absorbing an already-identified dysfunction. ("La Ilusión del Camino Recto" develops this same tension in more detail: why the linear career path stopped being the standard against which to measure competence, and what gets lost when we keep evaluating talent as though it still were.)

But "it isn't instability" is, on its own, an insufficient defense — it leaves the conversation on the ground of reasonable doubt, not evidence. What actually allows short tenure to be evaluated rigorously is separating three questions almost always merged into one:

• Evidence of impact — what did they produce, verifiable beyond their own account? A project delivered, a documented efficiency gain, a system that keeps working after they left.

• Judgment — did the departure reflect a reasoned reading of the ecosystem — a mismatch of values, an absence of governance, a structural ceiling — or a reactive pattern with no diagnosis?

• Integrity and congruence — not the tenure itself, but whether the same values, the same judgment, and the same way of working hold up recognizably across different ecosystems. This is verifiable with considerably more precision than it seems: professional relationships the person keeps active beyond the organization that originated them, projects former colleagues or former bosses call them back to by their own choice, references that describe the same behavioral pattern across completely different companies. Congruence isn't staying — it's whoever crossed paths with that person in more than one place independently describing the same person.

And when those traditional references don't exist — the increasingly common case of someone who built an independent practice, their own platform, or documented achievements outside the structure of an employer who could vouch for them — the evidence doesn't disappear, it just changes form: public deliverables, their own publications, clients who return by choice, a verifiable body of work with no need for a former boss to confirm it.

It's also worth naming, plainly, something almost never said out loud within a hiring process: the generic suspicion that someone with a non-linear career "must have something wrong with them" — the same prejudice of assuming they're a bad person before even meeting them — has, in the vast majority of cases, no statistical foundation whatsoever. Genuinely toxic profiles in the clinical sense are, according to available epidemiology, a real minority within any population: Frank Stinson and colleagues, in the reference NESARC study (2008), documented a lifetime prevalence of narcissistic personality disorder of 6.2% in the general population; William Compton and colleagues, in a comparable representative sample (2005), documented a prevalence of antisocial personality disorder of 3.6%. Even adding both disorders without overlap, more than ninety percent of any group of candidates fits neither one. Treating the ambiguity of a career path as presumptive evidence of pathology is, statistically, almost always an error — and is, almost always, the same mechanism as the fixed mental prototype of the leader described in Part IV, in darker vocabulary that's harder to question out loud.

And there's a documented irony that makes this error worse still: evaluation schemes that rely on impression and charisma instead of work evidence aren't just blind to the genuinely toxic minority of profiles — they frequently prefer them actively, precisely because those profiles project the confidence, quick decisiveness, and apparent capacity to "bring order" that the same scheme confuses with leadership. Paul Babiak and Robert Hare, in their reference research on corporate psychopathy — synthesized in Snakes in Suits: When Psychopaths Go to Work (2006) — documented that traits like superficial charm, unshakeable confidence, and a willingness to make drastic decisions without hesitation, which a conventional interview process reads as "leadership material," are exactly the same traits that best predict a high-risk psychopathic profile in corporate settings — and that same charisma facilitates, rather than hinders, advancement within structures that reward impression over evidence. What that profile brings, consistently documented, isn't order: it's relational violence, the destruction of entire teams, and measurable waves of negative consequences the organization pays for over years after the selection process read it as strength. It's the same underlying error again: confusing the signal — confidence, charisma, decisiveness — with the substance that signal is supposed to represent.

Evaluated separately, these almost always tell a different story than the start and end dates on a résumé — and often, in fact, tell the opposite story of what that résumé suggests at first glance. A profile with verifiable impact at every stop, with reasoned judgment behind every departure, and with integrity recognizable by independent third parties across those stops, doesn't describe someone unstable. It describes, more precisely, exactly the previous section's Ferrari: a person of high capability and sustained integrity, who up to now simply hasn't found the ecosystem with the right road for them — and whose résumé, read only by dates, disguises as risk what is, in reality, accumulated evidence of good judgment.

When Technical Truth Clashes with the Commercial Goal

There's one more tension almost never part of the leadership conversation, and one that in technical professions — architecture, engineering, medicine, auditing — carries a weight other fields don't share: the moment correct professional judgment and the commercial goal of whoever's in charge don't line up. A site resident who spots that a spec cut compromises structural safety; an architect who knows a delivery date promised to a client is technically unrealistic; an auditor who sees a figure that doesn't add up. The literature on professions has had a name for this clash for decades: professional-organizational conflict (extensively documented since the 1970s in research on professionals inside bureaucracies), the structural friction between the technical standard a profession requires and the pressure of the organization employing whoever practices it.

Robert Jackall, in Moral Mazes: The World of Corporate Managers (1988), the fruit of years of direct ethnographic observation inside American corporations, documented starkly how corporate hierarchies, under sustained commercial pressure, end up producing a moral logic of their own, distinct from the individual professional ethics of those inside them — one in which telling an inconvenient technical truth to whoever holds authority becomes, over time, the decision with the highest career cost, and softening or withholding it becomes the "reasonable" decision. It is, in essence, Flight 801 again, but with the power variable in place of the cultural one: the correct information existed, the person with the technical knowledge had it, and the cost of stating it clearly exceeded, within that specific system, the apparent cost of staying silent.

This connects back, precisely, to Part V of this article: a Kelley exemplar in a technical profession doesn't just need independent judgment and commitment — they need an ecosystem where flagging technical truth doesn't compete, in daily practice, against the commercial goal of whoever's evaluating their performance. When that competition exists and isn't systematically resolved in favor of technical truth, it isn't the person who has a loyalty or attitude problem — it's the system's design that's asking, without saying so in any official document, for technical integrity to lose to commercial convenience every time the two conflict.

The Treatment Received, Specifically, by Candidates for Leadership Roles

It's worth closing this section by pointing out something that follows directly from the status-threat mechanism described in Part IV, and that has an almost mathematical logic: the higher the level of the role in play, the greater the status the evaluator has to defend if the candidate demonstrates a capability that surpasses their own — and, following Exline and Lobel, the greater the likelihood that threat translates into hostile treatment rather than genuine recognition. This predicts, uncomfortably but consistently with the evidence, that selection processes for senior leadership and top management shouldn't be, on average, more civilized than those for operational roles — they should be, if the outperformance mechanism operates with the force the literature suggests, more prone to the image clash described in this article, not less, precisely because that's where the mismatch between the real candidate and the implicit prototype has the most at stake for whoever's evaluating.

What This Means for Every Actor in the System

For HR — if the selection process doesn't explicitly distinguish between styles, the default filter ends up being the interviewer's implicit prototype, not a deliberate criterion set by the organization.

For headhunters — the work starts before the first call with the candidate, and it has three layers rarely separated consciously. First: confirm that the job description the client handed over doesn't carry the role ambiguity from Part IX — "Principal" when they're really looking for "Job Captain," "Project Manager" when they're really looking for a shop head — because no later diagnosis fixes a posting that was mis-named at the source. Second: anticipate the image clash from Part IV — ask the client, with the same directness, what mental prototype they carry fixed in their head before meeting anyone, so it can be named and flagged before it operates unnoticed during the interview. Third, once those two are handled: the question posed to the client shouldn't just be "what profile are you looking for?" but "what style does this team need, given its maturity level and its current ecosystem?" Placing epistemic authority into an ecosystem of conformists, or positional command in front of a team of exemplars, isn't a matching error — it's a diagnostic error that happened before the matching even began, and that prior diagnosis has to cover all three layers at once, not just the last one.

For the Board of Directors, owners, and shareholders — the mental image of "what a competent leader looks like" the board carries internalized determines, without anyone declaring it as formal policy, who the organization promotes and who it protects for years, even when actual performance says the opposite. A board that never examines its own implicit prototype governs by aesthetic instinct, not by evidence.

For senior executive leadership — the executive level that designs strategy, structure, and culture: vice presidencies, functional general management, the immediate circle around the CEO, distinct both from the Board, which governs from outside day-to-day operations, and from middle management, which executes without having designed anything it executes — the most direct responsibility for the five ecosystem layers described in Part VIII falls here. This is, with enormous frequency, whoever delegates downward the responsibility for a result without delegating, along with it, the real authority to change the structure producing that result. When Kanter documents that middle management gets blamed for execution failures that are really design failures, senior leadership is, almost always, who designed — or never finished designing — whatever later failed below. The question that falls to this level isn't just what leadership to hire or promote beneath itself, but what structure, what culture, and what real distribution of power it is itself building so that leadership even has somewhere to function.

For middle managers — from front-line supervisor up through functional management, deliberately grouped here as one because they share the same structural position — this is where almost everything described in this article ends up breaking hardest. It's the only position on the org chart where all three leadership directions from Part VI occur simultaneously, every day, in the same person: leading downward, following upward, and coordinating laterally with peers who don't report to them either. Floyd and Wooldridge, in The Strategic Middle Manager (1996), documented the structural tension this produces: middle managers translate strategy downward without having taken part in designing it, and translate operational reality upward without real authority to change a decision already made above them. Rosabeth Moss Kanter, going back to The Change Masters (1983), already pointed out that this layer is, with enormous frequency, held responsible for execution failures that are actually senior leadership's design failures — precisely because it's the most visible and least protected layer when something breaks.

It's also, exactly, the point where the absence of structure and process described in Part VIII — the WBS/PBS/EPS chain — hits hardest: middle management rarely designs the system it has to execute, but is the one expected to answer for its results as though it had. And it is, almost by structural definition, the point of greatest exposure to Part IV's image clash in both directions at once: it can suffer backlash from above if its judgment contradicts its superior's prototype, and lateral violence from its own team if its authority is perceived as illegitimate or poorly earned. No other level of the org chart absorbs, simultaneously, as many of the frictions this article has named one by one. If an ecosystem is going to visibly fail somewhere, the structural evidence suggests it's going to fail there first — not because middle management is the weakest link, but because it is, without having chosen it, the link carrying the greatest simultaneous tension in the whole system.

Turnover Isn't the Other Level's Fault — and It Almost Never Has a Consequence for Whoever Produces It

There's an indicator almost no organization reads correctly, and it's worth naming separately because it isn't a problem specific to middle management — it's a problem that runs through every level of the org chart equally, including the very top: the voluntary turnover rate. Bennett Tepper, in a landmark study published in the Academy of Management Journal (2000), documented with data that abusive supervision directly increases voluntary turnover, and that those who stay under that same supervision show lower affective and normative commitment, often remaining not out of loyalty but because they feel trapped, with no real alternative. This doesn't respect rank: it happens the same way to a team under a front-line supervisor as to an entire division under a CEO whose style no one on the Board dares to name.

The pattern that keeps this going is almost always the same, and it has a name. Albert Bandura, in his reference work on moral disengagement (1999), documented that two of the most common mechanisms for evading responsibility for harm caused are displacement of responsibility — attributing blame to a higher authority who "made" someone act that way — and diffusion of responsibility — spreading blame across so many people or levels that no one ends up responsible for anything in particular — and that both mechanisms are, per his own analysis, rooted precisely in organizational and authority structures. Inside a real hierarchy, this looks like: middle management blames senior leadership for impossible targets designed without its input; senior leadership blames middle management for not knowing how to "retain talent"; the CEO blames the labor market, the younger generation, or culture in general — "people just don't commit like they used to" — and each level, looking somewhere else, avoids the uncomfortable question of how much turnover its own specific leadership style is producing. No one is consciously lying by doing this — Bandura is clear that moral disengagement rarely feels, from the inside, like deliberate evasion. But the result is the same whether or not it's intentional: responsibility dilutes until it disappears, and with it, any real consequence for whoever actually produced the departure.

The cost of sustaining this pattern isn't only human: the Society for Human Resource Management estimates, as a standard industry benchmark, that replacing an employee costs between six and nine months of their salary. Each departure gets filed and explained separately, as if it were an isolated coincidence, with no one connecting the dots between accumulated turnover and the real quality of the leadership producing it at each specific level — the same error of analytical level this article has been naming since Guam, now expressed in a figure that already sits in every HR report, just almost never read for what it is, and almost never reaching, without diluting along the way, whoever actually produced it.

And there's a twist that complicates the diagnosis even further, one rarely named: not all turnover is evidence of bad leadership. It's often evidence of good leadership doing the most uncomfortable part of its job. Will Felps, Terence Mitchell, and Eric Byington, in their landmark study on group dysfunction (2006), documented that a single destructive member within a team — what's colloquially called a "bad apple" — can reduce the entire group's performance by thirty to forty percent, and that this damage frequently persists precisely because those with the authority to act lack the real power or institutional will to do so. When a middle manager does act — removing that bad apple, or the weeds that have been choking the rest of the garden for a while — that departure enters exactly the same turnover statistic as any other, with no distinction made. And the middle manager who made the correct call can end up penalized not because they were wrong, but because that correction generated real, visible friction elsewhere: a replacement search that costs time and budget, the annoyance of other departments that depended on the person removed, the short-term operational disruption any change produces. The correct correction and the original problem look, in the quarterly report, exactly the same.

This reveals something no turnover figure alone can show: what the organization actually prioritizes, beyond what it declares. If the short-term cost of removing a bad apple — the friction, the search, the disruption — systematically weighs more, in the real evaluation of that middle manager, than the long-term cost of tolerating it, the organization is revealing, through its own behavior, that it prefers the convenience of a garden with tolerated weeds over the visible cost of keeping it healthy. And when that happens, the entire work culture ends up training its middle managers not to act — not because they lack judgment, but because the system, without saying so in any document, punishes correct action almost as hard as it would punish inaction. Breaking that pattern demands something more uncomfortable than a better dashboard: it demands that every level of the hierarchy, starting with the highest, stop looking at the level below when asked why people are leaving — and learn to tell, within that same figure, how much turnover is a symptom of harm, and how much is evidence that someone, finally, decided to heal the garden.

And there's something that complicates this scenario even further, worth naming precisely because it isn't the same mechanism as the leader prototype from Part IV, even though the two frequently clash at the same time. Charles O'Reilly, Jennifer Chatman, and David Caldwell, in a landmark study (1991) that gave rise to the Organizational Culture Profile, documented that organizations also operate with a culture mold — a profile of expected values, just as precise as the implicit leadership prototype, though almost never written down anywhere — against which every person gets measured, and that fit or misfit with that mold measurably predicts job satisfaction a year later and actual turnover two years later. It's, under a different name, the same kind of template Rivera documented as a class filter disguised as "cultural fit" — except this one operates even after hiring, not just at the door.

This means that in the bad-apple scenario, there are potentially two molds clashing at once, not one. The middle manager who decides to act may not fit the expected leader mold — too direct, too willing to generate visible friction instead of maintaining the surface harmony the implicit prototype rewards. And whoever ends up replacing the bad apple may, in turn, not fit the existing culture mold — precisely because that mold was built, over time, around what the weeds tolerated, not around what a healthy garden would actually need. When both clashes happen at once, the whole system can end up reading a correct intervention as a double anomaly: a leader who "doesn't fit" and a replacement who "doesn't fit either," when in reality both are signaling, from different angles, that the original mold was never designed to sustain health — it was designed, without anyone saying so, to sustain whatever was already there.

The Exercise That Falls to the CEO — Not as Audience, But as Subject

After mapping seven leadership archetypes, five followership patterns, three directions, and five ecosystem layers, the final question can't stay at "what leadership are you hiring?" It has to turn toward whoever has the most power in the room:

What kind of leadership do you exercise, right now, with the people in front of you — the leadership you believe you exercise, or the leadership your team would describe if no one was listening to them?

Almost no executive sees themselves as pure positional command — almost all of them narrate themselves internally as visionaries, mentors, or transformational leaders, even when the real pattern they produce is systematic alienation or silent conformity. And almost no executive who talks more than everyone else in every meeting sees themselves, either, as a beneficiary of the mechanism described in Part IV — the one that confuses volume with judgment, the one from the babble hypothesis documented by MacLaren and colleagues. The honest question that follows from that finding is uncomfortable and specific: how much of your perceived authority in the room depends on genuinely having the best available read of the problem, and how much simply depends on the fact that you spoke first, spoke most, and no one stopped to check whether you were right? The gap between the style a CEO believes they exercise and the one their own matrix of followers actually experiences is, probably, the most expensive and least audited blind spot in any organization. It is, literally, the same mechanism as the captain of Flight 801: he didn't see the accident coming, not because he didn't care, but because his own self-image as a competent pilot left no room to process the signal two people, with less formal authority than him, were already giving him.

After such a long journey, it's worth returning with its full weight to the phrase that opened this article: leadership is not a problem of character. It never was. Saying it at the start was a thesis. Saying it here, after seven styles, five followership patterns, five ecosystem layers, fifty thousand years of evolution, and an algorithm that amplifies all of it, is something else — it's the conclusion that has now earned the right to state itself without hedging. It doesn't mean character doesn't matter: integrity, congruence, the value of holding on to an uncomfortable technical truth against commercial pressure, all of that is real, and this article has defended it in every one of its parts. It means something more precise, and harder to accept: that no character, however solid, is enough on its own to produce leadership that works, if the system around it — structure, culture, power, psychological safety, the implicit prototype, the algorithm — isn't designed to recognize it in time. The captain of Flight 801 didn't have bad character. Most people who exercise backlash against whoever outperforms them don't have it either, most of the time. What they all have is a system that never taught them to distinguish between the signal that confirms what they already expected to see and the signal that should have made them stop. That's why it isn't enough to ask people to have better character, more discipline, or more self-awareness — even though none of that hurts. What's needed is to design systems that don't depend on people having it.

And there's a specific, widespread confusion this statement has to dismantle explicitly, so it doesn't remain half-finished: the idea that "strong" and "soft" character are the two ends of a single gradient, and that more leadership naturally lives toward the strong end. It is, in other words, exactly the same error already documented by name and evidence in Part IV: confusing volume, perceived firmness, or assertiveness — what's colloquially called strong character — with greater real leadership capacity, when Anderson and Kilduff, the babble hypothesis from MacLaren and colleagues, and the Grant, Gino, and Hofmann study itself already showed that firmness predicts perceived competence, not real competence, and that it performs worse, not better, than a quieter style with proactive teams. A soft character isn't a character with less leadership in it — it can be, just as often and with better documented business results, epistemic authority exercised without needing to impose itself. And a strong character isn't, by itself, evidence of more leadership — it can be, just as often, positional command or pure theatricality, guaranteed smoke with no substance behind it. The strength or softness of a character describes a temperament style. It doesn't describe, in any sense this article's evidence supports, how much real leadership stands behind it.

The best captains in the world crash too — not for lack of character, and not because someone else was right and they weren't. They crash for lack of a system capable of recognizing, in time, the otherness of whoever's in front of them — even, especially, when that otherness doesn't wear the same rank.