An engineer by training, an architect by instinct, and a builder by trade, I work at the intersection of technology, capital, and institutional design.
I was trained as an electrical engineer at a technical university in Turkey and completed my graduate studies in the United States. That foundation shaped something more than technical competence — it installed a way of seeing. Not problems in isolation, but systems: how components interact, how constraints propagate, how structures that look stable from the outside are quietly failing at the joints.
For most of my career, I worked inside one of those systems. For over twenty years — sixteen of them as the institution’s most senior executive — I led a national technology development foundation positioned at the intersection of public capital, private enterprise, and R&D policy. I designed programs, governed capital deployment, built governance structures, and watched from close range how organizations built explicitly to catalyze innovation can quietly become obstacles to it. Simultaneously, I served on investment committees and boards — at a country’s first fund of funds, at a publicly listed private equity firm, at university research centers — accumulating a parallel education in how capital moves, and why it so often moves in the wrong direction.
I also spent a year leading a network of European innovation agencies, which meant sitting briefly at the center of how multiple national innovation systems understand their own failures. That cross-national vantage point confirmed something I had been slowly learning domestically: the pathologies are remarkably consistent across contexts. The names change. The structures do not.
Before all of this, I began my career in defense, in business development for complex command-and-control systems. I worked on large procurement programs, negotiated with international partners, coordinated engineering teams under contractual pressure. It was a formative encounter with what I would later come to think of as the gap between stated doctrine and operational behavior — the distance between what an organization says it is doing and what it is actually doing.
The White Whale grows out of that accumulated experience. The name comes from a familiar professional sensation: chasing problems that are clearly visible, manifestly important, and persistently unresolved. Not because the people pursuing them were wrong or incompetent, but because the system surrounding them could not process what they were trying to do. I have been on both sides of that experience — the one watching the effort dissipate, and occasionally the one doing the chasing.
This blog revisits those patterns — not as stories, but as structures. The unit of analysis is rarely the individual. It is almost always the system: how decisions form and get constrained, how coordination breaks down in predictable ways, how capital reinforces existing convictions rather than challenging them, how well-designed metrics quietly displace the purposes they were built to serve.
These are not prescriptions. Most of what I have learned resists prescription. They are models — ways of making the system visible, so that the people working inside it can at least know what they are contending with.
If you work at the place where technology, capital, and institutions meet, you will recognize most of what is described here. The specific contexts will differ. The underlying dynamics, almost certainly, will not.