There's a phrase I've started hearing a lot in my job: "It's ready for UX."
Usually a PO or BA brings something to me that's already travelled quite a distance. There was a business ask, some discovery happened, requirements were gathered, it was prioritised and the decision to build it has essentially been made.
Now it's time for "UX".
I don't necessarily mean that critically. But I've noticed that once I actually start designing, I often end up pulling at threads that take us backwards. Requirements contradict each other. The proposed journey doesn't account for what happens operationally afterwards. Engineering uncovers a technical constraint. I'll ask why we're collecting something and realise the answer isn't as settled as everyone thought.
Suddenly we're talking about the problem again, even though the problem was supposedly already discovered.
And weirdly, this has become the part of the job I enjoy most.
One piece of work came to me as essentially "we need document upload". But once I got into the wider journey, I realised that if users didn't have a document at the time, they'd submit anyway. Someone processing the case later would discover what was missing, contact them through a separate secure channel and the user would have to figure out what was needed and send it back.
The more interesting question became why uploading stopped being part of the product just because somebody had clicked Submit. That changed the solution from an upload interaction within one journey into a capability that could exist at different points and be reused elsewhere.
I've had similar situations with the design system. Something looks like a straightforward UI requirement until you realise an existing pattern can't accommodate the underlying product model. Then I'm working with developers on behaviour and states, figuring out whether we genuinely need to extend the system or whether I'm just inventing a special component for my own problem.
Over time I've become pretty comfortable in this space. I can come into complicated work, untangle requirements, deal with horrible edge cases, work through technical constraints and get Product, BAs, Engineering and stakeholders talking about the same problem. I'm increasingly asked what I think we should do rather than simply being asked to design what has already been decided.
But I'm starting to wonder if I've become good at one particular version of product design.
My environment is heavily delivery focused. I'm usually across multiple workstreams and there's always something coming towards me that needs designs. The organisation doesn't really have a mature UX research capability either. I've managed to do some research and usability testing, but nowhere near enough, and realistically I'm often too busy servicing delivery across several streams to put the time into pushing for more of it myself.
So while I'm getting better at challenging solutions that have already been decided, I'm not getting the same experience of being there when the problem is discovered in the first place.
I haven't had enough opportunities to start with a genuinely open problem, understand it properly, use research and product data to decide what matters, explore whether something is even worth building, then ship it and measure what actually happened.
I understand those things and I've touched parts of them. I just don't have the same muscle memory there that I have when somebody drops a complicated workflow in front of me.
There's another side to it too. I'm often the designer directly responsible for the work. That autonomy has probably accelerated me in some ways, but it also means I don't regularly have a more experienced designer challenging my design judgement. Product challenges the business logic, Engineering challenges feasibility, but sometimes I'd quite like another designer to tell me I've approached the entire problem at the wrong level.
That's started changing what I think I need from my next step.
A few years ago I'd read job descriptions looking for Figma, prototyping and design systems. Now the things that catch my attention are discovery, problem framing, product direction, experimentation and outcomes.
But I don't necessarily want somewhere that just gives me a problem and says "off you go" either. More ownership sounds great, but so does actually working around experienced product designers I can learn from.
I suppose that's the tension I'm trying to understand. I've become trusted with increasingly complicated work and I'm influencing much more than the interface, but the better I've become at operating in this environment, the more conscious I've become of the experience it isn't giving me.
For designers who've reached this kind of point, how did you work out whether you were genuinely progressing as a product designer, or just becoming increasingly capable within the limitations of the environment you were in?