Judgement does not automate.
I started by writing code. Front-end, more than ten years ago, when the job was turning someone else's decision into a screen that worked. It did not take long to realise the screen was the least of it. What mattered was the decision behind it: what the user was asked for, what was hidden from them, what was assumed about them. That is where I stopped being someone who executed decisions and became someone who questioned them.
That is the path that brought me here. From building to designing, from designing to leading product, and from leading product to working in the one place where something real is now at stake: the boundary between what a person decides and what a machine decides.
I have designed and led product in healthcare, in finance and in energy. Sectors where the margin for designing badly is tiny, because an automated recommendation can affect a course of treatment, someone's savings or a city's power supply. That exposure to real consequence is what separates me from the comfortable conversation about AI. I am not interested in whether a model is impressive. I am interested in what happens when it gets it wrong, who answers for it, and whether the system leaves the person better or worse off than before.
My thesis is uncomfortable for much of the industry: most organisations do not have an AI problem, they have a judgement problem. They optimise the model, the prompt, the latency, and defer the hard question of whether that system should be making that decision at all. That question is neither technical nor a matter of compliance. It is a question about what kind of product, and what kind of organisation, you want to be.
To answer it I wrote PRAXIS. A framework for deciding what is delegated to the machine and what stays human, built on a tradition that takes human agency seriously: Arendt, on what happens when we stop thinking because the system thinks for us; Jonas, on a responsibility proportional to our power to act; Murdoch, on attention as a moral act in itself. I do not cite these authors for decoration. I use them because product design has spent decades making ethical decisions without naming them, and AI has made that impossible to keep getting away with.
Today I work at the intersection of three things most people treat separately: product strategy, system behaviour and applied ethics. Not as three services, but as a single discipline. Because a product that decides for you is, whether it means to or not, a product with character. And character is designed.
If you are looking for someone to tell you that AI changes everything and you have to jump on board now, I am not your person. If you are looking for someone to help you decide, with judgement, where the machine adds and where it subtracts, let's talk.
The future of AI is not decided in the models. It is decided in who accepts responsibility for what those models do.
Manu Abuín
How I work
Delegation judgement
Deciding which decisions a system may make and which it may not, and designing that boundary explicitly instead of leaving it to the accidents of implementation.
Product behaviour under AI
Designing how a system acts under ambiguity: its initiative, its limits, the errors it can afford and the ones it cannot.
Ethics as architecture
Turning ethical limits into structural constraints of the product, not a compliance layer added at the end.