Faking it before making it
Typical mistake many startups do is engineering idea before validating to learn whether it'd solve the problem. Obvious approach, also another mistake, is to run in a shorter sprints, demo, & get feedback till team realizes that features doesn’t seems delightful or satisfactory. Consequently, the app isn't often used by many as predicted once shipped. Speaking of learning, experimenting with a fake app to validate the idea is a cheaper, faster, a smarter strategy that's worth investing therefore.
What's there to validate about your ideas? What are the cheaper, smarter, and faster ways to engage with users to decide what a good idea is and what a stupid idea is? Let's meet to learn some of the pragmatic ways to validate your ideas before putting everything to leap-of-faith.
I had been introducing some of these tactics to many product teams, forums such as IIBA, Google Business Group events during last few years and now that entrepreneurship and startups has become one of the buzzwords, I am pleased to learn new methods that audience has to share.
Outline/Structure of the Experience Report
The session is timeboxed approximately 40 minutes. As to begin with I will be upfront about the typical mistakes we repeatedly do when building apps and share some of the real-life experience of failures. I will be sharing some of the quotes from the customers I had been working and will branch out to the next discussion point about figuring out ways to fake before engineering apps. I will be talking mostly about tactics such as landing pages, audience building, fake doors, and wizard of Oz tried at some of the products and startups I worked with. I'd hope to discuss why we chose those methods to fake some of the functionalities during the session and would like to engage with the audience to share some of the approaches they may have tried out to validate and learn about what's hot and what's not about their app ideas.
This presentation carries some of the pragmatic ways to validate your app ideas and features quickly and cheaply. It is ideal not only for engineers and designers but also for those who doesn't have prior knowledge on programming. The knowledge and the experience gathered from several product teams and startups I worked during last couple of years that are based on mobile-first.
Startups and Lean enthusiasts. Engineers and Designers. Business Analysts and those who mingle with requirements. Those who doesn't have prior knowledge on programming and those who don't like coding.