FOR FREE PEOPLE

Read All of Our Coverage Since October 7

FOR FREE PEOPLE

People gather around the Robert E. Lee statue on Monument Avenue in Richmond, Virginia, in June 2020, amid continued protests over the death of George Floyd. (Photo by Ryan M. Kelly/AFP via Getty Images)

I Criticized BLM. Then I Was Fired.

The data about police shootings just didn't add up, but no one at Thomson Reuters wanted to hear it.

If you are a devoted reader of Common Sense, by now you have surely noticed a trend: workplaces—in some cases, storied institutions—that turn hostile to independent thinking seemingly overnight.

That’s what Paul Rossi experienced at Grace Church School. It’s what Jennifer Sey went through at Levi’s. It’s what Antonio García Martínez dealt with at Apple. And Roland Fryer at Harvard. And Gordon Klein at UCLA. And Maud Maron at Legal Aid.

Now comes the story of Zac Kriegman, who, until not so long ago, was a director of data science at Thomson Reuters. Kriegman’s crime? Questioning the Black Lives Matter narrative.

Kriegman is a person who loves numbers and statistics. As you’ll read below, he didn’t just voice an opinion to his colleagues. He made an argument after having done extensive research. He thought logic would win out. He was wrong.

This story is most obviously about the assault on difference. The assault on the notion, previously taken for granted, that you shouldn’t punish employees for having heterodox opinions or for voicing disagreement with the political consensus in an organization. But it is also about the assault on reason itself. — BW


Common Sense is a reader-supported publication. If you appreciate our work, please become a subscriber today.


Until recently, I was a director of data science at Thomson Reuters, one of the biggest news organizations in the world. It was my job, among other things, to sift through reams of numbers and figure out what they meant.

About a year ago, I stumbled on a really big story. It was about black Americans being gunned down across the country and the ways in which we report on that violence. We had been talking nonstop about race and police brutality, and I thought: This is a story that could save lives. This is a story that has to be told.

But when I shared the story with my coworkers, my boss chastised me, telling me expressing this opinion could limit my ability to take on leadership roles within the company. Then I was maligned by my colleagues. And then I was fired.

This is the story Reuters didn’t want to tell. 


I had been at Thomson Reuters for over six years—most recently, leading a team of data scientists applying new machine learning and artificial intelligence algorithms to our legal, tax and news data. We advised any number of divisions inside the company, including Westlaw, an online legal research service used by most every law firm in the country, and the newsroom, which reaches an audience of one billion every day around the globe. I briefed the Chief Technology Officer regularly. My total annual compensation package exceeded $350,000.

In 2020, I started to witness the spread of a new ideology inside the company. On our internal collaboration platform, the Hub, people would post about “the self-indulgent tears of white women” and the danger of “White Privilege glasses.” They’d share articles with titles like “Seeing White,” “Habits of Whiteness” and “How to Be a Better White Person.” There was fervent and vocal support for Black Lives Matter at every level of the company. No one challenged the racial essentialism or the groupthink.

This concerned me. I had been following the academic research on BLM for years (for example, here, here, here and here), and I had come to the conclusion that the claim upon which the whole movement rested—that police more readily shoot black people—was false. 

The data was unequivocal. It showed that, if anything, police were slightly less likely to use lethal force against black suspects than white ones. 

Statistics from the most complete database of police shootings (compiled by The Washington Post) indicate that, over the last five years, police have fatally shot 39 percent more unarmed whites than blacks. Because there are roughly six times as many white Americans as black Americans, that figure should be closer to 600 percent, BLM activists (and their allies in legacy media) insist. The fact that it’s not—that there’s more than a 500-percentage point gap between reality and expectation—is, they say, evidence of the bias of police departments across the United States. 

But it’s more complicated than that. Police are authorized to use lethal force only when they believe a suspect poses a grave danger of harming others. So, when it comes to measuring cops’ racial attitudes, it’s important that we compare apples and apples: Black suspects who pose a grave danger and white suspects who do the same. 

Unfortunately, we don’t have reliable data on the racial makeup of dangerous suspects, but we do have a good proxy: The number of people in each group who murder police officers. 

According to calculations (published by Patrick Frey, Deputy District Attorney for Los Angeles County) based on FBI data, black Americans account for 37 percent of those who murder police officers, and 34 percent of the unarmed suspects killed by police. Meanwhile, whites make up 42.7 percent of cop killers and 42 percent of the unarmed suspects shot by police—meaning whites are killed by police at a 7 percent higher rate than blacks.

If you broaden the analysis to include armed suspects, the gap is even wider, with whites shot at a 70 percent higher rate than blacks. Other experts in the field concur that, in relation to the number of police officers murdered, whites are shot disproportionately.

There has been only one study that has looked at the rate at which police use lethal force in similar circumstances across racial groups. It was conducted by the wunderkind Harvard economist Roland Fryer, who is black, grew up poor, had his fair share of run-ins with the police and, initially, supported BLM. In 2016, Fryer, hoping to prove the BLM narrative, conducted a rigorous study that controlled for the circumstances of shootings—and was shocked to find that, while blacks and Latinos were likelier than whites to experience some level of police force, they were, if anything, slightly less likely to be shot. The study generated enormous controversy. (In 2018, Fryer was suspended from Harvard over dubious allegations of sexual harassment.)

Unfortunately, because the BLM narrative was now conventional wisdom, police departments, under intense scrutiny from left-wing politicians and activists, scaled back patrols in dangerous neighborhoods filled with vulnerable black residents. This led to soaring violence in many communities and thousands of needless deaths—otherwise known as the Ferguson Effect.

For many months I stayed silent. I continued to read Reuters’ reporting on the movement, and started to see how the company’s misguided worldview about policing and racism was distorting the way we were reporting news stories to the public. 

In one story, Reuters reported on police in Kenosha, Wisconsin shooting a black man, Jacob Blake, in the back—but failed to mention that they did so only after he grabbed a knife and looked likely to lunge at them.

In another story, Reuters referred “to a wave of killings of African-Americans by police using unjustified lethal force,” despite a lack of statistical evidence that such a wave of police killings had taken place. (In 2020, 18 unarmed black Americans were killed by police, according to The Washington Post database.)

And in yet another, Reuters referred to the shooting of Michael Brown as one of a number of “egregious examples of lethal police violence,” despite the fact that an investigation conducted by the Justice Department—then run by Barack Obama’s Attorney General Eric Holder—had cleared the police officer in question of all wrongdoing.  

A pattern was starting to emerge: Reporters and editors would omit key details that undermined the BLM narrative. More important than reporting accurately was upholding—nurturing—that storyline. 

At some point, the organization went from ignoring key facts to just reporting lies. When Donald Trump declared, in July 2020, that the police kill more white than black people—this is true—Reuters, in its dispatch, repeated the false claim that blacks “are shot at a disproportionate rate.” In December 2020, Reuters reported that black Americans “are more likely to be killed by police,” citing a 2019 National Academy of Sciences study that, our reporters claimed, found that black men were 2.5 times likelier than white men to be killed by police. In fact, the only rigorous study to examine the likelihood of police use of force—Roland Fryer’s—found that police, as mentioned, were less likely to use lethal force against black Americans.

All this left me deeply unsettled: It was bad for Reuters, which was supposed to be objective and withhold judgment. It was bad for our readers, who were being misinformed. And it was bad for black people in rough neighborhoods, where local officials, prompted to take action by reporting like ours and the public outcry it triggered, were doing things like defunding the police.

Reuters, which is headquartered in London, is hardly the biggest news organization in the United States, but its stories are published in newspapers across the country and read by millions of Americans. It influences our perception of reality. It matters. I didn’t know what to do. I thought I should speak up, but I wanted to preserve my career. My wife, Cynthia, and I started arguing. I’d stay up late into the night compulsively reading the news and studies about policing. I took a two-month leave of absence while I agonized over what to do. 

While I was gone, I started writing a post about the disconnect between what we thought was true and what was actually happening. I wasn’t sure what I planned to do with it. Maybe I would share it. More likely it would just be a kind of therapy, a chance for me to work through some of these issues.

In my post, I examined all the data I had compiled, and I cited the Justice Department’s National Crime Victimization Survey and several academic studies (see, for example, here, here, here and here) to help back up my conclusions—in addition to Fryer’s.

I also pointed out that there had been zero properly designed studies refuting Fryer’s findings. And I noted that a growing number of criminologists—like Paul Cassell, at the University of Utah; Lawrence Rosenthal, at Chapman University; and Richard Rosenfeld, at the University of Missouri-St. Louis—now believed that the false rhetoric around police bias had played a key role in the recent spike in violent crime. This suggested that the BLM lie had led to the murder of thousands of black people.

To drive home my point, I included this striking statistic: On an average year, 18 unarmed black people and 26 unarmed white people are shot by police. By contrast, roughly 10,000 black people are murdered annually by criminals in their own neighborhoods.


When I returned from my leave of absence, I was ready to post my summary to the Hub, where my colleagues regularly posted things about any number of hot-button issues. Cynthia wasn’t sure. She wasn’t just worried about my job, but also about her job, and she was worried that word would get out to the rest of our community. BLM lawn signs lined our street. Our friends sympathized with the cause. We wondered whether we’d be ostracized. We spent many hours over many weeks talking it through. I had come close to posting and then pulled back, and then again, and again. We were talking about it in couples therapy. Finally, I got the okay from Cynthia to publish. She understood that this was about me speaking freely and honestly about something I knew about, cared about and felt I had the responsibility to do something about. I took a deep breath and shared my post on the Hub. It was early May 2021.

Within an hour or two, the moderators had taken down my post.

I messaged my Human Resources contact to inquire why my post had been removed. She told me anyone could flag a post for review, at which point it would be immediately taken down. She didn’t say anything else. I had no idea who had objected or what the grounds for the objection were, or when, if ever, my post would be reinstated. 

Over the next two weeks, I kept checking back with her to see when they would reinstate it. After a good bit of waiting and wondering, she told me that “a team of human resources and communications professionals” was reviewing it. I asked if I’d be allowed to discuss the moderators’ concerns with them. She said no. Finally, she told me my post would not be reinstated because it had been deemed “antagonistic” and “provocative.”

When I asked what, exactly, was antagonistic or provocative, she suggested I speak with the Head of Diversity and Inclusion. So, I scheduled a meeting.

I should mention that, while this was going on with H.R., I met with my manager, who expressed surprise and concern that I had written and then shared my post. It could hurt me at the company, she said. It could put the kibosh on any future promotions.

The next week, I met with the Head of Diversity and Inclusion. I asked what was wrong with my post. She said she couldn’t tell me, because she hadn’t been involved in the decision to remove it. (I was unclear whether she’d actually read it.) 

The next week, there was another meeting—this time with H.R. and Diversity and Inclusion. I wanted to know what I had to change in my post to make it acceptable. They suggested scrubbing all instances of the term “systemic racism,” to start. 

So I did that, and the piece was reinstated. I was relieved. Such discussion about facts and statistics had to be permitted. It was impossible to report the news accurately if employees were not allowed to have internal, sometimes heated discussions about pretty much anything.

Then the comments started rolling in. A handful of BLM supporters, all of them white, said that, as a white person, I had no place criticizing BLM. They called my review of the academic literature “whitesplaining” (failing to note that many of the academics I cited were black). I was publicly derided as a “troll,” “confused,” “laughable,” and “not worth engaging with or even attempting to have an intelligent conversation” with. One colleague said: “I do not believe that there is any point in trying to engage in a blow-by-blow refutation of your argument, and I will not do so. My unwillingness to do so doesn't signal the strength of your argument. If someone says, ‘The KKK did lots of good things for the community—prove me wrong,’ I'm not obligated to do so.”

Notably absent from the attacks directed at me was even a single substantive challenge to the facts I was citing.

It was insulting and painful. Not a single executive, no one in H.R., no one in Diversity and Inclusion, condemned any of the public attacks on me. They were silent. I’m not surprised no one came to my defense. Who would take that kind of a risk? It became very clear very fast that my public takedown was intended to ensure that there would be no discussion around BLM or the question of police brutality and race.

After enduring waves of abuse, I emailed H.R. to express my concern about these attacks on me and their chilling effect. They responded by removing my post—and shutting down the conversation. I was told that, if I discussed my experience on any internal company communications channel, I would be fired.

I was distraught.  Here I was trying to bring the company's attention to how we were spreading lies that were contributing to the murders of thousands of black people, and I was compared to a Klansman sympathizer, and forbidden by the company to discuss any of it.

I had little doubt about the sincerity of H.R.’s threat to fire me.  But I still had a faint hope that the company’s senior leadership would right the ship if I could only make them aware of the matter.  Regardless, given the way the internal conversation had ended, I didn’t see a tenable way to continue working at the company without some sort of resolution. 

So, I sent an email to colleagues and company leadership, again expressing concern about how the attacks against me had successfully shut down any productive conversation and left my reputation in tatters. The next day, H.R. called me to say that my access to all company computer and communications systems had been revoked.

Three days later, on June 8, 2021, I was fired.

“As we discussed on Friday,” H.R. said in their parting email, “you’ve violated our expressed direction and have repeatedly refused to follow the counsel offered.” The email went on:“The manner in which you’ve conducted yourself in recent weeks does not align with our expectations for you as a leader within Thomson Reuters.”


A decade ago, my experience at Thomson Reuters would have been unthinkable. Most Americans probably think it’s still unthinkable. That’s what makes it so dangerous. Most of us don’t understand how deeply compromised our news sources have become. Most of us have no idea that we are suffused with fictions and half-truths that sound sort of believable and are shielded from scrutiny by people whose job is to challenge them. This is true, above all, of my fellow liberals, who assume that only Republicans complain about the mainstream media. But this is not a partisan issue. This is a We The People issue.

In January, I filed a complaint with the Massachusetts Commission Against Discrimination stating that I was fired in retaliation for complaining about a racially hostile work environment. (The MCAD works in conjunction with the U.S. Equal Employment Opportunity Commission.) We’ll see whether the state finds that there are grounds for a lawsuit.

However that shakes out will not change the fact that thousands of black Americans are dead, in part because too many people are still unaware of basic facts about policing since their trusted news sources meticulously obscure the truth. The job of journalists is to report the stories that don’t comport with the prevailing or popular narrative. We desperately need them to do that again.

Subscribe now

our Comments

Use common sense here: disagree, debate, but don't be a .

the fp logo
comment bg

Welcome to The FP Community!

Our comments are an editorial product for our readers to have smart, thoughtful conversations and debates — the sort we need more of in America today. The sort of debate we love.   

We have standards in our comments section just as we do in our journalism. If you’re being a jerk, we might delete that one. And if you’re being a jerk for a long time, we might remove you from the comments section. 

Common Sense was our original name, so please use some when posting. Here are some guidelines:

  • We have a simple rule for all Free Press staff: act online the way you act in real life. We think that’s a good rule for everyone.
  • We drop an occasional F-bomb ourselves, but try to keep your profanities in check. We’re proud to have Free Press readers of every age, and we want to model good behavior for them. (Hello to Intern Julia!)
  • Speaking of obscenities, don’t hurl them at each other. Harassment, threats, and derogatory comments that derail productive conversation are a hard no.
  • Criticizing and wrestling with what you read here is great. Our rule of thumb is that smart people debate ideas, dumb people debate identity. So keep it classy. 
  • Don’t spam, solicit, or advertise here. Submit your recommendations to tips@thefp.com if you really think our audience needs to hear about it.
Close Guidelines

Latest