Part 2: Product thinking, problem statements and the Bistro case

Module 1 · Sun 12 Jul

Product thinking problem se shuru hoti hai, feature se kabhi nahi. Poocho: user kaun hai, use kya outcome chahiye, aur kaunsa pain use rokta hai? Ek achha problem statement teeno ko itna clearly bataata hai ki designer us par kaam kar sake.

Problem statement template (class): "User ko yeh outcome chahiye because of yeh insight." "Blind logon ke liye smartwatch design karo" (class example) jaise design question mein, features se pehle key nouns kholo - "blind" exactly kaun hai, aur "smartwatch" ko unke liye kya karna chahiye.

Innovation step by step hoti hai. Wright Brothers se pehle balloons aur zeppelins already the - airplane agle stage ka better solution tha. Uber se pehle bhi log travel kar sakte the. Build karne se pehle market readiness check karo aur validate karo - real users se baat karo, imaginary personas se nahi. "Sahi" solution is par depend karta hai ki existing options kya nahi kar paate.

• Great products intuitive lagte hain, trust banate hain aur repeat use ke saath better hote hain - isi se log wapas aate hain.
• Teardowns se product sense banao: real apps aur launches study karo aur poocho "unhone yeh kyun kiya?"
• Prioritisation ongoing aur business-driven hai; har feature ke liye build karne se pehle ek success metric chahiye, warna aapko kabhi pata nahi chalega ki woh kaam kiya ya nahi.

Class case - Bistro by Blinkit (10-minute food): log try karte hain lekin wapas nahi aate. Class ne dig kiya kyun - kya khaana fresh hai, kya menu repetitive hai, kya refunds painful hain, kya trust hai? Discounts trial laate hain, habit nahi. Lesson: retention perceived value, freshness, trust aur habit ke baare mein hai, aur aapko evidence chahiye, guesses nahi.