Two Sides of the Regulatory Coin: UK ‘Agility’ vs EU Process — An Engineer’s Perspective from Both Worlds

Sunday Reflection — 2026-06-18

I’ve had more arguments about documentation in Germany than pints poured warm in Yorkshire. This week’s debate about AI laws dragged me right back: the EU’s all-embracing AI Act on the one hand, and the UK’s patchwork of guidance on the other. To most people, this is politics. For those of us trying to actually build things, it’s yesterday’s culture war dressed up as regulation—only now the stakes are your codebase, not your choice of biscuits.

There’s an old joke between British and German engineers: the UK team turns up, bins the requirements spec, and gets something that just about works running by day’s end. The German team spends day one on the risk matrix and the interface contracts, and day two debating if the checklist covers trolley problems as well as toaster fires. If you learn anything leading teams in both places, it’s that neither extreme is daft, but whichever mindset runs the process, you live with the consequences.

I watched the EU’s AI Act getting through the pipeline from Saxony-Anhalt—whitepaper after whitepaper, a forest of position papers, then the regulation itself: hundreds of pages, cross-referenced footnotes, enough compliance workshops to launch a new industry, which is more or less what’s happened. Process in Germany isn’t a bug. It’s the selling point. Most of the engineers I work with want every edge case specified. Project meetings turn into risk audit rehearsals. Nobody assumes you’ll fix it later. I remember a healthtech project in Jena—two months to get a clinical AI prototype running, eight months documenting the thing. We grumbled, but the day the client’s regulator arrived, we were ready. The UK team who delivered an AI tool faster for a similar NHS roll-out spent six weeks patching up docs and bolting on explanations after the first legal inquiry.

The UK government has stuck to its usual form: sector guidance, no single AI law, let industries figure it out. Sounds liberating, and for a while it is. The speed—real or imagined—can get you ahead of the pack. In the London fintech scene, I once saw a team rewrite half their product in a weekend once the FCA dropped new notes on data transparency. People wear that scramble as a badge of honour—never mind the sleep debt. Agile, they called it. Same word as the manifesto printed out on half the walls I visited in Shoreditch. The danger is it breeds short-term thinking. You put off the hard questions, invent as you go, and hope nobody cares about your grey zones until you’ve shipped version two. That’s fine if you’re building a chatbot for bus times. Lousy if the chatbot tells patients which drugs to take.

German compliance is slow, but it makes people sleep at night. British agility moves fast and breaks things, and then someone in QA is left holding the mess. Most real-world projects end up picking a bit of both, but you only get the luxury of choice if you’ve seen both in action. My favourite paradox is the UK teams who worship speed but end up mired in ISO templates later, and the German teams who want every risk nailed down but quietly bin the paperwork as soon as the auditors have left.

The headlines this week had plenty of hot takes about sovereignty, innovation, whatever word they’re using for ‘not being left behind’. None of that matters at three in the morning when you’re choosing between hitting delivery or failing your first compliance check. My bias? For all I wince at the paperwork, I’d rather have dull meetings now than lawyers picking over half-baked deployments later. The path isn’t fast, but at least you know where it leads.

The lesson that sticks after years stuck between these two systems is simple: sometimes a little clarity, even if it slows you down, is a gift—especially when you operate outside the ‘move fast and pray nobody notices’ bracket. Modern teams will have to find their own way between agility and rigour, but if you build for safety first, your future self—however German or British they feel—will probably thank you.