DeepMind Workers Say Google Rerouted Internal Chat Channels to Block Their Union Drive

DeepMind, Google's London-based AI research lab, is in the middle of its first formal fight over whether its researchers can unionize, and the dispute has settled on an unusual subject: the company's own internal chat tools.

In late June or early July 2026, a Wednesday meeting convened under Acas — the UK's state-backed service that mediates recognition disputes when an employer refuses to voluntarily recognize a union — brought together DeepMind HR, an Acas arbitrator, union officers, and DeepMind employees behind the organizing drive. Senior DeepMind leadership did not attend. WIRED first reported the meeting's conduct.

The session began with a DeepMind employee reading a prepared letter on behalf of colleagues supporting unionization. The letter, reviewed by WIRED, said: "Instead of having meaningful dialogue with its employees about our concerns, Google DeepMind workers have been treated as a problem handed off to HR." The employee reading the statement was interrupted twice by DeepMind HR representatives, according to multiple people with knowledge of the meeting.

The letter goes further than procedural complaint. It alleges that Google attempted to "quash open dialogue between DeepMind employees and crack down on dissent, by shutting down or reconfiguring internal chat venues, and preventing staff from responding to company-wide communications about the unionization bid." Employees who worked around the restrictions, the letter claims, were "reprimanded" by HR. A DeepMind employee involved in drafting the letter, who asked for anonymity because they were not authorized to talk to the press, told WIRED: "The intention was to intimidate. These are well-established union-busting techniques."

The accusation reframes the dispute. Most UK tech-sector union fights are about scope, pay, or working conditions. Here, the named mechanism is internal infrastructure: the same chat tools DeepMind employees use to coordinate research were, according to the allegations, reconfigured in ways that limited how the organizing campaign could communicate. If accurate, that gives a company that controls the communication substrate a structural lever that does not require an explicit anti-union statement.

John Chadfield, a CWU officer who attended the meeting, framed the senior-management absence at the opening session as a labor-relations signal. "Recognition talks not being attended by senior management at the opening stage is a leading indicator that a company isn't engaging in good faith," Chadfield told WIRED. "It's just a time-wasting exercise. Negotiations have stalled at an early stage."

Google DeepMind disputes both the procedural and the behavioral characterization. Al Verney, a Google DeepMind spokesperson, told WIRED: "The first step in the process is to define who the unions want to represent and the parties agreed on next steps to do this. The appropriate representatives attended this initial meeting." The company's on-record position is that the session went as planned and the next move (formalizing who the CWU and Unite would cover) is a matter of negotiation, not breakdown.

The organizing push is not narrowly about pay or research conditions. In May 2026, The Guardian reported that DeepMind staff raised union concerns partly in response to the lab's AI being deployed by the US and Israel in defense contexts, a backdrop that gives the suppression allegations their political weight. The Communications Workers Union and Unite are acting as joint representatives, per labor-industry coverage of the Acas process.

UK recognition law gives the dispute a clear procedural shape. When an employer refuses voluntary recognition, the unions can pursue an Acas-mediated path; if that fails, they can apply to the Central Arbitration Committee for statutory recognition, which can compel bargaining if a ballot shows majority support. Chadfield's "stalled" framing and Verney's "agreed next steps" framing are not just rhetorical; they map onto whether the unions view the current process as a genuine negotiation or a procedural holding pattern.

The next concrete step the parties agreed to is scope: defining which DeepMind employees the CWU and Unite would cover. That definition will determine whether the dispute stays inside Acas or escalates to a Central Arbitration Committee application. Until then, the chat-reconfiguration allegation sits in the public dispute without formal testing, and the procedural argument the unions want to make in writing is whether a company that controls the channels its employees communicate on is bargaining from the same position as the unions.