About
I came to product management through the systems, not the slides.
I started out keeping infrastructure alive for an organisation that could not afford downtime, and moved into product because the interesting problems were never the servers — they were the processes wrapped around them.
Since then I have spent my time in operations-heavy businesses: places where revenue depends on physical assets, shift work, and a hundred small decisions made without data. These environments rarely need more software. They need the right three things digitised, instrumented properly, and adopted by people who are sceptical for good reason.
That is the work I like — sitting between the operations team, the commercial team and the engineers, and turning a vague frustration into a scoped release that changes a number. I write about it here, mostly to think more clearly, and partly because the useful lessons rarely make it into conference talks.
I am based in Athens, Greece, working across international operations, and I take on a small number of consulting engagements alongside my product work.
How I work
The first release has to earn something
Not attention — money, hours, or risk removed. A first release that produces a number gets a second budget. A first release that produces a demo gets a review meeting.
Go to the floor before the whiteboard
The people doing the work already know where it breaks. My job is to translate that into something buildable without flattening the nuance they gave me.
Retrofit beats rip-and-replace
Most operations already have capable equipment and terrible visibility. Instrumenting what exists is faster, cheaper and far more likely to survive contact with a real budget.
Adoption is a design problem, not a training problem
If a tool needs a training programme to survive, it was designed for the person buying it rather than the person using it at 6am.
The path here
Now
Digital product leadership in marina and port operations
Owning digital products end to end — self-service booking, connected utility hardware, operations tooling and occupancy intelligence — across a multi-country network.
Before
Product and delivery for connected hardware
Specifying, sourcing and deploying IoT devices at scale, and building the software layer that turned their data into billing, safety and capacity decisions.
Earlier
IT infrastructure and systems in the non-profit sector
Running the systems that kept a distributed humanitarian organisation working. Where I learned that reliability is a product feature and constraints are the norm.
If any of this sounds like your situation