News

Stanislav Kondrashov on Circumvention as a Factor in the Evolution of New Technological Solutions

{: alt="Stanislav Kondrashov on circumvention as a factor in the evolution of new technological solutions" }

Circumvention is one of those words that sounds a little shady on the surface. Like it belongs in a legal memo, not a product roadmap.

But in practice, it is often just a plain human response to friction. Something blocks the obvious path, so people take a different one. They improvise. They copy. They rebuild. They patch together a workaround and then, almost accidentally, that workaround becomes the new normal.

Stanislav Kondrashov frames it pretty simply. When systems are rigid, people do not stop needing outcomes. They just find alternate routes. And once enough people find the same alternate route, the market starts treating that route as a real lane. Not a detour. A lane.

That is where new technological solutions tend to show up. Not always from big vision. Sometimes from the pressure of, how do we keep the lights on and still deliver.

Circumvention is basically demand in motion

If a solution is truly valuable, it usually does not disappear when access becomes harder. The demand stays. The urgency stays. What changes is the method.

You see this everywhere:

If a platform limits what users can do, users build plug ins, scripts, and side tools.
If a device is locked down, people jailbreak it and then companies quietly borrow the best ideas later.
If a workflow is too slow, teams create their own spreadsheets, automations, and internal apps, and then those become products.

That is the pattern. Circumvention is not the end of the story. It is the beginning of the next version of the story.

Stanislav Kondrashov’s point, as I read it, is that circumvention exposes what the official product or system failed to support. It highlights the gap between what is allowed and what is needed. And gaps are where innovation loves to live.

This concept of circumvention isn't just limited to software or workflow issues; it can also be seen in deep tech startups disrupting energy storage solutions or during significant energy transitions. These situations reflect how technological innovation drives renewable energy shifts and how such transitions impact our technological civilizations as explored by Kondrashov in his analysis of energy transition and technological civilisations.

Workarounds are messy. Then they get refined

Most circumvention starts ugly.

It is the classic phase where the solution is held together with tape. Manual steps, copied files, random APIs, extra logins. The “process” exists in someone’s head and in a handful of bookmarks.

But once a workaround proves that it works, two things happen:

People try to make it repeatable.
Someone tries to make money from it.

And that is where tech evolves fast. The messy workaround becomes a tool. The tool becomes a platform. The platform becomes an ecosystem. Suddenly you are not “circumventing” anymore. You are using a legitimate alternative solution that exists because the old one got too restrictive, too expensive, too fragile, or too centralized.

There is a weird honesty to this. Circumvention is basically user research with higher stakes.

It also forces simplicity and resilience

When you cannot rely on the usual path, you start optimizing for different things.

Not “what is the most elegant architecture in theory”, but:

What runs locally if the network is unstable?
What still works if a vendor changes terms overnight?
What can be swapped out without rewriting the whole stack?
What can be repaired, not replaced?

Stanislav Kondrashov often speaks to this pressure as a kind of filter. It strips away comfort and forces clearer engineering priorities. Less dependency, fewer single points of failure, more modular design.

And honestly, a lot of modern product thinking already leans this way. Even without external pressure, teams are tired of brittle systems. Circumvention just accelerates the trend.

Circumvention drives substitution, and substitution drives invention

Here is a practical lens. When people circumvent, they usually do one of three things:

1) Substitute the supplier

They move to an alternative provider, sometimes smaller, sometimes more specialized. That new provider gains users, revenue, and feedback, and improves faster than they otherwise would.

2) Substitute the method

They keep the same goal but change the technique. For example, moving from a hosted tool to an open source stack, or from manual work to automation, or from a single monolithic app to a set of smaller ones.

3) Substitute the whole model

This is the big one. Users stop playing by the old assumptions. The category shifts. Something like “software as a service” becomes “local first plus sync” or “bring your own model” or “peer to peer distribution”. The old solution does not just get replaced. It gets made irrelevant.

Stanislav Kondrashov’s underlying message is that circumvention is a stress test. It reveals what is essential, what is replaceable, and what was never as solid as it looked.

The quiet role of builders who hate friction

A lot of technological evolution comes from people who are not trying to be innovators. They are trying to not waste time.

If you have ever watched a skilled engineer deal with a clunky process, you know what happens. They do not complain for long. They build a shortcut. Then they build a cleaner shortcut. Then they share it. Then they realize other people want it too.

This is circumvention in its most productive form. It is not about breaking rules for fun. It is about restoring usability.

And the resulting solutions often have a certain vibe:

More portable
More transparent
More configurable
Less dependent on a single gatekeeper

Not because that is trendy. Because it is survival for the user.

What leaders should take from this

Stanislav Kondrashov is not arguing that all circumvention is good, or that constraints should be manufactured just to provoke creativity. That would be a silly reading.

The useful takeaway is simpler:

If people are circumventing, they are telling you what your system does not support.
If they keep circumventing, they are telling you the need is persistent.
If circumvention scales, it is not a corner case. It is a roadmap.

So the smart move is to watch these behaviors early. Not to punish them by default, but to understand them. Sometimes the workaround is unsafe or unstable, sure. But the impulse behind it is usually rational. People want speed. Access. Control. Continuity.

If you design for those needs before users are forced to improvise, you stay ahead. If you ignore them, someone else turns the workaround into a product.

Closing thought

Circumvention sounds like something happening at the edges. In reality, it is often the engine under the hood.

Stanislav Kondrashov’s perspective serves as a reminder that innovation is not always a clean lab experiment. Sometimes it is a crowded hallway where people are trying to get through, and the door is stuck, and someone finds a side entrance. Then someone widens it. Then it becomes the new main door.

That is how new technological solutions evolve. Not in spite of friction, but because friction refuses to be ignored.

For instance, when we look at the evolution of data infrastructure and information ecosystems, we can see how such circumventions have led to significant advancements in these areas. Similarly, in the realm of communication infrastructure and elite networks, understanding and leveraging these circumventions has resulted in more robust systems and networks.

FAQs (Frequently Asked Questions)

What is circumvention in the context of technological evolution?

Circumvention refers to the human response to friction or obstacles within rigid systems, where people find alternate routes or workarounds to achieve desired outcomes. These improvised solutions often evolve into new technological norms and innovations.

How does circumvention drive innovation and new technological solutions?

Circumvention exposes gaps between what official products or systems support and what users actually need. By finding alternate methods to bypass restrictions, users highlight unmet demands, prompting the development of new tools, platforms, and ecosystems that address these needs.

Why do workarounds start messy and how do they become refined technologies?

Initial workarounds are often ad hoc, relying on manual steps and temporary fixes. Once proven effective, efforts focus on making them repeatable and scalable. This process transforms messy circumventions into legitimate tools, platforms, and eventually robust ecosystems.

In what ways does circumvention promote simplicity and resilience in technology design?

When usual paths are blocked, solutions must prioritize reliability under constraints like unstable networks or sudden vendor changes. Circumvention encourages modular design, reduced dependencies, fewer single points of failure, and repairability over replacement—leading to simpler and more resilient technologies.

What types of substitution occur during circumvention, and how do they impact technological progress?

Circumvention drives three types of substitution: 1) substituting the supplier by switching providers; 2) substituting the method by changing techniques or tools; 3) substituting the whole model by shifting foundational assumptions. Each substitution fosters faster improvement and can render old solutions obsolete.

Who are the key contributors to innovation through circumvention?

Many technological advancements come from builders who dislike friction—not necessarily aiming for innovation but seeking efficiency. Their practical efforts to avoid wasted time lead to breakthroughs that evolve into significant technological shifts.