What Are You Building?

I remember my first idea like it was yesterday. I was just so excited , I wrote down the plan, and all I saw was a thousand ways my idea would revolutionize the world. I just could not see it fail, It was that good until I started building with grit and focus. I just knew when I shipped the whole world would bow. I finished the MVP and then the cracks started showing, who I thought the idea was for was not actually the target market and as I tried to twerk the idea to fit whatever I feel was the right market the motivation started going down until I started avoiding the idea and so it got covered by newer idea and newer hope. However, after so many trials and errors, I concluded that the right questions with deep, truthful answers are the first step towards building any solutions that would last. And these questions are very much valid today. So many people have rushed into tech with fancy ideas and solutions, putting so much, only to ship and realize nobody needs the solution. What are you building? I have always asked myself this question whenever I get overly excited during my quiet time in the loo. Mark Zuckerberg was crazy about Facebook, likewise Steve Jobs, and a host of other amazing inventors, but the times have changed; Today, we have faster technology, shorter attention spans, and a rapidly evolving market that doesn’t wait for second chances. That is why, before you write a single line of code or launch a product, you must pause and ask yourself: Do people need this, and is the time right for such a solution? What are you building? Who needs this? Why now? These are not questions for investors or pitch decks. They are the core of product-market fit, and they should echo in your mind every time you write a line of code, design a wireframe, or register a domain name. The Rise and Fall of Google Glass Let’s talk about Google Glass, a prime example of brilliant technology with a poorly timed entrance. It had everything: augmented reality, voice commands, head-up display. But it lacked two major things: need and social readiness. People weren’t ready to walk around with mini-computers on their faces in 2013. There were privacy concerns, style issues, and most importantly, no urgent use case for the average consumer. Google Glass flopped in the consumer market, even though it was backed by one of the biggest tech companies on the planet. So, was it a bad idea? Not entirely. Google Glass found new life in enterprise settings—warehouses, surgeries, manufacturing lines—where hands-free computing solved real problems. Lesson: Sometimes your idea is good, but the market or timing is wrong. Ask: "Who exactly needs this right now?" From Flop to Fame: The Story of Airbnb On the other side of the spectrum, take Airbnb. Imagine telling investors in 2008, during a recession, that your big idea is to let strangers sleep in each other’s homes. Sounds crazy, right? But the timing was perfect. Hotels were expensive, and people needed extra income. The idea wasn't just clever—it solved a very real problem. Airbnb grew from renting air mattresses in a living room to a billion-dollar hospitality disruptor. They started with a problem they personally faced—finding affordable accommodation during a conference—and scaled it up. That’s key: they weren’t building for everyone; they were solving a real, relatable problem. Lesson: If your solution doesn’t solve a real pain point, it’s just a feature looking for a problem. Innovation Is Not Just Building Cool Stuff Too many founders fall into the trap of building for themselves or building what they think the market wants. Innovation isn’t just building cool stuff—it’s building useful, timely, and accessible solutions. Take Clubhouse, for instance. During the COVID-19 pandemic, everyone was stuck at home, craving interaction. Clubhouse capitalized on that need and blew up overnight. But as restrictions eased, user engagement dropped. Why? Because the product was built for a specific moment in time. Lesson: Temporary hype does not equal longevity. Always ask, “What will make people stick when the noise fades?” Asking the Right Questions Before You Build To avoid building solutions for nobody, adopt a product validation mindset from day one. Here are key questions to drive real innovation: What problem am I solving? Is this a problem others face, or just something I think is interesting? Who is this for? Can I describe the exact person who needs this? Be specific—age, job, habits, pain points. Why now? Is the market ready? Is there urgency or a shifting trend making this idea viable? How are people solving this today? If the answer is “they’re not,” maybe the problem isn’t real. If they’re using spreadsheets or WhatsApp groups, you might be onto something. Would I use this product if someone else built it? Be brutally honest. Excitement fades. Practicality stays. ## The Power of Community-Driven Valid

May 12, 2025 - 18:10

I remember my first idea like it was yesterday. I was just so excited , I wrote down the plan, and all I saw was a thousand ways my idea would revolutionize the world.

I just could not see it fail, It was that good until I started building with grit and focus. I just knew when I shipped the whole world would bow.

I finished the MVP and then the cracks started showing, who I thought the idea was for was not actually the target market and as I tried to twerk the idea to fit whatever I feel was the right market the motivation started going down until I started avoiding the idea and so it got covered by newer idea and newer hope.

However, after so many trials and errors, I concluded that the right questions with deep, truthful answers are the first step towards building any solutions that would last.

And these questions are very much valid today.

So many people have rushed into tech with fancy ideas and solutions, putting so much, only to ship and realize nobody needs the solution.

What are you building? I have always asked myself this question whenever I get overly excited during my quiet time in the loo.

Mark Zuckerberg was crazy about Facebook, likewise Steve Jobs, and a host of other amazing inventors, but the times have changed;

Today, we have faster technology, shorter attention spans, and a rapidly evolving market that doesn’t wait for second chances. That is why, before you write a single line of code or launch a product, you must pause and ask yourself:

Do people need this, and is the time right for such a solution?
What are you building?
Who needs this?
Why now?

These are not questions for investors or pitch decks. They are the core of product-market fit, and they should echo in your mind every time you write a line of code, design a wireframe, or register a domain name.

The Rise and Fall of Google Glass

Let’s talk about Google Glass, a prime example of brilliant technology with a poorly timed entrance. It had everything: augmented reality, voice commands, head-up display. But it lacked two major things: need and social readiness.

People weren’t ready to walk around with mini-computers on their faces in 2013. There were privacy concerns, style issues, and most importantly, no urgent use case for the average consumer. Google Glass flopped in the consumer market, even though it was backed by one of the biggest tech companies on the planet.

So, was it a bad idea? Not entirely. Google Glass found new life in enterprise settings—warehouses, surgeries, manufacturing lines—where hands-free computing solved real problems.

Lesson: Sometimes your idea is good, but the market or timing is wrong. Ask: "Who exactly needs this right now?"

From Flop to Fame: The Story of Airbnb

On the other side of the spectrum, take Airbnb. Imagine telling investors in 2008, during a recession, that your big idea is to let strangers sleep in each other’s homes. Sounds crazy, right?

But the timing was perfect. Hotels were expensive, and people needed extra income. The idea wasn't just clever—it solved a very real problem. Airbnb grew from renting air mattresses in a living room to a billion-dollar hospitality disruptor.

They started with a problem they personally faced—finding affordable accommodation during a conference—and scaled it up. That’s key: they weren’t building for everyone; they were solving a real, relatable problem.

Lesson: If your solution doesn’t solve a real pain point, it’s just a feature looking for a problem.

Innovation Is Not Just Building Cool Stuff

Too many founders fall into the trap of building for themselves or building what they think the market wants. Innovation isn’t just building cool stuff—it’s building useful, timely, and accessible solutions.

Take Clubhouse, for instance. During the COVID-19 pandemic, everyone was stuck at home, craving interaction. Clubhouse capitalized on that need and blew up overnight. But as restrictions eased, user engagement dropped. Why? Because the product was built for a specific moment in time.

Lesson: Temporary hype does not equal longevity. Always ask, “What will make people stick when the noise fades?”
Asking the Right Questions Before You Build

To avoid building solutions for nobody, adopt a product validation mindset from day one. Here are key questions to drive real innovation:

What problem am I solving?
Is this a problem others face, or just something I think is interesting?
Who is this for?
Can I describe the exact person who needs this? Be specific—age, job, habits, pain points.
Why now?
Is the market ready? Is there urgency or a shifting trend making this idea viable?
How are people solving this today?
If the answer is “they’re not,” maybe the problem isn’t real. If they’re using spreadsheets or WhatsApp groups, you might be onto something.
Would I use this product if someone else built it?
Be brutally honest. Excitement fades. Practicality stays. ## The Power of Community-Driven Validation

Let’s look at Notion, the all-in-one productivity tool. It didn’t go viral on day one. It was quietly built, tested, refined, and talked about in niche communities. Reddit threads, YouTube reviews, and product managers spread the word. Notion listened and iterated fast. That’s another secret—don’t just build, build with your users.

SEO tip: Engage in “community-driven product development,” “feedback loops,” and “user testing before launch” as part of your growth strategy.

Avoid the Build-First Trap

Here's a simple truth: Shipping fast doesn’t matter if you’re shipping the wrong thing.
Think of Quibi, a $1.7 billion mobile video startup that launched in 2020 with short-form content designed for on-the-go viewing. It failed within six months. Why?

They ignored the growing influence of user-generated content on platforms like TikTok and YouTube. Also, people were not on the go in 2020. They were locked in their homes. The timing and user behavior were completely mismatched.

Lesson: Don’t let a big budget fool you into thinking you don’t need validation. You do.

Build With Purpose, Not Just Passion

Yes, you should be passionate about what you’re building. But don’t let passion blind you. Build with purpose. Validate with empathy. Innovate with discipline.
Here’s a framework to help you

Dream it – Have your crazy, bold idea.
Define it – Find the “why,” the “who,” and the “when.”
Validate it – Talk to real users. Don’t assume.
Build it – Now, go build it. But keep listening. ## Conclusion

The difference between a flop and a breakthrough is often one question well asked.
Don’t just chase trends or duplicate what worked for others. Context matters. Your timing, your audience, and your solution must align like puzzle pieces.

Remember: You’re not building an app. You’re building value.
And value starts with understanding—what are you building?

If you want to see some of the side projects I built through this chaotic journey of failure, check out my posts.

Follow me on X to stay updated on what I’m up to in the world of Web3, AI, and what it means to grow as a developer in 2025.