4) Morten Eikeland: Det finnes alltid et hierarki

Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · podcast · 2026-06-01 source ↗ Reader 🖥️

theoretical · expository-argumentative interview built around a single thesis-and-derivation: hierarchy is structurally inevitable in groups beyond a certain size, and the rhetoric of 'flat structures' in tech/agile/smidig miljøer is at best naive and at worst a self-deception that simply hides which hierarchy is actually operating. Eikeland develops the argument deductively from first principles (one person → no coordination; two people → relational hierarchy; eight people → coordination need that calls forth ledelse) using Adam Smith's division of labour as the ontological backbone. Interspersed are diagnostic vignettes (innvandrere bewildered by tilsynelatende flat offices; psykiatri opphørsåk; fylkesordfører digitalisering speech) and a clinical case-study sub-thread on the developer-to-leader transition as a sorgprosess. — Eikeland is a psykolog at AFF working with toppledere and ledergrupper, profiling them with Big Five and observing samspill. The conversation has two interlocking layers: (1) the thesis on hierarchy as inevitable, applied especially to teknologi-organisasjoner; (2) the practitioner's framework for understanding why utviklere struggle when they enter lederrollen. The episode is canonical for Heis: Printzell Halvorsen (ep 8) explicitly defers to Eikeland's abstraksjonslag framing as the operational meaning of 'å lede på riktig nivå.'

Structure

Key terms

• hierarki Hierarchy & Org Charts
  Eikeland uses 'hierarki' deliberately broadly to mean any pattern in which influence, decision-weight, or credibility is distributed unequally — including (a) formelle hierarkier on the orgkart, (b) uformelle (relasjonelle) hierarkier within any group of two or more, (c) ekspertise- og kunnskapshierarkier (the developer who is 'flink' has more say), and (d) definitional or framing power (whichever profession plukker opp et element gets to name it). The thesis 'det finnes alltid et hierarki' is therefore not the trivially true claim that someone usually decides — it is the much stronger claim that the unification of these layers into a single operating pattern always exists, whether or not the group admits it.
• abstraksjonslag Organizational Abstraction Levels
  Borrowed from software engineering by analogy. Each level of an organisation (individ → team → område → divisjon → selskap) is a distinct abstraction layer with its own time horizon, granularity, and language. To lead at level N means to reason at level N's granularity and time horizon, not at level N-1's. A leder must abstrahere upward and forward in time (morgen, not akkurat nå), explicitly giving up konkretisering. The skill of moving between abstraction layers is the developer's transferable instinct for leadership; Printzell Halvorsen (ep 8) explicitly cites Eikeland on this point as the operational meaning of 'å lede på riktig nivå.'
• lede på riktig nivå Organizational Abstraction Levels
  Operating at the abstraction layer appropriate to the role one occupies. For a leder of 8+, this means giving up detail focus and detailed konkretisering, generalising the gruppe, and operating with a longer time horizon. The discipline is to remain interested in lower levels without intervening at them. Failing to lede på riktig nivå produces two characteristic errors: micromanaging from above (drar detalj-fokus opp), or overdreven selvsetthet at the abstract level (illusion of explanatory depth).
• uformell leder Informal Leadership
  The leader the gruppe itself selects as its prototype-representative — historically and evolutionarily, the only kind of leadership there was. Functions to (a) coordinate the gruppe and (b) represent the gruppe to ekstern parties (the talsperson). In modern organisations a formal leder is appointed from outside; this is 'unaturlig' (not 'wrong,' but not evolutionary). The split between formal and uformell leder is a permanent feature, and if the formal leder fails to serve the gruppe, the gruppe will appoint a different uformell prototype. Mistreating uformelt lederskap as negative misunderstands a natural prosess.
• selvbedrag (flat struktur som) Hierarchy & Org Charts
  The specific kind of selvdeception involved in believing that one operates in a flat team. Selvbedrag because the operating hierarchy is fully present (expertise, definitional power, uformelt lederskap) and is in fact stronger for being unspoken; the participants are not lying, they have genuinely talked themselves into not seeing it. Distinct from straightforward lying or from intentional concealment.
• kunnskapshierarki Hierarchy & Org Charts
  A hierarchy organised by who has the most-valued expertise. In utviklingsmiljø, kunnskapshierarki is intense ('er du lite flink, er det ikke noe kult'). In NAV historically, the juridical kunnskapshierarki dominated; over the last 20-25 years it has been displaced by the teknologiske kunnskapshierarki. Crucial point: the dominant kunnskapshierarki determines whose language gets to name problems.
• division of labour / arbeidsdeling
  Eikeland calls this 'ontologien av vår organisering.' As complexity exceeds individual capacity, specialisation arises; specialisation buys depth but costs breadth; coordination then becomes a separate task requiring a separate function (ledelse). The Smithian pin-factory example is invoked to make the point that even a simple end-product entails thousands of specialists.
• ledelse er en prosess (ikke en person) Informal Leadership
  Ledelse arises as a coordination need from group structure; it is not the property of a person. The person currently occupying a leder-rolle is doing the rolle, not being the leader. Closely tied to the rolle-vs-person distinction.
• rolle vs person Informal Leadership
  Once you reach a senior level, you are not there as a person but as a rolle. The rolle's shape is determined by the constellation of forventninger from everyone with a stake (not by the person hiring you), and shifts on the day you arrive — and continually thereafter as kontekst changes. The personal task is to find or grow into a rolle one can sustain over time without being stressed apart by it; this requires tålmodighet. Failure of fit does not mean the person is elendig, only that råd-marginen was too small. Counter-illustration: Trump as 'too much person, too little role.'
• sorgprosess (developer-to-leader) Hands-On Leadership & the Pendulum
  The grief process a strong-identity utvikler goes through when becoming a leder: identity-loss of the kjente faget, loss of dybdekunnskap, forced generalisering, and being conscripted into an identitetsramme (corporate, anti-anarkist, ledende) that the person actively dislikes. Compounded by being met as inkompetent by the new milieu. Eikeland says he tries to ryde i de følelsene so the person can tydeliggjøre sitt valg. He recommends not deciding 'whether to become a leader' but trying to become a god leder for a year first, then deciding.
• illusion of explanatory depth (forståelsesdybde-illusjon) Mental Models & Understanding
  Eikeland's Norwegian rendering of the Rozenblit/Keil cognitive psychology finding. People believe they understand mechanisms (klima, digitalisering, AI) when in fact they merely gjenkjenner the begrep. The illusion is unmasked when one asks 'how does the mechanism actually work?' instead of 'what is your view?' At the strategy level in ledergrupper, asking for mekanismer in place of meninger reliably produces forbannelse and sometimes ejection from the room, because the leaders' own inkompetanse is suddenly visible.
• gjenkjenne vs forstå Mental Models & Understanding
  Repeated use of a generalised begrep makes us recognise it; recognition is not understanding. Organisations using a word over and over (digitalisering, AI, agile, smidig, hierarki) drift toward feeling they share a meaning when they only share a label. The fix is to drop down into mekanisme — to be forced to explain how the thing actually works.
• inngruppefølelser
  Once a group has a sterk identity, we automatically experience us-as-we (not us-as-I), and feel that 'we are right, they are less'; 'we are like each other, they are different from us.' Eikeland claims this finding survives the replication crisis ('dette funnet står seg uansett'). Applied: teknologi-gruppe identity is sterk; produkt-gruppe identity is diffuse; teknologer naturally feel their kunnskap is superior to other professions. This is the mechanism behind the kunnskapshierarki realisations of hierarchy.
• self-managed teams (selvledelse) Team Autonomy
  Eikeland names self-managed teams / selvledelse / 'leading without a leader' as concepts he considers tøy in practice, while acknowledging that a formal leader is not always required. The point is that the gruppe still has a coordination need and external groups still need a single talsperson; both forces produce de facto hierarchy whether or not a formal leader is appointed.
• flerfaglighet
  When more than one fag-tradition is needed to address a problem; distinguished implicitly from tverrfaglig (cross-functional within a more bounded sense). Eikeland's claim: teknologer have strong empati within their own fag, less for andre fag, and especially under-extend it to flerfaglighet — they retain skråsikkerhet on behalf of their own profesjon. This is where hierarki-kamper between professions show up most starkly.

Propositions

• explicitHierarki finnes uansett — in any group of more than one person there is always some operating hierarchy, even if the formal one is absent.conf: high
• explicitTech-culture preference for flat hierarchies is partly a sociological inheritance from gutterom-introvert-anarkist roots, carried into smidig and agile, and is naivt i møte med den reelle organisasjonen.conf: high
• explicitBelieving one operates in a flat team while a strong kunnskapshierarki is in fact present is selvbedrag — not lying, but a collective self-deception that hides the operating hierarchy.conf: high
• explicitcontestedSuppressing the visible signals of hierarchy (no separate offices, no penere bil for the sjef) does not abolish hierarchy; it makes it harder to read, especially for newcomers from høy-hierarki cultures, who are then destabilised by the diffuseness.conf: high
  contradicts ←Your AI strategy has a trust problem, not a tooling problem · p14 — Elena credits Anthropic's flat title structure with its velocity; Eikeland holds that suppressing visible hierarchy markers does not abolish hierarchy, it only makes it harder to read.
• explicitPeople with power do not want hierarchy interrogated; this explains the structural avoidance of the topic in organisational discourse.conf: high
• explicitWhichever profession plukker opp et element and successfully imposes its begrepsapparat on it controls the framing of organisational problems — making kunnskapshierarki the operating hierarchy in knowledge-intensive orgs.conf: high
• explicitFINN's drift from a sales organisation to a teknologi-organisasjon is itself a hierarchy change — teknologene fikk mer makt, selgerne mindre.conf: high
• explicitOrganisations are samfunnsspørsmål, not vitenskapelige problemer; the teknologisk-tenkning urge to find rotårsak and solve is the wrong methodological frame.conf: high
• explicitLedelse arises as a coordination function when group size exceeds roughly eight — not as a person and not as a status, but as a structural need.conf: high
• explicitThe evolutionary form of leadership is selection by the gruppe of an uformell prototype; the modern practice of being chosen by outsiders is 'unaturlig' but not 'feil.' The split between formell and uformell leder is permanent and the gruppe will appoint a new uformell leder if the formelle leder fails to serve them.conf: high
• explicitLedergruppe is a sosial lært praksis (kultur), not a juridical necessity — we stop interrogating it and treat the weekly multi-hour meeting as obligatory.conf: high
• explicitThe developer who becomes a leader must forlate faget — not in the sense of la stryk in it, but in the sense of letting it stop styring identity.conf: high
• explicitThe developer-to-leader transition is a sorgprosess, not a skill change. The identitetstap of dybdekunnskap and the forced entry into a kategorisk uønsket identitet (corporate ledelse) is the real cost, and most failures of the transition are failures to tåle the resulting følelser.conf: high
• explicitA leder operating at level N must give up konkretisering and operate with a longer time horizon (i morgen, not akkurat nå), seeing the whole gruppe rather than enkelte members.conf: high
• explicitGeneralisering at the top is necessary but produces overdreven selvsetthet — an illusion of explanatory depth that is unmasked when one asks for mekanismer instead of meninger.conf: high
• explicitRepetitive use of a generalised begrep makes us recognise but not understand it; gjenkjenne ≠ forstå. This is why digitalisering, AI, hierarki etc. drift into shared-label / un-shared-meaning failures.conf: high
• explicitAt sufficiently senior levels you are not there as a person but as a rolle; the rolle is shaped by all stakeholders' forventninger and shifts continually with kontekst; fit and råd-margin matter more than the personal qualities the hiring exchange named.conf: high
• explicitThe 'å være seg selv' demand on leaders is misplaced in many roles — a dommer, lege, kirurg's rolle exists specifically to depersonalise consequential action, and using rolle as the operative unit protects the person from impossible personal weight.conf: high
• explicitcontestedSelf-managed teams / leading without a leader is tull in the descriptive sense — group still has a coordination need and the external world still needs a single talsperson — even though formal leadership can sometimes be elided.conf: high
  contradicts ←Your AI strategy has a trust problem, not a tooling problem · p7 — Elena prescribes prototyping flat, high-autonomy pods; Eikeland holds leaderless self-managed teams are descriptively incoherent because coordination and single-spokesperson needs persist.
• explicitTwo structural mechanisms force hierarchy: (a) the internal coordination need that grows superlinearly with group size, and (b) the external need for one talsperson because outsiders cannot keep track of every gruppemedlem.conf: high
  extends0) Velkommen til Heis · p2 — Grounds the show's thesis that autonomous teams still need leadership in two structural mechanisms: superlinear internal coordination cost and the external need for a single spokesperson.
• explicitOffice layout is a quiet hierarchy lever: teknologer sitting next to selgere produces cross-empathy; teknologer concentrated on their own etasje produces stronger in-group identity and decayed empathy for andre fag.conf: high
• explicitTverrfaglig problems must be solved tverrfaglig; flerfaglig problems must be solved flerfaglig; mono-fag problems (e.g. pure koding) can be solved within one fag.conf: high
• explicitTeknologi gave introverte, ofte sosialt-angste nerds a place where their fag created sosial status and gode penger; 30 years ago they would have been på NAV and slitt som et uver. This was a net good — but partly på bekostning av enklere selgere who lost makt as the dominant kunnskapshierarki shifted.conf: medium
• explicitDecide on becoming a leader only after seriously trying to become a good one for a year; do not pre-decide the identity question.conf: high
• explicitLedelse er en prosess, ikke en person; the closing prescription is to look at the prosess in which one is participating, not at the individual identities involved.conf: high

Arguments

Narratives

• Eikeland's hiring at AFF: he was working in psykiatri, mid-utageringssituasjon (physically restraining a patient) when the AFF sjef called. He took the call, said 'I'm in an utageringssituasjon, I'll call back,' and the sjef — being a psykolog himself — understood. After interviews (including Eikeland interviewing four of the AFF staff himself), he was hired as the youngest in AFF, where many thought he didn't belong. Fifteen years later he learned he had been hired not for kunnskap but for verdier and pågangsmot — qualities the organisation needed.
  → Establishes Eikeland's clinical vantage on organisations and quietly seeds the rolle-vs-person argument (he was the right person for a rolle-shaped need, not for the qualifications named in the interview).
• First meeting with the hosts: they were enthusiastic about teams as the most important enkelkomponent in a virksomhetsarkitektur and about flate strukturer. Eikeland simply said 'hierarki finnes uansett.' The episode is, in effect, his elaboration of that one sentence.
  → Frames the conversation as the unpacking of a single counter-thesis that the hosts have lived with since.
• Innvandrere med høy utdanning relocating to Norwegian workplaces and being destabilised because they could not read the hierarchy: pene biler not distinguishing the sjef, open landscape office, no separate pult. They came from høy-hierarki cultures where signals were clear; the diffuseness of the Norwegian setup was disorienting precisely because the hierarchy was still there but invisible.
  → Concrete diagnostic case that hierarchy-suppression is a UX problem for newcomers, not a real reduction in hierarchy.
• FINN's drift from a sales organisation (15-20 years ago) to a teknologi-organisasjon over the intervening period — Audun and Eikeland trace this together. The shift in dominant kunnskapshierarki is, for Eikeland, the real story of what 'hierarchy change' looks like in a modern company.
  → Empirical anchor for the kunnskapshierarki proposition; ties the abstract thesis to a concrete Norwegian institution the audience knows.
• NAV and jurister: historically the juridical kunnskapshierarki was dominant; over the last 20-25 years the teknologi-language has displaced it. The Kristian-anecdote from a prior podcast (NAV teknologer meeting the jurister) frames how a flerfaglig handoff works (and fails) when kunnskapshierarkier are in tension.
  → Extends the FINN case to a public-sector context and shows the framing-power mechanism explicitly.
• The bjelle at FINN: selgerne slo en bjelle when they made big salg; teknologene found it kjempeirriterende. Eikeland uses this micro-story to ground the personality-test data (selgere score higher on begeistring, teknologer closer to russer in expression) and to make the cross-fag empathy gap concrete.
  → Vivid micro-illustration of the inngruppe-følelser mechanism inside one workplace.
• The Adam Smith pin-factory expansion: roughly 10,000 people contribute to a single nål reaching the consumer — frakt, gruve-arbeid, boring, etc. This is the ontological basis for arbeidsdeling and therefore for the rise of ledelse as a coordination function.
  → Provides the deductive backbone for the structural-inevitability claim using a canonical economics example.
• Gutterturen: any group of menn going on a tur sees ledelse arise within minutes — someone bestiller billetter, someone wants så badly to go to Roma that they take initiativ. Initiativ er en del av ledelse. The leader emerges; nobody appointed them.
  → Casual empirical example of evolutionary, ground-up emergence of ledelse in any group.
• The fylkesordfører-digitalisering speech: Eikeland is to speak after a fylkesordfører who said 'digitalisering' (Eikeland estimates 150 times in five minutes). Eikeland abandons his planned beslutninger talk and instead asks the audience two questions: what feelings they have after hearing the speech, and what they think the man said. 340 different interpretations emerge — including 'now I'll lose my job' and 'now I get a meaningless rolle' that the speaker never said.
  → Central empirical illustration of gjenkjenne-vs-forstå and of the illusion of explanatory depth at scale. Also a demonstration of Eikeland's own intervention style.
• Strategy work with ledergrupper: when Eikeland asks them to explain mekanismer instead of meninger, they get forbannet, sometimes throw him out, because they are confronted with their own inkompetanse.
  → Practitioner anchor for the illusion-of-explanatory-depth argument; demonstrates that the diagnostic intervention is itself disruptive.
• Eikeland's own kode-tap: 'jobben min nå er jo mindre teknisk enn det den var før' — he had to give up day-to-day koding as he moved up, and was overrasket how tungt it was. He uses this self-disclosure to ground the sorgprosess claim from inside, not just from observation.
  → Establishes that the sorgprosess is Eikeland's own experience as well as his diagnosis of others'.
• Trump as a worked example of role-vs-person failure at the highest level: too much person, too little role. The conversation contrasts this with the dommer-rolle, kirurg-rolle, politi-uniformen, lege-frakk — institutional designs that depersonalise consequential action to protect both persons and outcomes.
  → Distils the rolle-thesis with a vivid contemporary example and a series of canonical institutional ones.
• Hosts' closing self-assessment. Audun deadpans 'hierarki er en illusjon, flat struktur fungerer som bare rakk' as a parodic mis-reading. Truls says the thesis 'det finnes alltid et hierarki' has been the most useful frame in his work because so many people come in with the opposite framing. Eikeland's own takeaway: ledelse er en prosess, look at the prosess, not the person.
  → Closes the loop on what was useful to learn — and confirms the Heis-internal place of this episode as theoretical anchor.

Questions addressed

• ✅ What kind of hierarchy does Eikeland insist always exists — formal, informal, decision, expertise, status — and is the claim descriptive or normative?
  He insists on a deliberately broad definition that unifies (a) formell, (b) uformell/relasjonell, (c) ekspertise- og kunnskapshierarki, and (d) definitional-framing power. The core claim is descriptive (these layers always operate, individually or in combination, in any group of more than one). The normative implication, applied especially to tech, is that pretending otherwise is selvbedrag and that the right work is operating at the right abstraksjonslag inside the inevitable hierarchy rather than flattening.
• ✅ What does abstraksjonslag / 'lede på riktig nivå' mean operationally?
  An organisation is a stack of abstraction layers (individ → team → område → divisjon → selskap). Each layer has a different time horizon and granularity. The leder at level N must reason at N's granularity, lengthen the time horizon (i morgen, not akkurat nå), and generalise the gruppe. The discipline is to remain interested in lower layers without reaching down to direct work at them. The developer's instinct for moving between abstraction layers is the transferable skill. Crucially, generalisering is necessary but generates an illusion-of-explanatory-depth risk that must be countered by descending into mekanismer when stakes are high.
• ✅ Why does tech culture in particular resist hierarchy talk, even though it operates a strong kunnskapshierarki?
  A sociological-historical hypothesis: utviklere come from a gutterom/anarkist/introvert tradition that grew up culturally outside formal systems, then carried that anti-hierarchy stance into smidig and modern team practices. The kunnskapshierarki within utviklingsmiljø ('er du lite flink, er det ikke noe kult') is strong precisely because the formal hierarchy is denied; identity-strong groups cannot see their own hierarchies.
• ✅ How do you transition a developer into leadership without breaking them?
  Recognise it as a sorgprosess and ryd i de følelsene before any skill work. Do not pre-decide the leadership identity question; try being a god leder for a year first. Make the rolle-vs-person distinction explicit so the developer can stop interpreting fitting problems as judgments on their elendighet. Expect identitetstap of dybdekunnskap and forced generalisering; expect to be conscripted into an identitetsramme one does not like; expect to be met as inkompetent in the new milieu. Life-stage maturation (partner, children) often coincides with a natural softening of the identity-grip on faget.
• ✅ Why is 'å være seg selv' the wrong demand on senior leaders?
  Because at senior level you are not there as a person but as a rolle, and roles in consequential positions (dommer, kirurg, politi, statsminister) exist specifically to depersonalise action and protect both persons and outcomes. Trump exemplifies the failure mode of too-much-person-too-little-role. The modern individualiserings-tendens (calling statsministeren 'Jonas') drifts us toward the wrong unit of analysis. Coaching should focus on rolle-shape and råd-margin, not on personality.
• ✅ What is the right structural model for a working group?
  Eikeland uses Adam Smith's division-of-labour as the ontological backbone: as complexity exceeds individual capacity, arbeidsdeling produces specialisation; specialisation costs breadth; past roughly 8 people, coordination need exceeds the group's self-organising capacity and ledelse arises as a function. External-facing groups also need a single talsperson. Ledergruppe as institution is a sosial lært praksis rather than a juridical necessity, and is therefore open to interrogation. He does NOT prescribe a specific operating model — instead he reframes the question.
• ✅ Why does no one consult Eikeland on hierarchy and makt despite his interest?
  Because power-holders prefer hierarchy to be unspoken; making it discussable threatens their position. The structural avoidance of the topic is part of how the hierarchy sustains itself.
• ✅ What is the cost of teknologi's rise as the dominant kunnskapshierarki?
  Eikeland names a clear net good (introvert, sosial-angst-prone nerds got a place where their fag created status and gode penger; 30 years ago they would have been på NAV) but also a cost (enklere selgere, the kind without a master's, lost makt as the dominant fag shifted). He does not develop the cost side in depth; it remains a flagged trade-off rather than an analysis.

Gaps

• incompleteThe thesis 'det finnes alltid et hierarki' is rescued from triviality by Eikeland's broad definition (formell + uformell + kunnskaps- + framing-makt), but the same breadth makes the claim nearly unfalsifiable. Every conceivable group has some asymmetry of influence on some dimension; calling that 'hierarki' wins the argument by definition. The conversation does not engage the harder question of when the unit of analysis is wrong — when treating a temporary, context-dependent, weak asymmetry as a 'hierarchy' obscures more than it reveals.
  Read next: Compare to network-and-influence literature (Cross/Parker on organisational networks, Vedres/Stark on structural folds) where the alternative unit is the network of weak ties rather than the layered hierarchy. Also Heath/Sunstein on consensus-driven decision-making to test where 'hierarchy' really is the operating frame.
• incompleteThe claim that flat-org rhetoric is selvbedrag is supported by Eikeland's clinical observation and the innvandrer vignette but not by counter-evidence from organisations that have made the rhetoric operationally real (or that have failed in distinctively non-Eikeland ways). The conversation does not engage Holacracy, Buurtzorg, sociocratic governance, or the long literature of self-managing teams. The result is a strong descriptive claim resting on a single vantage point.
  Read next: Read Laloux Reinventing Organizations, Buurtzorg case studies, Robertson's Holacracy critically — both for examples of self-organisation that genuinely changes which hierarchy operates and for documented failures that Eikeland's frame would explain well. Pair with Lee/Edmondson's typology of self-managing organisations.
• incompleteThe role-vs-person distinction is presented as universal but it conflicts with a strong current of contemporary leadership literature (authentic leadership, bring-your-whole-self-to-work, vulnerability-based trust à la Lencioni/Brown) that holds that role-thick depersonalised leadership is itself the failure mode in knowledge work. The conversation does not engage these counter-positions; it treats them only implicitly via the Trump example, which is a one-sided foil.
  Read next: Read Brené Brown on Dare to Lead, Goffee/Jones 'Why Should Anyone Be Led by You?', Lencioni on vulnerability-based trust against Eikeland's role-thick line. The most interesting test case is: are there role-domains where role-thickness is right (dommer, kirurg, politi) and other domains where it is wrong (product-team leadership, R&D leadership)?
• incompleteEikeland's developer-to-leader sorgprosess prescription is rich on the loss side but thin on the gain side. The transition presumably brings new sources of meaning (impact through others, system-level effect, mentoring, organisational design), but the conversation barely names them. The risk for the listener is to internalise the loss-frame and miss the path through.
  Read next: Camille Fournier's Manager's Path; Will Larson's Staff Engineer/An Elegant Puzzle on the IC-vs-manager fork; Lara Hogan on growing engineering leaders. Pair with Olga Khazan or Lori Gottlieb on the psychology of mid-career identity transitions.
• incompleteThe illusion-of-explanatory-depth intervention (ask for mekanismer not meninger) is presented as reliably productive but Eikeland admits it provokes forbannelse and ejection from rooms. The conversation does not address how to make the intervention land without burning the relationship — i.e., the practice question of how to descend into mekanisme safely. This matters because the intervention has weight only if it can be sustained inside an ongoing leader relationship.
  Read next: Edgar Schein on humble inquiry; Marshall Goldsmith on stakeholder-centred coaching; Patterson et al. Crucial Conversations. The Heis-internal pairing is with Brede Moe (ep 9) on psykologisk trygghet as the precondition for being usable as a diagnostic outsider.
• uninformedThe argument that teknologene have gained makt at the expense of 'litt enklere selgere' is named as a flagged trade-off but not analysed. The conversation does not engage the broader political-economy story of which professions rise and fall with each kunnskapshierarki shift, or the consequences for democratic and labour-market dynamics when one type of fag becomes dominant. Eikeland's clinical vantage is not designed for this question; the gap is honest but real.
  Read next: Read Daniel Markovits The Meritocracy Trap, Michael Sandel The Tyranny of Merit on the consequences of credentialist hierarchies. For the Norwegian case specifically, NAV's own reports on labour-market polarisation.
• incompleteEikeland insists hierarchies are inevitable but does not develop how to design good hierarchies versus bad ones. Hierarchy as a design object — its arity (span of control), its time-horizons per level, its dual lines (formal/uformell), its rotation, its accountability — receives no operational attention. The descriptive claim therefore stops short of a constructive prescription beyond 'operate at the right abstraksjonslag and recognise rolle vs person.'
  Read next: Elliott Jaques on requisite organisation and time horizons per level; Stafford Beer's Viable System Model; James Mwangi on adaptive governance. Pair with Printzell Halvorsen (ep 8) on the Vend operating model as a worked example of an explicit, designed hierarchy that honours these structural pressures.
• incompleteThe claim that ledelse-as-coordination kicks in around eight people is asserted as 'avhenger litt av hvor mye interaksjon du trenger' but not defended against the broader social-science literature on group size, span of control, and self-organisation thresholds. The number is plausible but the conversation does not engage why eight rather than five or twelve, what happens in distributed/asynchronous groups, or how the threshold shifts with technology.
  Read next: Robin Dunbar's hierarchies of group size (5, 15, 50, 150); Christopher Allen's optimal group sizes; Tuckman's small-group dynamics. For the distributed case, GitLab's all-remote handbook on team sizing and the post-COVID literature on async coordination.

Related documents

• The engineering manager role is splitting in two
  Hands-On Leadership & the Pendulum Hierarchy & Org Charts Informal Leadership
• Leder du fra sidelinjen – eller ute på banen?
  Hands-On Leadership & the Pendulum Organizational Abstraction Levels Team Autonomy
• Update on Software Engineering Career Ladder
  Hands-On Leadership & the Pendulum Informal Leadership Team Autonomy
• What 60 Years of Data Reveals About How Men and Women Experience Leadership
  Hierarchy & Org Charts Mental Models & Understanding
• Introduction
  Hierarchy & Org Charts Mental Models & Understanding
• Alex Ewerlöf's Post
  Hands-On Leadership & the Pendulum Informal Leadership
• Scaling the Practice of Architecture, Conversationally
  Hierarchy & Org Charts Team Autonomy
• The Power of Strategic Centering
  Hands-On Leadership & the Pendulum Team Autonomy
• 0) Velkommen til Heis
  Hands-On Leadership & the Pendulum Team Autonomy
• 3) Christin Gorman leder uten tittel
  Hands-On Leadership & the Pendulum Informal Leadership