I’m curious about the context of this argument is this shift mainly happening in startups or across agencies and corporates too? The dynamics seem very different depending on speed, structure, and incentives.
If engineers are now prototyping and designers are coding, who carries the responsibility for UX depth things like user testing, understanding customer behavior, and iterating based on real feedback?
Are teams where this role blending works successfully doing something specific to stay aligned on user experience? How are PMs, engineers, and designers maintaining a shared understanding of what users are actually going through?
Key thing is about getting AI to do things we can’t do, don’t want to do, or need help with.
I like most of programming. So I’ll write code myself.
I like the design process. But I use AI to expand upon my wireframes and notes and turn them into something that my users can understand. Then I tweak it.
I don’t enjoy marketing. So the limited social media presence I have is heavily influenced by AI.
But if you’re happy with where you are in a part of a project, or the whole thing, don’t feel pressured to use AI.
We’re still at a point where no one knows exactly which direction working with AI will go but what every designer can be certain of is this: by not engaging with it, and by standing in opposition to what design actually is and why reducing it to pushing pixels is a dead end, they’re putting themselves in a very difficult position in the market in the coming years, if not months.
Hi, thanks for putting this together. As someone schooled years ago by "always bring a prototype to the meeting" and learning about agile from colleagues/teams at Pivotal, I'm curious about a couple things. Because of the fluidity, flexibility, ease of building "something" which seems it could lend more time to iteration, exploration...How are teams adjusting their "research inquiries", when it is quite unclear what to build, specifically with questions about expanding share-of-wallet (new products for existing customers) or expanding marketshare (existing product for new customers) or just getting started (new customer, new product)? Maybe you've written about this already, apologies, if so. Thx.
Yes, that’s what he said: designers won’t just be “designers” anymore, but rather orchestrators, directing AI tools, shaping workflows, and ensuring consistency across products, all while bringing that essential design touch. Just like in development, where relying on AI without understanding code and logic isn’t ideal, in design it will be similar, only with a design-oriented focus.
I’m curious about the context of this argument is this shift mainly happening in startups or across agencies and corporates too? The dynamics seem very different depending on speed, structure, and incentives.
If engineers are now prototyping and designers are coding, who carries the responsibility for UX depth things like user testing, understanding customer behavior, and iterating based on real feedback?
Are teams where this role blending works successfully doing something specific to stay aligned on user experience? How are PMs, engineers, and designers maintaining a shared understanding of what users are actually going through?
Key thing is about getting AI to do things we can’t do, don’t want to do, or need help with.
I like most of programming. So I’ll write code myself.
I like the design process. But I use AI to expand upon my wireframes and notes and turn them into something that my users can understand. Then I tweak it.
I don’t enjoy marketing. So the limited social media presence I have is heavily influenced by AI.
But if you’re happy with where you are in a part of a project, or the whole thing, don’t feel pressured to use AI.
What does year one even look like for a junior designer now?
We’re still at a point where no one knows exactly which direction working with AI will go but what every designer can be certain of is this: by not engaging with it, and by standing in opposition to what design actually is and why reducing it to pushing pixels is a dead end, they’re putting themselves in a very difficult position in the market in the coming years, if not months.
key is to use ai as a thinking partner and not use it to think for you
Awesome, thanks for sharing
Hi, thanks for putting this together. As someone schooled years ago by "always bring a prototype to the meeting" and learning about agile from colleagues/teams at Pivotal, I'm curious about a couple things. Because of the fluidity, flexibility, ease of building "something" which seems it could lend more time to iteration, exploration...How are teams adjusting their "research inquiries", when it is quite unclear what to build, specifically with questions about expanding share-of-wallet (new products for existing customers) or expanding marketshare (existing product for new customers) or just getting started (new customer, new product)? Maybe you've written about this already, apologies, if so. Thx.
Looking forward to reading. I assume this has some AI component to it?
What do you mean sorry?
The future of product design, I assume there is some integration of AI technology with the future of Product design, no?
Yes, that’s what he said: designers won’t just be “designers” anymore, but rather orchestrators, directing AI tools, shaping workflows, and ensuring consistency across products, all while bringing that essential design touch. Just like in development, where relying on AI without understanding code and logic isn’t ideal, in design it will be similar, only with a design-oriented focus.
Thank you for sharing, it feels like eye opening
Thanks for reading. Glad it was helpful!