Designing products for the long run — on screens and on trails

  • Address the user voices on Twitter.
  • Plan Your Build, Don’t Build Your Plan.
  • Keep things on target instead of on track.
  • Always A/B test in case of doubts via Firebase.
  • Be a spy among the user groups to hear the voice.
  • A spec document is better than a verbal conversation.
  • A mock-up is better than a written spec document.
  • Build your FAQ page from user’s queries on social media.
  • A working prototype or a PoC (Proof of Concept) is better than a bunch of mock-ups.
  • Adding Amplitude events to measure the numbers for every feature release.
  • Use the competitor apps in the market to follow the trends.
  • Do your homework before design sprints adding the wow factor.
  • Keep track of the number crunching for every event and be smart.
  • When building a feature, think ahead of the developer and the QA.
  • Scrape a feature if it’s not gelling well with the audience, low on numbers and those are the lessons learned.
  • Read a lot of start-up ideas and follow the trends not just in your country but also the Chinese apps.
  • Pitch product ideas effectively under 10 minutes to get majority votes in the room. Default vote is ‘Yes’ including the absentees. An objection requires strong reasons.

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

— The Agile Manifesto

Leave a comment