{"id":20684,"date":"2025-10-07T04:08:25","date_gmt":"2025-10-07T04:08:25","guid":{"rendered":"https:\/\/uxmag.com\/?p=20684"},"modified":"2025-10-07T04:08:26","modified_gmt":"2025-10-07T04:08:26","slug":"designing-the-invisible-between-humans-and-technology-my-journey-blending-design-and-behavioral-psychology","status":"publish","type":"post","link":"https:\/\/uxmag.com\/articles\/designing-the-invisible-between-humans-and-technology-my-journey-blending-design-and-behavioral-psychology","title":{"rendered":"Designing the Invisible between humans and technology: My Journey Blending Design and Behavioral Psychology"},"content":{"rendered":"\n

I’ve been thinking a lot about how much has changed in my career and what I do.<\/p>\n\n\n\n

For me, it never has been about being an expert at tools or even being industry-specific, but really about what’s underneath it all, that connects humans to tech.<\/p>\n\n\n\n

I used to focus on concepts, mapping user flows, and obsessing over consistency vs creativity. (Which is still important at the right time.) Now? I’m focusing on designing systems you can’t even see. Yes, the invisible.<\/p>\n\n\n\n

When I first started in design, everything felt so tangible. You could point to a button, critique a color choice, or debate the placement of a navigation menu. Work that was great for a portfolio. Somewhere along the way, that started to feel incomplete, I felt unsatisfied, like I was simply touching the surface, what’s beneath this surface level?<\/p>\n\n\n\n

To my older brother’s annoyance, I was always asking questions, and I was never satisfied with the superficial answer. I didn’t care as much about “How does this look?” (I know it should look good \u2014 there\u2019s a bunch of great visual designers out there \u2014 that’s not me), but rather “How does this feel?” It\u2019s not just about where this button should go, but “What is this person actually trying to accomplish, and what’s preventing them?”<\/p>\n\n\n\n

With AI products, the interface isn\u2019t the key focus of the product anymore. The prompt box is just the starting point to create the connection between humans and tech \u2014 Will this thing keep its promises? It\u2019s now about what you can’t see.<\/p>\n\n\n\n

You can have the most beautiful interface in the world, but if your AI doesn’t remember what we talked about five minutes ago, trust is broken (and as humans, we know how hard it is to trust once broken). You can have the smoothest animations, but if the system consistently misunderstands what I’m asking for, I’m gone.<\/p>\n\n\n\n

So how do you design for trust? How do you design for something as intangible as reliability? (Now this makes me excited!)<\/p>\n\n\n\n

My thoughts on this<\/h2>\n\n\n\n

I’ve started thinking about this as the invisible connection between humans and technology. Every time someone interacts with AI, there’s an unspoken agreement happening:<\/p>\n\n\n\n

    \n
  1. I’ll give you my time and attention.<\/li>\n\n\n\n
  2. I’ll explain what I need.<\/li>\n\n\n\n
  3. In return, you’ll understand me and help me get there (my old friend reciprocity).<\/li>\n<\/ol>\n\n\n\n

    The interface is just the introduction \u2014 the entry point. The relationship happens in the invisible layer. It’s about context and how reliably the system delivers what you asked for, not what it thinks you asked for.<\/p>\n\n\n\n

    Going from flows to psychology, my background used to be in designing concepts and user flows. Map the journey, optimize the touchpoints, reduce friction \u2014 traditional UX thinking.<\/p>\n\n\n\n

    However, AI systems don’t work like traditional software. They’re not following predetermined paths or presenting fixed options. They’re interpreting, inferring, and making connections that weren’t explicitly programmed.<\/p>\n\n\n\n

    Which means the design challenge isn’t just about the interface anymore. It’s about psychology.<\/p>\n\n\n\n