Agile Leadership Team Collaboration

What Stays When Everything Changes? Integrity

Svetozar Eliseev

17 Mar 2025 — 1 min read

In this personal and reflective episode of The Delia Network Podcast, Gehtsoft CEO Ivan Gekht shares a rarely heard side of his story—how growing up in a family business shaped his views on leadership, responsibility, and what it truly means to build something that lasts.

This isn’t a story about startups or scale. It’s about values. And what holds when pressure rises.

Topics Ivan touches on:

How Soviet-era resilience taught him that trust must be earned, not expected
Why his definition of “team” is rooted in accountability over hierarchy
How growing up surrounded by business problems created a deep respect for long-term thinking
The role of moral clarity when building high-stakes systems—especially when no one is watching
Why “integrity” is more than a trait—it’s a design principle

“Integrity isn’t just a leadership quality. It’s how systems should behave too—predictable, auditable, and reliable under pressure.”

For those leading teams, managing legacy systems, or facing ethical crossroads in tech, this episode is a grounding reminder: what you build is only as strong as what you believe.

Listen now: The Importance of Integrity — Ivan Gekht on The Delia Network

The Real Management Failure Is Not Lack of Frameworks. It Is Ideology Replacing Operational Judgment.

Over the last two decades, I have worked with organizations across very different environments: regulated finance, SaaS platforms, operationally constrained delivery, large engineering organizations, transformation programs, and Agile implementations at multiple scales. And one pattern appears repeatedly. Organizations stop managing operational reality and start managing management ideology. Sometimes the ideology

Risk Management under Real Velocity: Push Detection Downstream, Limit Blast Radius

I was recently quoted in a TechBullion article on balancing speed and security in business risk management. The core idea was simple: increasing business velocity does not remove the need for risk management. It changes its economics. This is not a technical nuance. It is a decision problem. At higher

AI and the missing first step in learning

What could be the long-term impact of AI on career progression in knowledge work? I saw a post recently asking whether AI will replace junior Scrum Masters. That question itself is not new. But it triggered a realization I had not connected this way before. And it is not very

Code Is No Longer the Bottleneck. Now What?

An advantage that everyone has is not an advantage. Agentic tools handle boilerplate, tests, and even non-trivial features. If your bottleneck was implementation speed, it's gone. Yet Amdahl's Law still applies: the speedup you get from accelerating one part is limited by the parts that don&

Read more

The Real Management Failure Is Not Lack of Frameworks. It Is Ideology Replacing Operational Judgment.

Risk Management under Real Velocity: Push Detection Downstream, Limit Blast Radius

AI and the missing first step in learning

Code Is No Longer the Bottleneck. Now What?

Cookie Settings