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.

 
4 favorite thumb_down thumb_up 8 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

The session is timeboxed approximately 80 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.

Learning Outcome

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.

Target Audience

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.

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Shiv Sivaguru
    By Shiv Sivaguru  ~  11 months ago
    reply Reply

    This session is proposed under the 90 minute format.

    The description mentions a 40 minute timebox.

    please clarify.

    Also, in 40 minutes, other than showing videos, how much time do you plan to spend in sharing your thoughts and taking questions?

    • Kosala Nuwan Perera
      By Kosala Nuwan Perera  ~  11 months ago
      reply Reply

      The approx. time would be 80mins. Sorry about the confusion, my mistake. I have updated the content. The videos would take approx. 10mins. and would be quite important to the audience since the experience is directly related to the topic. I will be engaging with the audience to get their thoughts during the video sharing so it will not be just watching the videos.

      Rest of the 60-70mins I will be mostly sharing my experience categorised into tactics mentioned in the Outline;

      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.

      Whilst, I will be engaging with the audience to learn their experience also mentioned in the Outline;

      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. 

      • Karthik Kamal Balasubramaniam
        By Karthik Kamal Balasubramaniam  ~  11 months ago
        reply Reply

        Thanks for your response. I see that you have mentioned that you will engage with the audience during this session, however I am not very clear about how you plan to engage with them. Any specific videos would give us an idea.

        Also I would like to know if the session duration is negotiable or you would need entire 90 minutes?

        • Kosala Nuwan Perera
          By Kosala Nuwan Perera  ~  11 months ago
          reply Reply

          Engagement with the audience mostly a self-learning, self-healing type Conversational to hearing Audiences' Opinion. Presentation duration can be brought down to 45min talk somewhat similar to the Agile DC http://agiledc.org/2016-schedule/.

           

          • Karthik Kamal Balasubramaniam
            By Karthik Kamal Balasubramaniam  ~  11 months ago
            reply Reply

            Thanks Kosala. If we reduce the session to 45 mins what will the audience miss? I see the same slidedeck, not sure if I missed it. Could you please clarify?

            • Kosala Nuwan Perera
              By Kosala Nuwan Perera  ~  11 months ago
              reply Reply

              Some of the case studies and work I have done for the last few months will not be added to the 45min session in best case scenario, so I will not run out of time.

              I have updated the talk to 45mins but will have to get the slidedeck up-to-date with new content.

  • Balaji Ganesh N
    By Balaji Ganesh N  ~  11 months ago
    reply Reply

    Hi Kosala,

    I share similar thoughts as Shiv.

    Can you please clarify if this is a 45 minute or 90 minute presentation.

    Other points:

    The presentation looks theoretical.

    It will be great if you could correlate the nuances from your experience which helped create better UX and accelerated product discovery.

    In case it is a 90 minutes presentation, are you planning to include any activity based exercises.? How are you planning to engage audience interest for 90 minutes ?

    Regards,

    Balaji

    • Kosala Nuwan Perera
      By Kosala Nuwan Perera  ~  11 months ago
      reply Reply

      Take from Shiv's reply.

      The approx. time would be 80mins. Sorry about the confusion, my mistake. I have updated the content. The videos would take approx. 10mins. and would be quite important to the audience since the experience is directly related to the topic. I will be engaging with the audience to get their thoughts during the video sharing so it will not be just watching the videos.

      Rest of the 60-70mins I will be mostly sharing my experience categorised into tactics mentioned in the Outline;

      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.

      Whilst, I will be engaging with the audience to learn their experience also mentioned in the Outline;

      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. 

      There will no exercises/activities other than the discussions and conversations that I am planning to have with the audience.