
12: Coherent Interface Design
Complementary
How to Tell When a Designer Shouldn't Code
I think what they're talking about is that they're noticing something isn't quite lining up or it doesn't feel coherent. But they don't really know why, so instead of digging in to figuring out why, it becomes more of an implementation or a designer blame game kind of thing. I do think maybe there's this diminishing, not diminishing returns, but the effort you have to put in is much higher towards the end of the coherence spectrum. So it's not necessarily diminishing returns.
00:00
Transcript
Play full episode
Remember Everything You Learn from Podcasts
Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.