Working at the interface where things usually fail

Reflexions on Technology, governance, and people – turning ideas into something that actually works

Most ideas don’t fail because they are bad. They fail because no one takes responsibility for the space in between.

In my work, I’ve seen brilliant technical solutions stall, well-funded projects lose momentum, and highly motivated initiatives quietly fade away. Not because of a lack of intelligence, funding, or goodwill — but because the interfaces between disciplines were left unattended; and often a lack of systemic thinking can be noted. That is exactly the space I work in.

Where failure usually happens

Failure rarely occurs at the center of a discipline. Engineers tend to solve engineering problems. Policymakers design frameworks. Communities articulate needs. Businesses focus on efficiency and growth. Things begin to fall apart at the borders and the missing ties between them.

Do you know these issues?

A technology is technically sound but does not fit regulatory realities.
A policy framework is coherent but ignores operational constraints.
A social initiative is well-intended but introduced too late to those affected.
A funded project delivers outputs — but struggles to turn them into outcomes.

These are not individual failures. They are systemic ones.

Why projects fail – what research shows

Across industries, studies by organisations such as the Project Management Institute and McKinsey & Company consistently show that 60-70% of projects fail to fully achieve their intended objectives.

The dominant causes are not technical shortcomings, but
– weak governance and unclear ownership
– misalignment between stakeholders
– poor translation between strategy and implementation
– and unmanaged interfaces between disciplines.

In short: projects rarely fail because ideas are weak — they fail because the space between systems, people and responsibilities is neglected.

Why the interface matters

I am less interested in perfect solutions than in solutions that survive contact with reality and actually prevail. The interface between technology, governance, and people is messy. It requires translation, patience, and the willingness to engage with contradictions. It is also where most real-world progress either happens — or breaks down.

Working at this interface means accepting that clarity does not come first. It emerges through iteration, alignment, and dialogue. It means understanding that innovation is rarely a straight line, and that structure is not the enemy of creativity, but its enabler.

Patterns across very different contexts

At first glance, my current work may appear diverse: infrastructure and noise mitigation systems, European research and innovation projects, local social initiatives, and a series of digital and AI-assisted experiments. For me, they follow the same logic.

Technical systems need to function within regulatory and operational constraints.
EU-funded projects need to move from research logic to deployment reality.
Community initiatives only work if participation is designed, not assumed.
Digital tools create value only when they reduce friction instead of adding complexity.

Across all of these, the core question remains the same: What needs to be aligned so that an idea can actually take root?

“The task is not so much to see what no one has yet seen,
but to think what nobody has yet thought,
about that which everybody sees.”

Arthur Schopenhauer, Philosopher

Working with systems, not against them

I like this quote by Arthur Schopenhauer a lot and often reflect on it. I have learned to respect systems — even when they are slow, complex, or imperfect. One needs to read the connections first before laying hand on them.

Regulation, governance structures, and institutional processes are often perceived as obstacles. In practice, they are the environment in which lasting solutions must survive. Ignoring them does not make them disappear; it merely postpones failure.

My role is often not to invent something entirely new, but to make existing elements work together: technologies, rules, incentives, and human behavior. This requires a pragmatic mindset and a tolerance for ambiguity — but also a strong sense of direction. And it is my greatest pleasure to work on such projects when they can attribute to sustainable impact.

Comment: On using AI as a practical tool

Lately, I experiment extensively with AI — not as a promise, but as an instrument. For me, AI is not about replacing thinking. It is about making action affordable.

It allows rapid prototyping, early testing of ideas, and the creation of low-threshold tools that would otherwise require disproportionate resources. Used well, it shortens feedback loops and helps expose weak assumptions early — before they become expensive.

Used poorly, it adds noise. The difference lies in intention and restraint. However, I honestly believe we need to learn the ropes with these tools fast!

What I am interested in now

Today, my work spans technical innovation, structured project environments, and social spaces. I am particularly interested in contexts where complexity is high, responsibilities are fragmented, and outcomes matter beyond presentations or reports.

I enjoy working where disciplines overlap, where roles are not yet clearly defined, and where progress depends on translation rather than persuasion.

A quiet invitation

I work best with people and organisations who are not looking for the perfect concept, but for the next meaningful step. Those who understand that progress often happens in the margins — at the interfaces — and that making things work in the real world requires both structure and empathy.

That space is rarely glamorous. But it is where things either fail — or finally begin to work.