Author Info

We often talk about learning as something we consume. But learning only becomes meaningful when it changes behaviour.

I rarely use the word "Agile." It carries too much baggage. And yet, not a month goes by without someone asking about an "Agile PMO."

Idea to Value is often mistaken for a delivery model. It is not. It does not prescribe agile, waterfall, or portfolio mechanics. It is a way of seeing.

In every workshop or leadership conversation, someone asks the same question: "What technology would you recommend to solve our problems?" There is always a new option. Always a silver bullet.

I use a lot of paper. Not out of nostalgia. Not out of rebellion against digital tools. I use paper because it changes how I think.

The economic premise beneath the Idea to Value system is simple: financial value appears only when we create something worth paying for — and someone is willing to pay for it. Everything else inside an organisation is cost.

Most organisational problems are not technical. They are interpretive. People misunderstand intent, fill gaps with assumptions, and react to tone as much as content.

After a keynote last week, someone approached me with feedback that was, shall we say, unvarnished. This happens. There is always someone compelled to offer what I now think of as inflicted help.

I had planned to record this reflection in Budapest, in the hum of the conference hall — that strange mixture of anticipation, nerves, and collective attention. Instead, I found myself doing what I often do: waiting for the perfect moment. There rarely is one.