> Hello World // March 1, 2025

Hey, I'm Nizar—sharing my thoughts here. I'm a programmer who's always wanted to create a very simple red-and-black website, and this blog is my excuse to create it. You can drop me a line at nizar@deriva.ai.

> Not a Manual, Just My Journey: Notes on Customer Conversations // March 11, 2025

I believe that customer validation is a skill. There are two stages of validation: problem validation—determining whether the assumed problem truly exists—and problem-solution fit validation—confirming that the solution you propose is the optimal one.Product-wise, the most important hypothesis you’ll ever make during your startup journey is the problem hypothesis. If it’s wrong, it will be very hard to change later on, and the signals become more vague as you start to focus on other aspects of the product.I also believe that we learn different skills throughout life, and the best way to master them is through practice. Theory is great, but nothing can replace practice. I am a musician, and I’ve learned the hard way that knowing all the theory is useless if you don’t pick up your bass and practice; you’ll never truly play well. The same applies to programming. No matter how many design patterns you know, if you never encounter them in real-life programming, you will never internalize them. Now, I’m trying to apply the same methods I use in music and programming to my entrepreneurial journey.

Learning to Listen by Practicing
One of the main skills you need as an entrepreneur is the ability to conduct customer discovery calls. As simple as it might seem, these calls are very challenging, and it takes tens of calls to grasp how to do it effectively. The goal of these calls is to observe and listen carefully. This is especially challenging for a hyperactive person like myself because when a hypothesis turns out to be true, I get so excited that I want to share that excitement with the customer—to tell them, “This is what we found!” However, talking at this stage can cut short the customer’s chain of thought, and you risk losing the real data that comes when the customer validates your problem hypothesis and starts to elaborate. Learning to listen is a skill that must be developed; I don’t think people are born with it. I’ve worked with many talented product managers and it’s clear that the more interviews they conduct, the better they become at listening.

Focus, Focus and Focus!
Another challenge is maintaining focus. When you think about what you’re going to say next, you risk losing focus and missing important points said between the lines. Don’t misunderstand me—you will always lose focus to some degree. I believe that good entrepreneurs often have a “monkey mind,” able to juggle multiple thoughts simultaneously. Still, you need to concentrate on the data being shared in the moment. Focusing on the next question always detracts from what is most important right now. One piece of advice I received was to write down the question I want to ask on paper and then forget about it. Later, when you have time, you’ll revisit the paper and often find that many of those questions are irrelevant as the customer’s story unfolds.

The Most Important Question
Our mission as entrepreneurs is to create something people want. As simple as it might seem, this is a challenging idea.
First, we have many biases—we naturally tend to favor what we want rather than what customers truly desire. Moreover, what people want is often not clearly articulated; sometimes, even they aren’t sure what they want. I believe that guiding a customer to understand what they truly desire—and then having them reveal that information—is a skill that takes a lot of practice.
I’ve discovered that there are several questions which, when asked in the correct order, can lead customers to reveal valuable insights. The main problems we aim to solve—and the reasons users end up loving our products—are typically gaps in existing offerings. These gaps make customers struggle with what’s available and yearn for a solution that fills that void. Therefore, I’ve found that asking a simple question about an existing product—“What doesn’t work in _____?” (where _____ is the product or service you’re trying to improve)—is a golden question. If you listen carefully, you’ll be amazed to hear not only your hypothesis discussed but also the customer’s perspective, complete with practical examples. When the customer starts to elaborate and finishes their thought, one piece of advice I was given is to count to 10 in your mind before asking the next question. Often, the most interesting information emerges after that pause, when their brain takes a moment to process and analyze.

Document the Interviews and Read Them Again
I always document the interviews I conduct. Sometimes I use modern note-taking apps, and sometimes I write them down manually—I still haven’t decided which is better. While note-taking apps record the entire conversation with no information loss, I’ve noticed that some customers feel it’s rude to be recorded, and others don’t share all the details because they find it hard to reveal their true feelings, struggles with current products, or internal information when they’re being recorded. However, it’s always good advice to document the interview, review it, and compare it to others. You’ll invariably discover information you missed or didn’t have time to process during the conversation—information that is pure gold.

> The Focus Factor: Zeroing In on What Matters // March 1, 2025

If you can’t sum up your startup in one sentence, you might be spreading yourself too thin. It sounds simple from the outside, but as founders, we know it’s a herculean task. We’re so intimately familiar with every nuance of our business—the big problems, the little details, the endless ideas—that distilling everything into a single, punchy sentence becomes nearly impossible. Yet, that one sentence isn’t just about describing what you do; it’s a statement of your priorities and, most importantly, your focus.

One Sentence, Total Clarity
Think about the way stock prices encapsulate every aspect of a company’s performance—product quality, go-to-market execution, customer churn, and more. Your one-sentence pitch should work the same way. It doesn’t just explain your product and vision; it defines where you’re putting your energy and resources. It’s a clear, data-driven signal to the market and your team about what truly matters.

Feeling Lost in a Sea of Possibilities
There was a time not long ago when I felt lost—even when everything looked great. Our product, designed to automate research in the life sciences, could extract, analyze, and visualize data from multiple sources, cutting research time from months to minutes. Design partners loved it. Yet, I couldn’t shake the feeling that we were overextending ourselves. Our product was growing in every direction, and with a small team, every new feature was a potential distraction.
While I was in San Francisco, chatting with fellow entrepreneurs and even my former boss—a serial entrepreneur now leading a successful startup—it became clear: it’s crucial to challenge whether you’re really focused, even if you think you are.

Strategic Steps to Sharpen Your Focus

1. Narrow Your Use Cases
Our product’s horizontal appeal was a double-edged sword. It worked across drug discovery, genetics, business development—you name it. But every new use case brought new requirements, diluting our focus. Look at companies like Monday: they started with one clear use case before branching out. We learned that excelling in one area is more valuable than being average in many.

2. Zero in on Your Ideal Customer Profile (ICP)
In our early days, we talked to a wide array of biotech professionals. Every conversation revealed unique needs and perspectives. One business development lead even pushed us to add a specialized module. While that module worked wonders for him, catering to every persona meant endless tweaks and distractions. By narrowing our ICP, we’re dedicating our limited time to truly understanding and serving one customer group exceptionally well.

3. Sequential Over Parallel Execution
Imagine you have 10 video processing tasks. You could use one powerful server to handle them sequentially, or 10 smaller servers to run them in parallel—costing the same but with very different learning curves. Trying to perfect 10 use cases simultaneously means you’ll only understand what works—or doesn’t—in a year. Instead, focusing on one use case at a time lets you iterate quickly, learn faster, and pivot when necessary.

4. Start from the End

It’s tempting to perfect every detail from the start of your process. But every customer has a specific job to be done. Focus on delivering that end result first. By programming backwards—solving the customer’s ultimate need before refining the middle or the beginning—you can validate your approach rapidly and adjust course before overinvesting in non-essential features.