Modestas Stragys

I keep seeing the same pattern in Web3. A team launches something, posts about it, opens a discussion, asks for a feedback, and then suddenly everyone has something to say. Some people are supportive. Some are confused. Some want a different feature. Some complain about the tokenomics. Some think the project should more target developers. Some think it should target big institutions. Some think the team should “just focus on community.” Someone always thinks the docs are bad. On the surface, ...

In Web3, founders often become the bottleneck. Not because they are weak. Not because they want control for its own sake. And not because their teams are incapable. They become bottlenecks because the organization around them is built in a way that keeps pulling decisions, clarity, and momentum back to one central point. That point is usually the founder. At first, this does not look like a problem. In early-stage teams, founder-led execution often feels efficient. Things move fast. Communica...

Web3 is full of ideas. It’s a world built on vision, ideology, personalities, and hype. A world of projects. And over time, that becomes a problem. Because it doesn’t move Web3 forward. It doesn’t create real value. And it doesn’t offer any meaningful advantage over traditional businesses. In many cases — it does the opposite. Instead of creating new value, Web3 often ends up copying what already exists in traditional markets. That’s not progress. That’s stagnation...

Over the last 15 years working as an operator, I’ve seen many different kinds of projects. Some succeeded. Some didn’t. Some had great products, others didn’t. Some teams kept moving forward, while others eventually collapsed. For the past six years I’ve been working inside the Web3 ecosystem, and one pattern keeps repeating itself. The reasons for failure are always complex. Markets shift, teams break, funding dries up. But there is one factor that appears far more often than people like to ...