Pradeep Kumar ✏️

controversial take: "because it felt right" is usually the correct answer. it's also the one that loses every argument. portfolio round in a hiring loop this week. senior candidate, easily the strongest work in the pipeline. i pointed at the best interaction in their case study and asked why it feels right. they froze, offered "it just… reads better?" and then did the thing i hate watching — started doubting the work itself, live, mid-sentence. the work was right. the why just hadn't arrived yet. that freeze isn't a design problem. intuition and articulation are two different skills and they don't grow on the same clock. think about how you actually learned this craft: you built the thing, it sucked, you rebuilt it a dozen times, and somewhere in there — sometimes by accident — it landed in a place that feels really good. only then, standing in the version that works, could you explain why the old ones sucked. the why shows up after the feeling. every time. articulation is archaeology, not prophecy. meanwhile the feedback economy runs in exactly the wrong direction. design is visual, so the bar for having an opinion about it sits on the floor — anyone can glance at your screen and ask "why is this in two columns?" nobody does that to engineers. engineers get functional feedback, "pressing this button gives me this error," cause giving vague technical feedback requires being able to engineer. but the bar for a good answer to a low-bar question is disproportionately high. "it felt right" satisfies nobody, even when it's true. so you're holding a correct decision you can't defend yet, against questions that cost nothing to ask. that's why designers fold in rooms. not cause they're wrong. cause the vocabulary is still in transit. two moves fix this. in the room: stop converting "i can't explain it" into "i must be wrong." unrelated facts. after the room: do the archaeology while it's cheap. put the version that feels right next to the last one that didn't and name what actually changed. every "felt right" i've ever dug into eventually decomposed into something nameable — a grouping, an alignment, a delay, a metaphor borrowed from somewhere the user already lives. name it once and it's yours forever. next review you're not defending a feeling, you're stating a rule. that's most of the gap between senior and principal, btw. the design skill was already there. (they got the offer.) one edge: this only protects earned intuition. intuition is compressed iteration history — if you haven't built the pattern enough times to watch it fail, your "feels right" is a preference, not a signal. doubt that one freely. and if you're thinking "if intuition's probably right, why bother articulating" — rooms don't run on correctness. an unarticulated right answer loses to an articulated mediocre one every single time. that's exactly how good design gets negotiated away. your intuition is ahead of your vocabulary. that's not a reason to doubt it. it's a reason to catch up.