From making sense to making things.

I tiptoed into use of LLM chatbots out of desperation. I was buried in information with no time to make sense of it all, which is a common PM experience. AI was a tool to help with messy work.

I learned to assemble a clearer reflection of the day’s issues more quickly and more coherently than any daily escalation standup could. I used it to build a knowledge base that could be queried rather than stuffed on a wiki, and more. Most of what I built was scaffolding, things that made the work easier for me and my teammates to understand.

These weren’t assignments. I saw problems worth solving and solved them. Then I pointed the same habit at problems that were mine.

What I’ve made

Line illustration of a requirements page: engagement, customer and problem statement across the top, three groups of stakeholders beneath, and a tabbed panel with User Journey active beside Requirements and Success Metrics, showing a five-lane journey diagram. A phased timeline runs across the foot. Line illustration of a requirements page: engagement, customer and problem statement across the top, three groups of stakeholders beneath, and a tabbed panel with User Journey active beside Requirements and Success Metrics, showing a five-lane journey diagram. A phased timeline runs across the foot.

Living PRD

A requirements document gets read once, if it gets read at all. Instead of a ticket or a wiki page, I built an internally hosted requirements page you could move through. User flows, actors, outstanding questions, and the decisions with the reasoning still attached.

The Trip Wrangler home screen: a London arrivals and activities page with collapsible traveller sections, an Activities tab beside Pay Mandy, and a day-by-day list of outings showing who is in.

Trip Wrangler

I built this for a 10-person family trip to London in August. Arrivals, activities, what everyone needs to know before they go, and the part nobody wants to handle out loud, which is who owes what.

This was my first time with GitHub and a hosting setup. I built it with Claude Code six weeks before the trip, deciding along the way what mattered enough to make the cut. Getting to a workable version took one Saturday. And I loved every minute of it.

It ran the trip. That was the test.

View Trip Wrangler (opens in a new tab)

This portfolio site

The copy is mine, written out loud and cut down. I built it with Claude Code. The design system, the color, the structure, those are calls I made. I’ve kept adjusting it as my thinking has sharpened.

Trip Wrangler was built in a rush of joy. This one started small and moved slowly, because its mission is to reflect an accurate picture of my work and who I am.

The hardest part was noticing when something well-made needed to go anyway.