Ten hours back every week: a hands-on AI delegation workshop in Vilnius
Three hours in Vilnius on 25 Nov: build AI assistants and routines on your own computer, with your own data, without depending on one…
They lack a shared language between the people who set the rules, the people who run the business, and the people who build the systems.
I’m a thinking partner for leaders working through decisions that span Legal, Business, and Data-IT at once, helping you see your domain clearly enough to act on it.
Each language is doing its job. The connections between them are where things break, and where the work happens.
| Languages involved: Legal, Business, Data-IT | What you see | What usually sits underneath |
|---|---|---|
| You bought the platform. The results aren’t there. Organizations invest in technology to solve problems that aren’t technology problems. The tool works. The data flows. But nobody agreed on what to measure, who acts on it, or what ‘good’ looks like. | A technology gap is often misdiagnosed where the actual gap is structure or maturity. | |
| Things run fine, until someone leaves or an auditor asks. The process works because the person doing it has done it for ten years. Nothing is written down. When they leave, the knowledge leaves. When compliance asks for evidence, there is none. | This isn’t a documentation project. It’s knowing which controls are real versus which exist only on paper. | |
| Legal says one thing, business does another, IT builds a third. Business teams optimize for speed. IT builds what’s specified. Compliance enforces what’s mandated. Each is doing their job correctly, and the whole system underperforms because nobody connects them. | The fix isn’t better communication. It’s a structure that makes the connections visible. | |
| When things break, they break at the handoff. A compliance issue surfaces. Three things become visible at once: nobody owns the control, the handover between teams has no record, and documentation exists but nobody follows it. | These aren’t three separate problems. They’re one problem showing up in three places. | |
| You pass every audit. You still get surprised. Regulation mandates the parts: a responsible person, control measures, risk measurement, an audit trail. Most organizations implement each requirement separately. Compliant, and still exposed. | Compliance is the floor, not the system. | |
| You have policies. Nobody follows them. Risk policies, handling procedures, security standards, everywhere. Nobody reads them. Not because people are careless, but because the documents don’t connect to how work actually happens. | The gap isn’t missing documentation. It’s documentation that serves the wrong audience. |
| Capture before you conclude. | Most opinions about the business are interpretations of a process nobody captured. Name what’s actually happening before naming what’s wrong. |
| Tool owner, not tool executor. | Knowing the buttons is execution. Knowing why the tool exists is ownership. The work is to move people up that ladder. |
| Compliance is the floor. | Passing audit is necessary. It is not sufficient. The interesting work lives in the structure above the floor. |
| Consistency beats intensity. | A steady process run a hundred times beats a heroic effort that exists only once. |
| Structure before tools. | Tools amplify what already exists. If the structure underneath is unclear, the tool makes the unclarity faster. |
Three hours in Vilnius on 25 Nov: build AI assistants and routines on your own computer, with your own data, without depending on one…
We spend an hour defining “done” with strangers, and eight words on the people we work with daily. An AI agent is the colleague…
Fintech networking on a forest path: I’m speaking at Out of Office – Fintech Edition, a 10,000-step Walk & Talk at Žalieji ežerai on…
If something here resonates, a problem you’ve been circling or a decision you can’t quite name, send a note. A 30-minute conversation is how every relationship starts.