← Explore all 41 people

Darren Murph

Remote-work leader and former Head of Remote at GitLab

  • Role vs person
  • Business
  • Professional case
  • Case 30 of 41
  • Record last updated October 5, 2026

The case question

Can a role invented for remote work outlast the emergency that made it visible?

What this case shows

Murph shows that a person can carry a method out of an institution without carrying the institution. The asset is clearest where authorship, rights, evidence, direct distribution, and teachable routines are identifiable; it remains founder-dependent where one person's reputation and delivery remain essential.

Sourced to public records9 sources (0 independent)Not independently reviewedHow we check

The career in brief

Murph became known for prolific technology journalism before GitLab appointed him head of remote, where he documented and advocated the company’s all-remote operating model.

Why the case matters

The case asks whether a role created around an organizational experiment can become a durable profession beyond the company and moment that made it visible.

Build · Carry · Control · Continue

Four separate questions. Public visibility alone answers none of them.

Build

What was built

Turning point

A way of working became a formal executive function, public handbook, and portable field of expertise.

Carry

What can travel

Open question

What employment and IP terms governed reuse of methods, language, examples, and materials after GitLab?

Control

What can be governed

Open question

What binding budget, policy, hiring, tooling, or design authority did the role hold?

Continue

What persists if a dependency changes

Open question

What team, recurring revenue, evaluation evidence, and successor capacity exist beyond Murph's delivery?

The tension in this case: here, role vs person means whether authority belongs to the office, the person, or the relationship between them. Look for decisions, methods, relationships, and trust associated with the person as well as the title.

What happened

  1. Before 2019

    Murph developed a portable writing and editorial practice through technology journalism, authorship, and distributed-team experience. Those credentials preceded GitLab but did not constitute ownership of its remote operating system.

    Sources: 09, 01

  2. 2019

    GitLab hired Murph into a newly formalized Head of Remote role. He joined an already all-remote company whose founders, employees, open handbook, tools, and accumulated practices supplied the institutional base he was asked to articulate and scale.

    Sources: 01, 02

  3. 2020–2021

    During the pandemic, Murph became a visible interpreter of GitLab's methods through guides, interviews, talks, and an emergency resource center. External distribution grew while the handbook remained openly and collectively maintained by GitLab contributors.

    Sources: 02, 04, 03

  4. 2021–2022

    As GitLab became public and grew across more than 60 countries, Murph described a cross-functional organizational-design remit. Public accounts document collaboration, not unilateral authority over culture, systems, or employment policy.

    Sources: 05, 06

  5. 2023

    Murph left GitLab and was identified as Andela's Vice President of Workplace Design and Remote Experience, carrying methods and credibility without GitLab's workforce, brand, handbook governance, or platform.

    Sources: 08

  6. 2024–2026

    Murph developed an independent advisory, speaking, and facilitation practice around organizational design, asynchronous work, knowledge systems, and AI transformation. His site presents an 'Org Brain' framework, while private client outcomes, ownership, audience rights, and operating capacity remain undisclosed. A July 2026 interview byline on Allwork.Space also lists him as Head of Culture at Lovie and founder of Page 52 Consulting; this record has no second source for the Lovie role and does not establish the terms of either.

    Sources: 09, 07

What it may mean, and where the evidence stops

Murph's public record distinguishes portable institutional authorship from ownership of the institution authored. He helped make GitLab's distributed-work system legible and exportable, then carried the resulting expertise into Andela and independent advisory work. GitLab's handbook, workforce, products, governance, and collective knowledge were never his personal assets.

Evidence that complicates the first reading

  • GitLab was all-remote and handbook-first before Murph arrived; his contribution was articulation, systematization, education, and field building rather than sole creation.
  • A public handbook makes knowledge portable, but openness does not transfer employees, brand, data, customer relationships, authority, or contributors' labor.
  • Pandemic demand amplified remote-work authority; visibility in 2020–2022 does not establish enduring adoption or client outcomes.
  • The role crossed people operations, communications, marketing, and organizational design; breadth may increase influence while leaving formal rights diffuse.
  • Independent advising increases control over positioning and methods but may deepen dependence on Murph's reputation, selling, speaking, and delivery.

What remains unknown

  • Which handbook sections, frameworks, research products, and programs did Murph originate, co-author, edit, or represent?
  • What employment and IP terms governed reuse of methods, language, examples, and materials after GitLab?
  • What binding budget, policy, hiring, tooling, or design authority did the role hold?
  • Who inherited the GitLab role’s duties after Murph, and what continued at comparable quality?
  • What authority and measured impact did Murph's Andela role carry?
  • Who owns the Org Brain name, curriculum, client work, lists, recordings, and derivatives?
  • What team, recurring revenue, evaluation evidence, and successor capacity exist beyond Murph's delivery?

Change one dependency

Use a counterfactual to expose the architecture: answer first, then compare your reasoning with the record.

Write a sentence or two before you look at the record. Your answer is kept only in this browser; nothing is sent, scored, or stored on a server.

Read it against another career

Hold the tension constant across different careers, or hold the field constant and inspect a different path. A comparison is useful because it can challenge the first explanation.

Open the full comparison tool →

Sources and their limits

9 sources: 0 independent and 9 other (primary, institutional, subject interviews, self-authored, or republished reports). First-party sources and interviews establish what a person or organization said or announced; they do not independently prove performance, ownership, causation, or impact. This is analysis of a public record and makes no rating of the person.

Each link was checked by hand during the record’s source review; the site does not continuously re-check them. A broken link, or one that does not support its statement, is a defect in the record. Please report it. 1 link leads to a publisher or organization landing page rather than the exact supporting item, so it identifies a research lead rather than a claim-level citation.

  1. Podcast episode in which Murph describes joining GitLab as head of remoteSubject interview · Running Remote · 2020
  2. Murph-authored account of GitLab's pre-existing all-remote system and handbookPrimary source · GitLab · December 10, 2019
  3. Current collectively maintained all-remote operating handbookPrimary source · GitLab · Current record
  4. Institutional interview on the Head of Remote remitInstitutional source · Crowe · March 11, 2021
  5. First-person account of cross-functional work and distributed-workforce scalePrimary source · Twist · September 28, 2022
  6. Institutional interview documenting leadership principles and GitLab roleInstitutional source · Coursera · January 20, 2023
  7. Interview byline listing Murph as Head of Culture at Lovie and founder of Page 52 Consulting, and announcing a November 2026 bookSubject interview · Allwork.Space · July 20, 2026
  8. Podcast interview in which Murph describes his move from GitLab to AndelaSubject interview · Between Two COOs · October 17, 2023
  9. Current first-party advisory practice, frameworks, and former GitLab rolePrimary source · Darren Murph · Current record

Part of RN Collins, selected work (opens in a new tab)

Turn the lens on your own work

The same four questions (Build, Carry, Control, Continue) apply to any career, including yours.

The I/1 Edit

One sharp idea. New editions arrive by email.

One argument about work, power, and ownership, made concrete through a real case. Sources and tools live on the web edition.