About · where the way of seeing comes from
Not a CV. The origin of a lens — why I read a floor the way the rest of this site does.
I'm Facundo Luluaga, an industrial engineer from the Universidad Nacional de San Juan, Argentina. The last decade I've spent between the plant floor and the systems that run it — manufacturing, logistics, fintech — in Argentina, the Netherlands, Spain, Ireland and the United States. Different roles, different industries, different languages. The same thing underneath: organizations as collections of systems, all of them changing, most of them changing faster than they can see.
The technical challenge was always complicated — difficult, but knowable. Study it, find the cause, apply the fix. The human challenge was always complex — emergent, relational, impossible to deduce your way through. Most projects didn't fail because the technology was wrong. They failed at the interface: people asked to change something they couldn't see.
The fear wasn't irrational. Changing what's invisible is a gamble, and everyone on the floor knew it. The root of that problem isn't a communication failure — it's a methodological one. Deterministic approaches, designed for a world where cause and effect are knowable, don't work in complex environments. They import the right tool into the wrong domain.
The response that actually works in complex environments is adaptive: iterate, deliver value in small increments, let the system respond and correct. The Agile Manifesto wasn't written for factories — but the logic underneath it is the only honest way to operate in complexity: empiricism, tight feedback loops, shared knowledge, trust built through work. The technical methods told me what to build. The adaptive mindset told me how to build it with the people who'd have to live with it.
The lever, every time, was the team. The constraint, every time, was communication.
What I kept doing — in every environment — was the same move: bring the complex situation down to the level where the tools can take over. Make the operation legible. Get agreement on the standard. Then let the method run. That's what every case on this site is about.
Automation is absorbing the complicated. Tasks that once required a trained eye and a stopwatch are being handled by systems. That's not a threat to the work — it's an elevation of the bar. Simple and complicated domains are being handed off to machines; what remains is harder, more consequential, and more human.
What grows in value is the ability to read a complex situation, navigate the human layer, and make it legible enough that the next tool can be deployed without sitting on sand. The engineer who can do that — who can hold the whole operation in view — becomes more necessary, not less.
That's where the Lab comes from. And it's why making things legible keeps mattering more, not less.
This site is where I keep what I see when I look at an operation that way — the tools, the cases, the thinking. Not a portfolio. A working notebook.
If any of it resonates, the door's open.