Comment by Spooky23 | Hacker News Reader

Comment by Spooky23 | Hacker News Reader

Parent Full thread

The way I've interpreted it, when done well, it's usually focused on designing experience first (ie the "what") and then focusing on the "how" afterward. Think about a well designed mobile app with thought out user journeys vs. a circa 1999 VB6 app, which was focused on whatever IT nonsense was were doing first.

When done poorly, it means you get trapped in a room with some folks with religious zeal and a set of post-it notes in various colors, sharpies, and colored paper sticky dots for a few days. Afterward, you get... not much. It's just like agile.... if the "practitioner" is hyper-focused on the rituals and ceremony, it's easy to miss doing actual work.

My personal beef with the concept is that the ceremonial aspects mean you need a special UX/design/etc specialist, who comes in and leaves. Usually the "design" processes focus on 80% solutions, and nobody comes back to finish the other 20%. You used to notice this when people built out responsive websites -- key functions that weren't in the "Top X", would just disappear on mobile.

A realistic portrayal. Always amusing when I step into a conference room and the little cubbies or trays full of post it notes and sharpies and markers left behind telegraphs how the next few hours in talking with the stakeholders will go since it's clear now I'm here for the "how".

Then when I started leading the design thinking sessions all I can think of is how silly all this is. When we went remote during covid, introducing in virtual whiteboards like Miro and Figma, made the rituals and ceremonies more tolerable and more importantly actionable.

After all this time weaving through Stanford where this all went down, the corporate war rooms all over, settling down now, ultimately I think it just comes down to this: design thinking is really just empathetically solving problems rather than apathetically solving problems (as in working off requirement documents or best practices or protocols or just because you're told what to do).

All the little ceremonies and rituals is inclusivity of everyone to empathize and feel good about each other, and consider things from additional POVs. Which back then at the tail end of Gen-Y transition into the workforce was needed. Now you talk to the Gen-Z workforce about using empathy at work more and they'll just go: facts.

So I guess it’s almost like the “Scrum” of the design world. It can help you focus on the right thing, but just following the process won’t magically give you good results.

Focusing on the what with no grounding of the how is the start of the ongoing struggle between design and engineering. Eventually you need a tight feedback loop between what and how, as the how will do a good job tearing up those post-it notes otherwise.

Well put.

Reply on news.ycombinator.com