GitLab's CREDIT Values Are Gone. What Does That Actually Tell Us?

When the company that wrote the remote-work playbook quietly closes the book, something worth examining just happened.

The Document That Became a Movement

Think about what it means to make your entire company operating manual public — not just a polished 'About Us' page, but the real stuff. How decisions get made. What the company actually values. How people are expected to treat each other on a Tuesday afternoon when nobody is watching. That is what GitLab did with its public handbook and its CREDIT values framework, and for a long time, it was genuinely remarkable. GitLab describes itself as 'the intelligent orchestration platform for DevSecOps where teams and their AI agents ship secure software faster.' But for a generation of remote-first tech workers, GitLab was equally famous for something else: the idea that a company's culture could be documented, version-controlled, and made visible to the entire internet. Dozens of companies copied the model. It shaped how people thought about async work, transparency, and what it even means for an organisation to have values. That is the context you need before the next part of the story lands properly.

What CREDIT Actually Was — And What It Was Supposed to Do

CREDIT stood for Collaboration, Results, Efficiency, Diversity, Iteration, and Transparency. These were not just words on a poster in a lobby nobody visits. They were supposed to be load-bearing — the kind of values that shape actual decisions, not just describe decisions already made for other reasons. The transparency piece was the most visible expression of this. Shannon Maccado, a Strategic Account Executive at GitLab, described what she found when she joined: 'I expected GitLab to be transparent, but I was amazed by the level of access to information.' She had visibility into companywide objectives and key results, into strategic decision-making processes. 'The company truly lives its values, and you can feel that in every interaction,' she said. 'The transparency, collaboration and everyone can contribute mindset creates an environment where you can thrive, both personally and professionally.' That is the promise of a values document done seriously — that it produces a felt reality, not just a framed sentence.

The Layoffs and the Retirement: Why the Timing Is the Story

Here is the uncomfortable question that the simultaneous announcement of workforce reductions and the retirement of the CREDIT framework forces into the open: were those values ever load-bearing, or were they always decorative? Load-bearing values are ones that constrain decisions. They make certain choices harder to make because the company has publicly committed to something. Decorative values describe decisions already made — they are the narrative layer applied after the fact. The pattern is not unique to GitLab. Public values documents tend to survive good times and get quietly retired in bad ones. That timing is itself data. It tells you something about the relationship between a company's stated principles and its actual decision-making machinery. When the pressure is low, the document and the decisions can coexist comfortably. When the pressure rises — when there are hard choices about headcount, about resources, about direction — the document either shapes those choices or it gets shelved. The retirement of CREDIT, alongside layoffs, is a case study in which of those two things happened.

What GitLab's Own Team Said the Culture Actually Was

The sources available here are employer-brand profiles, which means they capture the experience of people who chose to speak positively about working at GitLab. That is worth naming. But even within that framing, what team members described is genuinely interesting. Harshit, an IT Enterprise Applications Engineer on GitLab's global CIO team in India, described the remote-first environment as 'seamless in the best sense' — a place where the work he did and the decisions he contributed to had real global impact. Pratik, a leader in Robotic Process Automation on the same team, described the work as 'not just building tools' but 'giving people back time they can spend on more meaningful work.' Monali, a QA manager, pointed to a portfolio of automation solutions that 'saves thousands of hours every quarter across various departments.' What these accounts describe is a culture where the iteration and efficiency components of CREDIT were genuinely operational — where the values showed up in how work was structured, not just how it was talked about. That makes the retirement of the framework more complicated, not less.

What to Watch Next

The question that outlasts this particular moment is one that any organisation with a public values document should be sitting with: what happens to your stated culture when the conditions that made it easy to live by disappear? GitLab's public handbook model was genuinely influential. The companies that copied it are now watching to see what the original author does next. If the values framework gets replaced by something more honest about trade-offs, that is one kind of outcome. If it simply disappears and is replaced by nothing, that is a different kind of signal entirely. The broader pattern — values documents surviving good times and retiring in bad ones — is worth tracking across the industry. The next time a company publishes a detailed, public, version-controlled culture document, the GitLab story is the reference point people will reach for. Whether that reference point becomes a cautionary tale or a more nuanced lesson about what documentation can and cannot do depends entirely on what GitLab does with the space where CREDIT used to be.