I turn regulatory and technical complexity into something people can actually use. Most of the real work happens before the screens: the flow decisions, the system architecture, the call on what to build and what to cut. In practice I'm the one connecting what legal, engineering and product each know but haven't put together, and turning it into a decision the team can move on.

Writing to align decisions

I write the document the team argues from, then decides from. On LEAN ID, that was the UX solution design.

How I work with AI

I use AI to work faster, understand complex systems and test ideas. The judgment stays mine.

Understanding the system

I use AI to work through large amounts of internal material: meeting notes, documentation, decision history. On LEAN ID, I traced how features had changed over the years, to understand why the system worked the way it did and which dependencies a fix had to respect. I used the company's approved tool, Microsoft Copilot, so internal material stayed inside company systems. AI finds the pattern; I check it against the source.

Building and proofs of concept

I build working versions to test an idea or fill a gap before it costs engineering time. On ID2GO, there was no budget for apps, so I built the shop's missing features in code with Claude.