When you're starting to build a product, it's easy to get overwhelmed by the idea of creating the perfect solution right from the start. But the truth is, the best way to build a successful product is to start with something… even if it's just a high-level sketch or a basic storyboard. This initial brainstorming phase is obviously important because it allows you to visualize your concept and get a clearer sense of what might solve your users' problems. In our case, we started with different storyboards, brainstorming diagrams, business model canvas, and a whole lot of Miro. Some great examples are provided below by Maad Labs:

image.png

Once you're getting more detailed about what the actual product looks like (if you're working with software), use tools like Figma for quick mockups. PLEASE don't feel like you need to dive into coding right away. At this stage, it's all about being scrappy and efficient. Build quick prototypes, even if they’re just rough versions of what you envision. There's no need to spend weeks or months perfecting the design before you get feedback from potential customers. We started with a rough idea for wireframes and turned it into Demo videos (think of a walkthrough).

image.png

image.png

The goal here is to get something in front of users as soon as possible to see if it’s actually solving any of their problems. Ask them questions like: "Do you see yourself using it?", “Would this save you time and why?”, and “Why is it better than what you are currently using?”

If you start to see a pattern and users confirm that it's addressing their pain points, then you can start building a product. But even then, keep it small. The key is to continue adding on top, iterating and iterating so you can get closer to a product that's worth paying for. And even then, I’m sure the process never ends! The demo we showed to users looked like this:

https://youtu.be/mgCz37yXMns

To be honest, I’d say for us this was probably the biggest lesson we were forced to learn: it’s better to iterate 10 times in a month than to spend three months building something more robust. The risk you face is realizing that it's not what your users wanted in the first place, and at that point, you’ve wasted a lot of valuable time. Quick iterations based on real feedback will always move you closer to the right solution and keep your team motivated rather than getting a big blow at the end.

In short, start small, build quickly, and iterate fast. Your users will tell you what works, and that feedback will guide your next steps.

Resources: Storyboards by Maad Labs

https://medium.com/the-lean-lab/week-1-the-importance-of-iteration-and-the-lean-startup-model-1b329cf0ed9f

https://www.goodreads.com/book/show/9549300-do-more-faster