Part 1: Framing the problem - JTBD, 5 Whys, HMW, first principles

Module 4 · Sat 1 Aug

Research tabhi useful hai jab aap use ek sharp problem mein badlo: user kaun hai, pain kya hai, impact kitna bada hai, aur why now. Achha product kaam hai sahi problem, sahi user ke liye, sahi time par.

Jobs To Be Done (JTBD): customer product ko kaunsa job karne ke liye "hire" kar raha hai? Class example - guitar: log guitar seekhte hain stress relief, self-expression, discipline, identity ya cool dikhne ke liye. Agar real job discipline hai, to shayad jawab gym routine hai, guitar nahi. Tab tak "kyun" poochte raho jab tak deeper goal na mil jaaye.

• 5 Whys = root cause diagnose karo. How Might We = us diagnosis ko solution prompt mein badlo.
• Systems thinking = jude hue causes aur feedback loops trace karo (class examples: Twitter, marketplaces).
• First principles = basic truths se dobara banao (batteries aur rockets). Tab use karo jab problem ambiguous ya strategic ho.

Class example - wallet preload (jaise pehle app wallet mein paisa daalna): first order par friction badhta hai, lekin bacha hua balance users ko wapas kheenchta hai - top-up → spend → top-up. Companies jaan-boojhkar first-order conversion ki jagah retention chunti hain.

Kya optimise karna hai, yeh job par depend karta hai: design-first jab looks aur identity se kharidari hoti hai, utility-first jab performance matter kare, validation-first jab baat status ki ho. Wallets aur subscriptions upfront friction badhate hain lekin repeat use boost karte hain. Aur prioritisation thoda analysis, thoda politics hai - best leverage wali problem chuno, sabse loud request nahi.