How I work
I’m a maker. I’ve never cared much about titles.
I care about the problem and what it takes to solve it.
I am equally comfortable with senior leadership, with users, in Figma, inside a process or deep in the technology.
I go into the details to understand reality.
I return to the bigger picture to decide what should change.
That is where I work best: between strategy and execution.
I stay with the problem.
There is a product principle I keep coming back to: “Fall in love with the problem, not the solution.”
It resonates with me because requests often arrive as solutions:
Build this.
Introduce this technology.
Add this feature.
I start one step earlier:
What are we actually trying to change?
Sometimes the requested solution is right. Sometimes there is a simpler one. Sometimes the right answer is not to build anything.
I make things real early.
A prototype. A working product. A process. A model.
Something people can actually use and react to.
Building is how I learn.
Speed matters because it gets us to the truth faster.
I build for independence.
I do not want products, teams or organisations to depend on me.
I try to leave behind something others can use, improve, build on or own.
If it only works while I am there, it is not finished.
What shaped me
People I learned from directly
Alain Van Buyten · Olaf Giehl · Reghu Ram
All three through Deutsche Telekom — people whose thinking and way of working influenced mine.
Product
Marty Cagan · Roman Pichler · Jeff Patton
Strategy & decision-making
Richard P. Rumelt · Daniel Kahneman
Leadership & coaching
The Coaching Habit · Michael Bungay Stanier · Corvinus coaching studies
Beyond work
Alan Watts · Jordan Peterson
Their influence has been more personal than professional.
And before all of this: theatre and entrepreneurship.
Both shaped how I think about people, responsibility, feedback and making things real.
Technology
I do not start with technology. But I want to understand it well enough to know what it makes possible.
SharePoint · Microsoft 365 · Power Platform
AWS · Serverless
Figma · Jira · GitHub
Generative AI · local LLMs · Llama / llama.cpp
I am not a specialist engineer in all of them.
My strength is connecting technology to a real business problem and turning it into something that works.
The employment model matters less to me than the work.
I have done this as an employee, as a leader, independently and as an entrepreneur.
The arrangement changes. The work does not:
Understand the problem.
Build what changes it.
Leave behind something that lasts.
Employee, leader, consultant or entrepreneur is secondary.
Is there a meaningful problem here that I can help solve?
