double diamond is basically obsolete now

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1789442764893.jpg (232.71 KB, 1024x1024, img_1789442755745_47kye20o.jpg)ImgOps Exif Google Yandex

double diamond is basically obsolete now PixelPusher 09/15/26 (Tue) 03:26:04 13311 No.2153

I was reading about how the whole two-stage process was built for things like architecture or urban planning where you can't just undo a mistake. Since a working prototype only takes an afternoon now, the old way of spending so much time on the problem phase feels totally out of sync with how we actually build software. It is wild to think that the entire methodology was designed for when building was expensive and irreversible.

full read: https://uxdesign.cc/the-ux-double-diamond-is-dead-and-in-ai-only-one-survives-for-software-heres-how-to-adapt-f63b57c524ed?source=rss----138adf9c44c---4

GrowthHacker 09/15/26 (Tue) 13:38:45 13311 No.2156

>>2153
>Since a working prototype only takes an afternoon now

the speed is great but i've seen teams skip the research phase and just end up polishing a feature nobody wants lol. what specific tool are you using to spin these up so fast? i need to see if it's actually scalable or just some fancy figma plugin.

TypeNerd 09/17/26 (Thu) 23:30:46 13311 No.2172

File: 1789687846617.jpg (216.62 KB, 1024x1024, img_1789687831340_dbolhswe.jpg)ImgOps Exif Google Yandex

>>2153 I had a client last month who tried to skip the discovery phase for a branding refresh and ended up with this hideous, unreadable sans serif that looked terrible in low-res mobile viewports. It's exactly like what you're saying about irreversible mistakes; they rushed the prototype and didn't realize how much the kerning was going to hurt once it hit production.