I spent the first half of my career collecting answers. In venture capital, the person with the most data wins. The best frameworks. The sharpest models. The fastest pattern recognition. At OpenVC, I was surrounded by people who could dissect a business model in under five minutes and tell you exactly why it would or wouldn't work. I admired that speed. I emulated it. I built my entire professional identity around it.

Then I moved to the other side of the table. I started building. And I discovered that everything I thought I knew about asking the right questions was backwards. The questions that made me a great investor were making me a mediocre founder. Not because they were bad questions. Because they were the wrong questions at the wrong time.

The VC Question vs. The Founder Question

In venture capital, the default question is: "What's wrong with this?" You walk into a pitch meeting and your job is to find the risk. The hidden assumption. The market gap the founder hasn't considered. The unit economics that don't hold up at scale. The question is always diagnostic. Always reductive. Always working toward a binary: yes or no, invest or pass.

When I started building Kubrick.social, I brought that same question with me. Every product decision, every strategic pivot, every hiring choice — I asked what could go wrong before I asked what could go right. And for a while, that felt responsible. It felt like the discipline that separated serious operators from naive dreamers.

But here's what I didn't see: when your default mode is threat detection, you never get to the deeper question. The founder question. The one that sounds deceptively simple and takes years to actually answer: "Who is this

really for, and what do they actually need?"

That's not a VC question. VCs ask it superficially — TAM, SAM, SOM, customer persona — but they don't live inside it. Founders do. Or at least, the good ones do.

The Day I Sat in a Clinic in Sao Paulo

The shift happened during a trip to Brazil. I was exploring how healthcare compliance worked across different systems — US regulations versus Brazilian ones — and I spent an afternoon sitting in a small clinic on the outskirts of Sao Paulo. Not as a consultant. Not as an investor. Just watching.

I watched a clinic administrator toggle between three different software systems to process a single patient intake. I watched her print a form, fill it out by hand, then re-enter the same data into a second system because the two platforms didn't talk to each other. I watched the frustration on her face — not the dramatic frustration of someone who's angry, but the quiet resignation of someone who's been doing this workaround for years and has stopped believing it will change.

In that moment, I felt something I had never felt in a single VC pitch meeting: proximity. Not to a market opportunity — to a human being stuck inside a broken system. And the question that formed in my mind wasn't "What's the TAM for healthcare compliance software in Latin America?" It was: "What would it take for this woman to never have to print that form again?"

That question — specific, human, grounded in observation rather than analysis — changed everything. It was the first founder question I ever asked. And it taught me something Stanford's Design Thinking program later gave me the language for: empathy isn't a soft skill. It's a strategic advantage disguised as vulnerability.

Why the Right Question Is Harder Than the Right Answer

Here's the uncomfortable truth about building in healthcare: the right answer is often available. There are studies, regulations, frameworks, and best practices for almost everything. The knowledge exists. What doesn't exist is the right question — the one that connects all that available knowledge to the specific human context where it needs to apply.

I see this constantly in cross-border healthcare technology. A team in San Diego will build an AI compliance tool that works beautifully with US regulatory frameworks. Then they try to deploy it in Brazil and discover that the regulatory logic is fundamentally different — not just in the rules, but in the assumptions underneath the rules. The American system assumes certain data infrastructure. The Brazilian system assumes certain human relationships. No amount of right answers can bridge that gap. Only the right question can: "What does compliance actually mean in this specific context, for this specific person?"

This is where my training at UC San Diego in International Business intersects with my work in AI strategy. International business teaches you that markets aren't monolithic — they're cultural, regulatory, and institutional ecosystems that require deep local understanding. AI strategy teaches you that technology scales. The tension between those two truths is where the real work happens. And navigating that tension requires not better answers, but better questions.

What I Ask Now That I Didn't Ask Before

My VC self used to walk into every situation asking: "What's the return on this? What's the risk profile? Where's the competitive moat?" Those questions aren't wrong. But they're second-order questions. They assume you already understand the problem. And in my experience, most people — most founders, most operators, most strategists — skip the first-order question entirely.

Now I ask different questions. Before I evaluate a market, I ask: "Have I actually sat with the person who lives inside this problem?" Before I design a feature, I ask: "Am I building what they told me they need, or what I observed they actually need?" Before I make a strategic decision, I ask: "Am I optimizing for the outcome I can measure, or the outcome that actually matters?"

These questions don't come from venture capital. They come from building. They come from shipping a product at Kubrick.social and watching how real users interact with it — not in the way your pitch deck predicted, but in the messy, surprising, humbling way that real people actually use technology. They come from sitting in that clinic in Sao Paulo and realizing that the smartest analysis in the world is useless if you're analyzing the wrong thing.

The Question That Guides Everything I Build Now

Every morning, before I open Slack, before I check metrics, before I read a single email, I ask myself one question: "If I could only solve one problem today for one person, who would that person be and what would I solve?"

It sounds impossibly simple. It is impossibly simple. And that's precisely what makes it powerful. Because the question forces specificity. It forces empathy. It forces you to think about one human being instead of a market segment. One workflow instead of a platform strategy. One moment of frustration instead of an industry trend.

The irony is that this approach — starting with one person, one problem, one specific context — is what actually builds scalable businesses. Not the other way around. The companies that tried to boil the ocean from day one are the ones sitting in my old portfolio at OpenVC with impressive pitch decks and declining traction. The companies that started by solving one person's problem with uncomfortable specificity are the ones that grew into something real.

I don't claim to have figured this out completely. I still catch myself defaulting to the VC question — the analytical, risk-first, pattern-matching question — especially when I'm tired or stressed or facing a decision with too many variables. The critic never fully goes away. But I've learned to notice when he shows up. And I've learned that the best thing I can do in that moment is not to silence him, but to redirect him. To take that analytical energy and point it at a different target: not "What's wrong with this idea?" but "What am I not seeing about the person I'm building for?"

That redirect — from evaluating ideas to understanding people — is the single most valuable skill I've developed in my career. More valuable than financial modeling. More valuable than pattern recognition. More valuable than any framework I learned in venture capital or any methodology I studied at Stanford.

Because the right answer will change. Markets shift. Regulations evolve. Technology leaps forward. But the right question — asked with genuine curiosity, grounded in real empathy, and directed at a specific human being — that question will lead you to the next right answer, and the one after that, and the one after that.

Stop chasing the right answer. Start asking the right question. The answer will find you.

Igor Eduardo is a Healthcare Technology & AI Strategy leader based in San Diego, CA. With experience spanning venture capital (OpenVC), SaaS founding (Kubrick.social), and specialized training in Design Thinking (Stanford) and International Business (UC San Diego), he helps organizations navigate the intersection of innovation and execution. Connect on LinkedIn or visit igoreduardo.com.