<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sofia Modesto on Medium]]></title>
        <description><![CDATA[Stories by Sofia Modesto on Medium]]></description>
        <link>https://medium.com/@sofia.modesto?source=rss-43665411a72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*NrDqjxI9Ed6lXktQ.</url>
            <title>Stories by Sofia Modesto on Medium</title>
            <link>https://medium.com/@sofia.modesto?source=rss-43665411a72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:54:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sofia.modesto/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The best designs should be invisible… So should the best AI experiences]]></title>
            <link>https://medium.com/design-bootcamp/the-best-designs-should-be-invisible-so-should-the-best-ai-experiences-fdb766f4dbe2?source=rss-43665411a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdb766f4dbe2</guid>
            <category><![CDATA[agents]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[genai]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Sofia Modesto]]></dc:creator>
            <pubDate>Thu, 03 Jul 2025 14:53:37 GMT</pubDate>
            <atom:updated>2025-07-05T14:37:35.405Z</atom:updated>
            <content:encoded><![CDATA[<p>In recent years, as the AI hype has grown, we’ve started to think more and more about how to design for AI. As a UX designer myself, here are my thoughts on the matter.</p><p>GenAI has promised (not yet confirmed though) to revolutionize everything from basic, mundane tasks like picking what to wear, what to eat, or where to drive, to more complex tasks like finding cures for diseases or revolutionizing the way we work. In today’s global landscape, AI generates both fascination and uncertainty about the future, leading us to question the role of humans in the workforce and society. However, instead of viewing AI as an existential threat, I do believe we should embrace it as a powerful capability, capable of amplifying our potential and solving complex problems, as technology is the invisible hand that has sculpted the course of our civilization.</p><p>Technologies have always changed humanity, and we have always adapted to new ways of working or living. We see this pattern throughout history, from the first stone tools that led us to hunt, to the agricultural revolution that settled us, to the invention of writing that enabled us to spread news and knowledge, and the evolution of scientific knowledge that originated the personal computer revolution that led to smartphones in our pockets. That’s why AI seems to be the natural next step in this journey. Would it be?</p><p>Behind the hype and the show-off of complex algorithms, there’s a critical truth that is often overlooked: the true importance of AI doesn’t lie in its ability to be intelligent, but rather in its capacity to solve real problems and improve people’s lives. From the user’s perspective, the magic of AI isn’t the technology itself, but the benefit it delivers, so seamlessly that it often goes unnoticed.</p><h3>The “AI” label</h3><p>The AI label appears everywhere, all at once, yet often without showing its purpose. Every company and product rushes to announce its AI capabilities. Yet, this communication often leaves me wondering, “What is this AI for?”. If a product claims to have AI but cannot clearly articulate how that AI improves the user experience or solves a specific problem, then the promise is empty.</p><p>Let’s get into real-world examples:</p><ol><li>Think about the spam filter in your email. You don’t need to understand how it works, what machine learning models it uses, or how many layers its neural network it has. What matters is that your inbox stays clean, free from unwanted messages. This is AI in action, designed with a clear focus, making your email organized and efficient.</li><li>Think about smartphones. Even though last year’s smartphone release events focused on delivering new AI capabilities, no one buys a smartphone just because it uses AI. Instead, you buy it because it takes amazing photos, provides great graphics for your gameplay, its battery lasts all day, or typing is faster. And in all these cases, AI is the invisible thing<strong> </strong>that makes these features possible.</li></ol><p>Isn’t this valuable by itself, even without the AI labeling? What I want to say is that the user’s focus is always on the tangible thing, not the underlying technology enabling it. “We have AI” is only relevant if it’s followed by “to give you this” or “to solve this problem”.</p><h3>Invisible UX design and AI</h3><p>As a UX designer, invisible design is a core principle we strive for. We don’t aim to make things literally disappear, but rather focus on crafting experiences where the technology and interface are so intuitive, seamless, and effortless that the user doesn’t even consciously notice them. The design simply works, allowing the user to focus on their task or goal, rather than on how to use the product.</p><p>Designing for an AI-led world that focuses on the user experience means that every product, algorithm, chatbot, and recommendation system is built with human needs and behavior in mind. It’s not about how smart the AI can be, but how useful and intuitive it is for those who use it.</p><p>Some examples of invisible design are when you go into your car and it automatically suggests the best route for a place you’re used to go on that specific time, when you receive a weather forecast for your location reminding you to use an umbrella as it’s going to rain, or, when you are on Netflix, Spotify, or online shopping, and you are suggested with content and products you’ll likely enjoy, always with the option to reject or adjust those preferences.</p><p>In these examples, AI is an invisible enabler, optimizing processes and reducing friction, without requiring the user to understand its underlying complexity, and always respecting their freedom of choice.</p><h3>What about the future of AI?</h3><p>Maybe not so invisible.</p><p>As AI continues to evolve, its measure of success won’t be its ability to pass the Turing test or create artworks on its own. The next step for AI isn’t just about making it more intelligent, but rather about making it more human in its interaction and more effective in its ability to serve our needs.</p><p>While the pinnacle of many AI applications lies in their invisible efficiency, the evolving landscape of conversational AI and intelligent agents presents a shift. These aren’t meant to disappear into the background. Their purpose relies on a visible interaction with the user. Like an advanced AI assistant that manages your calendar, prioritizes your tasks, or even participates in complex discussions. Here, the AI’s presence, its ability to understand context, and its capacity to communicate become central to its utility. <strong>The design challenge shifts from making AI invisible to making its visibility intuitive, trustworthy, and helpful.</strong></p><p>Ultimately, while the invisible AI will continue to solve countless problems behind the scenes, the future demands that we, as UX designers, master the art of making AI’s visible interactions intuitive, transparent, and ethical, proving that sometimes, the most effective tool is one you can directly engage with and understand.</p><p>Let’s see what the future holds.</p><figure><img alt="Invisible AI interactions" src="https://cdn-images-1.medium.com/max/1024/1*M4da4MOiSWpSQe23yAEm8A.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdb766f4dbe2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-best-designs-should-be-invisible-so-should-the-best-ai-experiences-fdb766f4dbe2">The best designs should be invisible… So should the best AI experiences</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a UX team with product mastery]]></title>
            <link>https://medium.com/@sofia.modesto/building-a-ux-team-with-product-mastery-540561de915b?source=rss-43665411a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/540561de915b</guid>
            <category><![CDATA[outsystems]]></category>
            <category><![CDATA[team-management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Sofia Modesto]]></dc:creator>
            <pubDate>Fri, 31 May 2024 10:29:52 GMT</pubDate>
            <atom:updated>2024-05-31T10:29:52.263Z</atom:updated>
            <content:encoded><![CDATA[<h3>A bit about myself:</h3><p>Let me introduce myself first. I’m Sofia and I’m currently leading the UX App Development team at OutSystems.</p><p>Ever since I was little, I have liked to create things. It started with huge Lego towers, then evolved into creating elaborate mansions in SIMS. Eventually, this creative drive led me to develop a calculator computer program. That moment made me realize that I would like to be a Software Engineer and solve complex problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/0*ekdi90ZTz1D6zc3e" /><figcaption>One of the first Lego towers I’ve made</figcaption></figure><p>Ever since I can remember, I have woken up every morning wanting to change something in the world and fix something for the better.</p><p>That’s why I ended up working at OutSystems, I love our mission. We enable every one, every human on the planet to create whatever app they want. Regardless of its complexity, anyone can use our platform to create it.</p><p>On top of that, OutSystems has this huge team of superheroes that work there, that make everything possible. Anything we want to do, there’s a team of developers that can turn it into reality.</p><p>A couple of years ago, I started my journey as Team Lead for the app dev area, which is one of the most complex areas of our product. This area includes our IDE, which is more oriented to developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iqlPUlpIgOZd0YRk" /><figcaption>ODC Studio (IDE) and ODC Portal</figcaption></figure><h3>The challenge:</h3><p>Back then, I was presented with a considerable challenge. I needed to build a team capable of leveraging our IDE to the next level, meaning, making something technical a little bit easier to use. For that I needed to find a group of UXers who are masters in this area, who know our product and how to use it, so they can understand our users’ challenges and enhance their experiences.</p><p>At first, I thought we needed engineers with UX expertise due to our product’s complexity. However, upon further reflection, I realized that prioritizing UX specialists might be more beneficial. This approach would allow us to strengthen our team with dedicated UX experts who can bring their insights and skills to the forefront, ensuring a user-centric focus in our development efforts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t0xu9rLcCeGVmZJR" /><figcaption>Number of UXers with and without tech background in our UX group</figcaption></figure><p>Unfortunately, this didn’t go as planned.</p><p>I’ve lost multiple people within my team, because of the challenges posed by such a complex product. This was disheartening for me and for the team, as those people were amongst the best, they just lacked the technical context.</p><h3>The “Code Afternoon”:</h3><p>One day, I had an idea: What if we could help the UXers acquire technical knowledge specific to our product usage without the whole engineering side? Our product is for everyone to use, remember? If anyone can use it, our team can learn how to use it too.</p><p>At first, I started small. I started an initiative we called the “Code Afternoons” where our team would create apps for an entire afternoon, using our IDE. This could be any app.</p><p>This moment was a game changer for the team, as until that moment the team was focused on delivering, and barely had the time to stop and breathe.</p><p>Having time for you to learn and relax at the end of every Friday, made a huge difference.</p><p>During those afternoons we have built apps for internal use, and we’ve built apps for personal use. The real value of these afternoons weren’t the apps themselves, but the learning and getting familiar with the platform instead. This was great, we kept doing it for over a year, and it was amazing to see that not only did the team get more motivated to have this time to stop working on their daily tasks, to learn, but we were also able to find tons of issues in the product that otherwise wouldn’t have been caught so fast.</p><p>At this point, I was happy with the result, but some of the members without an engineering background were struggling in these sessions, requiring step-by-step guidance by others and that wasn’t effective.</p><p>At this point, we tried another approach, an intensive course over a week to provide them with this context. Unfortunately, that still didn’t work.</p><p>So I realized I had to start fresh.</p><p>This time I had to go big! Go big or go home they say, you know?</p><h3>The “Dev Pilot Program”:</h3><p>So I proposed creating a dev pilot program to apply to my team’s next newcomer. A distinct approach, never tried in the company.</p><p>This is an immersive program. The key point is that this person will have dedicated time, full-time for one and a half months to learn to use our product and put it into practice as if they were a developer in a team using OutSystems on a daily basis.</p><p>The first step was to find a dev team that would be able to welcome the newcomer.</p><p>The second step was to find the time for the newcomer to learn about this.</p><p>The third step was to find a newcomer willing to try this.</p><p>At this point we defined the success metrics for such a program, so that we could check weekly whether it was helping the newcomer, the team in which the newcomer was, and whether it was being effective.</p><p>Let me tell you, this went soooo well!</p><p>In the newcomer’s first days with the company, she did self-guided training. After a few weeks, she joined the internal apps team and they set up some more basic, other more complex tasks on our platform.</p><p>As this was a time she had dedicated to this, she had minor stress regarding their compromises. We made it clear that she wouldn’t be evaluated on her dev skills, this was a time to learn.</p><p>Once the program ended, it was amazing to see this newcomer, with a very deep knowledge of our product, also able to teach other colleagues without a tech background about what she’d learned.</p><p>She not only learned but was able to multiply her knowledge by helping others.</p><p>This also impacted our daily activities such as projects and feedback analysis, as she understood most of the context because she’d been through it.</p><p>After this program, a few things happened:</p><ul><li>The team’s eNPS was raised.</li><li>The team’s happiness increased.</li><li>The feedback from other teams regarding our knowledge of the product, improved.</li><li>The proximity with users increased, due to understanding their pains and ability to understand their feedback.</li></ul><p>I was so happy with the result, as this improved the vibe of the team and the quality of what we delivered. So now, we’re trying to expand and test on a larger scale.</p><h3>Conclusions:</h3><p>What I learned is that providing an immersive product experience to the UX team makes a huge difference in the quality of the product that is designed in the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_XkmnFdfqYjwGh7t" /><figcaption>A happy team of superheroes</figcaption></figure><p>If you are building a complex product, and facing a similar situation, an immersive program in your product might do the trick for you. In this case, the solution was to put the UXer learning how to develop in OutSystems, but in your case, it could be teaching your team to master medical equipment, finance software, or any other thing.</p><p>And never forget, happiness is what matters the most. If you’re doing all this, but the team isn’t happy, it’s not worth it. You’d better start finding another strategy that works for your team. In the end you want a happy team that is confident and knows the product they’re building well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=540561de915b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>