The reason keeps changing but the answer is always no

After a while, you start to notice a pattern. Data centers? Keep them out of Minneapolis. Driverless cars? Put a paid driver in every one. Flock cameras? Take them down. A police drone pilot? Vote it down. Delivery robots at the University? Get City Hall involved. ShotSpotter? Oppose the longer contract.

Council Member Robin Wonsley has a different explanation each time. Sometimes it’s privacy. Sometimes it’s public safety, jobs, the environment, corporate power or the police. But the answer keeps coming back the same: no.

To be fair, she has not gotten her way every time. The delivery robots are still rolling around campus. Minneapolis already had other police drones when she voted against the Skydio pilot. And questioning a piece of technology is not the same as banning it. But we should keep three things straight: what she opposed, what she tried to do about it and what finally happened. Those are separate questions. The outcomes have varied. Her opposition has not.

First the Flock cameras

The latest fight is over Flock Safety’s automated license-plate readers. Wonsley and Council Member Jason Chavez announced a resolution calling on the University of Minnesota and the Hennepin County Sheriff’s Office to end their relationships with Flock and remove the cameras. Wonsley did not leave much room for misunderstanding: It’s time to get Flock out of Minneapolis.

There are real questions about these systems. They record the plates of innocent drivers along with everyone else. Around the country, people have raised concerns about outside agencies searching the data, immigration enforcement and information traveling farther than the public was told. We should take all of that seriously.

But we should also look at what actually happened here. Independent 2025 audits of the University program and the Hennepin County program found both in compliance with Minnesota law. Both programs reported 30-day retention, controlled access and audit trails. Neither audit found a violation. That does not prove the cameras are effective, necessary or worth the money. It does mean nobody has shown that these two local programs were running outside the law.

If the data are kept too long, shorten the retention period. If too many agencies can search them, tighten access. Publish the search logs. Require approval tied to a real case. Punish anyone who misuses the system. Those are the kinds of rules adults write when a useful tool also creates a risk. Taking every camera down should come after we find that the risk cannot be controlled. Wonsley reached that answer before the resolution hearing and before making the public case that the local safeguards had failed.

The easy cases

There’s no need to read between the lines on data centers. In an August bulletin called Stopping Data Centers in Minneapolis, Wonsley said they do not belong anywhere in the city. Not in the wrong neighborhood. Not without tougher rules. Anywhere. That is not a zoning standard. It is a flat no.

City staff have proposed a conditional-use process that would limit data centers to downtown, cap the amount of server space, require estimates of water and electricity use, control noise and protect active ground-floor uses. Maybe those rules should be tougher. Maybe a particular proposal should be rejected. That’s what reviewing an actual project is for. Wonsley skipped that part and convicted the whole category.

Then there are autonomous vehicles, where the proposed solution practically tells us the real purpose. The Workers Drive Minneapolis ordinance would reportedly require every commercial autonomous vehicle to have a paid, licensed person sitting in the driver’s seat with immediate access to the controls. It would also prohibit fully remote commercial operation. In plain English, Minneapolis would allow a driverless car only if it had a driver. That is a taxi having an identity crisis.

Wonsley and her coauthors have been pretty direct about the labor argument. In their September 15 commentary, they focus on protecting rideshare jobs, especially jobs held by immigrants. They cite about 10,000 rideshare drivers in Minnesota, more than 90 percent of them in the Twin Cities. What they do not tell us is how many of those drivers Waymo would replace, or how quickly that might happen. They also acknowledge that the city is still studying what other safety rules autonomous vehicles may need.

Think about that order of events. The city has not finished studying the safety rules, but Wonsley has already picked the answer: make the driverless car employ a driver. That rule is a direct response to possible job losses. It is not a direct answer to the real safety questions. How does the vehicle perform in snow? How does it report crashes? What insurance must it carry? Can it serve riders with disabilities? What happens when the software fails? The city can set standards for every one of those things without requiring the old job to sit inside the new technology forever.

Winter testing is not a silly concern. No company has proved full commercial performance through a Minneapolis winter, and Waymo has had safety failures and recalls. A real winter-testing period could make sense. A permanent driver requirement, with no published way for the company to earn its way out of it, is something else. It protects the job by making sure the technology never gets to do the job.

Losing the vote does not change the position

The delivery robots at the University are a good example of why the final outcome can be misleading. Wonsley started a council inquiry after tying the robots to the rideshare fight, labor exploitation and accidents reported elsewhere. The University said there were no similar campus delivery jobs for the robots to replace and that the program created jobs in loading and maintenance. The city discussed operating rules instead of banning the robots, and the program continued. Wonsley did not succeed in stopping them. That does not mean she supported the deployment or approached it as a neutral fact-finding exercise.

The Skydio drone case is more complicated. Wonsley raised specific concerns about the original proposal, police surveillance, data handling and the vendor’s relationships with ICE and the Israeli military. The revised plan was a 75-day pilot. It called for deleting non-evidentiary footage after seven days and publishing a dashboard of flights. In other words, it was supposed to produce the Minneapolis evidence that critics said was missing. Wonsley voted against it, and the pilot failed.

That doesn’t prove she opposes every police drone in every situation. She acknowledged that MPD already owned drones used to support officers. It proves a narrower point: she opposed the particular technology and deployment in front of her, even after safeguards were added so the city could test it on a limited basis.

ShotSpotter gives her supporters their best argument. Wonsley questioned whether it worked and later opposed the longest contract option. A 2026 city audit backed up part of her criticism. Minneapolis had not gathered enough independent evidence to show the system’s full public-safety value. That is a fair criticism of the city.

But worked is doing a lot of work in that argument. ShotSpotter might not reduce the total number of shootings and still alert police before anybody calls 911. It might help officers find an unreported victim or recover evidence. The honest question is whether those benefits are worth the cost, the false dispatches and the civil-liberties concerns. Minneapolis should have measured all of that years ago. Asking for evidence was reasonable. Measuring the technology only by whether it solves gun violence all by itself was not. Wonsley still opposed it.

When the answer is always no

We don’t have to pretend we can read Wonsley’s mind. We can read her public record. Again and again, the debate is framed as workers against corporations, residents against surveillance, neighborhoods against extraction or communities against police power. Sometimes that way of looking at things uncovers a real abuse. But it can also decide the case before anyone gives performance, safeguards or local facts a fair chance.

A concern is meaningful only if it works like a test. It should tell the rest of us what evidence would matter, what safeguard would be enough or what level of performance would earn approval. If no audit, pilot, retention limit, operating rule or safety result could ever get to yes, then the concern is not really testing the technology. It is helping sell a decision that was already made.

So here is the question Wonsley should answer in every one of these fights: What would change your mind? What specific evidence or protection would make you willing to let the technology operate? She has been very clear about what she fears. She has been far less clear about whether there is any path to yes.

New technology should not get a free pass. Companies can be required to carry insurance, report incidents, respect privacy limits and submit to independent audits. Break the rules and operations can be suspended. Some technologies will fail those tests. Some projects will be a bad fit for Minneapolis. Good regulation says what the harm is, writes a standard to control it and then checks whether the standard works.

The city also has responsibilities when technology threatens jobs. It can enforce wage laws, pay for retraining programs, and help workers get through the change. What it cannot do is preserve every occupation forever by ordering new technology to keep doing things the old way. We did not save elevator-operator jobs by requiring a human attendant in every automatic elevator. We should not save driving jobs by requiring a driver in every driverless car.

Wonsley has offered Minneapolis plenty of reasons to say no to new technology. What she has not offered is the evidence that could ever get her to yes. Until she does, residents are entitled to judge the pattern for what it is. The reason changes. The answer does not.