The future usually looks boring at first

In 1996, when my co-founder and I were starting Virage Logic, we were working on embedded memory solutions for System-on-Chip. If you said that sentence at a dinner party, people changed the subject.

There was no consumer excitement around what we were building. No press coverage. No cultural moment. Just a small team working on a technical problem that most people outside the semiconductor industry couldn't have explained if their lives depended on it.

Six years later, components built by our engineering team in Yerevan were inside the first-generation Apple iPod. By then, everyone understood why that technology mattered. In 1996, almost nobody did.

That gap — between when something becomes important and when the world recognizes it as important — is where I've spent most of my career. And the longer I've been in technology, the more convinced I am that the gap is the point. It's not a bug in how innovation works. It's the feature.

Why the future looks the way it does

The future doesn't usually announce itself. It doesn't arrive with a press release or a cultural consensus or a line of people waiting to get in.

It arrives as a research paper that twelve people read. As a prototype that fails in three different ways before it fails in only one. As a company that spends its first three years explaining to investors why the market they're describing will exist, while the investors nod politely and pass.

I've sat on both sides of that table — as the founder explaining, and as the investor being explained to — and I can tell you that the feeling of early-stage technology is not excitement. It's a specific kind of low-grade discomfort. The technology is real but incomplete. The market is real but not ready. The team believes deeply in something they can't yet fully prove.

That discomfort is actually useful information. It tells you you're early. And being early is the only position from which the real returns are available.

By the time something feels exciting, obvious,s and safe, the most important decisions have already been made. The cap tables are set. The talent is committed. The compounding has started. The people who were in the room when it felt boring are the people who will be in the room when it feels historic.

The signals that matter are quiet

I spent years learning to look for what I call quiet signals — the things that don't generate headlines but that suggest a direction the world is moving, whether or not the world has noticed yet.

A specific type of talent starting to cluster around a problem. A technical constraint that's been limiting an industry for years suddenly loosening. A generation of researchers finishing PhDs in a domain that's about to become commercially relevant. A cost curve crossing a threshold that changes what's economically viable. A regulatory environment shifting in a way that opens a door that was previously closed.

None of these things make the news when they happen. They show up in academic papers and conference proceedings and the conversations that happen at the edges of industry events, not in the keynotes.

The trend arrives later, louder, and more legible — and by then the opportunity has changed shape. What was a wide-open field is now a competitive race. What was a contrarian position is now conventional wisdom. What you could have built for ten million dollars two years ago now costs a hundred million and has three well-funded competitors.

This is not cynicism about markets. It's just how technology development actually works, and it has enormous implications for how you position yourself relative to it.

The discomfort is the signal

When I decided to plant Pinot Noir in Armenia, the reaction from most of the wine world was polite skepticism at best. Pinot Noir is one of the most demanding varieties in existence — notoriously difficult to grow even in the established regions where it's been cultivated for centuries. Armenia was not on anyone's map for serious wine production. The altitude was unusual. The volcanic soil was unusual. The whole premise was unusual.

Jeff Ritchey, our winemaker, has been making wine for over thirty years. When I described what I wanted to do, he was intrigued but cautious. The first years were genuinely difficult. We broke through seventy centimeters of volcanic rock to plant the vines. We learned the land slowly, season by season, making decisions whose consequences we wouldn't understand for years.

Last month, that wine won a gold medal at Concours Mondial de Bruxelles.

I'm not telling that story to brag. I'm telling it because it follows the same arc as every meaningful technology bet I've ever made. Long period of difficult, unglamorous work. External skepticism that is not entirely unreasonable. Gradual accumulation of evidence that the underlying premise was correct. And then a moment of recognition that arrives, to outside observers, as if it came from nowhere.

It never comes from nowhere. It comes from years of work that looked boring.

What this means if you're building something

The most common mistake I see in founders — and I've made this mistake myself — is calibrating too much to external validation. Adjusting the story to match what investors are currently excited about. Pivoting toward what's getting funded rather than what's becoming necessary. Measuring progress by how much attention the company is getting rather than by how much closer it is to solving the actual problem.

Attention is not the same thing as importance. Sometimes they correlate. Often they don't. And in deep technology especially, the period of maximum importance frequently coincides with the period of minimum attention.

The companies I've backed that turned out to matter most were not the ones that had the best pitch decks or the most polished go-to-market narratives. They were the ones where the founders had an almost unreasonable conviction about a specific technical problem, and where that conviction was grounded in something real — domain expertise, proximity to the market, a specific insight about why the timing was right — rather than in optimism alone.

The question worth asking

If you're a founder, an investor, or a leader trying to figure out where to put your energy over the next decade, I'd suggest spending less time on the question "what is exciting right now?" and more time on the question "what is becoming necessary?"

Those aren't the same question, and they don't always lead to the same answers.

What problems are getting worse faster than existing solutions can address them? What technologies are quietly improving in ways that will make things possible in five years that are impossible today? Where is serious talent concentrating, and what does that tell you about where value is going to be created? What does the world structurally need that it doesn't yet have a reliable way to get?

These questions are harder to answer because they require you to hold uncertainty for longer. But they point toward the opportunities where the real work is still available to be done — where you can still be in the room before the room fills up.

The future is already being built somewhere. In a lab, probably. In a small company that's had the same twelve employees for three years and can't yet explain itself in a sentence the average person would understand. In a research paper that has been cited forty-seven times, all by people in the same field.

It looks technical. It looks slow. It looks uncertain. From the outside, honestly, it looks a little boring.

That's how you know it's real.