<?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 Simonluca Definis on Medium]]></title>
        <description><![CDATA[Stories by Simonluca Definis on Medium]]></description>
        <link>https://medium.com/@SLDefinis?source=rss-42deb78ec68a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pH1QAOJPHvuNGbQPMaw6vQ.jpeg</url>
            <title>Stories by Simonluca Definis on Medium</title>
            <link>https://medium.com/@SLDefinis?source=rss-42deb78ec68a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 21:35:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SLDefinis/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[Learning, teaching, and designing 
for experience outcomes]]></title>
            <link>https://medium.com/@SLDefinis/learning-teaching-and-designing-for-experience-outcomes-de1717fb25ed?source=rss-42deb78ec68a------2</link>
            <guid isPermaLink="false">https://medium.com/p/de1717fb25ed</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[ixdf]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Simonluca Definis]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 21:39:36 GMT</pubDate>
            <atom:updated>2026-01-24T21:32:18.451Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Learning, teaching, and designing <br>for experience outcomes</strong></h3><h4>The IxDF Experience</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vro1A5aDjilHKM7IkG9NQ.jpeg" /></figure><p>A junior designer in my team recently asked me two questions I hear more and more often:</p><p><strong>1. How can I present my design work more confidently to non-design stakeholders and get a buy-in?</strong></p><p><strong>2. How do I evolve into my next career step in a tough, uncertain, and rapidly transforming design market?</strong></p><p>Pretty much around the same time, I was asked how the<em> Interaction Design Foundation</em> (IxDF) has been relevant to my work.</p><p>Those two conversations clicked immediately, because they point to the same underlying challenge.</p><p>Design should not just be not just be evaluated at the screen level, but at the <strong>experience and outcome level</strong>. What is changing is not only <em>what</em> we design, but <em>how</em> we explain it, position it, ‘own it’and scale it inside organizations.</p><h3>Two short answers, one root problem</h3><p>Here are my short answers, upfront.</p><h4>1- On confidence</h4><p>Confidence comes from building a <strong>shared business vocabulary</strong> on top <br>of your design. I often practice short “stakeholder reps” where I frame problems starting with:</p><ul><li>Evidence</li><li>Business impact</li><li>Metrics</li><li>Risks or cost of delay</li><li>Downstream implications (teams, policies, data, handoffs)</li></ul><p>This translation slowly shifts your role from <strong>screen owner</strong> to <strong>outcome owner, </strong>and it will bring your conversation to a different level, closer to people outside of the design environment. It starts changing the culture around you, moving product teams toward being genuinely more <br>UX-driven.</p><h4>2- On career evolution</h4><p>Growth also happens when you start to think more holistically, considering the <strong>full orchestration</strong>:</p><ul><li>People</li><li>Policies</li><li>Handoffs</li><li>Data</li><li>Journey</li></ul><p>Leading with system-level artifacts, such as frameworks, experience models, or measurable journeys, helps decisions happen at the <strong>experience level</strong>, not the pixel level, in other words, what we used to call: <br>Service Design (is it just me or nobody is talking about it, while they still understand the value once they recognize the approach?)</p><p>Both answers point to the same root issue: designers often struggle not because they lack skill, but because they lack <strong>language, structure, and positioning</strong>.</p><h3>Why IxDF became relevant for me</h3><p>Five years ago, during Covid, I finally had the time to step back and reflect on my own practice. Like many others, I used that pause to question what <br>I had been doing instinctively and to explore other perspectives. <br>IxDF became part of that reflection.</p><p>I completed <a href="https://www.interaction-design.org/literature/topics/ux-management?srsltid=AfmBOopIOBBVyFNjNgd_smKKtzacMcdfseH8DzVSsRLHnAWmEGImCk2G"><strong>UX Management</strong></a> to strengthen how I frame decisions in product environments and speak the language of product development. <br>I followed <a href="https://www.interaction-design.org/literature/article/service-design-design-is-not-just-for-products"><strong>Advanced Service Design</strong></a> to expand my way of thinking more holistically and apply structured frameworks and team rituals when projects required stronger research or strategic direction upfront.</p><p>At the same time, I was mentoring entry-level designers and working on healthcare and banking projects. This created a demanding but powerful cycle of <strong>learning, teaching, and applying</strong>. But that cycle slowly improved my language, expanded my toolkit, and helped me build more credibility across people, policies, and platforms, not just within my design peers.</p><h3>Why this matters even more now</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Po3APBde0tBrFf2PrWz6QQ.png" /></figure><p>Looking at this with a more contemporary lens, the shift becomes even clearer. As AI moves interactions toward conversations, notifications, agents, and automation, the advantage no longer sits in interface polish alone. It belongs to designers who can understand and design <strong>system orchestration</strong>, including roles, policies, and data flows. This is where structured UX thinking stops being “nice to have” and becomes essential.</p><h4>1- Making UX discussable, scalable, and defensible</h4><p>I was fortunate to grow within two strong global design cultures: <a href="https://www.frog.co/">frog</a> <br>(part of Capgemini Invent) and Fjord (now <a href="https://www.accenture.com/ch-en/about/accenture-song-index">Accenture Song</a>). Both rely heavily on critique, shared rituals, and common tools, from workshops <br>to journey models. Those environments trained my intuition.<br>IxDF helped me add <strong>structure</strong> to that intuition.</p><p>One of the most valuable shifts was learning to see UX not as a set of activities, but as a <strong>capability that needs to be planned, scaled, and grown</strong>. Instead of jumping straight into methods, I started asking more foundational questions:</p><ul><li>What role do we expect UX to play in this product?</li><li>What problems is UX meant to solve for the team and the business?</li><li>Where does UX realistically sit today in terms of maturity?</li></ul><p>This reframing moves conversations away from <em>“Can you design this screen?”</em> Toward <em>“What kind of UX impact are we aiming for?”</em></p><p>That single shift changes the quality of decision-making.</p><figure><img alt="One of the deep-dive PDFs or blank framework canvases available as downloadable takeaways within the course lesson modules, in this case from the Advanced Service Design course." src="https://cdn-images-1.medium.com/max/1024/1*ptmE6V-3Lo-E8JSsi9Jqpg.png" /><figcaption><em>One of the deep-dive PDFs or blank framework canvases available as downloadable takeaways within the course lesson modules, in this case from the Advanced Service Design course.</em></figcaption></figure><h4>2- Choosing the right UX, not more UX</h4><p>Another key learning was understanding that UX maturity is not about using all the methods all the time, but about choosing the <strong>right ones</strong>. <br>Not every product needs full service design. Not every problem needs <br>a <a href="https://www.interaction-design.org/literature/topics/customer-journey-map?r=simonluca-definis">journey map</a>.</p><p>Real value comes from knowing when <a href="https://www.interaction-design.org/literature/topics/ux-research?r=simonluca-definis">research</a>, <a href="https://www.interaction-design.org/literature/topics/usability-testing?r=simonluca-definis">usability testing</a>, <a href="https://www.interaction-design.org/literature/topics/design-systems?r=simonluca-definis">design systems</a>, or UX management practices make sense, and when they do not.</p><p>IxDF also reinforced how powerful <strong>shared language and tangible artifacts</strong> are for scaling UX. Pattern libraries, scorecards, and simple maturity assessments give teams common reference points.</p><h4>3- Measurement, culture, and the work outside Figma</h4><p>Measurement was another important theme. <br>UX success is not only quantitative.<br>Balancing data with qualitative insight, understanding engagement, confidence, and emotional response, and translating outcomes into business terms are all signs of a more mature UX practice. <br>Small ROI examples or lightweight scorecards are often enough <br>to show where UX is today and where it can grow next.</p><p>Just as important, the courses made one thing very clear:<br><strong>UX maturity is as much cultural as it is methodological.</strong></p><p>Protecting the UX team, investing in training, bringing in outside perspectives, and continuously evangelizing UX are not “nice to have” activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wknoxRBn1RBaP1rVamwYOw.png" /><figcaption><em>A screenshot from one of the evaluated video lessons. Across the course, learning is supported <br>by a balanced mix of text, videos, and quizzes.</em></figcaption></figure><h3>Closing: a note to that colleague</h3><p>We are witnessing one of the fastest and most uncertain shifts in design roles. Across the industry, teams are redefining responsibilities, ownership, and the role design plays within organizations. As interfaces become easier to produce, focusing only on UI will not be enough for long. My advice is simple: try to invest in the space outside of it, while still owning design craft and expertise.</p><p>Listen carefully. Apply what you learn. Consciously expand your role beyond execution.</p><p>Self-education could be one of the most effective ways to accelerate this shift. For me, <a href="https://interaction-design.org/">IxDF</a> became a practical support in that process. <br>I saved quotes, frameworks, canvases, and key moments from the courses, building a personal reference library over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D-JPUiZ5Mk5CCi1MKwJJZw.jpeg" /><figcaption><em>A snapshot of my IxDF certificate dashboard showing the courses and master classes I’ve completed <br>so far.</em></figcaption></figure><p>That is where designers grow from screen makers into experience orchestrators, and where long-term relevance is built.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de1717fb25ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>