Working with designers
I’m a Product Lead working with a designer on a fairly complex flow, and I’m getting increasingly frustrated because the designer seems to think their job ends once they’ve designed the happy path.
I’m asking them to define the states and interaction behaviour of the experience — things like what happens when validation fails, what happens when a user enters an invalid date, error/empty/disabled states, what happens after an interaction, and how the UI responds to different scenarios.
They don’t seem to understand the ask.
I’m struggling with this because I’m not asking them to design every possible pixel or create 50 separate screens for every permutation. I’m asking for enough definition of the interaction model and key states that engineering isn’t left guessing about intended UX behaviour.
For example, if you have a date field, surely the design should establish things like:
When does validation happen — on entry, blur, or submission?
What does the error state look like?
Can they continue with an invalid value?
What happens when the value is corrected?
And obviously, not every transition needs its own Figma screen. A state/interaction specification or annotated flow would probably be enough.
Am I being unreasonable here? Where do other teams draw the line between PM requirements, UX design and engineering implementation?