I like getting close enough to the work to see where it breaks: a missing handoff, unreliable data, or a decision nobody quite owns. Then I help the team make the problem visible and build what comes next.
Move through the questions.
What is someone trying to get done? Where does the work slow down or lose trust? What can we put in front of people now?
Built a shared workflow for documents, pricing, timelines, and accountability in a market that had been coordinating the work through spreadsheets, email, and disconnected data rooms.
Read the case study →An experiment in turning fragmented market documents into decision-ready intelligence without losing the trail back to source.
Simulated and sanitized data · Built to explore the product question
Joined the founder and team for 90 days to make an AI coaching product more useful: clearer product focus, stronger onboarding, and better context for users and managers.
“A rare mix of product judgment, operating clarity, AI fluency, and hands-on execution.”Jonathan Raymond · Founder & CEO
A feature only matters if it changes the work for the better.
Missing data, unclear ownership, and awkward handoffs are product problems.
A prototype gives the team something concrete to question.
Their behavior shows which parts deserve to keep moving.
I write about the parts of product work that rarely stay inside a roadmap: how trust gets earned, why people adopt something, and what AI still leaves to human judgment.
My path has moved through structured finance, institutional markets, data, operations, product leadership, and early-stage building. It looks less linear from the outside than it feels from here.