Building products.
Leading teams.
Making music.
Writing and reflections on product leadership, technology, geography, and life beyond work.
What I do
By day, I'm a Vice President of Software Product Management in enterprise data and analytics. I lead product management for tools that organizations use to understand consumers, markets, and places. This is my executive role, and it's where most of my week goes.
Separate from my day job, I write about AI, product, and geography — it's where I work out my ideas in public about how location, data, and behaviour reveal patterns worth acting on.
Essays & talks
The Cost of Iteration Has Collapsed
What a year of building with AI taught me about product management — and why the biggest change is not faster documentation, but a dramatically lower cost of learning and iteration.
From Dev to VP: The Roundabout Way
A personal reflection on the nonlinear career path from software developer to product executive — and how not getting the job shaped the career I did not know I wanted.
Geospatial Tools for the Visualization and Analysis of Local News Distribution
A research paper exploring how GIS and spatial analysis can be used to visualize and analyze the geographic distribution of local news coverage, revealing concentrations and gaps in reporting.
From developer to product leader.
I've worked across engineering, geography, and product. Engineering taught me how things get built; geography and analytics taught me how to see patterns in how people behave. Here are the decisions that shaped the path.
Hungarian folk music and dance have been part of my life for years. I play violin, teach dance, and help bring people together through camps and community events.
Vice President of Software Product Management
I lead product management for enterprise analytics software: what we build, who it is for, and why it matters. The work pulls together everything before it — engineering, analytics, geography, business strategy, and now AI.
Geography and spatial analysis
I studied geography and spatial analysis because I was curious about something specific: how location, data, and human behaviour combine to reveal patterns that are not obvious at first glance. I still use that lens on every problem.
From writing code to choosing what gets built
At some point I realized my biggest contribution was not the software I wrote. It was deciding which problems were worth solving and helping teams build the right thing. That realization, and a manager who put my name forward, moved me into product.
Software developer
I started as a developer because I liked building systems and solving technical problems. That hands-on background still shapes how I work with engineering teams today.
The kinds of problems I keep coming back to.
The questions I keep coming back to in my writing, about AI, product, and spatial thinking.
When Iteration Gets Cheap
How teams change when a prototype takes minutes instead of weeks.
Thinking Spatially
Why where something happens is often the most overlooked variable in a decision.
Practical Machine Learning
Deciding where a model genuinely changes an outcome, and where it just adds cost and complexity. Usually that is a much smaller list than people expect.
New essays, once a month.
One email a month with new writing and talks on AI, product, and geography. Unsubscribe whenever you like.
Your email stays private.
Get in touch.
A question, an invitation, or an idea you'd like to think through? Send me a note.
Toronto, Canada.
Reach out directly, or use the form. All inquiries are handled personally.
Speaking invitations, questions about something I've written, or just a good idea you want to talk through. I read every message myself.