A Few Things About Me.

Michal often Michael, depending on who is asking.

Sketch of a large machine built from gears, monitors, and cables, with people collaborating around it and a bike, skateboard, and sailboat nearby.

I was born in Poland while it was still a communist country and trained as a network engineer. My career, however, began at the intersection of technology, agencies, and marketing.

That combination shaped the way I still approach technology today. Engineering matters, but so do customers, communication, commercial reality, and the people expected to turn an idea into something useful. Over the years, I have worked across industries, markets, and organizations at very different stages of maturity.

About a decade into my career, I followed the work beyond Poland. That decision took me through Germany and the United States before bringing me to Asia in 2017. Living and working across these regions taught me that technology travels easily; context, culture, and trust do not. Good leadership requires understanding all three.

What I Do.

Today, I serve as a Chief Digital and Information Officer.

My work sits where business strategy, digital products, data, technology, operations, and organizational change meet. It involves setting direction, making difficult priorities visible, building capable teams, and ensuring technology produces meaningful outcomes rather than simply more technology.

My technical background remains an important part of how I lead. I have worked hands-on across cloud platforms, software architecture, data systems, infrastructure, security, observability, and product development. I no longer measure that experience by the number of technologies I can list. What matters is knowing which questions to ask, where the risks are hiding, and when a simple solution is better than an impressive one.

My leadership style is based on trust, clarity, and accountability. Productive teams need room to make decisions, permission to challenge assumptions, and the confidence to discuss mistakes before those mistakes become expensive.

I care deeply about monitoring and metrics-for systems, not people. I value clean engineering, thoughtful testing, and continuous learning. Agile principles have influenced my work since before “agile transformation” became something that required its own steering committee.

The goal is not technology for its own sake. It is an organization that can learn, adapt, and deliver with confidence.

The Ace
Michal's assistant eye