{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihukrupddwerlln4cpyhvi4h3gougbnik3c25givsilm6uymha2fi",
    "uri": "at://did:plc:fsxdrar45fdrarzog6x2vyow/app.bsky.feed.post/3mh5uobuauan2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreic6u6axdhjzc7pb4dufad5v2xxhzmuc26jckkziyqeujdemy24nqm"
    },
    "mimeType": "image/jpeg",
    "size": 67970
  },
  "description": "UX Interview Question That Breaks Candidates: Master the art of explaining your design decisions beyond just colors and layouts",
  "path": "/the-one-question/",
  "publishedAt": "2026-03-16T06:52:08.000Z",
  "site": "https://ux.prithivkumar.com",
  "textContent": "In the heat of a UX interview, there is one request that consistently catches even the most talented designers off guard: **\"Walk me through your design decisions.\"**\n\nOn the surface, it sounds simple. But this is the moment where many candidates \"break.\"\n\n### **The Common Pitfall: Explaining the \"What\"**\n\nWhen asked to walk through their decisions, most designers default to describing the visual layer. They talk about the vibrant color palette, the specific layout grid, or the choice of a particular icon set.\n\nWhile these details matter, they are the **outcome** , not the **decision logic**. If you only explain the \"What,\" you’re positioning yourself as a visual executor rather than a strategic thinker.\n\n### **The Senior Approach: Explaining the \"Why\"**\n\nGreat answers—the ones that get you hired—shift the focus from pixels to principles. To answer this question successfully, you must anchor your work in three specific areas:\n\n  * **User Context:** What was the user trying to achieve at this specific moment?\n  * **Constraints:** What technical, business, or time limitations were you working within?\n  * **Trade-offs:** Why did you choose this path over another? What did you give up to gain clarity elsewhere?\n\n\n\n### **The Power of Storytelling**\n\nThis is exactly why portfolio storytelling is your most valuable skill. It isn't just about documenting a project; it's about preparing the narrative of your logic. When you can articulate your trade-offs as clearly as your final UI, you prove that your designs aren't just \"nice\"—they are intentional.\n\n**The Bottom Line:** Your goal in an interview isn't to show that you can make things look good. It's to show that you can think clearly under pressure.",
  "title": "The One Question",
  "updatedAt": "2026-03-16T06:52:08.936Z"
}