3) Christin Gorman leder uten tittel

Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · podcast · 2025-10-27 source ↗ Reader 🖥️

Go to the Floor (Gemba)Hands-On Leadership & the Pendulum Informal Leadership Public-Sector Digitalization

Title-less leadership is influence through clear, accountable public voice — anchored in actually delivering working software and a financial freedom that lets you keep telling the truth — and it is one legitimate, complementary mode of leadership in a tech industry that needs many such modes, even though it has real costs (intimidation effects, defensive listeners, and an asymmetry where formal leaders take credit when title-less leaders' ideas do get adopted).

practical · mixed — Hybrid: argumentative (Gorman defends a specific stance toward formal leadership and the role of clear, named voices in tech), narrative (anecdotes from JavaZone, Kodemaker, home renovation, helse-IT), and dialogic (hosts probe and reframe). Practical because the joint thesis is action-oriented: how to influence software practice and decisions without formal title — and when the title might nevertheless become necessary.

Structure

Part	Role
Opening framing by hosts: Gorman as both 'high and low' — on the floor coding and on the Arendalsuka stage — and as Norway's clearest developer voice who nevertheless doesn't think of herself as a leader.	context
Gorman's account of why she has avoided formal leadership: she would have to climb a 'middle-management ladder' where she can neither deliver herself nor wield real authority on the big problems; she would 'quit after a month.'	evidence (autobiographical)
How she operates: stage talks, writing, and LinkedIn debate as a way to think through her own positions and propagate knowledge — driven by 'liking the process of formulating and conveying' rather than wanting to lead.	evidence (mechanism)
Recognition of an emerging problem: as her public weight grows, she can no longer act as 'a normal team member' — colleagues either accept her statements without challenge ('but it was Christin Gorman who said it') or become defensive; she is rethinking what assignments she can take.	self-critical evidence / qualification
Story-craft: how she builds talks (Hibernate as cake-mix, Tower of Babel, 140-slide helse-IT talk) — analogy as the primary cognitive tool for making ideas memorable and shareable.	evidence (mechanism)
The authenticity / economic-independence argument: she can speak honestly because she lives cheaply in Drammen and could 'go back to working at Kiwi' — economic freedom is the precondition for truth-telling.	premise (load-bearing)
Industry-level argument: software has matured as a craft but Norwegian public sector lags; bottom-up change is insufficient; senior leaders must be reached, which requires translators (a role she increasingly plays — 'wearing a nicer shirt') without becoming managers themselves.	argumentative core
Plurality-of-modes claim: many different forms of leadership are needed; she will never get done what the hosts (more diplomatic, more formal) can get done, and vice versa. Don't tell anyone to lead more like you.	central prescriptive claim
Picture of good formal leadership when it exists: the manager at 'Western' (likely a former workplace) who knew the work, was decisive, said 'I'm not paying for that' — clarity, willingness to be unpopular, technical understanding.	evidence (positive example by contrast)
Take the floor seriously: developers, like the carpenter who project-led their home renovation, are 'more than ticket-converters'; AI can only replace developers who shouldn't have existed in the first place.	narrative / analogy
Self-examination of why she would be a bad formal leader: she 'takes up a lot of space,' swallows fewer camels when she has authority, and might be too vain about being liked — therefore best as an external voice.	qualification / self-criticism
Reciprocity: she actively tries to elicit disagreement ('what do you think?'), defers in her current role to her client on contested calls, and accepts technological choices she disagrees with when delivery is the goal.	qualification
Closing humor: turtles and a minigris named Templeton Pig — and hosts' takeaway that her interest in vision and direction sits oddly with her self-description as 'midt på treet.'	framing

Key terms

uformell ledelse / leder uten tittel Informal Leadership
Influence on how software is built and decisions are made, exercised through public voice (talks, writing, LinkedIn) and through delivering working software — without formal organizational authority. Gorman explicitly distinguishes this from being a 'lederskikkelse' (leadership figure) and treats it as a chosen complementary mode, not as a step below formal leadership.
basis
An evidential foundation, grounded in current practitioner experience, that gives public statements credibility. 'Hvis ikke du har noen basis som du kommer fra, så er du ikke troverdig.' The contrast figure is the 'arkitekturperson som bare kommer med utdaterte råd som ingen klarer å implementere.'
levere verdi / faktisk levere
Producing working software that is actually used and makes a measurable difference (e.g. shared journal documents in healthcare). This is both her source of meaning and the alignment point with private-sector leadership — 'jeg er enig med dem at jeg prøver å levere resultater.' Used as the dividing line between productive technologists and unproductive ones (architects who argue, budget-growers in public sector).
stolt og ydmyk
Used pejoratively as an example of LinkedIn 'bullshit and meaningless pjatt' — the empty self-congratulatory cliché that signals nothing and that her own clear voice is a deliberate refusal of.
svelge kameler
Putting up with decisions and practices you disagree with because you have no mandate to change them. She does this constantly as a consultant ('jeg har jo ingen formell ledelsesstilling — jeg er jo ikke vant til å få viljen min i det hele tatt'); becoming a manager would mean swallowing fewer, which she sees as a *risk*, not a perk.
autentisk
Speaking and acting consistently with what you actually believe, made possible by economic conditions that mean you do not need to be coerced into a position. 'Jeg trenger ikke å tjene noe som helst, vi har det helt fint.'
tydelig / tydelige stemmer
Speaking clearly enough that real disagreement is possible. 'Hvis du sier noe som ingen er uenig i, da har du ikke sagt noe interessant.' Contrasted with Norwegian consensus culture, especially in public-sector healthcare governance.
engasjert utvikler
Used semi-ironically — what she is dismissed as by senior leaders who think developers cannot see the bigger picture. The framing that disqualifies her from being heard by exactly the leaders she most wants to influence.
intimidet / skummel
The effect her presence now has on lower-experience managers and teammates, even when she does not intend it. She names this as a cost of having accumulated public weight without a corresponding bounded role.
kampen
The political fight a leader has to take to overrule a popular but wrong direction. She praises the manager who 'tør å ta den kampen' and explicitly says she would not, because she cares too much about being liked.
ta folkene på gulvet på alvor Go to the Floor (Gemba)
Treating practitioners as intelligent collaborators capable of understanding the bigger picture if let in — illustrated by the carpenter analogy. The substantive content of the 'good leadership' she advocates.

Propositions

explicitTitle-less leadership is a chosen, legitimate, and complementary mode of leadership — not a consolation prize for those who couldn't get titles.conf: high
explicitPublic credibility for a title-less leader requires a 'basis' — current practitioner experience producing working software — otherwise you become the architecture-person dispensing outdated, unimplementable advice.conf: high
explicitEconomic independence — living below your means so that losing all your work would still be survivable — is the operational prerequisite for being able to speak truthfully in public.conf: high
explicitBecoming a formal middle manager would mean swallowing fewer 'camels' — that is, getting more of your way — which is precisely why Gorman fears it: she does not trust herself to remain self-critical without the resistance of having to argue.conf: high
explicitTitle-less leadership has real costs: the bearer becomes intimidating to less experienced colleagues, gets either uncritical agreement or defensive rejection, and can no longer function as a normal team member — costs that a bounded formal role would absorb.conf: high
explicitThe Norwegian public sector's leadership problem is not too little leadership but too many layers of middle management combined with top leaders who lack the technical understanding to know what to ask for.conf: high
explicitNorwegian consensus culture systematically suppresses clarity, and clarity is the precondition for productive disagreement: 'If no one disagrees with what you said, you haven't said anything interesting.'conf: high
explicitAnalogy ('Hibernate as cake mix,' 'Tower of Babel') is the primary cognitive medium for moving software ideas — it makes them memorable, relateable, and survivable across audiences.conf: high
explicitAI can only replace developers whose role was reduced to converting tickets to bits — and those roles should never have existed; the developers who matter were always more than that.conf: high
explicitTreating people on the floor as capable of understanding the bigger picture — and giving them that picture — produces better outcomes than delegation through layers of middle management.conf: high
explicitPrivate-sector leadership is easier to align with because management and engineers share an objective (deliver value per kroner); Norwegian public sector replaces this with a game of growing one's budget.conf: medium
implicitGorman is the right person to be a clear public voice partly because she actively wants disagreement and would be unable to suppress dissent if she were the boss — making her better as an external pressure than as a formal authority.conf: high
explicitThere is an asymmetry in credit: when the title-less leader's ideas get adopted, the formal leader takes the recognition — and Gorman explicitly accepts this trade as the price of having said the thing at all.conf: high
explicitHosts' framing: Gorman is in a power position despite having no title — clear public voice is a kind of agenda-setting power, and the responsibility that comes with it cannot be evaded by denying the title.conf: high
explicitGood formal leadership is characterized by technical understanding, willingness to be unpopular, and the ability to say 'I won't pay for that' even when the team disagrees — Norwegian leadership culture is short on this kind of clarity.conf: medium
implicitImplicit: a title-less leader's most replicable skill is not opinion but analogy-construction — turning specialist knowledge into stories laypeople and leaders can retain.conf: medium

Arguments

Christin Gorman should remain a title-less leader rather than enter formal management. strength: high

Explicit premises:

She would not survive the first rungs of a management ladder where she can neither deliver nor wield real authority on big problems.
She would be at risk of being unchallenged: 'I would say so, and people would just do it.'
She cares too much about being liked to take the unpopular fights formal leadership requires.
Her contribution — clear public voice grounded in delivery — is one legitimate form of leadership among many that the industry needs.

Implicit premises:

Authority without resistance corrupts judgment: she trusts her own thinking only because she has to argue for it.
The formal-leadership ladder selects against the very traits (delivery competence, public clarity) that make her useful.
Plurality of leadership modes is intrinsically valuable — no single mode can substitute for the others.

Inferences:

Career advice that frames title-less influence as a stepping-stone to formal leadership is structurally mistaken.
Organizations that rely on her kind of voice need to design ways to receive it without requiring her to take a title.

Title-less leadership requires both a delivery basis and economic independence. strength: high

Explicit premises:

Without a basis in current practice you become the architecture-person nobody can implement.
Without economic independence you are coerce-able into pulled punches.
Authenticity — saying what you actually believe — is the medium of this leadership mode.

Implicit premises:

Most people in tech do not have either condition, so this mode is not freely available — it is a privileged position.
Public-voice leadership without a basis is not just ineffective but actively harmful (the consultant-with-outdated-advice).
Material modesty (Drammen, willingness to return to retail work) is the actual mechanism — not high income.

Inferences:

Title-less leadership is only stable as a generalizable model if either (a) more practitioners adopt material modesty, or (b) institutions create funding structures that protect honest public voices.
The model has a survivorship-bias problem: we hear from Gorman because her conditions hold; we do not hear from those whose conditions do not.

The Norwegian public sector's IT problem is mostly a leadership problem, and bottom-up change is insufficient to fix it. strength: low

Explicit premises:

Senior leaders do not understand the technology enough to know what to ask for.
There are too many layers of middle management between knowledge and decision.
Public-sector incentives reward budget growth over delivery efficiency.
Consensus culture (e.g. four health regions, none with authority) blocks decisive action.

Implicit premises:

Software-development practice has matured enough that there is a 'right' set of questions leaders should be asking — and most are not.
The translator role (developer who can speak to executives) is currently underprovided.
Private-sector alignment around 'levere verdi' is closer to natural than to engineered — Gorman attributes private-sector tractability to shared goals.

Inferences:

Title-less leadership cannot fix this on its own — it depends on senior leaders being willing to be reached.
Therefore the optimistic case for Gorman's mode requires complementary formal leaders who actively want translation.

Many modes of leadership are needed; one should not advocate that others lead more like oneself. strength: high

Explicit premises:

Gorman acknowledges her own style limits what she can get done (people become defensive).
The hosts will accomplish things she cannot because of their different style.
Both clear-stem and consensus-building styles produce different but real value.

Implicit premises:

Industry conversations about leadership style tend toward prescriptive monoculture — and this is the move she is resisting.
There is something like a portfolio diversification argument for leadership style: a community needs a distribution.

Inferences:

Critiques of Gorman's directness ('you should swallow more camels') misunderstand the function of clear voices in the ecosystem.
Mentorship models that try to make everyone into a 'Christin Gorman' would degrade the very signal her style provides.

Talented developers are not interchangeable with AI; treating them as ticket-converters is itself the leadership failure that makes them seem replaceable. strength: low

Explicit premises:

AI can replace developers who only convert tickets to bytes.
Such developers 'should never have existed.'
Real developers — masters-degree-level, problem-engaged — can do far more if given the bigger picture (carpenter analogy).

Implicit premises:

The 'replace developers with AI' framing is a symptom of an already-degraded view of developer work.
The fix is leadership that lets developers in, not better AI tooling.
Offshoring layers (the 'India consulting team' figure) are the same anti-pattern at a different scale.

Inferences:

Organizations panicking about AI replacement of developers should first audit whether they were ever using their developers correctly.
Investing in 'better prompts' downstream of bad delegation chains is solving the wrong problem.

The host's challenge — 'you have informal power too, what do you do with it?' — is answered by Gorman's account of using it carefully (soliciting disagreement, deferring on contested calls, accepting choices she disagrees with). strength: medium

Explicit premises:

She actively asks 'what do you think?' precisely because she fears people will just go along.
In her current role she defers to the client on contested decisions and says so explicitly.
She can live with technology choices she would not have made if delivery happens.

Implicit premises:

Informal power is more easily abused than formal power because it has no built-in accountability mechanism.
The remedy is voluntary self-binding — choosing to surface disagreement, defer, and let things go.
Hosts' framing (that responsibility comes with audience) is correct and she has internalized it.

Inferences:

A code-of-practice for title-less leaders could be sketched from her behavior: visible self-binding, active dissent-seeking, willingness to be wrong publicly.
Title-less leadership without these self-bindings is just unaccountable influence.

Narratives

The JavaZone 2011 Hibernate-as-cake-mix talk: comparing Hibernate to a cake mix that is supposedly beneath a real baker's dignity — analogy as the primary tool for making a technical position memorable and shareable.
→ Supports the proposition that title-less leadership's medium is well-told analogy grounded in specialist knowledge; also evidence that her voice has compounding reach (second-most-viewed JavaZone video ever).
The helse-IT (healthcare IT) talk: 140 slides cut to fit a 45-minute slot, saved by a fire alarm that bought 25 extra minutes; positive feedback from Statens Vegvesen running up afterward to say 'this was us too.'
→ Supports the unity claim that delivery experience (shared journal documents in healthcare) is the basis for public voice — and that resonance happens when others recognize their own situation in the analogy.
Home renovation by working directly with an experienced carpenter rather than going through architects' drawings and bidding — letting him project-lead because he had ideas they had never considered.
→ Carries the argument that respecting practitioners' judgment and giving them the bigger picture produces better outcomes than layered delegation — transposed analogically from carpentry to software.
The 'Western' (likely former workplace) manager who said 'I'm not paying for that' to a developer still polishing a finished task — controversial but technically literate and decisive.
→ Provides her positive example of formal leadership; supports the argument that the failure mode of Norwegian leadership is diffuse consensus-seeking, not authoritarianism.
The Kodemaker observation: she has stayed longest at Kodemaker because consultants are allowed to remain technical without being pushed onto the management track — and even there, some were initially worried she was 'too controversial.'
→ Evidence for the structural claim that the Norwegian tech career path defaults to assuming senior developers want to manage, which is structurally hostile to title-less leadership.
The 'KrangleFantTumblr.com' (early blog/site) era of going hard on opinions online and accepting consequences.
→ Origin story for her public-voice mode; supports the implicit premise that being a clear voice is something one practices into.
The 'nicer shirt' / Arendalsuka turn: deliberately presenting herself differently to reach senior leadership audiences because bottom-up change has hit a ceiling.
→ Supports the proposition that the title-less leader has to adapt medium and register to influence levels of the system that the floor cannot reach.
Templeton Pig (minigris named after The A-Team's Templeton Peck) — and the family joke that they like him even though they would not like him if he were a person.
→ Framing humor — but also a small instance of her habit of finding the surprising analogy that holds two things together (admirable / unlikeable; effective / annoying).

Questions addressed

✅ What does it mean to lead without a title in tech?
Influence through clear public voice (talks, writing, debate) grounded in delivery experience and protected by economic independence, accepting that credit may go to formal leaders.
✅ Why has Gorman chosen this mode rather than formal leadership?
The middle-management ladder is hostile to delivery competence; she would not trust herself with the unchallenged authority of a senior role; her style would do more damage from inside a hierarchy than from outside.
✅ What are the costs of title-less leadership?
Intimidation effects on less-experienced colleagues, uncritical agreement OR defensiveness, inability to function as a normal team member, and asymmetric credit allocation when ideas are adopted.
✅ How does one construct the talks that make this kind of leadership possible?
Find the resonant analogy; treat the audience as capable of relating new ideas to existing concepts; ground the talk in delivery experience.
✅ Why doesn't Norwegian public-sector IT improve faster?
Too many middle-management layers, top leadership without technical literacy, budget-growth incentives instead of value-delivery, and consensus culture that blocks decisive moves.
⭕ Is title-less leadership universalizable, or is it a privileged mode?
Gorman names her preconditions (delivery basis, economic modesty) but does not address whether they generalize. Implicit answer: it is at least partly privileged — those without economic cushion or platform access cannot adopt it.
⭕ When is the formal title load-bearing rather than optional?
Gorman gestures at it — the unpopular fights, decisive 'I'm not paying for that' moves, the ability to overrule popular but wrong directions — but does not fully theorize when title-less voice cannot substitute.
⭕ Whose work is invisible without titles? Who can't be a title-less leader for reasons of safety, privilege, or platform access?
Not addressed — the episode assumes a speaker who can choose between modes.

Gaps

incompleteThe episode does not address whose work is *invisible* without a title — those without platform, conference speaker credibility, financial cushion, or social safety to speak controversially. Gorman names her own preconditions (cheap living in Drammen, ability to return to retail work) but does not extend the analysis to those whose preconditions do not hold. Title-less leadership in her account is universally legitimated but materially restricted.
Read next: Read against Cutler on institutional overload and 'who gets to think' / power and space (TBM 413); against work on visibility and credit allocation in tech (especially gendered patterns); and against critiques of 'thought leadership' as a privilege economy. The Bekk/Kodemaker consulting ecosystem also deserves examination as the platform infrastructure that makes Gorman's mode possible at all.
incompleteWhen is the formal title load-bearing? Gorman gestures at the answer (taking unpopular fights, decisive 'I'm not paying for that' moves) but does not theorize when title-less voice strictly cannot substitute. The carpenter renovation analogy works because the homeowners had authority — Gorman in a team without it cannot replicate that pattern.
Read next: Read Morten Eikeland (Heis ep 4) 'det finnes alltid et hierarki' as the explicit counter-claim. Also read Una Aamodt Mathisen (Heis ep 10) 'lede uten fasit' as a complementary refusal-of-answer-key mode. The cross-cutting question: which leadership functions can be unbundled from title and which cannot?
incompleteThe asymmetry of credit ('formal leaders take recognition when title-less leaders' ideas land') is named as a price Gorman is willing to pay, but not analyzed as a systemic problem. Who benefits from this asymmetry? It serves the formal leadership class — both the leaders who take credit, and the system that does not have to compensate the title-less.
Read next: Read on credit assignment in collaborative work, on academic citation/recognition norms, on the labor economics of 'thought leadership' (Substack, conferences). Connects to Cutler on 'directly responsible individuals' from the recognition side.
incompleteThe framing of public-sector dysfunction as 'budget growth instead of value delivery' is a strong claim presented anecdotally. The implicit comparison to private sector ('we are on the same team') under-acknowledges that private-sector alignment is also engineered and partial — shareholder vs. employee interests, sales vs. engineering, short- vs. long-term.
Read next: Read Nils Brede Moe (Heis ep 9) on the AI-paradox and learning culture; read public-sector reform literature (NAV's 'optimizing for fast flow' is on the user's list). Also read industrial-organization work on aligned vs. misaligned incentives across sectors.
incompleteImplicit premise about authority and self-correction ('I trust my own thinking only because I have to argue for it') is asserted as autobiographical but generalized. The argument that formal authority degrades judgment by removing resistance deserves more scrutiny — many formal leaders maintain rigorous self-criticism, and many title-less voices ossify.
Read next: Read on epistemic humility and authority (Annie Duke on 'Thinking in Bets' framing of belief-updating; Greger Teigre Wedel (Heis ep 12) 'når sjefen har svaret' on the inverse problem). Also Beck on Tidy First / TDD as institutionalized self-correction independent of authority.
uninformedThe episode does not engage with how AI coding agents change the picture of who counts as a 'delivery-grounded' practitioner. Gorman's 'basis' criterion is rooted in writing code yourself — but what counts as that basis when much code is now generated and curated? The 'AI replaces ticket-converters' framing is correct but stops short of asking what the basis becomes.
Read next: Read Heis ep 11 (Vilde Opsal / Anders Sveen AI special) and ep 13 (Tobias Torrissen on code quality + AI); read the user's Kent Beck Tidy First and Claude Code material — what is the 'basis' equivalent when the medium shifts?

3) Christin Gorman leder uten tittel

Structure

Key terms

Propositions

Arguments

Narratives

Questions addressed

Gaps

Related documents