When you get the idea there’s a bug in your hair, your skin crawls even if there’s nothing there. This week, I fixed countless bugs in my app, but I still feel like they’re crawling all over me.
Well, that was fast. This is getting hard. I’ve definitely hit “the dip” already. You saw this coming, right? This was a frustrating week and I felt that progress really slowed down—but I did meet one really important milestone.
Beginners have a huge advantage over experts: the ability to imagine without the burden of experience limiting that imagination. My first week of development is proof that beginners can be formidable.
You’ve carefully planned your new business around user research, but then you throw it all away when you pick your tech stack by choosing something that isn’t for users at all.
Before you build a product, you need to verify you’re designing based on the right data and whether you can successfully market the business. The best way to do that is to run an early user test. Here’s how I did that and what happened.
Is there such a thing as enough design? I am a designer after all. But, I still think the answer is yes. There can be enough—and too much—design, and it’s important to consider when in the lifecycle of a product you commit your time and effort to design. See how I began my product design and why I stopped short of designing the complete product.
Keeping your product small and focused is the smart way to launch quickly and be agile enough to react to data you get from real users. The usual advice says to cut all the features you can and focus on the core value. But making a minimum viable product is much more difficult than it sounds.