I help small and medium businesses adopt AI without breaking the work that already works. Four and a half years building localization platform infrastructure at Workday, now pointed at one problem: mapping where AI genuinely helps a team, where a person must stay in the loop, and where it isn't ready yet.

Engineer of systems. Guardian of teams. From thought to deed. Draws oddities. Seeks change with meaning.

Most AI adoption starts from the tool and asks the team to reshape itself around it. I start from the work. Role by role, workflow by workflow, I map inputs and outputs, decisions, exceptions, authority, autonomy zones and circuit breakers. The result is a readiness architecture the owner can read, price and sign off on, and an adoption path that lights up one interface at a time.

• The work is the fixed point. The technology adapts to the people who do it, not the other way around.
• Bespoke is the future. Off-the-shelf "AI employees" copy your org chart, and the org chart is not a map of how value moves.
• Traditional automation everywhere it fits. AI only where it earns its place.

If you lead a team feeling the pressure to "just adopt AI", let's talk.

Tools I build for my own daily work and release when they hold up.

• Domain-Driven Design and Clean Architecture as the working foundation. Volatility-based decomposition (Löwy) and residuality theory (O'Reilly) as the stress test.
• Agentic systems are a prescription, not a vibe. Every autonomous step needs a named owner, a threshold, and a way to stop.
• Diagram before code. I came to software from mechanical engineering. You design before you cut material.

Recent writing: The chart is not a Map — why an org chart cannot be stressed, and what to draw instead.

"Build boldly. Sketch weirdly. Hike far. Always think before you do." — André Amâncio de Moraes