GitLab's 'Act 2': Pivoting to an Agentic Future via Workforce Reduction

GitLab has announced a sweeping transformation it calls "Act 2," a strategic pivot designed to position the company for what CEO Bill Staples describes as the "agentic era" of software engineering. This transition is not merely a product update but a fundamental restructuring of the company's operational footprint, organizational hierarchy, and core cultural values.

While the company frames this as a proactive move to capture the largest opportunity in its history, the announcement has sparked significant debate among employees and the broader technical community regarding the intersection of AI hype, corporate restructuring, and the erosion of company values.

The Structural Shift: Flattening and Right-Sizing

To align with its new strategic thesis, GitLab is implementing several aggressive operational changes aimed at increasing speed and reducing bureaucracy:

• Workforce Reduction and Footprint Optimization: GitLab plans to reduce its operational footprint by up to 30% in countries where it maintains only small teams, shifting those markets toward a partner-led model.
• Organizational Flattening: The company is removing up to three layers of management in certain functions. Staples argues that eight layers of management were too deep, creating filters that slowed down communication and priority setting.
• R&D Reorganization: The R&D department is being restructured into roughly 60 smaller, empowered teams with end-to-end ownership, nearly doubling the number of independent teams to foster autonomy.
• AI-Driven Process Rewiring: Internal processes—including reviews, approvals, and handoffs—are being automated via AI agents to "right-size" roles across the organization.

The Strategic Thesis: The Agentic Era

At the heart of "Act 2" is a set of core beliefs about the future of software. GitLab posits that software will increasingly be "built by machines, directed by people," where AI agents handle the planning, coding, reviewing, and deploying, while humans provide the high-level judgment on architecture and customer problems.

To support this, GitLab is making five primary architectural bets:

1. Machine-Scale Infrastructure: Reengineering the underlying infrastructure (and Git itself) to handle the high-frequency commit and pipeline rates generated by agents.
2. Full Lifecycle Orchestration: Moving beyond simple AI code generation to a layer that coordinates agents across the entire software lifecycle.
3. Context as a Competitive Advantage: Leveraging GitLab's connected data model (planning, code, security, and ops) to provide agents with superior context, reducing token spend and improving results.
4. Core Governance: Building identity, audit, and policy services directly into the platform to ensure enterprises maintain control over autonomous agents.
5. Hybrid Operational Modes: Supporting a spectrum of human-owned, agent-assisted, and agent-autonomous work across cloud and model-neutral environments.

A Cultural Pivot: Retiring CREDIT

Perhaps the most controversial aspect of the announcement is the retirement of the CREDIT values (Collaboration, Results for Customers, Efficiency, Diversity, Inclusion & Belonging, Iteration, and Transparency). In their place, GitLab is introducing three new operating principles:

• Speed with Quality: Prioritizing faster movement with tighter cycles and stronger guardrails.
• Ownership Mindset: Expecting individuals to act as stewards of the company, removing handoffs that dilute accountability.
• Customer Outcomes: Measuring success by actual customer impact rather than internal activity or roadmap milestones.

Community and Employee Reaction

The response from the Hacker News community and GitLab employees has been largely skeptical, with many viewing the "agentic era" narrative as a cover for financial pressures.

Skepticism Toward AI Narratives

Critics argue that the pivot is a reaction to a declining stock price rather than a genuine technological breakthrough. One observer noted, "What a shock, company whose share price is in the shitter lays people off and blames AI." Others questioned the logic of reducing resources while simultaneously claiming to pursue the "largest opportunity in [their] history."

Concerns Over Quality and Governance

Technical contributors expressed concern over the plan to automate reviews and approvals. Given past security vulnerabilities, some users are wary of a "speed run to a parallel autonomous unreviewed code base."

"Having used AI to write code, and seen the bs it outputs half the time, any org speed running to a parallel autonomous unreviewed code base is going to get hit with a massive rude awakening when their cluster f of a codebase melts down."

The Loss of DEI and Transparency

The removal of "Diversity, Inclusion & Belonging" from the core values sparked significant backlash. Critics argue that DEI is not a "convenience" to be discarded during tough times but a fundamental value.

"DEI isn’t something you pick up when the popular movement swings towards it as a method of convenience, it’s a value you have to live by especially when times are tough."

Furthermore, employees expressed anxiety over the "transparent" restructuring process, which includes a voluntary separation window and a delayed finalization date of June 1, which some described as leaving staff in a state of prolonged uncertainty.