Part 1: What design and UX really mean for a PM

Module 5 · Sat 8 Aug

Design = ek existing situation ko preferred situation mein badalna. Yeh problem-solving hai, ek chair se lekar poore sheher tak. Achhe design ke teen sides hain: beauty, sustainability aur utility.

UX poora end-to-end experience hai, sirf screen nahi. Achha UX effective, efficient, easy aur enjoyable hota hai. Use real system mein bhi kaam karna chahiye - interruptions, aapas mein ladte pop-ups, aur woh ek action jiske liye user actually aaya tha.

• PMs ko trade-offs karne aur UX protect karne ke liye design sense chahiye - designers ko replace karne ke liye nahi.
• Session-recording tools (class example: AppSee) dikhate hain ki users kahan atakte hain. Lekin app mein zyada time ka matlab confusion bhi ho sakta hai, engagement nahi. Inse privacy aur app-weight concerns bhi aate hain.
• Docs flow: BRD → PRD → FRD/SRS/TRD. Kai teams mein PRD main doc hai, aur prototypes heavy docs ki jagah le rahe hain.

Execution: kaam ko backlog aur user stories mein todo, acceptance criteria, metrics aur edge cases ke saath. Jira, Confluence, Trello, Asana - workflow seekho, tool nahi. Interviews mein open design questions clarifying questions aur problem framing se shuru hote hain, brainstorming se nahi. Kya kaam karega, yeh decide karne ke liye local market behaviour use karo, global templates nahi.