Does anyone feel stakeholders expect night fidelity designs almost immediately without having the patience to review wireframes and refine the flow first?
With vibe coding I feel if designers take time with usual design process, stakeholders or even your own PM/BA will immediately vibe code something and present it as the working solution to be iterated.
I would like to know, has vibe coding changed how you approach your design process in this context and should designers move faster into higher fidelity designs now?
I swear this post was written by AI but intentionally included typos. The question format and username is textbook. I don’t know what to believe anymore.
Well.. you're wrong.
I can same thing about comments like yours going around calling posts Ai and down voting them
On what basis do you think its AI generated? Your response looks more like a bot reply to me.
If you dont have an answer dont reply at all. Move on.
If you dont want to answer the post then dont reply at all. Ignore and move on.
Formal/academic “ux process” waste too much time only to output everything abstract. No pm/dev would understand/know what to do with whatever typical ux artifacts like journeys, flows, wireframes etc. I don’t even know what the hell should i designed on the interface anytime the ux person in the team handoff me some wireframe or flows. Stakeholder not knowing design should not been a ‘newly discovered reality’ not even in early 2020s, yet its always funny to see this sub felt surprised that nobody respect design. Well graphic design suffers this exact issue for decades and ux made it worse since its best practice dogma is literally every method of design by committee with little to no expertise judgement existent as it believes everything need to be tested
sounds like you’ve worked with a lot of shitty UXers. Or you’ve taken little time to understand the value of a user-centered product approach. Mature product leaders and orgs will absolutely value proper UX, as it speeds things up and translates the abstract to concrete.
Different fidelities for different purposes Wireframes are great to strip look and feel away. Do we need this function. Is this structure correct. High fidelity can come later. Too many stakeholders get caught up in the ‘can we change button colour’ loop.
Yes. It's called the Dunning Kruger Curve. They have just enough knowledge to believe it's simple, with no concept of the intricacies.
In my opinion, it really depends on the outcome you're trying to achieve and why you're doing it in the first place.
If the goal is simply to explore ideas without going too deep, then sure, why not vibe code?
For the use case you described ("immediately vibe code something and present it as the working solution to be iterated on"), it's actually a great way to avoid spending too much time on something that might not even survive the first discussion.
That said, I wouldn't call it "the working solution". Before anything else, you need to find out whether it actually works for the business. And if it does, that's when the real work begins: thinking through the technical details, edge cases, constraints, and trade-offs. AI is great at generating ideas, but it doesn't always have enough context to understand the full picture or the project's limitations.
Ngl, yesterday I was showing my tech manager the web designs I made for an app redesign. I was just a day late in sharing them and you know what he told me? They had already started working on it using Claude because I hadn’t shown the designs earlier. Tbh hearing that has seriously made me rethink this career