{"id":1193,"date":"2026-04-24T11:37:52","date_gmt":"2026-04-24T11:37:52","guid":{"rendered":"https:\/\/adhdux.com\/?p=1193"},"modified":"2026-04-15T11:40:18","modified_gmt":"2026-04-15T11:40:18","slug":"always-ask-why","status":"publish","type":"post","link":"https:\/\/adhdux.com\/?p=1193","title":{"rendered":"Always Ask Why"},"content":{"rendered":"\n<figure class=\"wp-block-video\"><video height=\"720\" style=\"aspect-ratio: 1280 \/ 720;\" width=\"1280\" controls src=\"https:\/\/adhdux.com\/wp-content\/uploads\/2026\/04\/The_Most_Important_Question.mp4\"><\/video><\/figure>\n\n\n\n<p><a href=\"https:\/\/open.spotify.com\/episode\/4IpMfFPJwkq0GfHV8QZY1g?si=lIo7Nx34RFWFeFTmcL9t2Q\">Spotify<\/a><\/p>\n\n\n\n<p>I wish I had learned this earlier.<\/p>\n\n\n\n<p>Not the frameworks. Not the tools. Not the processes.<\/p>\n\n\n\n<p>Just one habit.<\/p>\n\n\n\n<p>Always ask why.<\/p>\n\n\n\n<p>Early in my career, I was focused on doing things right. Hitting deadlines, delivering designs, following the process. If something was requested, I executed. If a feature was defined, I designed it. If leadership aligned on a direction, I supported it.<\/p>\n\n\n\n<p>And for a while, that worked.<\/p>\n\n\n\n<p>Until it didn\u2019t.<\/p>\n\n\n\n<p>I remember a project where everything looked like a success. We shipped on time. The design was clean. The flows were efficient. Stakeholders were happy.<\/p>\n\n\n\n<p>Users weren\u2019t.<\/p>\n\n\n\n<p>Engagement dropped. Confusion increased. Support tickets went up. Nothing catastrophic, just enough to know something was off.<\/p>\n\n\n\n<p>At first, we treated it like a usability issue. We made adjustments. Tweaked layouts. Improved labels. Smoothed out flows.<\/p>\n\n\n\n<p>It didn\u2019t fix the problem.<\/p>\n\n\n\n<p>That\u2019s when someone on the team asked a simple question.<\/p>\n\n\n\n<p>Why are we solving this problem in the first place?<\/p>\n\n\n\n<p>It sounds obvious now.<\/p>\n\n\n\n<p>At the time, it stopped the room.<\/p>\n\n\n\n<p>Because the truth was, we hadn\u2019t asked it. We had been so focused on delivering the solution that we never questioned the problem. The feature we built wasn\u2019t wrong, it just wasn\u2019t necessary. It solved something that didn\u2019t actually matter to users.<\/p>\n\n\n\n<p>We had optimized the wrong thing.<\/p>\n\n\n\n<p>That moment changed how I approach everything.<\/p>\n\n\n\n<p>From that point on, \u201cwhy\u201d became part of the process. Not once, but continuously.<\/p>\n\n\n\n<p>Why are we building this?<br>Why does this matter to the user?<br>Why now?<br>Why this approach over another?<\/p>\n\n\n\n<p>And more importantly.<\/p>\n\n\n\n<p>Why does this feel off?<\/p>\n\n\n\n<p>Because it almost always does, before you can explain it.<\/p>\n\n\n\n<p>Over time, I started to notice a pattern. The biggest issues in products were rarely execution problems. They were thinking problems. Problems that came from assumptions that were never challenged.<\/p>\n\n\n\n<p>A roadmap filled with features no one needed.<br>A workflow that made sense internally but confused users.<br>A \u201cbest practice\u201d applied in the wrong context.<\/p>\n\n\n\n<p>All of it could have been caught earlier with one question.<\/p>\n\n\n\n<p>Why?<\/p>\n\n\n\n<p>As I moved into leadership roles, this became even more important. Teams move fast. There\u2019s pressure to deliver, to align, to show progress. It\u2019s easy to confuse momentum with direction.<\/p>\n\n\n\n<p>Asking why slows things down in the right way.<\/p>\n\n\n\n<p>It forces clarity.<br>It surfaces assumptions.<br>It creates better conversations.<\/p>\n\n\n\n<p>And sometimes, it stops you from building the wrong thing entirely.<\/p>\n\n\n\n<p>This is especially true now.<\/p>\n\n\n\n<p>With AI, data, and increasingly complex systems, it\u2019s easier than ever to build something that looks impressive but doesn\u2019t actually help. More capability, more automation, more output.<\/p>\n\n\n\n<p>But if you don\u2019t ask why, you end up adding complexity instead of removing it.<\/p>\n\n\n\n<p>You end up with systems that do more, but make it harder for users to understand what to do next.<\/p>\n\n\n\n<p>That\u2019s the risk.<\/p>\n\n\n\n<p>The discipline of asking why is not about being difficult. It\u2019s about being intentional. It\u2019s about making sure that what you\u2019re building actually matters.<\/p>\n\n\n\n<p>Looking back, the biggest growth in my career didn\u2019t come from learning new tools or processes.<\/p>\n\n\n\n<p>It came from getting comfortable challenging what seemed obvious.<\/p>\n\n\n\n<p>From asking why when it would have been easier not to.<\/p>\n\n\n\n<p>So if there\u2019s one piece of advice I\u2019d give, especially to people earlier in their careers, it\u2019s this.<\/p>\n\n\n\n<p>Don\u2019t just do the work.<\/p>\n\n\n\n<p>Understand the work.<\/p>\n\n\n\n<p>And never stop asking why.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Spotify I wish I had learned this earlier. Not the frameworks. Not the tools. Not the processes. Just one habit. Always ask why. Early in my career, I was focused on doing things right. Hitting deadlines, delivering designs, following the process. If something was requested, I executed. If a feature was defined, I designed it.<\/p>\n<p><span class=\"more-wrapper\"><a class=\"more-link button\" href=\"https:\/\/adhdux.com\/?p=1193\">Continue reading<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3,6,7],"class_list":["post-1193","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-ux","tag-uxresearch","tag-uxstrategy"],"_links":{"self":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts\/1193","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1193"}],"version-history":[{"count":1,"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts\/1193\/revisions"}],"predecessor-version":[{"id":1195,"href":"https:\/\/adhdux.com\/index.php?rest_route=\/wp\/v2\/posts\/1193\/revisions\/1195"}],"wp:attachment":[{"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1193"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1193"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/adhdux.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}