Here's the unpopular take that nobody wants to hear right now: restraint, not speed, may be the smarter strategy for tech regulation.
Watch what's happening across the Atlantic. EU lawmakers are demanding action on child protection. Regulators are scrambling to govern data centers. Gatekeepers are being carved out and reclassified. Everyone is moving at velocity, and the underlying assumption is that faster action equals better protection.
But speed in regulatory architecture is rarely a virtue. It's often just motion that creates its own problems.
Let me be clear about what I'm not saying. I'm not arguing for regulatory inaction. The landscape of artificial intelligence, data collection, and algorithmic decision-making genuinely raises novel questions that existing law doesn't cleanly answer. The child safety issues that concern EU policymakers are real. The environmental impact of data centers matters. These aren't phantom problems invented by alarmists.
The question is whether the current instinct to legislate, enforce, and adapt on the fly actually produces better outcomes than a more deliberate approach.
Consider what happens when regulators move at the speed of political panic. You get rules written by people who are learning the technology as they write about it. You get compliance obligations that make sense on their face but create perverse incentives when applied to real-world systems. You get companies spending more resources on regulatory choreography than on actually solving the underlying problems. You get legal uncertainty that chills innovation across the board, not just the bad actors you meant to target.
The EU's gatekeeper regime is instructive here. There's real logic to the idea that platforms with sufficient market power deserve special scrutiny. But the execution has involved drawing lines that were arguably too binary, creating classifications that don't map neatly onto business reality, and generating compliance costs that smaller competitors can't absorb. Was the speed worth it?
The conversation around legal tech at recent industry conferences suggests something worth noting: people in the space are simultaneously excited about innovation and exhausted by regulatory whiplash. That exhaustion is a signal. It suggests we're burning credibility and cooperation by moving faster than our collective ability to think clearly.
Here's what slower, more deliberate regulation might actually accomplish:
It would allow for better evidence gathering. What do we actually know about the harms we're trying to prevent? What do the data tell us about different regulatory approaches? Right now, a lot of tech regulation is written on assumption and intuition.
It would permit genuine stakeholder input rather than the rubber-stamping that happens when legislation moves on a compressed timeline. Companies, civil society groups, and technical experts all have useful things to say. Speed eliminates that conversation.
It would create space for sectoral approaches rather than one-size-fits-all frameworks. Generative AI systems raise different questions than social platforms. Data infrastructure raises different questions than both. But when everything is urgent, you default to broad rules.
It would allow for actual testing and iteration. You could pilot regulatory approaches in limited contexts, observe what works and what doesn't, and adjust before full implementation.
None of this is radical. It's what sensible institutional design looks like.
The counterargument is obvious: harms are happening now. Waiting feels irresponsible. But consider that poorly designed regulations can themselves cause harm. They can entrench existing market power. They can destroy promising technology before it proves itself. They can create compliance burdens that amount to a tax on innovation.
Speed makes regulators feel like they're doing their job. Restraint requires confidence that thoughtfulness produces better outcomes than velocity.
We should try it.