Why this site exists (and why a broken diagram fixes itself above my name)
The animation on my homepage shows a tangled mess of nodes slowly reorganizing itself into clean, parallel lanes. That’s not decoration. It’s the most honest summary of my job I could come up with.
Every role I’ve had — volunteer president in Córdoba, RPA tinkerer at DXC, implementation associate at Avature, and now business analyst in cloud migrations at MobiLab — followed the same arc: walk into a system, find where it hurts, redesign it, and hand it over so it keeps working without me.
Why write about it
Two selfish reasons, honestly.
First: I was losing what I was learning. In the last eighteen months my role changed three times — PM Coordinator, Migration Coordinator, Business Analyst. Each change came with lessons about migrations, stakeholder communication, and automation that I’d internalize and promptly forget to articulate. Writing forces the articulation. This blog is my learning ledger, published.
Second: visibility compounds, but only if you own it. A LinkedIn post lives 48 hours. A well-written field note lives for years and works while I sleep. I’d rather build equity on my own domain than rent it from an algorithm.
What to expect
One post every two weeks, in one of three lanes:
- Process — how workflows actually break, and how to redesign them so they survive their creator.
- Leadership — what I learned giving teams ownership of themselves, from pandemic-era volunteering to enterprise migrations.
- Innovation — automation as a philosophy: the discipline of asking “why does this step exist?” until the answer is a better system.
No theory dumps. No recycled frameworks. Field notes from real work, with the numbers attached when I can share them — like the 3-to-6-week process we recently cut down to 3 days.
If that sounds useful, the next post is already in the pipeline. And if you’re working on something where a tangled diagram needs to become clean lanes — say hi.