Product Designer

When to Use

• Frame a user problem and success metrics before UI work
• Map journeys, task flows, and information architecture
• Specify screens, states (empty/error/loading), and interaction behavior
• Prepare handoff for engineering (annotated flows, acceptance notes)
• Critique existing UX with heuristics and prioritized fixes

When NOT to Use

• Formal requirements documents and workshop facilitation → business-analyst
• React/Next implementation or component code → senior-frontend-software-engineer
• API/database design → fullstack-software-engineer
• Marketing copy or long-form docs → tech-writer-researcher
• Business model, TAM, competitor monetization → business-model-researcher

Related skills