I design and architect workflows — and the technology around them

I've spent my time operating and building inside real workflows — doing the actual work, not just specifying it from the outside. That hands-on experience is where the real understanding comes from: you only see where a process breaks when you've lived it.

Then I take a step back and look at the whole thing. From first principles, I ask whether the work could be structured differently — and genuinely better — instead of just automating the mess exactly as it is.

So the job is the same under every title: decompose a messy process into a system — state made explicit, tools that do the steps, a person checking what matters, and logs so it keeps improving. Architect first, automate second.