Where the goblins came from: Lessons in team identity

If you’ve spent any time digging into the history of AI development, you’ve likely stumbled across the term "Goblins." It sounds like a piece of lore from a fantasy novel, but for the team at OpenAI, it represents a pivotal moment in the evolution of reinforcement learning. Understanding where the goblins came from isn't just about trivia; it’s about how naming conventions and internal culture dictate the trajectory of high-stakes technical projects.

Most people assume that high-level research teams are named with clinical, sterile precision. They expect "Project Alpha" or "Alignment Initiative 4." But the reality is that the most effective teams often adopt names that feel slightly rebellious or self-deprecating. The "Goblins" moniker emerged during the early, messy days of RLHF. It was a way to signal that the work was iterative, unpolished, and fundamentally different from the rigid academic structures that preceded it.

Why internal culture drives technical output

When you label a group of engineers and researchers as "Goblins," you’re doing more than just picking a fun Slack channel name. You’re creating a psychological container for the work. In this case, the team was tasked with the grueling, often tedious process of cleaning data and refining model outputs. It’s the kind of work that burns people out if they view it as mere "data entry." By embracing the goblin identity, the team reframed the drudgery as a specialized, almost subterranean craft.

Here is why this matters for your own technical projects:

• Shared identity: A unique team name creates an "us vs. the problem" mentality.
• Psychological safety: It allows for failure in a way that "Project X" does not.
• Reduced friction: It signals that the team is operating outside the standard corporate bureaucracy.

If you’re struggling to get a team to own a difficult, long-term objective, stop trying to make it sound prestigious. Give them a name that reflects the reality of the grind. Does your team have a name that actually resonates with the work they do, or is it just a placeholder from HR?

The edge case of naming conventions

There’s a counter-intuitive truth here: the more "professional" a team name sounds, the more likely the team is to hide their mistakes. When you call yourself the "Advanced Alignment Research Group," you feel a pressure to be perfect. When you call yourself the "Goblins," you’re allowed to be messy.

This is where most managers get tripped up. They want to project authority, so they choose names that sound like they belong in a boardroom. But in the trenches of AI research, authority is earned through iteration, not through branding. The Goblins succeeded because they were comfortable being in the weeds, iterating on feedback loops that everyone else found too boring to touch.

That said, there’s a catch. You can’t force a culture. If you try to manufacture a "cool" team name, it will feel like a corporate mandate and backfire immediately. The best names emerge organically from the shared pain of the work. If you want to know where the goblins came from in your own organization, look at the projects that everyone else is avoiding. That’s where your next high-performing team is hiding.

If you’re currently leading a team that feels disconnected from their mission, try shifting the focus toward the specific, gritty problems they solve daily. Stop worrying about the optics and start focusing on the identity. Read our breakdown of how to build high-performing research teams next, and share your own experiences with team naming in the comments.