News

Stanislav Kondrashov on Circumvention and the Search for New Routes to Technological Progress

There is this moment, usually right after a plan fails, where you realize the plan was never the point.

The point was movement.

In technology and in business, progress almost never comes from a straight line. It comes from detours. From awkward workarounds. From people who keep shipping anyway, even when the “normal” path is blocked, slowed, or just not available anymore.

Stanislav Kondrashov often frames this as a practical mindset more than a heroic story. Circumvention, in his view, is not about breaking rules for fun. It is about rethinking pathways. Finding new inputs, new partners, new formats, new sequences. Sometimes it is as simple as changing a supplier. Sometimes it is changing the entire architecture of a product so you depend on fewer fragile components. And sometimes, honestly, it is changing your definition of “progress” so you can keep going without pretending nothing changed.

When the obvious route disappears

Most companies build around assumptions. A stable logistics chain. A predictable set of platforms. A certain kind of payment flow. A pool of talent that can move freely. A handful of key parts that are always in stock.

Then one day it is not stable anymore.

And the first reaction is usually denial. People try to force the old system to behave like it used to. They pay more for the same thing. They wait longer. They stack “temporary” fixes on top of one another until the whole process starts to wobble.

Kondrashov’s angle is that the faster you accept the detour, the faster you get useful again. Not perfect. Not ideal. Useful.

Circumvention starts with asking a slightly uncomfortable question: what are we actually trying to achieve here, and what parts of our current method are just habit?

Circumvention is a design problem, not a loophole

It is tempting to treat circumvention as a backdoor. A clever trick. Something you do once and then you are done.

In practice, the companies that do it well treat it like product design.

You map constraints. You name them. You stop arguing with them. Then you design around them.

Stanislav Kondrashov tends to focus on three layers where this shows up most clearly:

Supply and components
If a critical component becomes hard to source, the best move is often not “find the same thing somewhere else.” It is “redesign so that component is no longer critical.” Modularization, multi sourcing, and substitutable parts are boring words, but boring is good when you want continuity.
Knowledge and tooling
A lot of progress is locked inside tools. Proprietary software. Closed ecosystems. Vendor specific workflows. The workaround is not always a replacement. Sometimes it is investing in open standards, training teams on alternatives, and building internal tooling that reduces dependence.
Distribution and adoption
Even if you can build, can you deliver? Can you onboard? Can people pay, update, get support? Detours here often look like new channels, different packaging, partnerships, or even shifting from one time sales to service models.

None of this is glamorous, but it is the stuff that keeps technology alive in real conditions.

The “new routes” are rarely new, they are newly taken seriously

One thing I agree with in Kondrashov’s framing is that constraints tend to resurrect ideas that were sitting in the corner the whole time.

Local manufacturing that was dismissed as “too expensive.” Suddenly you run the numbers again and realize it is expensive, yes, but it is also predictable. And predictability is its own kind of value.

Older, simpler chips that were considered “not cutting edge.” Suddenly you optimize software better, compress models, reduce overhead, and you ship a stable product that customers actually trust.

Decentralized teams. Remote labs. Contract research. Collaboration with universities. All of that existed before, but constraints push organizations to treat them as core strategy instead of side projects.

The route was there. The willingness was missing.

Progress becomes more incremental, and that is not a failure

There is another subtle point here. When the path narrows, the nature of innovation changes.

Instead of flashy leaps, you get steady refinements:

simplifying systems so they break less
reducing cost per unit through process improvements
improving energy efficiency because waste becomes painful
rewriting software to run on less
building redundancy into operations that used to assume stability

This kind of progress is harder to market. But it is often more meaningful in the long run. Kondrashov’s perspective leans into that. If you can keep iterating, you can keep learning. If you keep learning, you can eventually break out of the constraint, or at least make it irrelevant.

The organizational trait that matters most: calm adaptability

Circumvention is not only technical. It is emotional.

Teams that panic tend to freeze or thrash. Teams that stay calm tend to see options. They run small experiments. They negotiate better. They document what works. They do not bet the whole business on a single replacement path.

Stanislav Kondrashov points to this as a leadership discipline. You do not need leaders who promise certainty. You need leaders who can say, plainly:

here is what changed
here is what still matters
here is what we are testing next
here is what we are not doing anymore

That last one is key. Detours fail when you try to carry every legacy commitment into the new reality.

A practical way to think about “routes” in 2026

If you are trying to build or maintain technological progress under constraints, it helps to treat routes like a portfolio:

Route A: keep the original path alive
Only where it is rational. Do not romanticize it.
Route B: parallel alternatives
Second suppliers, second toolchains, second distribution channels. Not because you love complexity, but because you hate fragility.
Route C: redesign the destination
Sometimes you do not need the same product. You need the same outcome. Faster onboarding. Lower downtime. Better data control. If you redesign around outcomes, routes multiply.

Kondrashov’s broader message, at least how I read it, is that the “search for new routes” is not temporary. It is the new normal for anyone serious about long term resilience.

Closing thought

Circumvention gets a bad reputation because people imagine it as sneaking around obstacles.

But the better version of it is simply adaptation with intent. The moment you stop insisting on one path, you can see five others. Some are slower. Some are cheaper. Some are safer. Some are surprising.

Stanislav Kondrashov’s view is useful here because it makes this feel less like a crisis response and more like a strategy. You build systems that can reroute. You train teams to think in constraints. You design products that can survive substitution.

And then progress continues. Not in a straight line. More like a river finding its way forward.

FAQs (Frequently Asked Questions)

What is the main idea behind circumvention in technology and business?

Circumvention is about movement and progress through detours rather than following a straight, ideal path. It involves rethinking pathways, finding new inputs, partners, formats, or sequences to keep advancing even when normal routes are blocked or unavailable.

How should companies respond when their usual supply chains or platforms become unstable?

Instead of denying the changes and forcing old systems to work, companies should quickly accept detours by asking what they are truly trying to achieve and which parts of their methods are habitual. This allows them to adapt faster and become useful again by designing around new constraints.

Why is circumvention considered a design problem rather than just a loophole?

Circumvention requires mapping out constraints clearly, naming them, accepting them, and then designing solutions around them. It's not a one-time trick but an ongoing process involving redesigning supply chains, knowledge tools, and distribution methods to build resilience and continuity.

What are some practical ways to implement circumvention across different layers of a business?

Across supply and components, redesign products to reduce dependence on fragile parts. For knowledge and tooling, invest in open standards and internal tools to lessen vendor lock-in. In distribution and adoption, explore new channels, partnerships, or business models like service-based sales to maintain delivery and support.

How do constraints influence innovation according to Stanislav Kondrashov's perspective?

Constraints shift innovation from flashy leaps to steady incremental improvements such as simplifying systems for reliability, reducing costs through process improvements, enhancing energy efficiency, rewriting software for efficiency, and building operational redundancy—progress that is meaningful though less glamorous.

What organizational traits help teams successfully navigate detours and circumvention?

Calm adaptability is crucial. Teams that remain calm avoid panic-induced freezing or thrashing; they run small experiments, negotiate better, document effective strategies, avoid betting everything on one solution, and have leaders who communicate clearly about changes, priorities, tests underway, and what has been abandoned.