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

Module 5 · Sat 8 Aug

Design = changing an existing situation into a preferred one. It's problem-solving, from a chair to a whole city. Good design has three sides: beauty, sustainability and utility.

UX is the full end-to-end experience, not just the screen. Good UX is effective, efficient, easy and enjoyable. It has to work in the real system too - interruptions, pop-ups fighting each other, the one action the user actually came for.

• PMs need design sense to make trade-offs and protect UX - not to replace designers.
• Session-recording tools (class example: AppSee) show where users get stuck. But more time in the app can mean confusion, not engagement. They also raise privacy and app-weight concerns.
• Docs flow: BRD → PRD → FRD/SRS/TRD. In many teams the PRD is the main one, and prototypes are replacing heavy docs.

Execution: break work into a backlog and user stories with acceptance criteria, metrics and edge cases. Jira, Confluence, Trello, Asana - learn the workflow, not the tool. In interviews, open design questions start with clarifying questions and problem framing, not brainstorming. Use local market behaviour, not global templates, to decide what works.