About Me

How I Work

I tend to work best in environments where the path forward is not yet fully defined.

A lot of enterprise projects start with competing priorities, fragmented systems, unclear ownership and teams that are struggling to align around a shared direction. That’s usually where I'm called in. My role is often less about imposing a perfect architecture upfront and more about creating clarity: understanding where the real problems are, identifying what is actually sustainable long-term and helping teams move toward solutions they can realistically support and evolve.

I naturally operate in two connected spaces:

• Business and delivery alignment. I spend a significant amount of time translating between stakeholders, product teams and engineering teams. That often means helping teams work through uncertainty, identifying hidden dependencies, defining priorities and turning high-level business goals into implementation approaches that are both practical and scalable.

• Data and technical architecture. My technical focus centers heavily around data architecture, integrations and platform design. I care a lot about system integrity and long-term maintainability, especially in complex environments where multiple systems, teams and workflows intersect. I’d rather spend additional time designing strong foundations than roll-out short-term solutions that create operational problems later.

Over the years, I’ve found that successful architecture work is rarely just about technology. The technical solution itself matters, but so does how people communicate, make decisions, and operate within the system over time. The best solution on paper is not always the best solution for the organization, the delivery timeline, or the teams responsible for maintaining it long-term. I care a lot about balancing scalability, usability, governance and operational reality rather than optimizing for only one dimension.

I’m generally at my best when I’m helping organizations move from reactive and fragmented toward structured, scalable and resilient.

Outside of Work

When I step away from systems work, I move into more hands-on creative projects. 

I crochet amigurumi (small stuffed toys) for local foster care programs and community charities. It’s a small thing, but there’s something grounding about making something physical that can end up being meaningful to someone else.

I’m also drawn to fantasy and storytelling, and I often get lost in my own worlds. I write fantasy stories for all ages, and over time I’ve realized that designing a strong system uses the same part of my brain as building a fictional universe. Both rely on structure, rules, and imagination working together.

I just like building worlds, whether they run on magic or metadata.