- Initial thoughts
- How to read these profiles
- E3 - The Self-Centric Manager
- E4 - The Group-Centric Manager
- E5 - The Skill-Centric Manager
- E6 - The Principled Manager
- E7 - The Systemic Manager
- E8 - The Enabling Manager
- E9 - The Wise Manager
- When the lines don't match
- Silence folds back on itself
- When your stage and the manager's don't fit
- Wrapping up
- Further reading
The delivery manager sits next to the developer all day, owning priorities, shielding (or pressing) the team, answering for the outcome. Their developmental stage determines what the team actually lives through.
Initial thoughts
We already laid out the model in Ego development: The Eight Professional Stages, then charted it in Ego development: The Visual Atlas. We already profiled Ego development: Developers by Stage: the person at the keyboard. This one zooms into the person standing next to that developer all day: the delivery manager, not necessarily the career manager.
In many orgs those are two different people: a career manager (HR line, promotions, salary) seen at review time, and a delivery manager on the team every day. This article profiles the second. The seat travels under many names: project manager, Product Owner, Scrum Master, Delivery Lead, Agile Coach. The function is the same: someone who decides priorities, shields (or pressures) the team, talks to the sponsor, and answers for the outcome. The work itself sits on a ladder of levels of responsibility: Follow, Assist, Apply, Enable, Ensure and advise, Initiate and influence, Set strategy. A process-cop week asks Apply and Enable; servant-leadership asks Initiate and influence. Agile titles promise that higher ask. Whether the person can inhabit it is not a question of training. It's a question of stage. No new title, no new operating model, no new dashboard moves a person from one of those asks to the next. A Scrum Master at one stage is a genuine enabler of team autonomy; at another, the very same job description produces a process cop.
So rather than slicing the topic by theme, this article profiles the delivery manager at each stage, head to toe. On Cook-Greuter's N=4,510 sample (dissertation, Table 3), the adult modal center sits at E5–E6 (~67%); and most people in that seat in ambitious organizations land there too. The bulk of the field spans E4 through E8. The arc is bracketed by two profiles worth knowing at the edges: E3 (Self-Centric) at the bottom: the manager who manages by fear and only performs when watched; and E9 (Construct-Aware) at the top, easy to mistake for something far more ordinary. Read these as developmental snapshots, not as a ladder of worth.
How to read these profiles
Each profile below describes the same set of dimensions, so you can compare stages directly:
- What drives them: the underlying motivation, the thing they're really optimizing for.
- Authority & decisions: how they relate to their own boss, the sponsor, the client; how priorities and scope actually get decided.
- Running the team & its ceremonies: what standups, planning, retros, and the backlog mean to them. The week and the title can diverge here.
- Slips, blockers, and feedback: what happens when a deadline moves, something breaks, or a retro surfaces an uncomfortable truth.
- Managing remote, and being unsupervised: how they handle a team they can't see, and how they behave when nobody is watching them.
- Relationship to AI: how they use (or resist) AI for planning, reporting, and team work.
- Career trajectory: where their path tends to go over years.
- What their silence means: when they go quiet in a steering committee, a retro, or a one-on-one. A decoder, not a personality trait: the trap is named after the portraits.
And because most readers here are developers who report to one of these profiles rather than being one, each profile closes with a developer's field guide: how to keep them at ease (speak their language), how to deal with their control and surveillance, and what to avoid at all costs. It's a survival map, not an endorsement, adapting to a manager's stage is what lets you do good work despite the gap, and buys you the room to push for change.
Two caveats before you start typing names of colleagues into the margins. First, stage is not a global label: thanks to Wilber's lines of development, someone can be E7 in systemic thinking and E4 in office politics. Second, everyone regresses under stress: an E8 manager during a brutal go-live can behave like an E5. These are centers of gravity, not fixed coordinates.
E3 - The Self-Centric Manager
The political operator. Rare on a healthy team, but unmistakable once you've seen it. The governing rule isn't "deliver well"; it's don't get caught holding the bag. Morality has collapsed into a cost/benefit calculation, and the team is a resource to extract from or a shield to hide behind.
- What drives them: immediate personal advantage and avoiding blame. They want to survive the next steering committee and come out ahead of whoever they're dealing with. Nothing larger than the next status report is in view.
- Authority & decisions: obeys the sponsor out of fear and tells them what they want to hear. The "right" decision is whichever one is least likely to be traced back to them. Priorities are set by deniability, not by value.
- Running the team & its ceremonies: the standup is surveillance; the retro is theater they steer away from anything that implicates them. The backlog is a smokescreen. Delegation is mostly the offloading of blame, not of trust.
- Slips, blockers, and feedback: the slip is never theirs. "The devs underestimated, the client changed the scope, the previous lead left a mess". Status reports are fiction: the classic watermelon: green on the outside, red on the inside. Admitting fault is unthinkable because fault means exposure.
- Managing remote, and being unsupervised: this is the defining tell. They manage by surveillance, cameras on, hourly check-ins, mandatory status, because surveillance is their own operating model, projected onto the team. And when they are unwatched, their own output collapses: padded reports, manufactured busyness, work that exists mainly as a slide.
- Relationship to AI: a tool for cover. AI is used to fabricate plausible reports, generate status nobody will question, and game velocity metrics: with zero ethical distance. The question is never "should I?" but "can I get away with it?"
- Career trajectory: opportunistic. They jump before the project fails, take credit for others' wins, and build a purely transactional network. Each move is an arbitrage, not a step in a path.
- What their silence means: concealment. They go quiet to avoid leaving a trail, not because they're deliberating. This is the mutism end of the arc; and the pre/trans trap in its purest form: it can look superficially like the contemplative quiet of an E9, but it's the silence of someone hiding, not someone at peace.
Strength: in a genuine crisis with clear, immediate incentives, an E3 can be ruthlessly effective at self-interested damage control. Limit: corrosive to trust on any team built around them. The single most reliable tell is the remote one: a manager whose first instinct is to install surveillance, and whose own performance evaporates the instant nobody is watching.
Developer's field guide:
- Keep them at ease: give them cover. Frame everything so they look safe to their own boss, and make it clear you're not a threat to them.
- Deal with the control: build your own paper trail: confirm every decision and instruction in writing (email, ticket comments, recap messages) so their surveillance can't be turned against you. Their need for a trail is your protection too; document relentlessly.
- Avoid at all costs: never rely on a verbal promise, never be the sole witness to anything, never hand them something they can twist, never expect loyalty or credit. If you can, get yourself reassigned or escalate over their head with evidence; this is the one profile where "manage the relationship" has hard limits.
E4 - The Group-Centric Manager
The process keeper. The methodology is not a set of choices to be examined; it is reality. "That's not how Scrum works" is not pedantry; it's an identity statement. This is the textbook process cop. Organizationally they seek acceptance inside a clear hierarchy: command-and-control clarity, detailed instructions, and advice over open-ended initiative. Management coaching style collapses into telling people what to do: "the way we do it here" is right; other ways are wrong and must be corrected.
- What drives them: belonging and approval from above. Being seen as a reliable, by-the-book operator is the reward that matters. Following the official method is the identity. Shame (the group's gaze) weighs far more than private conviction.
- Authority & decisions: the hierarchy is the natural order. They relay management's decisions downward without filtering or challenging them, and escalate upward rather than deciding. Questioning the sponsor registers as a threat, not an option.
- Running the team & its ceremonies: ceremonies are sacred rituals performed for their own sake. The standup is a status round directed at them; the retro is a checkbox that never names the real problem; the burndown chart is maintained religiously. The "Scrum Master" who is really enforcing compliance, and the "Product Owner" who simply transcribes the backlog handed down from above.
- Slips, blockers, and feedback: a slip is exposure; it makes the team (and them) look bad in front of the group. Default move: follow the procedure, point at the procedure. "We followed the methodology". Feedback is acceptable from the boss but feels like an attack coming from the team.
- Managing remote, and being unsupervised: this is the hardest stage for full remote. The office is the group, and the ritual is the container. Strip away the physical room and the shared board, and the structure they rely on evaporates; so they recreate it artificially: mandatory cameras, rigid ceremony times, presence theater.
- Relationship to AI: mimetic. They adopt an "AI assistant for Jira" if the org mandates it, or distrust it if the group is wary. No independent stance: the organization's posture is their posture.
- Career trajectory: linear and loyal. They collect the group's current playbook, whatever method the floor is running this year, as proof of belonging. Same company or operating model for years.
- What their silence means: deference, not agreement. In a meeting they wait to see which way the room, or the boss, leans before committing. Silence here means "I don't dare contradict", not "I've decided".
Strength: dependable execution inside well-defined, stable delivery. Limit: ceremony theater: the very thing that makes them reliable makes them allergic to questioning the frame. This is the manager behind most "agile transformations" that are all ritual and no substance.
Developer's field guide:
- Keep them at ease: speak the language of rules and norms. Frame proposals as "this is the standard practice / what the framework recommends / how the other teams do it", never as "let's break the rule". Feed the ritual cleanly: show up to ceremonies, keep the board tidy, no surprises.
- Deal with the control: their control is the ritual, so satisfying the ritual buys you autonomy on everything else. Do the standup, update the ticket, and they'll mostly leave the actual work alone.
- Avoid at all costs: don't challenge the process publicly or bypass procedure without cover, don't blindside them in front of their boss, and don't pitch change as rebellion: to get a new practice adopted, repackage it as "the new standard" or get it blessed from above first.
E5 - The Skill-Centric Manager
The delivery optimizer. On time, on budget; and visibly so. This is the modal stage of the ambitious professional manager, and the engine of most delivery ladders. Organizationally they thrive in technocratic / engineering-style shops: pragmatic leadership unencumbered by fundamental questions: "Do what I do and you will be fine." As coaches they accumulate facts and ask "why did you…?" that subordinates often hear as blame; advice arrives as if it were the client's own conclusion.
- What drives them: recognition and measurable status: the promotion, the title, the green dashboard. They manage for the metrics that make them look good: velocity, on-time delivery, a clean steering committee. Their identity attaches to delivery craft: the methodology guild, the PM community, the tool stack of the year; and "the right way to run a project" comes from whichever authority that guild recognizes.
- Authority & decisions: respects the hierarchy but has started to see its limits; and plays the game to climb it. Decisions are weighed partly on outcome, partly on "how does this look for me and my project?" They expect sponsors and senior leaders to have answers: playbooks, benchmarks, best practice; and are genuinely unsettled when a director says "We're figuring this out together." That reads as weakness, not partnership.
- Running the team & its ceremonies: ceremonies are optimized for throughput and visibility. The standup tracks velocity; the retro produces action items that improve the numbers; the backlog is a performance engine. They'll push the team hard to hit the sprint commitment, because the commitment is their commitment. People are resources to optimize; and in steering committees, the habitual "yes, but…" reopens settled topics without ranking which risks actually matter: every concern weighs the same because context-priority isn't online yet.
- Slips, blockers, and feedback: received with discomfort but genuinely heard. The dominant emotion is embarrassment: fear of being seen as a weak manager. They'll work hard to recover the date, sometimes by squeezing the team. Any "I could have planned this better" is still about the dented image, not yet the genuine ownership that arrives at E6.
- Managing remote, and being unsupervised: highly effective as long as the output is visible. They need dashboards, reporting, and Jira hygiene: some channel through which the work (and the credit) can be seen. Take away visibility and you get anxiety, performative reporting, or a slide toward surveillance-lite.
- Relationship to AI: a performance multiplier. Fast adopter when it's a competitive edge; AI for forecasting, status generation, more visible velocity. The risk is velocity theater: optimizing for the appearance of delivery over real value.
- Career trajectory: the vertical climb. Senior PM, Delivery Lead, Program Manager: each level is validation, carefully curated on LinkedIn.
- What their silence means: ambiguous, and worth decoding. It's either strategic, withholding a position to avoid being wrong on record, or saving a contribution for a more visible moment, or checked-out, because nothing is personally at stake.
Strength: a strong manager who ships projects and hits dates: often the one who drives a delivery machine to its limits. Limit: systemic vision is shallow; they optimize their square of the board without questioning the game, and will burn the team for the metric if the metric is what's measured. They also struggle when leadership demands a good-enough release while they still see gaps: shipping the MVP on deadline feels like professional torture if their identity is perfect execution.
Developer's field guide:
- Keep them at ease: talk in metrics and visibility. Frame everything as "this improves velocity / reduces risk to your deliverable / makes the steering committee look good / makes you look good". Make your progress legible: a clean board is a gift to them.
- Deal with the control: they manage by dashboard, so push your status to them proactively rather than waiting to be asked. Visible output is what relaxes the surveillance.
- Avoid at all costs: never let them be surprised by bad news late: surface risks early, framed as "I'm protecting your deliverable", and you become indispensable instead of a liability. Don't let your real work stay invisible, and don't silently absorb velocity theater or crunch: negotiate scope explicitly, in the language of risk and numbers they understand.
E6 - The Principled Manager
The conscience of the team. On Cook-Greuter's map this is Self-Determining: standards are no longer inherited from the framework; they're internalized and self-chosen. Quality of delivery and care for the team are a matter of conviction, not applause. This is where "servant leadership" stops being a slide and starts being real. Where the Expert manager still leans on the playbook for legitimacy, the Achiever can name their own operating style, how they decide, what they protect, what they won't compromise, without needing a framework to hold them up. Self-reflection is possible here in a way it rarely is at E5; many leadership programs are really trying to teach Expert managers to do what Achievers already do. Alliances become task- and problem-oriented, roles shift by setting, and coaching gains playback: "How is it? What does it feel like?" without forcing their interpretation first.
- What drives them: integrity and genuine responsibility: for the team and for the outcome. They do right by the people whether or not anyone notices. Linear time is fully online: they carry last quarter's retro into next quarter's plan, and the energy points outward: build, deliver, improve the system. Long-term thinking and a real sense of ownership appear here.
- Authority & decisions: respects the function, not the person. Will challenge the sponsor or push back on the client when their principles or the data demand it: directly, without it being a status game. Says no to unreasonable scope. They can also broker task-level truces: "You're cost-driven, I'm quality-driven: for this milestone we optimize yours; for the next we pay down debt." Band together for the problem, disband, re-form for the next one, without requiring everyone to share one worldview.
- Running the team & its ceremonies: ceremonies serve the team, not the report. The retro actually surfaces hard truths and acts on them. They remove blockers, shield the team from noise, and keep the backlog honest. Process is a means, held to the standard of whether it's helping.
- Slips, blockers, and feedback: they take responsibility. "That's on me, here's how we recover". A slip is a lapse to own and correct, not a threat to deflect. They actively seek feedback. The risk is the opposite of E4: guilt and perfectionism.
- Managing remote, and being unsupervised: thrives. Self-disciplined and trusting, they grant the team autonomy and don't need to watch anyone; they hold themselves to a higher bar than any director would. The real danger is the inverse: they absorb all the pressure to protect the team, and over-responsibility tips into overwork and burnout.
- Relationship to AI: adopts with discernment and sincere questioning. "Does this actually help the team, or just the optics? Is this a report I can stand behind?" They neither worship nor reject the tool; they hold it to their standards. The delivery mindset shows up as "we'll find out: just not yet": confidence that the missing data will arrive once the right instrument, the right metric, the right retro, the right pilot, is in place.
- Career trajectory: values-driven. Will decline a toxic project or sacrifice status for mission alignment. The career is an expression of personal values.
- What their silence means: deliberation. They're listening and weighing, and they'll speak when a principle is actually at stake. Silence here is the sound of someone thinking, not someone withdrawing.
Strength: reliability rooted in conviction: the team genuinely trusts them; this is the stage that built most of what we call "professional management". Limit: standards can harden into rigidity, and the instinct to carry everything for the team can become a weight they can't put down. As coaches they're not yet aware of developmental differences, and may demand behavior that's simply over the person's head, expecting everyone to operate at their level. Reasoning stays rationally bounded; it has to make sense on a slide, it has to be defensible; and they still assume one correct reading of the situation. Sponsor and team look at the same slipped deadline and one sees resourcing, the other scope creep; the Achiever treats that as a fact dispute to settle, not as evidence that the observer shapes the story.
Developer's field guide:
- Keep them at ease: be honest and bring reasoning. They respond to well-argued positions, data, and a genuine concern for quality and the team, not to flattery or politics.
- Deal with the control: there's little surveillance to work around; they grant autonomy. Reciprocate with ownership and transparency: tell them the bad news yourself, early.
- Avoid at all costs: never cut a corner and hide it (they take dishonesty personally) and never BS them. The real risk is the opposite of the lower stages: watch them quietly drowning in over-responsibility: offer to carry your share, flag when they're absorbing everything, and don't exploit a trust that's freely given.
E7 - The Systemic Manager
The one who sees the whole system; and sometimes wishes they didn't. On Cook-Greuter's map this is Self-Questioning: roles stop defining the person, paradox becomes thinkable, and the manager starts questioning whether the project itself should exist. It is also the valley: a developmental milestone, not a burnout story. They begin to doubt what the organization handed them as given: Who am I as a leader when I'm one person in the steering committee and another in the retro? The turn is inward: less "what does the framework say?", more "how do I construct meaning this way and not another?"
- What drives them: authenticity, meaning, inner coherence. KPIs feel like "just numbers", a green steering committee feels hollow, hitting the date feels insufficient ("on-time delivery in a broken portfolio"). The conventional rewards have stopped working. Intuition and felt sense re-enter leadership, reading the room, trusting a gut call when the deck is incomplete, not instead of data, but alongside it. That can unlock genuinely creative reframes; it can also feel like too many inner voices, some energizing, some pulling toward withdrawal.
- Authority & decisions: detached from formal roles; they see the person behind the title. They'll question whether the team is even solving the right problem, whether the methodology fits the context at all: which is invaluable and, in the wrong room, exhausting for everyone.
- Running the team & its ceremonies: they challenge the frame itself. "Scrum isn't the problem: the funding model that forces fake estimates is". Sometimes that's the most important observation nobody else dares make; sometimes they tear out useful structure because they can see its imperfection too clearly.
- Slips, blockers, and feedback: welcomed as a mirror, and given with nuance: occasionally too much nuance. The risk is analysis that turns inward and paralyzes.
- Managing remote, and being unsupervised: autonomy is the default mode, so on paper this is ideal. But the valley changes the picture: remote can amplify isolation, and there's no friction to pull a cynical E7 back into engagement. Brilliant when engaged; quietly drifting when not.
- Relationship to AI: fascination paired with sharp critical distance. They see the second-order implications, teams deskilling, metrics gaming, what it does to the craft of leading people, and risk paralysis from seeing too far.
- Career trajectory: non-linear. They leave the corporate delivery track for freelance, coaching, or consulting; portfolio careers and bifurcations. Roles don't define them, so they wear them loosely.
- What their silence means: this is the dangerous silence. It signals withdrawal and cynicism: "Why fight for this deadline when the whole program is mismanaged?" Going quiet here is disengagement under the weight of seeing dysfunction everywhere without yet having the leverage to fix it. This is the valley made audible; or rather, inaudible.
Strength: a piercing systemic vision nobody else in the room has; and communication that starts to sound like a specific person, not a management type. Limit: fragile engagement. They can see exactly what's wrong and struggle to act on it without sliding into cynicism or retreat. Watch for the post-modern trap: deconstruct every process because all boundaries are artificial, without noticing that "nothing is real" is itself a stance; and for the two exits that look similar from the org chart: the manager following their own drummer (celebrating an unconventional path, energized by non-conformity) versus the one who survives on cynicism (total uncertainty, nothing worth fighting for). Communal "every voice is equally valid" relativism is a different flavor again, more herd-oriented, whereas the Individualist path here tends inward, celebrating my truth even when it doesn't match the room. Neither flavor is automatically pathological; both can float someone until the E8 re-engagement.
Developer's field guide:
- Keep them at ease: engage with the real problems. They're starved for an honest conversation about what's actually broken, bring them the systemic question, not just the ticket, and you'll have their attention.
- Deal with the control: there's almost none: the danger is the opposite: drift, vagueness, and decisions that never land. Pull them back to the concrete ("great, so what do we ship Friday?") and give them small, tractable problems to re-engage with.
- Avoid at all costs: don't feed the cynicism or let venting sessions substitute for delivery, and don't let their "everything is broken" pull you into disengagement. When they're deep in the valley, don't wait on them for crisp decisions: surface options and help them choose.
E8 - The Enabling Manager
The one who makes the team and the system better instead of directing them. On Cook-Greuter's map this is Self-Actualizing: they don't run the most meetings: every intervention is strategic. To an E5 colleague, they can look like they're "doing nothing".
- What drives them: systemic contribution and the growth of the whole. Recognition is welcome but no longer the fuel; it comes from impact, not from the gaze of others.
- Authority & decisions: a partner, not a subordinate. They collaborate with the hierarchy without dependence or opposition, and they'll renegotiate the frame of the engagement, not just its terms, when the context genuinely requires it.
- Running the team & its ceremonies: ceremonies are tools, kept, dropped, or redesigned to fit. They calibrate to each person's stage, a different register for an E4 junior than for an E6 senior, and they design the team's autonomy so it doesn't depend on them. Clear ownership, async documentation, well-placed feedback loops: a system that runs without a cop.
- Slips, blockers, and feedback: treated as data for the system, not just for the individual. "What does this teach us collectively?" A post-mortem is an investment, not a tribunal.
- Managing remote, and being unsupervised: they design the question away. Rather than needing to watch anyone, they build the conditions, clear ownership, transparent priorities, feedback loops, that make supervision unnecessary by design. The location of the work is irrelevant; the design of the work is everything.
- Relationship to AI: they think at the level of the system. Not "should I use it?" but "how should the team use it, and what are the second-order effects on our skills, our delivery, our hiring?" AI becomes part of organizational design.
- Career trajectory: the career is a vehicle, not a destination. They'll take a nominal step "down" if it serves the larger contribution. The role is an instrument, never the identity.
- What their silence means: restraint, the exact opposite of E7 withdrawal. They've identified the single intervention that makes ten others unnecessary, so they wait for the right moment and let the rest go. The discriminating test: an E8's silence coexists with the ability to speak sharply and decisively when it matters. The valley's silence cannot.
Strength: invisible value, maximum impact. Limit: that very invisibility; they are routinely undervalued by anyone who measures contribution in visible activity, and penalized by the 360° reviews that reward pleasant predictability over uncomfortable truth.
Developer's field guide:
- Keep them at ease: bring problems and proposals, not just status. They'll meet you at your level, so come with thinking, about impact, trade-offs, second-order effects, and they'll invest in you.
- Deal with the control: there's no surveillance to work around, and that's exactly the point; they've replaced it with ownership and feedback loops. Step into the autonomy fully instead of waiting to be told what to do.
- Avoid at all costs: don't mistake their restraint or silence for disengagement, indecision, or weakness; that misread is the classic pre/trans trap. Don't measure them by visible activity, and don't squander the rarest opportunity you'll get: a manager who will actively grow you if you show up ready to be grown.
E9 - The Wise Manager
Statistically rare, and the easiest profile in this article to misread. On Cook-Greuter's map this is Construct-Aware: the E9 has reconciled the inner conflicts that drive every other stage: the need to belong, to be recognized, to be right, to be lucid. What remains looks, from the outside, almost ordinary: simplicity. But it's a simplicity loaded with integrated depth, not the naive simplicity of an E4 who never asked the questions. This is the deepest pre/trans trap in the whole arc: an E9 can be mistaken for an E5 precisely because both seem unbothered and uncomplicated.
- What drives them: service and the reconciliation of opposites. Wide empathy, toward themselves and others. Learning is accepted as inevitable; what's unreachable is relinquished without bitterness. There's a quiet peace with what they are and what they'll never be.
- Authority & decisions: beyond formal hierarchy. Their authority is natural; it comes from wisdom and empathy, not from a title or even from systemic cleverness. The org chart is almost incidental to how people actually relate to them.
- Running the team & its ceremonies: presence over process. Ceremonies become genuine connection or quietly fall away; whatever structure serves is the structure they use. No status game, no defense, no agenda: just people making the work and each other better. Coaching adjusts to the other person's stage: mentoring, empathetic listening, challenge, or reframing: whatever helps them find their own way.
- Slips, blockers, and feedback: an error is part of the flow: neither dramatized nor minimized. "That's what needed to happen for us to move forward". No blame, no guilt, no performance of contrition; just integration and the next step.
- Managing remote, and being unsupervised: location is irrelevant; presence is internal. There is no gap between watched and unwatched, because there is no external scaffolding holding the behavior up: the discipline, the care, and the engagement come from within and don't depend on context at all.
- Relationship to AI: one tool among many: neither threat nor salvation. Integrated without drama. They neither evangelize nor resist; they use it where it fits and leave it where it doesn't, with no identity invested in the choice either way.
- Career trajectory: the very concept of "career" is relativized. The path is the point. Titles, levels, and trajectories are simply not the frame through which they organize their working life.
- What their silence means: genuine contemplative presence: the opposite pole of E3 mutism. They're comfortable saying nothing because nothing needs to be added, and equally comfortable saying the one thing that reframes everything. The discriminating test holds: this silence coexists fully with the capacity to act and speak with precision when it serves.
A caution worth stating plainly: real E9 is rare enough that you will meet far more people who perform this serenity than who embody it. The discourse of integration sitting on unintegrated shadow, calm words, E5–E6 reactions under pressure, is spiritual bypass. The genuine article reveals itself not in calm weather but under maximum stress, where the equanimity simply holds.
Developer's field guide:
- Keep them at ease: nothing to perform: just be real. Pretense and politics land flat; honesty and presence land.
- Deal with the control: there is none, and unlike the E3 whose absence of trust hides surveillance, here the absence of control is the trust: receive it as such.
- Avoid at all costs: don't perform for them, don't mistake their calm for absence or their simplicity for naivety (the deepest pre/trans trap in this article), and, most of all, don't waste the encounter. Working under a genuine E9 is rare; pay attention, because this is where you learn what the higher stages actually feel like from the inside.
When the lines don't match
The portraits above are centers of gravity on one line. Some people sit on two at once, cognitively here, pragmatically there, and the mix is easy to misread as a higher stage. This is a shelf: more later. The first is the one most often trusted by mistake.
The Green-Dashboard Manager - E5/E3
Not every E5 pushes the team hard. Some are eerily relaxed; and that relaxation is the trap. Their status is permanently green, the steering committee is smooth, and they radiate the unbothered confidence of someone who has mastered the chaos. They haven't. They've mastered the slide.
This is the watermelon: green on the outside, red on the inside. E5 on the cognitive line (they can read the project), E3 on the pragmatic line (the move is concealment). You know the pattern. The feature that was "85% done" for three sprints in a row. The risk that gets reworded out of the report instead of resolved. The project that sails along until, two weeks before the deadline, it suddenly needs another quarter; and somehow nobody saw it coming. They saw it. They just had no incentive to say it out loud, because naming the risk would have bruised the dashboard that keeps them safe.
The reason this reads as composure is that it borrows the surface of a genuinely autonomous E8: same calm, same lack of drama. What's underneath is the opposite. Hand an E8 a problem and they go looking for the root cause, because they actually want the system to be healthy; their reward comes from the outcome. Hand a watermelon manager the same problem and they go looking for the framing that makes it vanish from view. One is managing reality, the other is managing perception. For you on the team, that distinction is not academic: you're the one who inherits the red the morning the melon finally splits.
The defense is the same move as with any E5, just sharper: make the red legible and on the record. Raise risks in writing, early, with dates and numbers; so when the gap between the slide and the truth blows open, it's documented as something you flagged, not something you hid.
Silence folds back on itself
Watch the silence dimension especially, because it's the one most often misread. The arc folds back on itself: the quiet of an E3 covering their tracks and the quiet of an E9 at peace look identical from across the room, just as a checked-out E5 with nothing at stake mirrors an E8 who has integrated everything. That's the pre/trans confusion: the bottom impersonating the top. One test cuts through it: can the person also operate vocally and decisively when it matters? An E8 or E9 holds their fire and can name the problem with surgical clarity on cue; an E7 in the valley, a checked-out E5, or an E3 covering their tracks cannot. Getting this wrong, promoting the checked-out, sidelining the restrained, is how teams quietly lose their best people.
The green-dashboard manager above is the same trap in working clothes: a calm room is not wisdom.
When your stage and the manager's don't fit
Everything above profiles the manager in isolation. But what you actually live through depends on the gap between their stage and yours; and gaps don't resolve symmetrically. Two forces decide the outcome.
The first is that recognition runs one way. A higher-stage manager reads a lower-stage developer almost instantly; a lower-stage manager is structurally blind to a developer above them, because they lack the cognitive structures to perceive what they don't yet have. So a mismatch plays out completely differently depending on which side is higher. The second is that a one-stage gap is the growth corridor: close enough to understand each other, far enough to stretch. Stretch the gap to two or more and you get the failure modes below.
- E8 manager + E3 developer: ejection, fast. A self-protective dev survives on opacity: padded estimates, deflected blame, work that exists mainly as a status update. An enabling manager's entire design: transparent ownership, real feedback loops, nowhere to hide: strips that oxygen away. The E8 clocks the games in a conversation or two and has the person reassigned before they can say "it works on my machine". High-stage managers are death to opportunists, not out of harshness, but because they build systems where gaming has nowhere to live.
- E7 developer + E3 manager: won't last. Now flip it. A systemic developer reads the manipulation, the watermelon reports, and the cover-your-back politics with total clarity, and has zero appetite for it. They won't be managed for long by someone they've pegged as fundamentally dishonest. There's no growth corridor here, only contempt; and, unlike the E8 manager, the E7 dev has no lever to remove their boss, so they remove themselves. They disengage, then leave.
- E5–E6 manager + E8 developer: slow undervaluation. The recognition asymmetry at its most expensive, and the quietest failure of the lot; and the most common mismatch in practice, given how many managers sit at the conventional modal center (see distribution data). The manager measures contribution in visible activity and reads the E8's strategic restraint as "not doing much". The dev's highest-leverage move, the single intervention that made ten tickets unnecessary, is literally invisible to them. Nothing explodes; it just drifts. The dev gets passed over, the manager never understands why their best person is restless, and eventually someone who can see them hires them away.
- E6–E7 developer + E4 manager: suffocation. The process cop and the principled developer grind daily. Every "that's not how Scrum works" lands as an insult to someone who has internalized why the practice exists and when it shouldn't apply. The dev chafes, picks fights over rituals that don't matter to them, and burns goodwill they'll wish they had later.
- Same center of gravity (E5–E6 dev + E5–E6 manager): comfortable, stable, flat. Shared assumptions, low friction, nothing combusts. This is most of the industry, and it's perfectly fine: as long as nobody mistakes the calm for excellence or expects growth from it.
- E9+ on either side: the friction dissolves. At the very top of the arc, the clashes above stop registering. An integrated manager isn't threatened by any developer, including an E3: they see the games with the same clarity as the E8, but without the contempt; they act on the dysfunction while fully accepting the person, and they can meet a dev at any stage without needing them to be other than what they are. It runs the same way in reverse: an E9 developer can sit under an E3 manager without being eaten alive by the disgust that consumes the E7, because acceptance has replaced judgment. Crucially, this is not the conformist's "everything's fine" (E4); that's pre-personal tolerance, a refusal to see. The E9 sees everything and accepts it anyway, with no bitterness and no illusion. They may still walk away from a toxic situation, but they leave in peace rather than in revolt.
The practical takeaway is uncomfortable but freeing: if you're an E7 developer reporting to an E4 manager, no amount of being right will close the gap; they can't see the thing you're right about. Your realistic options are to translate ruthlessly down into their register (that's what each field guide above is for), find an ally one stage up who can see you, or move on. Reading the gap honestly is what stops you from burning years trying to be appreciated by someone structurally unable to appreciate you.
Wrapping up
The portraits are the point: same seat, different structure, and it shows up in everything from what motivates a manager to what their silence means in a retro.
Two practical levers fall out of all this. Read silence with the pre/trans test: never promote the checked-out or sideline the restrained on appearances alone; the green dashboard and the calm room are not proof of wisdom. And pair or mentor across a one-stage gap: same-stage mentoring is comfortable but flat, a two-stage gap frustrates both sides, and a single stage of difference is the growth corridor: close enough to challenge, far enough to stretch.
The cynical change agent, the process cop, the green-dashboard manager, the stalled agile transformation, the valley: none of these are personal failures. They're developmental transitions, as legible and as patterned as anything in our delivery dashboards. Understanding a stage won't change it on its own. But it can change how we navigate the valley, how we read a quiet colleague, and how we avoid mistaking the appearance of a stage for the thing itself.
Next, a companion piece locks the stages into memory: fantasy archetypes for E3→E10 (with E2 only as the Rogue's regression floor), so the names stay sticky without needing another table.
Illustrations generated locally by Draw Things using Flux.1 [Schnell] model
Further reading
This article was enhanced with the assistance of an AI language model to ensure clarity and accuracy in the content, as English is not my native language.
Top comments (0)