<?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 Alvaro Sanchez on Medium]]></title>
        <description><![CDATA[Stories by Alvaro Sanchez on Medium]]></description>
        <link>https://medium.com/@alvaroschz1?source=rss-18047fd9022a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*34838j7vzCd2JxJ1_-YMUw.jpeg</url>
            <title>Stories by Alvaro Sanchez on Medium</title>
            <link>https://medium.com/@alvaroschz1?source=rss-18047fd9022a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:23:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alvaroschz1/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[SAP Fiori as Your Design System Backbone]]></title>
            <link>https://medium.com/@alvaroschz1/sap-fiori-as-your-design-system-backbone-or-how-we-learned-to-stop-worrying-and-love-the-pattern-3baef4629a47?source=rss-18047fd9022a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3baef4629a47</guid>
            <dc:creator><![CDATA[Alvaro Sanchez]]></dc:creator>
            <pubDate>Sun, 23 Nov 2025 15:13:27 GMT</pubDate>
            <atom:updated>2025-11-23T15:15:29.445Z</atom:updated>
            <content:encoded><![CDATA[<h4>How We Learned to Stop Worrying and Start Loving the Pattern (If Someone’s Actually Watching It)</h4><p>Having worked extensively with internal application design systems, I’ve learned something valuable: having a design system doesn’t mean your organization has a design philosophy. And that’s the real tragedy — not the pixels, not the components, but the absent stewardship that lets beautiful systems become glorified component libraries nobody trusts.</p><p><strong>SAP Fiori, with its five core design principles (role-based, adaptive, simple, coherent, and delightful)</strong>, offers something genuinely useful for internal applications: a foundation that actually works. But here’s where the irony kicks in: <strong>a foundation is meaningless if no one’s maintaining the building</strong>. This article explores why adopting SAP Fiori as your design system’s core layer isn’t actually the hard part. The hard part is convincing your design system team that they’re not the gatekeepers of design; they’re the custodians of a vision.​</p><h3>Why Internal Applications Deserve Better</h3><p>Internal tools are used 6–8 hours a day by actual humans who deserve clarity and efficiency. Yet we design for resignation rather than delight, creating interfaces that feel assembled from scraps. When you design internal applications, you’re not just optimizing workflows; you’re shaping daily experiences that have direct monetary value. Mess this up, and you’re not failing aesthetically — you’re burning company money.​</p><p>The real problem: Design systems fail not in the creation phase — they fail in adoption. And adoption fails because somewhere between design files and production, there’s a vacuum. The design system team creates something. Product teams use it (or don’t). Nobody’s actually accountable for whether the vision survives.​</p><h3>What Makes SAP Fiori Actually Useful</h3><p>SAP Fiori isn’t revolutionary — it’s <em>competent</em>. For internal applications, competence might be the most underrated virtue.​</p><p>It offers predefined floorplans, modular UI components, and interaction patterns grounded in actual user research. More importantly, it separates concerns beautifully: role-based design patterns, responsive layouts, accessibility baked in, and <strong>visual consistency without reinventing the wheel seventeen times.​</strong></p><p>But here’s the problem: Most organizations adopt Fiori as a <em>constraint</em> rather than a <em>framework with intelligent exceptions</em>. They use the components because they’re supposed to, not because those components actually solve design problems. The irony?<strong> You choose a design system to avoid inconsistency, and then you create consistency that nobody values.​</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZkJkPBH1NAZeJPDIZFPug.png" /></figure><h3>The Missing Piece — Product Design Ownership</h3><p>A design system team’s job is not to ensure consistency. It’s to enable product teams to make coherent decisions.​</p><p>There’s a difference. When you optimize for consistency, you get handcuffs. When you optimize for enabling good decisions, you get flexibility within frameworks — which is what actually scales.​</p><p>Most organizations don’t have a person whose job is to own that tension. To own the vision of what internal applications should feel like and when to break the rules. Someone who lives in the space between “consistency” and “coherence.”​</p><p>What you need: a Product Design Owner. <strong>Someone from the Product Design team embedded in the design system process, but reporting to product leadership</strong>. Their job is specific: ensure that design system decisions actually serve product vision, not the other way around.​</p><p>This person asks:</p><ul><li>Does this pattern actually solve this user’s problem, or are we using it because it’s standard?</li><li>When should we break from SAP Fiori, and how do we do that coherently?</li><li>How do we use SAP Fiori as a foundation while building something that feels like <em>our</em> product?</li></ul><p>Without this role, you get design system teams that become Pattern Police, enforcing consistency through bureaucracy. You get product teams that resent the system because it feels like a constraint.​</p><h3>Building a Design System That Doesn’t Suck</h3><p>The design system team’s job is not to be gatekeepers. It’s to be advisors who can be challenged.​</p><p>When a product team needs something Fiori doesn’t provide, the answer shouldn’t be “Fiori provides this — use it.” The answer should be: “Let’s understand why you need this. Is this a genuine user need?”​</p><p>Clear governance without bureaucracy means:</p><ul><li>Clear decision-making processes for when something is a Fiori usage problem vs. a custom design problem</li><li>A product design representative responsible for vision, not just consistency</li><li>Permission for product teams to break rules <em>if they have good reasons</em></li><li>Documentation that serves product teams​</li></ul><p>Treat your Fiori implementation as a living system. Regular audits, feedback loops that feel safe, permission to retire patterns that aren’t working, and a roadmap that evolves based on actual product needs.​</p><h3>The Organizational Culture You Need</h3><p>Here’s where this becomes not a design problem but a leadership problem. You cannot have a Product Design Owner without someone in leadership who believes design <em>matters</em> to internal applications.​</p><p>What you need:</p><ul><li>A Product Design Owner with authority to make decisions</li><li>A Design System team that sees themselves as service providers, not enforcers</li><li>Clear organizational alignment that design system decisions enable product success</li><li>Safe communication channels for product teams to raise concerns​</li></ul><h3>Challenging Your Design System Team</h3><p>Ask these questions of your design system team:</p><ol><li>When we use SAP Fiori, are we using it because it solves the user problem, or because it’s standard?​</li><li>What happens when a product team needs something Fiori doesn’t provide? Is there a genuinely collaborative process?​</li><li>Who owns the vision of what our internal applications should feel like? This can’t be the design system team.​</li><li>Is our design system team empowered to say yes to exceptions when justified?​</li><li>How do you measure design system health — consistency metrics or product success metrics?​</li></ol><p>To design system teams: Your job is not to enforce consistency. Your job is to enable good decisions that <em>happen to be</em> consistent. That requires conversations instead of rules, collaboration instead of policing.​</p><p>To product teams: Challenge your design system. Ask why Fiori is the right pattern for your context. The design system that survives is the one that proves its value every single day.​</p><h3>Conclusion</h3><p>SAP Fiori is genuinely useful. It solves real problems: consistency, accessibility, role-based design, and interaction patterns grounded in research.​</p><p>But a foundation is only valuable if you build something on top that serves your users.</p><p>The real design system isn’t Fiori. It’s Fiori plus the decisions about when to use it, plus the exceptions, plus the vision, plus the person responsible for stewarding all of that.​</p><p>Here’s the sarcasm: We spend all this time perfecting design systems because it’s easier than perfecting the organizations that use them. Building a Figma library doesn’t require culture change. Establishing a Product Design Owner with real authority? That requires leadership to believe design matters.</p><p>Fiori gives you the mechanics. Your organization has to provide the vision.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3baef4629a47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Sin Glam]]></title>
            <link>https://medium.com/@alvaroschz1/ux-sin-glam-3ad355a2a203?source=rss-18047fd9022a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ad355a2a203</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Alvaro Sanchez]]></dc:creator>
            <pubDate>Sun, 31 Oct 2021 19:46:16 GMT</pubDate>
            <atom:updated>2025-01-22T14:13:42.651Z</atom:updated>
            <content:encoded><![CDATA[<p>SAP, Salesforce, Microsoft Dynamics, son algunos de los softwares lideres del sector productivo y necesitan el valor agregado de los diseñadores de UX durante su implementación, pero muchos diseñadores no están dispuestos a renunciar al <em>glamour</em> para realizar estos trabajos.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FFRsYCa9eYbxHG%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FFRsYCa9eYbxHG%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FFRsYCa9eYbxHG%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="200" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ac824b532dbe6f53da370b3c60895ed/href">https://medium.com/media/3ac824b532dbe6f53da370b3c60895ed/href</a></iframe><p>Los mayores proveedores de aplicaciones empresariales han publicado sus guías de estilo y sistemas de diseños (muy completos) que permiten a los proveedores <em>third-party </em>desarrollar y montar las aplicaciones empresariales.</p><p>Ante la falta de diseñadores para realizar estos trabajos, muchos proyectos terminan derivando el rol de UX a perfiles Front-End para montar estas aplicaciones. En muchos casos, esto termina afectado la navegación, la consistencia, la aplicación de las buenas prácticas de los sistemas de diseño, la falta de investigación, y los riesgos de que el producto se convierta en un Frankenstein.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FMQTBeMgUJciGs%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FMQTBeMgUJciGs%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FMQTBeMgUJciGs%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="321" frameborder="0" scrolling="no"><a href="https://medium.com/media/b208833b7b8f4cfa682d04058e2bf67b/href">https://medium.com/media/b208833b7b8f4cfa682d04058e2bf67b/href</a></iframe><p><strong>Hay lugar para el UX Research</strong></p><p>Muchas de las industrias (transporte, banca, farmacéuticas, etc.) que contratan los servicios de estas aplicaciones empresariales cierran contratos muy grandes y suelen tener capacidad para costear las investigaciones con usuarios.</p><p>No solo el presupuesto puede ser atractivo, también que estos clientes suelen tener trabajadores en distintas regiones o países lo cual hace a las investigaciones con usuarios más ricas, donde también se pueden realizar dinámicas remotas con perfiles de usuarios diversos.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F0IAPszdB8MMjPxNhFL%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F0IAPszdB8MMjPxNhFL%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExcTlyem80ZmFtbmg2M2tqZ3B5M3dweXNwaGFwdm5hc2NseDR3dTU3MCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F0IAPszdB8MMjPxNhFL%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/9206ea6f959394b6a8be7d49ff3e5a8a/href">https://medium.com/media/9206ea6f959394b6a8be7d49ff3e5a8a/href</a></iframe><p><strong>Efecto Wow</strong></p><p>Estas aplicaciones no están pensadas para producir un efecto Wow desde el look and feel, ni van a tener interacciones o un copywriting deslumbrantes.</p><p>Pero van a facilitarle a los trabajadores del sector productivo llevar las gestiones de su día a día de forma mas eficiente y a los managers los seguimientos de las actividades. En estás últimas, está el verdadero efecto wow que los desarrolladores de negocio están buscando.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fb8RfbQFaOs1rO10ren%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fb8RfbQFaOs1rO10ren%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fb8RfbQFaOs1rO10ren%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="362" frameborder="0" scrolling="no"><a href="https://medium.com/media/9b7a62783b9047009f522717e6c6a0c7/href">https://medium.com/media/9b7a62783b9047009f522717e6c6a0c7/href</a></iframe><p><strong>No todos los usuarios son millennials</strong></p><p>En proyectos de aplicaciones empresariales donde sobran las limitaciones para lucirse desde el punto de vista de la interfaz de usuario, es donde te enfrentas a desafíos en los cuales con pocos recursos tienes que mejorar la experiencia de usuario y hacer valer tu trabajo.</p><p>El diseño de UX no es patrimonio exclusivo de los usuarios de Uber, Airbnb o Duolingo, los trabajadores del sector productivo también merecen un buen UX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5t3gwpjC4ETCjcendzS2SA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ad355a2a203" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>