u/Ahmiiux

One thing I'm trying to improve is resisting the urge to open Figma too early.

When you're given a Business Requirements Document (BRD), PRD, or a feature request, what does your process actually look like before you start designing?

Some questions I'm curious about:

• How do you read and analyze a BRD/PRD?
• What information are you looking for first?
• How do you identify the real problem instead of just the requested solution?
• What framework or checklist do you use before creating wireframes?
• How do you connect business goals with user needs?
• What deliverables do you create before high-fidelity screens (flows, journey maps, assumptions, edge cases, etc.)?

I'd especially love to hear from Senior Product Designers or Staff/Lead Designers working on B2B SaaS or enterprise products.

I'm trying to build a stronger product thinking process rather than just becoming better at UI, so I'd really appreciate hearing how experienced designers approach this.

One thing I'm trying to improve is resisting the urge to open Figma too early.

When you're given a Business Requirements Document (BRD), PRD, or a feature request, what does your process actually look like before you start designing?

Some questions I'm curious about:

• How do you read and analyze a BRD/PRD?
• What information are you looking for first?
• How do you identify the real problem instead of just the requested solution?
• What framework or checklist do you use before creating wireframes?
• How do you connect business goals with user needs?
• What deliverables do you create before high-fidelity screens (flows, journey maps, assumptions, edge cases, etc.)?

I'd especially love to hear from Senior Product Designers or Staff/Lead Designers working on B2B SaaS or enterprise products.

I'm trying to build a stronger product thinking process rather than just becoming better at UI, so I'd really appreciate hearing how experienced designers approach this.