Compliance as Burden: Applying Clarify, Simplify, Systemise to Regulatory Overwhelm
There is a particular kind of tiredness that has nothing to do with hours worked. I felt it clearly the first time I sat down with a folder of EU AI Act requirements and realised I did not actually know what I was looking at. Not the legal text itself (that part is knowable, if tedious), but the shape of the burden. Was this a one-off project? An ongoing obligation? A trap that would quietly multiply every quarter? I did not know, and not knowing is exhausting in a way that doing the actual work rarely is.
That feeling, I think, is the real subject of this piece. Not the EU AI Act specifically, though I will use it as the case study, but the general pattern underneath almost every regulatory obligation a small operator faces: the burden is rarely the task itself. It is the fog around the task.
The fog is the enemy, not the form
I run Lion Ethos on three moves: Clarify, Simplify, Systemise. It is a small framework, deliberately so, but I have never found a compliance mess it did not apply to cleanly. Let me walk through it with the Norwegian aquaculture example, because it is concrete and current, and because I have already written up the regulatory detail elsewhere so I do not need to repeat it here.
If you run or advise an aquaculture operation in Norway and want the actual "what," the specific documentation obligations, risk categorisation, and reporting duties the EU AI Act creates for AI-adjacent systems in fish farming, I laid that out properly in a companion piece on IPRESTANDA: What the EU AI Act Actually Requires From Norwegian Aquaculture Operators. That piece is the "what." This one is the "how do I stop dreading it."
Clarify: see the actual shape of the problem
Most people skip Clarify and go straight to panic, which looks like frantic simplification of the wrong thing. You cannot simplify what you have not first seen clearly.
Clarifying a compliance burden means asking three blunt questions before touching a single form:
- What, specifically, is being required of me? Not the vibe of the regulation, the actual deliverable.
- Is this a single event or a recurring obligation? Most dread comes from treating a recurring obligation as if it were a one-time fire to put out, which means you never build anything durable and you refight the same battle every reporting cycle.
- Who actually has to do the work, and what does it cost them? This is the question people skip most often, and it is the one that turns compliance from an abstract legal category into a human, physical reality.
On that third point, I want to point at something I explored on TLE Fitness Lab: the physical and cognitive toll that manual reporting work takes on real people in aquaculture operations, the hunched hours at a laptop after a full shift on the water, the eye strain, the low-grade chronic stress of never being quite sure the paperwork is right. That piece is worth reading if you want the embodied version of this argument, because it makes something obvious that gets lost in policy discussions: compliance burden is not just an abstraction, it is paid by a specific person's back, eyes, and nervous system.
Once you have clarified the actual shape (a recurring documentation obligation, carried out by an already tired human, with genuine but bounded technical requirements), the fog starts to lift. You are no longer fighting an amorphous dread. You are looking at a defined, repeatable task with a defined cost.
Simplify: find the smallest version that actually satisfies the requirement
Simplify is where most well meaning people overcorrect. Faced with a clarified but still substantial obligation, the instinct is to build something comprehensive: a full compliance department, an elaborate tracking spreadsheet with forty tabs, a consultant retainer. That is not simplifying, that is just building complexity in a different shape.
Real simplification asks a plain question: what is the minimum viable version of this that genuinely meets the requirement, with nothing extra? For the AI Act documentation case, that might mean identifying the two or three actual risk categories relevant to your specific operation, rather than trying to document against every category in the regulation, and building a single, short template that captures exactly what an auditor or inspector would need to see. Not a comprehensive risk management framework. A clean, minimal, correct answer to the actual question being asked.
I have noticed that people confuse thoroughness with rigour. They are not the same thing. A three line answer that precisely satisfies a requirement is more rigorous than a thirty page document that circles the requirement without quite landing on it. Simplify is the discipline of cutting the second thing down to the first.
Systemise: make sure you never have to solve it from scratch again
This is the step that actually kills the dread, because dread is largely anticipatory. It is the knowledge that this exact confusion is coming back next quarter, and you will have to relearn it, or worse, have to remember who on your team knew how to do it last time before they left.
Systemising means turning the simplified, clarified process into something that runs without you having to think hard about it again: a checklist, a template, a scheduled reminder tied to your actual reporting calendar, a short standard operating procedure that a new team member could follow without needing you to explain it. In an aquaculture context, this might be as simple as a shared document with the minimal risk categorisation template from the Simplify step, a fixed quarterly date, and a named person responsible, reviewed once a year rather than reinvented every time.
The genuinely satisfying part of Systemise is that it converts a recurring source of anxiety into a boring, reliable habit. Boring is the goal. Boring means it is handled.
Compliance as pattern, not exception
I keep returning to this framework because regulatory burden is never really about the specific regulation. The EU AI Act will be superseded by something else eventually, and Norwegian aquaculture operators will face a new acronym with new documentation demands. The pattern, though, stays constant: unclear obligation, tired human, avoidable repetition.
Clarify what is actually being asked. Simplify to the smallest thing that genuinely satisfies it. Systemise so the work becomes routine rather than a recurring crisis. That sequence turns compliance from a source of dread into one more well run part of the business, and honestly, that shift matters more than any single regulation ever will.