<?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 Alan Ortiz on Medium]]></title>
        <description><![CDATA[Stories by Alan Ortiz on Medium]]></description>
        <link>https://medium.com/@fabriciorecman?source=rss-97f3aacd606b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oL2o9rtIJNcy1_u9rrKP6w.png</url>
            <title>Stories by Alan Ortiz on Medium</title>
            <link>https://medium.com/@fabriciorecman?source=rss-97f3aacd606b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:53:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fabriciorecman/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[AI Is Not a Feature: It’s a Product Strategy]]></title>
            <link>https://fabriciorecman.medium.com/ai-is-not-a-feature-its-a-product-strategy-903afca9f5fd?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/903afca9f5fd</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 20:21:04 GMT</pubDate>
            <atom:updated>2026-06-10T20:21:04.970Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI Product Strategy: Why Every Product Team Needs to Rethink Its Playbook</h3><p>For years, digital products were built around a simple assumption:</p><p><strong>Users interact </strong>directly with <strong>software</strong>.</p><p>They click <em>buttons</em>.<br>Fill out <em>forms</em>.<br>Search for <em>information</em>.<br>Navigate<em> interfaces</em>.</p><p><strong>Product teams</strong> optimized these interactions through better design, stronger technology, and more refined <strong>business models</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EWAHqrVVF-rnreFUwnJp8A.png" /></figure><p>Then Artificial Intelligence arrived.</p><p>Not as another feature.</p><p>Not as another technology trend.</p><p>But as a fundamental shift in how products create value.</p><p>Today, the most important question facing product organizations is no longer:</p><p><em>“How can we add AI to our product?”</em></p><p>The real question is:</p><p><strong>“How does AI change the product itself?”</strong></p><p>Welcome to the era of AI Product Strategy.</p><h3>AI Is Not a Feature</h3><p>One of the biggest mistakes organizations make is treating AI as a feature.</p><p>A chatbot.</p><p>An assistant.</p><p>A recommendation engine.</p><p>A content generator.</p><p>While these capabilities can create<strong> value</strong>, they often fail to transform the product experience because they are layered onto an existing product strategy rather than becoming part of it.</p><p>Successful AI products are built differently.</p><p>AI becomes a <strong>core capability</strong> that influences:</p><ul><li>User <em>experience</em></li><li>Product <em>architecture</em></li><li>Business<em> models</em></li><li>Team <em>structures</em></li><li>Decision-making<em> processes</em></li></ul><p>In other words, AI is not something you add.</p><p>It becomes something you design around.</p><h3>The Shift From Workflows to Outcomes</h3><p>Traditional software focused on workflows.</p><p>The product provided tools.</p><p>Users performed the work.</p><p>AI changes this relationship.</p><p>Increasingly, users are less interested in performing tasks and more interested in achieving outcomes.</p><p>Consider the difference:</p><p>Traditional Product:</p><p>“Use our software to analyze customer feedback.”</p><p>AI Product:</p><p>“Tell us what you want to learn and we’ll provide the insights.”</p><p>The value no longer comes from <em>interaction</em>.</p><p>The value comes from <strong>results</strong>.</p><p>This shift has profound implications for Product Managers, Designers, and Developers alike.</p><h3>What Changes for Product Managers</h3><p>Historically, Product Managers focused on prioritization, roadmaps, and feature delivery.</p><p>AI introduces a new strategic layer.</p><p>Product Managers now need to think about:</p><ul><li><em>Data </em>availability</li><li><em>Model</em> capabilities</li><li><em>User</em> trust</li><li><em>Automation</em> boundaries</li><li><em>AI</em> governance</li></ul><p>Questions that were once technical suddenly become product decisions.</p><p>For example:</p><p>Should the AI act autonomously?</p><p>Should recommendations require user approval?</p><p>How transparent should the reasoning process be?</p><p>These choices directly influence adoption and business outcomes.</p><p>The Product Manager becomes the architect of human-AI collaboration.</p><h3>What Changes for Designers</h3><p>AI is transforming the role of design more dramatically than many realize.</p><p>For decades, designers optimized interactions.</p><p>Now they must<strong> design intelligence</strong>.</p><p>The challenge is no longer limited to creating beautiful interfaces.</p><p>Designers must define:</p><ul><li>Trust<em> mechanisms</em></li><li>Feedback <em>loops</em></li><li>Transparency <em>patterns</em></li><li>Agent <em>behaviors</em></li><li>Decision <em>visibility</em></li></ul><p>As AI takes over more operational tasks, designers spend less time arranging screens and more time shaping how intelligent systems behave.</p><p>The future of UX is not only visual.</p><p>It is <strong>behavioral</strong>.</p><h3>What Changes for Developers</h3><p>For developers, AI introduces both opportunity and complexity.</p><p>Modern products increasingly combine:</p><ul><li>Application<em> logic</em></li><li>Large Language <em>Models</em></li><li>Agent <em>frameworks</em></li><li>Retrieval<em> systems</em></li><li>External<em> APIs</em></li></ul><p>Building software is no longer only about creating functionality.</p><p>It is about orchestrating intelligence.</p><p>Developers are becoming system integrators, connecting models, tools, workflows, and business logic into cohesive product experiences.</p><p>The technical challenge is evolving from coding features to designing ecosystems.</p><h3>The New Competitive Advantage</h3><p>Historically, companies competed on:</p><ul><li>Features</li><li>Usability</li><li>Performance</li><li>Price</li></ul><p>AI introduces a new competitive dimension:</p><p><strong>Adaptability.</strong></p><p>The most successful products of the next decade may not be those with the most features.</p><p>They may be the products that learn fastest, adapt continuously, and help users achieve outcomes with minimal effort.</p><p>This creates an entirely new strategic landscape.</p><p>Organizations that understand this shift early will have a significant advantage.</p><h3>Building an AI Product Strategy</h3><p>Many companies begin their AI journey by asking:</p><p>“Where can we use AI?”</p><p>A better question is:</p><p>“Which user problems become fundamentally easier to solve because AI exists?”</p><p>Start by identifying:</p><h3>1. High-friction workflows</h3><p>Where are users spending time on repetitive or manual tasks?</p><h3>2. Decision-heavy experiences</h3><p>Where can AI assist with analysis, recommendations, or prioritization?</p><h3>3. Knowledge bottlenecks</h3><p>Where do users struggle to find, understand, or apply information?</p><h3>4. Automation opportunities</h3><p>Which tasks create little value when performed manually?</p><p>The goal is not to replace users.</p><p>The goal is to amplify their capabilities.</p><h3>The Rise of AI-Native Products</h3><p>Some organizations are adapting existing products.</p><p>Others are building entirely <strong>new categories</strong>.</p><p>These AI-native products are designed around intelligence from day one.</p><p>They assume:</p><ul><li>Continuous <em>learning</em></li><li>Natural language <em>interaction</em></li><li>Personalized <em>experiences</em></li><li>Agent-driven <em>workflows</em></li></ul><p>Just as mobile-first products reshaped digital experiences in the smartphone era, AI-native products are beginning to reshape the future of software.</p><h3>Final Thoughts</h3><p>Every major technology shift forces organizations to rethink how products create value.</p><p>The internet changed distribution.</p><p>Mobile changed accessibility.</p><p>Cloud computing changed scalability.</p><p>Artificial Intelligence is changing execution itself.</p><p>The organizations that succeed will not be the ones that simply add AI features.</p><p>They will be the ones that redesign their products, teams, and strategies around a new reality:</p><p>Users care less about using software.</p><p>They care more about achieving outcomes.</p><p>And increasingly, AI will become the bridge between the two.</p><p>The future of product strategy is not AI-enabled.</p><p>It is AI-native.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=903afca9f5fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI-Powered Design Systems: The Evolution from Component Libraries to Intelligent Product Ecosystems]]></title>
            <link>https://fabriciorecman.medium.com/ai-powered-design-systems-the-evolution-from-component-libraries-to-intelligent-product-ecosystems-6b1bba8353aa?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b1bba8353aa</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Sun, 07 Jun 2026 18:50:40 GMT</pubDate>
            <atom:updated>2026-06-07T18:50:40.308Z</atom:updated>
            <content:encoded><![CDATA[<p>For years, Design Systems have been positioned as a <strong>Single Source of Truth</strong>. A collection of <strong>components, patterns, principles,</strong> and <strong>guidelines</strong> designed to ensure <strong>consistency, scalability, </strong>and<strong> efficiency</strong> across digital products.</p><p>But something has <strong>changed</strong>.</p><p>As organizations grew, Design Systems faced increasing pressure. More <strong>products</strong>, more <strong>teams</strong>, more <strong>platforms</strong>, faster <strong>release cycles</strong>, and greater <strong>business complexity</strong> exposed the limitations of systems that relied heavily on manual maintenance and governance.</p><p>Artificial Intelligence is not simply another tool added to the designer’s toolkit. It represents an opportunity to transform Design Systems into <strong>intelligent ecosystems </strong>capable of<strong> learning</strong>, <strong>recommending</strong>, <strong>generating</strong>, and <strong>evolving</strong> alongside the products they support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gYzWPxXSkyutWSXwTWZ7lA.png" /></figure><p>The question is no longer whether AI can be integrated into a Design System.</p><p>The question is how long organizations can continue scaling without it.</p><h3>From Static Repositories to Adaptive Systems</h3><p>Traditionally, a Design System functions as a library.</p><p><strong>It contains:</strong></p><ul><li>Components</li><li>Design tokens</li><li>Interaction patterns</li><li>Accessibility standards</li><li>Guidelines</li><li>Documentation</li></ul><p>The challenge is that these assets require continuous human effort to remain aligned with evolving product realities.</p><p>An AI-powered Design System introduces a new layer:</p><p><strong>Intelligence.</strong></p><p>This means the<strong> system can</strong>:</p><ul><li>Detect visual inconsistencies.</li><li>Recommend reusable components.</li><li>Suggest accessibility improvements.</li><li>Generate documentation.</li><li>Identify duplicate patterns.</li><li>Audit implementations.</li><li>Create component variations automatically.</li></ul><p>Instead of serving as a passive repository, the Design System becomes an active participant in the product development process.</p><h3>What Changes for Designers</h3><p>For years, designers have spent a significant portion of their time on repetitive activities:</p><ul><li>Building variants</li><li>Naming components</li><li>Organizing libraries</li><li>Creating documentation</li><li>Reviewing consistency</li></ul><p>AI has the potential to<strong> automate </strong>much of this operational work.</p><p>As a result, designers can shift their focus from interface production to <strong>system architecture</strong> and <strong>strategic problem-solvin.</strong></p><p>Imagine a team creating a new onboarding experience.</p><p>Traditionally, the process would involve:</p><ul><li>Research</li><li>Wireframes</li><li>Component selection</li><li>Flow creation</li><li>Documentation</li></ul><p>With an AI-enabled Design System, teams could receive recommendations for:</p><ul><li>Existing patterns</li><li>Relevant components</li><li>Required states</li><li>Edge cases</li><li>Accessibility considerations</li></ul><p>The outcome is faster execution and stronger consistency across experiences.</p><h3>What Changes for Product Managers</h3><p>Product Managers constantly balance two competing priorities:</p><p><strong>Speed and consistency.</strong></p><p>Business stakeholders want rapid delivery.</p><p>Product teams need quality, maintainability, and scalability.</p><p>AI-powered Design Systems help reduce this tension.</p><p>They can:</p><ul><li>Identify reusable assets.</li><li>Estimate the impact of proposed changes.</li><li>Detect duplication across products.</li><li>Recommend established design patterns.</li></ul><p>This creates faster decision-making while reducing design debt and improving product coherence.</p><p>Instead of relying solely on tribal knowledge distributed across teams, Product Managers gain access to institutional knowledge embedded within the system itself.</p><h3>What Changes for Developers</h3><p>One of the most persistent challenges in product development is the gap between design and code.</p><p>Design evolves.</p><p>Code evolves.</p><p>But they rarely evolve at the same pace.</p><p>AI can help bridge this gap.</p><p>Examples include:</p><ul><li>Generating technical documentation from components.</li><li>Detecting discrepancies between design files and production code.</li><li>Recommending implementation approaches.</li><li>Auditing accessibility compliance.</li><li>Identifying technical and visual debt.</li></ul><p>Rather than manually reviewing hundreds of components, teams can leverage AI to continuously monitor system health and consistency.</p><h3>Real-World Market Examples</h3><h3>Figma AI</h3><p><a href="https://www.figma.com/?utm_source=chatgpt.com">Figma</a> has introduced AI-powered capabilities that help teams generate interfaces, create content, and accelerate prototyping workflows.</p><p>While AI does not replace design thinking, it significantly reduces time spent on repetitive tasks.</p><h3>GitHub Copilot</h3><p><a href="https://github.com/features/copilot?utm_source=chatgpt.com">GitHub Copilot</a> assists developers by generating code aligned with existing patterns and standards.</p><p>For organizations with mature Design Systems, it helps accelerate implementation while maintaining consistency.</p><h3>Storybook</h3><p><a href="https://storybook.js.org/?utm_source=chatgpt.com">Storybook</a> is increasingly being used as a foundation for AI-assisted documentation, component governance, and system-wide audits.</p><h3>IBM Carbon Design System</h3><p><a href="https://carbondesignsystem.com/">IBM Carbon Design System</a> demonstrates how governance, scalability, and consistency can be maintained across large organizations.</p><p>Many enterprises are exploring AI layers on top of systems like Carbon to automate documentation and compliance reviews.</p><h3>Salesforce Lightning Design System</h3><p><a href="https://www.lightningdesignsystem.com/2e1ef8501">Salesforce Lightning Design System</a> showcases how a design language can scale globally across thousands of developers and product teams.</p><p>AI introduces an additional layer of intelligence through recommendations, audits, and pattern discovery.</p><h3>Five Capabilities That Will Define the Future of Design Systems</h3><h3>1. Automated Component Generation</h3><p>Components created from prompts, requirements, or existing patterns.</p><h3>2. Continuous Auditing</h3><p>Real-time detection of inconsistencies in both design and code.</p><h3>3. Living Documentation</h3><p>Documentation generated and updated automatically as systems evolve.</p><h3>4. AI-Assisted Accessibility</h3><p>Continuous validation against accessibility standards and best practices.</p><h3>5. Context-Aware Recommendations</h3><p>Suggestions based on historical usage, product context, and organizational standards</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b1bba8353aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IA en el Day-to-Day del Product Design (2026)]]></title>
            <link>https://fabriciorecman.medium.com/ia-en-el-day-to-day-del-product-design-2026-425fcf28adf9?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/425fcf28adf9</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 21:55:17 GMT</pubDate>
            <atom:updated>2026-03-04T21:55:17.028Z</atom:updated>
            <content:encoded><![CDATA[<p>La Inteligencia Artificial ya no es una tendencia futurista: es una pieza central del proceso de diseño de productos modernos. Desde <strong>ideación</strong> y <strong>prototipado</strong> hasta <strong>testing</strong>, <strong>product management</strong> y <strong>generación de código</strong>, la IA acelera flujos de trabajo, reduce tareas repetitivas y amplifica la creatividad humana.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5-_imr0H6U72rs-mPW2Xkg.png" /></figure><p>Para diseñadores, <em>managers</em> y desarrolladores, entender no solo <strong>qué hace cada herramienta</strong> sino <strong>cómo integrarla inteligentemente en el proceso</strong> es una ventaja competitiva clave.</p><h4>¿Qué significado tiene IA en Product Design?</h4><p>La IA en Product Design se refiere al uso de modelos de Machine Learning y grandes modelos de lenguaje (LLMs) para:</p><ul><li><strong>Automatizar tareas repetitivas</strong></li><li><strong>Generar ideas y variantes visuales</strong></li><li><strong>Traducir lenguaje natural a prototipos o código</strong></li><li><strong>Extraer insights de investigación cualitativa y cuantitativa</strong></li><li><strong>Apoyar decisiones estratégicas del producto</strong></li></ul><p>No reemplaza al diseñador: <strong>potencia tu creatividad y análisis</strong>.</p><h4>Herramientas AI para Diseño y Prototipado (UX/UI)</h4><p>Las siguientes herramientas están disponibles hoy y son valiosas para diseñadores:</p><h4>Figma + Figma Make</h4><ul><li>Asistente dentro de tu herramienta de diseño principal.</li><li>Genera layouts, renombra componentes, sugiere contenido y mejora prototipos.</li><li>Con el servidor MCP, algunas herramientas AI pueden extraer información estructurada de tus diseños para generar código más preciso.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aKDW5XAi2ZYQgTgCgLfrUA.png" /></figure><p><strong>Cómo usar:</strong> escribe prompts dentro de Figma para generar elementos de UI o haz <em>prompt-to-code</em> para componentes funcionales.</p><h4><strong>Subframe</strong></h4><ul><li>Permite diseñar usando <strong>React + Tailwind reales</strong>, con edición visual que genera código directamente.</li><li>El AI copilot aprende tu estilo y acelera iteración.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/1*ghxzUFMHNWtyvsDJtY2rYw.png" /></figure><p><strong>Uso práctico:</strong> Ideal para diseñadores que quieren acercarse a código sin perder precisión ni control.</p><h4>Uizard</h4><ul><li>Transforma <strong>bocetos y texto</strong> en pantallas editables.</li><li>Acelera la ideación temprana de UX.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*qnrdBAjsf5EKxzOKyJ1-_A.png" /></figure><p><strong>Uso práctico:</strong> En workshops de diseño para pasar de papel a prototipo digital al instante.</p><h4>Herramientas de <em>Management</em> y Product Thinking impulsadas por IA</h4><p>Integrar IA en <em>product management</em> permite aliviar carga administrativa, generar <strong>roadmaps</strong>, y extraer insights de investigación o métricas.</p><h4>Claude (para Product Thinking)</h4><ul><li>Genera <strong>user stories</strong>, descripciones de funcionalidades, resúmenes de feedback de usuarios, y más.</li><li>Ayuda a organizar ideas nebulosas en artefactos accionables</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*4qbndGswjKPZnV68I6_zyg.png" /></figure><p><strong>Uso cotidiano:</strong> resumir sesiones de diseño, crear listas de tareas y clarificar objetivos de producto.</p><h4>Perplexity / Abacus / otros asistentes de investigación</h4><ul><li>Extraen información de grandes volúmenes de texto (papers, entrevistas, métricas) en segundos.</li><li>Transforman grandes corpus en <strong>insights accionables</strong> sin leer todo manualmente.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*liLEhSeI7W52joCM4OOIRA.png" /></figure><p><strong>Uso práctico:</strong> desde análisis competitivo hasta resúmenes de entrevistas a usuarios.</p><h4>Herramientas de Código y Desarrollo</h4><p>La IA también está transformando el lado técnico del diseño de productos, conectando diseño con implementación.</p><h4>GitHub Copilot</h4><ul><li>Autocompleta código, sugiere fragmentos con prompts naturales y acelera la escritura de funciones.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsyeLoGveQfl8WgzfuX1lw.png" /></figure><p><strong>Uso práctico:</strong> escribir prototipos funcionales rápidamente o iterar sobre lógica compleja</p><h4>Claude Code</h4><ul><li>Agente de codificación de Anthropic que genera y corrige código a partir de prompts.</li><li>Disponible ahora en formato web y CLI.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrwDPAvYyD5srvyGvA7qWg.jpeg" /></figure><p><strong>Uso cotidiano:</strong> crear scripts utilitarios, funciones para prototipos o apps internas sin escribir cada línea.</p><h4>Google Antigravity</h4><ul><li>IDE impulsado por agentes IA autónomos que pueden escribir código con mayor independencia.</li><li>Soporta tareas asincrónicas como escribir, probar y documentar sin intervención humana directa.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*r4-qr89SxDYV9Fq5idvoQw.png" /></figure><p><strong>Uso práctico:</strong> gran ayuda para equipos que desean automatizar partes del ciclo de desarrollo.</p><h4>Integración de IA en Investigaciones UX y Datos</h4><p>Además de herramientas de diseño y código, la IA está transformando <strong>investigación cualitativa y cuantitativa</strong>:</p><ul><li><strong>Minería de datos de usuarios</strong> para detectar patrones de uso.</li><li><strong>Análisis de entrevistas</strong> y síntesis de insights cualitativos.</li><li><strong>Generación de hipótesis experimentales</strong>.</li><li><strong>Modelos de simulación de usuario</strong> en flujos complejos.</li></ul><p>Estas funciones se están integrando tanto en plataformas de <em>analytics</em> como en asistentes de lenguaje natural.</p><h4>Buenas Prácticas al Usar IA</h4><p><strong>Define claramente tus prompts:</strong> cuanto más preciso seas, mejores resultados obtendrás.</p><ul><li><strong>Usa IA como co-creador, no reemplazo:</strong> sigue validando con usuarios reales.</li><li><strong>Itera constantemente:</strong> la IA acelera ciclos, ¡aprovéchalos!</li><li><strong>Comprende las limitaciones:</strong> no todo resultado generado será óptimo — requiere sentido crítico.</li></ul><h4>La IA ya está integrada en múltiples fases del Product Design</h4><ul><li><strong>Diseño visual y prototipado</strong></li><li><strong>Gestión de producto y planificación estratégica</strong></li><li><strong>Investigación y análisis de datos</strong></li><li><strong>Desarrollo de código y prototipos funcionales</strong></li></ul><p>Esta convergencia permite a los equipos <strong>enfocarse en resolver problemas reales</strong> con rapidez, creatividad y calidad. La IA no reemplaza al talento humano: <strong>lo amplifica</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=425fcf28adf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dopamine Loops and Ethical UX in Notifications]]></title>
            <link>https://fabriciorecman.medium.com/dopamine-loops-and-ethical-ux-in-notifications-a3166320a0c1?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3166320a0c1</guid>
            <category><![CDATA[neuroscience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 18:17:53 GMT</pubDate>
            <atom:updated>2025-07-21T18:18:30.665Z</atom:updated>
            <content:encoded><![CDATA[<p>How your app might be hijacking attention — and what to do about it.</p><h4>“Just one more look…”</h4><p>A red dot flashes on your phone.<br> You tap.<br> It’s a like. Or a ping. Or someone typing.<br> Before you know it, you’ve lost 15 minutes.</p><p>This is no accident.<br> It’s a <strong>dopamine loop</strong> — and many digital products are designed to trigger it.</p><p>But as creators, <strong>we must ask</strong>:<br> How much engagement is too much?<br> When does persuasive UX become manipulation?<br> And how can we design notifications that <strong>respect the user’s mind</strong>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6UVOAqISaSnswtOtlo9peQ.png" /></figure><h3>What Is a Dopamine Loop?</h3><p>A <strong>dopamine loop</strong> is a neurobiological cycle that drives behavior through <strong>anticipation and reward</strong>.</p><ul><li><strong>Dopamine</strong>, a neurotransmitter, spikes <em>not</em> when we receive a reward, but when we <strong>expect</strong> one.</li><li>This expectation creates a feedback loop:</li><li>cue → action → reward → craving → repeat</li></ul><p>Digital systems exploit this:</p><ul><li>Red notification badges (cue)</li><li>Click to open (action)</li><li>Social validation, content, or novelty (reward)</li><li>Unpredictable outcomes (craving reinforcement)</li></ul><p>This loop <strong>mimics the psychology of slot machines</strong> — and it’s incredibly powerful.</p><h3>UX Patterns That Amplify Dopamine Loops</h3><h4>1. Red Badges &amp; Attention Grabs</h4><p>The color red is neurologically linked to urgency and alerts. Overused, it generates <strong>constant craving and micro-stress</strong>.</p><h4>2. Variable Rewards</h4><p>We don’t know what we’ll get — a comment? A match? A deal?<br> This <em>uncertainty</em> makes the reward stronger and the behavior stickier.</p><h4>3. Frequent Push Notifications</h4><p>Even when irrelevant, push notifications tap into fear of missing out (FOMO), creating <strong>compulsive checking</strong>.</p><h4>4. Infinite Scroll or Refresh Loops</h4><p>Like pulling a slot handle, swipe-to-refresh mimics gambling dynamics.</p><blockquote><em>“Maybe </em>this<em> time I’ll see something interesting.”</em></blockquote><h3>Why It Works (and Why It’s Risky)</h3><p>This design psychology is <strong>not inherently bad</strong>.<br> It can be useful in:</p><ul><li>Learning apps (Duolingo)</li><li>Mental health check-ins (Woebot)</li><li>Behavior change nudges (Habitica)</li></ul><p>But when used <em>purely to increase screen time or data generation</em>, it becomes:</p><ul><li>Distracting</li><li>Addictive</li><li>Emotionally exhausting</li></ul><blockquote><em>The user becomes the product.<br> And we become complicit.</em></blockquote><h3>The Ethical UX Mindset</h3><p>Here’s how ethical teams can balance engagement with respect:</p><h4>1. Design for Value, Not Addiction</h4><p>Ask: Does this notification help the user achieve their goal — or yours?</p><h4>2. Let Users Set the Tempo</h4><p>Allow custom notification preferences. Respect time zones, working hours, and mental space.</p><h4>3. Replace FOMO with Intentionality</h4><p>Use copy and visuals that encourage <em>purposeful re-engagement</em>, not urgency or fear.</p><h4>4. Make Rewards Transparent</h4><p>If gamification or progress mechanics are used, make the logic visible. Avoid “dark patterns” that confuse or withhold.</p><h4>5. Use Behavioral Data Responsibly</h4><p>Track not just clicks, but <strong>frustration</strong>, <strong>fatigue</strong>, and <strong>uninstalls</strong>. These are signals that attention is being abused.</p><h3>What This Means for Teams</h3><h4>Designers</h4><p>Map user emotions alongside user journeys. Use Fogg’s Behavior Model ethically: increase motivation, reduce friction — but don’t bypass consent.</p><h4>Developers</h4><p>Implement logic that avoids unnecessary polling, repetition, or noisy triggers. Partner with UX to build sustainable feedback systems.</p><h4>Product Managers</h4><p>Rethink KPIs: is more time in-app always better? Include qualitative signals of trust, clarity, and mental load in success metrics.</p><h4>HR &amp; Culture Leaders</h4><p>Audit internal communication tools. Slack, Teams, and productivity platforms can also drain attention if poorly configured.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3166320a0c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NeuroUX: Designing for the Mind, Not Just the Mouse]]></title>
            <link>https://fabriciorecman.medium.com/neuroux-designing-for-the-mind-not-just-the-mouse-871f3862cd85?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/871f3862cd85</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[neuroscience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[neuro-ux]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Fri, 11 Jul 2025 14:47:41 GMT</pubDate>
            <atom:updated>2025-07-11T14:47:41.638Z</atom:updated>
            <content:encoded><![CDATA[<p>Why user experience now demands a deeper understanding of the human brain.</p><h3>The Invisible Problem</h3><p>We interact with dozens of digital systems every day.<br> We <em>click, scroll, tap, decide, and forget</em> — often without realizing the <strong>mental toll</strong> it takes.</p><p>Most interfaces are built to be usable.<br> Few are designed to be <strong>mentally sustainable</strong>.</p><p>This is where <strong>NeuroUX</strong> enters the picture:<br> A new layer in the user experience stack that combines design, cognitive science, and neuroscience to create more humane digital products.</p><h3>What Is NeuroUX?</h3><p><strong>NeuroUX</strong> (Neuro-User Experience) is a multidisciplinary approach that aligns <strong>UX design with how the brain processes information, emotions, and decisions.</strong></p><p>It’s not just about delight or usability — it’s about:</p><ul><li>Reducing <strong>cognitive overload</strong></li><li>Enhancing <strong>emotional clarity</strong></li><li>Supporting <strong>mental models</strong></li><li>Designing for <strong>neurodiversity</strong></li><li>Promoting <strong>healthy interaction patterns</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_4qsWfy4168mL8AjAe0PA.png" /></figure><h3>The Technical Bridge: Design Meets Neuroscience</h3><p>NeuroUX draws on foundational concepts from <strong>cognitive psychology, behavioral science, and neurology</strong>, including:</p><h4>1. Cognitive Load Theory</h4><ul><li>Humans have limited working memory (typically 4±1 items).</li><li>Excessive choices, long forms, or poorly grouped content create mental fatigue.</li><li><strong>Design response:</strong> Chunk information, reduce steps, and create visual hierarchy to support memory.</li></ul><h4>2. Dual-Process Theory (Kahneman)</h4><ul><li>We use two systems to think:</li><li>System 1: fast, intuitive, automatic</li><li>System 2: slow, deliberate, effortful</li><li>Interfaces that trigger System 2 too often cause user drop-off.</li><li><strong>Design response:</strong> Use familiar patterns to activate System 1 unless reflection is needed (e.g., safety-critical tasks).</li></ul><h4>3. Attention &amp; Executive Control</h4><ul><li>Attention is a finite resource governed by the <strong>prefrontal cortex</strong>.</li><li>Interruptions, animations, or decision fatigue lead to task abandonment.</li><li><strong>Design response:</strong> Avoid unnecessary distractions and respect attention windows (especially in productivity tools).</li></ul><h4>4. Emotional Regulation</h4><ul><li>Interfaces affect our mood through <strong>color, pace, feedback, and tone</strong>.</li><li>Apps that provoke anxiety (e.g., finance or health) must include calming, clear cues.</li><li><strong>Design response:</strong> Use emotional design (per Don Norman) to create affective experiences that align with user context.</li></ul><h4>5. Predictive Processing &amp; Mental Models</h4><ul><li>The brain constantly predicts what comes next.</li><li>When systems break expectations (e.g., hidden menus or unclear flows), the brain must recalibrate.</li><li><strong>Design response:</strong> Respect mental models, use affordances, and ensure feedback matches user actions.</li></ul><h4>6. Neurodiversity Awareness</h4><ul><li>People process information differently (e.g., ADHD, autism spectrum, dyslexia).</li><li>One-size-fits-all design unintentionally excludes.</li><li><strong>Design response:</strong> Create adaptable, inclusive systems that embrace flexibility in interaction.</li></ul><h3>Why It Matters</h3><p>In 2025, <strong>attention is more valuable than clicks</strong>.<br> Designing without considering cognitive and emotional impact is a liability.</p><ul><li>Products that don’t match the way users think and feel → fail silently.</li><li>Teams that overlook mental sustainability → burn out their users and themselves.</li><li>Companies that ignore neurological diversity → leave potential and inclusivity on the table.</li></ul><blockquote><em>NeuroUX is not a trend. It’s the next layer of design maturity — the one that respects the brain behind the behavior.</em></blockquote><h4>What It Means for Your Team</h4><p><strong>Designers</strong> move beyond wireframes to shape <strong>mental journeys</strong>. They reduce overload, design for emotion, and map user intent with empathy.</p><p><strong>Developers</strong> understand how front-end decisions impact mental load. They apply accessibility, optimize performance, and simplify logic.</p><p><strong>Product Managers</strong> validate not just <em>what</em> works, but <em>how the brain interprets</em> what works. They track comprehension and emotional response, not just engagement.</p><p><strong>People Teams</strong> champion digital well-being by choosing internal tools that support attention, focus, and mental health — making NeuroUX a part of the company’s culture, not just its products.</p><p>The UX field is evolving. It’s not just about making things easier — it’s about making them <strong>mentally healthier</strong>.</p><p>NeuroUX invites us to <strong>design like neuroscientists</strong> and <strong>think like humans</strong>.<br> It’s about creating systems that the brain <em>wants</em> to use — not just ones it <em>can</em> use.</p><p>Because in the end, we’re not designing for screens.<br> We’re designing for <strong>minds</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=871f3862cd85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technology, Multimedia and Metacognition: A New Paradigm in Individual Metacognitive Training…]]></title>
            <link>https://fabriciorecman.medium.com/technology-multimedia-and-metacognition-a-new-paradigm-in-individual-metacognitive-training-709014ea1ad3?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/709014ea1ad3</guid>
            <category><![CDATA[metacognition]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[multimedia]]></category>
            <category><![CDATA[bias]]></category>
            <category><![CDATA[science]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Thu, 26 Jun 2025 18:32:03 GMT</pubDate>
            <atom:updated>2025-06-26T18:32:03.818Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Technology, Multimedia and Metacognition: A New Paradigm in Individual Metacognitive Training (MCT+) for Mental Health</strong></h3><p>This paper explores the convergence between Individual Metacognitive Training (EMC+), cognitive sciences, and multimedia arts. Focusing on patients with psychosis and schizophrenia, we propose the use of technological tools such as audiovisual media, virtual reality (VR), and mobile applications for the creation of innovative therapeutic resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lD-QcdG1aebI727yasxf9Q.png" /></figure><p>The work begins with a theoretical foundation on common cognitive biases, explores their clinical and everyday manifestations, and proposes an implementation model that merges technology, theory, and art as a strategy for psychoeducational intervention.</p><p><strong>Introduction</strong></p><p>Metacognition, understood as “thinking about thinking,” has gained a central role in third-generation cognitive therapies. Individual Metacognitive Training (EMC+), developed by Dr. Steffen Moritz, has shown clinical efficacy in patients with treatment-resistant schizophrenia and persistent psychotic disorders, particularly in reducing cognitive biases that perpetuate delusions, hallucinations, and disorganized thinking.</p><p>This work arises from the articulation between this methodology and the international project “The Density of Meaning.” In collaboration with the Dom Pomocy Społecznej institute (Poland), we propose a hybridization of science, technology, and art as a path for therapeutic intervention and social inclusion.</p><p><strong>1. EMC+, Psychosis and Schizophrenia: In-Depth Bias Treatment</strong></p><p>EMC+ addresses cognitive distortions systematically identified in individuals experiencing psychosis and schizophrenia. These distortions, known as cognitive biases, affect interpretation, judgment, memory, and emotional regulation. Below are the key biases targeted by EMC+, with their clinical relevance:</p><ul><li><strong>Jumping to Conclusions (JTC):</strong> Making hasty decisions based on insufficient evidence. Common in delusional interpretations, especially under paranoia.</li><li><strong>Overconfidence Bias:</strong> Excessive confidence in one’s beliefs or memories, even when evidence contradicts them. In psychosis, this can reinforce fixed false beliefs.</li><li><strong>Bias Against Disconfirmatory Evidence (BADE):</strong> A tendency to ignore or reframe information that contradicts preexisting beliefs. This bias prevents correction of delusional thinking.</li><li><strong>Attributional Biases:</strong> These include personalizing (believing events are directed at oneself) and hostile attribution (assuming others have negative intent), which fuel persecutory delusions.</li><li><strong>Theory of Mind (ToM) Deficits:</strong> Difficulty in inferring others’ emotions or intentions, which undermines social functioning and increases misunderstanding and social withdrawal.</li><li><strong>Cognitive Rigidity:</strong> Inability to adapt one’s thinking in response to new information. Leads to perseverative errors and poor problem-solving.</li><li><strong>Memory Bias:</strong> Distorted recall that selectively favors evidence supporting dysfunctional beliefs or delusions.</li><li><strong>Internalized Stigma and Low Self-Esteem:</strong> Negative self-concepts that reinforce social withdrawal and reduce motivation for recovery.</li></ul><p><strong>These biases are present not only in chronic schizophrenia but also in early-phase psychosis and prodromal states. EMC+ has been shown to help patients reinterpret their thought processes, increasing cognitive flexibility and metacognitive insight.</strong></p><p><strong>Dr. Ryszard Spychalski, director of Dom Pomocy Społecznej, notes:</strong> <em>“Metacognition is not merely a clinical technique, but a pedagogy of awareness. EMC+ empowers patients not by telling them what to think, but by helping them discover how they think — and how to think differently.”</em></p><p><strong>2. EMC+ in Practice: Structure, Sessions and Techniques</strong></p><p>EMC+ is delivered in structured individual sessions. Each session integrates playful logic-based tasks, reflective questioning, and interactive feedback. The therapist facilitates exercises that reveal specific biases, allowing patients to reflect on the emotional and functional impact of their cognitive distortions.</p><p>The sessions follow a modular format and are adapted based on patient profile:</p><ul><li>Early psychosis: brief and flexible modules to encourage insight.</li><li>Chronic schizophrenia: gradual exposure to metacognitive challenges with repetition.</li><li>Low insight or delusional conviction: indirect bias exposure using neutral analogies.</li></ul><p>The structure typically includes:</p><ul><li><strong>Introduction task:</strong> (e.g., optical illusions, paradoxes).</li><li><strong>Bias exploration:</strong> using metaphors or real-life examples.</li><li><strong>Application:</strong> relating to the patient’s lived experience.</li><li><strong>Reflection:</strong> questioning certainty, generating alternatives.</li></ul><p>The tone is collaborative and non-confrontational, and humor is often used to lower defensiveness.</p><p><strong>3. Multimedia Perspective of EMC+: Integrating Technology in Metacognitive Treatment</strong></p><p>The use of multimedia technologies in EMC+ represents a promising evolution in the field of cognitive psychotherapy. According to recent studies by Dr. Steffen Moritz and his team at the University of Hamburg, digital interventions can enhance the therapeutic outcomes of metacognitive training by facilitating access, personalization, and continuity between in-person sessions.</p><p>In particular, Moritz has explored the use of:</p><ul><li><strong>Self-help digital modules</strong> based on EMC+ for individuals with subclinical symptoms, such as “MCT &amp; More,” a free platform offering interactive and psychoeducational exercises.</li><li><strong>Audiovisual material</strong> designed with a clinical-pedagogical approach that simulates dilemmas, biases, and common errors in reality interpretation.</li><li><strong>Mobile applications</strong> like “COGITO” and “MyMCT,” developed to extend therapeutic work beyond the session through notifications, self-monitoring tools, and brief metacognitive exercises.</li></ul><p>The multimedia approach is grounded in studies showing that interactive content increases adherence, reduces treatment resistance, and promotes a more empathic understanding of biases. By integrating fiction, gamification, and simulation, these tools connect with different learning styles and allow work on both rational and emotional levels.</p><p>Moritz emphasizes: <em>“Digital resources do not replace clinical intervention, but they amplify its reach. They can be a bridge between suffering and understanding, between individual experience and scientific evidence.”</em></p><p>The multimedia vision of EMC+, supported by evidence from the Hamburg group, opens a new paradigm where the therapeutic experience becomes accessible, aesthetic, and deeply human.</p><p><strong>4. Conclusion and Future Perspectives</strong></p><p>The integration of multimedia tools into EMC+ enables the design of dynamic, engaging, and personalized interventions. These tools allow patients to visualize, simulate, and critically engage with their thought processes. As technology continues to evolve, so too does the potential for scalable, culturally adapted metacognitive training.</p><p>Platforms combining VR, apps, fiction, and documentary evidence foster new learning environments. These environments are not merely supplements to therapy but stand as mediators between clinical knowledge and personal insight. The challenge ahead lies in ensuring equitable access, validating content across populations, and preserving the therapeutic alliance in digitally enriched contexts.</p><p>Multimedia EMC+ is not a replacement for therapy — it is a powerful extension. Its promise is not only clinical efficacy but also the possibility of transforming how individuals relate to their own minds, their communities, and their healing journeys.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=709014ea1ad3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Totems, Blueprints, and Touchpoints: What Service Design Is and Why It Matters]]></title>
            <link>https://fabriciorecman.medium.com/totems-blueprints-and-touchpoints-what-service-design-is-and-why-it-matters-72664b5773ce?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/72664b5773ce</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[solutions]]></category>
            <category><![CDATA[methodology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[blueprint]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 15:18:31 GMT</pubDate>
            <atom:updated>2025-06-25T15:18:31.024Z</atom:updated>
            <content:encoded><![CDATA[<p>In the world of modern product and digital development, there’s a silent architect behind the curtain — shaping not just screens and code, but <strong>experiences, ecosystems, and interactions</strong>. That architect is <strong>Service Design</strong>.</p><p>You might’ve heard the term thrown around in workshops, design sprints, or strategic meetings, but what does it actually mean? And why is it essential for startups, tech companies, and mature organizations alike?</p><p>Let’s begin with a metaphor:</p><blockquote><strong><em>“The big guy of functional infrastructures who conserves users and customers navigating by touchpoints.”</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KxfKAs_Y-lsUL23PBaZZ4A.png" /></figure><p>That’s Service Design in a nutshell.</p><h3>Have You Ever Heard About Totems?</h3><p>Think of the last time you visited a government office, a museum, or even a well-designed bank branch. You probably saw <strong>digital totems</strong> — those sleek, touchscreen kiosks that guide you, help you check in, or navigate a space.</p><p>They’re not just interface devices. They’re <strong>nodes in a bigger service ecosystem</strong>.</p><p>Behind that physical interaction is a series of carefully orchestrated actions: people, processes, systems, and technologies working in sync to deliver a seamless experience. <strong>This orchestration is what Service Design maps, plans, and optimizes.</strong></p><h3>What Is Service Design?</h3><p><strong>Service Design</strong> is the practice of designing <strong>end-to-end experiences</strong> across all touchpoints, channels, and moments in a customer’s journey. It looks beyond the interface and thinks <strong>holistically</strong> — blending UX, business strategy, operations, and customer expectations into a coherent service.</p><p>It asks:</p><ul><li>How does a customer first discover our service?</li><li>What happens when they need help?</li><li>Where do delays, pain points, or confusion occur?</li><li>How do back-end systems and front-end interfaces connect?</li><li>Are the staff, tools, and data aligned to deliver what we promise?</li></ul><h3>Blueprints &amp; Journeys: The Backbone</h3><blockquote><em>“Blueprints and customer journeys are the base to build any of these integral scenarios and experiences.”</em></blockquote><p>If you’re a <strong>designer or developer</strong>, think of a <strong>Service Blueprint</strong> as the master plan behind a product roadmap. It includes:</p><ul><li><strong>Frontstage</strong> interactions (what the customer sees)</li><li><strong>Backstage</strong> operations (what the team does behind the scenes)</li><li><strong>Support processes</strong> (what enables the entire service to work)</li></ul><p>Customer Journeys, on the other hand, visualize how users <strong>flow through a service</strong> — their emotions, goals, and barriers along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ynwV0SqMMcae6F_XVlgUQ.png" /></figure><p>These tools allow teams to <strong>visualize complexity</strong>, uncover inefficiencies, and spot opportunities for innovation — whether it’s automating a step, simplifying a form, or integrating a new payment gateway.</p><h3>Why Should You Care?</h3><blockquote><em>“Looking for highest performances bringing quick results.”</em></blockquote><p>Good Service Design leads to:</p><ul><li><strong>Happier customers</strong> who come back and advocate for your brand.</li><li><strong>Better internal alignment</strong>, reducing chaos and confusion.</li><li><strong>Smarter investments</strong>, because you optimize the right parts of the experience.</li><li><strong>Faster delivery</strong>, with fewer surprises during implementation.</li></ul><p>For developers, it prevents wasted time on misaligned backlogs.<br> For designers, it gives context for their screens.<br> For stakeholders, it’s a lens to see the <strong>entire business</strong> from the outside in.</p><h3>In Short</h3><p>Service Design is <strong>not UX</strong>, but UX is part of it. It’s not just process mapping, but process is key. It’s not only for designers — <strong>it’s for anyone creating, supporting, or scaling a service</strong>.</p><p>So next time you walk past a touchscreen totem or book a flight online, remember: someone designed not just the interface — but the entire <strong>system of experiences</strong> around it.</p><p>If you’re building a product, launching a startup, or transforming a legacy system, <strong>Service Design isn’t optional — it’s foundational.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72664b5773ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Liquid Glass: Between Spectacle and Usability in Apple’s New UI Design]]></title>
            <link>https://fabriciorecman.medium.com/liquid-glass-between-spectacle-and-usability-in-apples-new-ui-design-c01930e41eec?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c01930e41eec</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[liquid-glass]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Mon, 16 Jun 2025 22:24:28 GMT</pubDate>
            <atom:updated>2025-06-16T22:24:28.827Z</atom:updated>
            <content:encoded><![CDATA[<p>When Apple introduced its new “Liquid Glass” design system in iOS 18, it instantly caught the attention of the design community. Social media lit up with stunning demos of fluid animations, glowing transitions, and refractive visual effects dancing behind icons. On the surface, Liquid Glass is a beautiful evolution — sleek, premium, and mesmerizing.</p><p>But behind this shimmering facade lies a tension we’ve seen before in UI design: <em>appearance versus usability</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OWi9Fd4ROSsXQnJrapZ2IA.png" /></figure><h3>The Apple Perspective: Liquid, Unified, Beautiful</h3><p>In its keynote and press materials, Apple describes Liquid Glass as a “translucent material that reflects and refracts its surroundings, dynamically transforming to bring greater focus to content.” It’s a poetic sentence — and there’s no denying the craftsmanship behind it.</p><p>For the first time, this design language is harmonized across platforms — iOS, iPadOS, macOS, watchOS, and tvOS — promising a unified, expressive system. Apple claims that this new material enhances focus, delight, and familiarity. It’s design as theater: a visual language meant to inspire and seduce.</p><p>And they succeed, to an extent. The demos are breathtaking. The polish is impeccable. The Liquid Glass aesthetic elevates Apple’s ecosystem into a more artistic, ambient realm — perhaps closer to sci-fi than skeuomorphism or flat design ever dared.</p><p>But is visual seduction enough?</p><h3>The Designer’s View: Lean-Back Demos vs. Lean-Forward UX</h3><p>Let’s get one thing straight: <strong>UX is not a demo</strong>.</p><p>As usability expert Jakob Nielsen famously said, UX is “lean-forward” — users don’t admire interfaces, they interact with them to achieve goals. And here lies the problem: <em>Liquid Glass might look like progress, but it raises questions about cognitive load, accessibility, and clarity</em>.</p><p>The new translucent layers and animated depth effects, while gorgeous in promotional videos, could blur boundaries between UI layers. Users navigating quickly — or in low-contrast environments — may find it harder to distinguish content from chrome. And for users with vision impairments or neurodivergent needs, dynamic shifting visuals can be disorienting.</p><p>From a product designer’s lens, <em>form must support function</em>. And while Apple has a long tradition of balancing both, the pendulum here seems to swing heavily toward visual emotion — perhaps at the expense of usability clarity.</p><h3>Design System vs. Design Delight</h3><p>This isn’t the first time Apple’s visual evolution has sparked debate. From the shift to flat design in iOS 7 to the arrival of neumorphism in recent years, Apple has often tested the boundaries of visual experimentation. Liquid Glass feels like the logical next step — a blend of motion, material, and mood.</p><p>But unlike industrial design — where material choice implies physical interaction — UI design operates in an abstract, 2D world. We don’t touch <em>glass</em>, we touch <em>functions</em>. When the visual language starts demanding attention <em>for itself</em>, rather than amplifying content and action, the design risks becoming noise.</p><h3>Bridging the Gap: Can Liquid Glass Work?</h3><p>The answer isn’t binary. There is space for beauty in digital design. Emotion matters. First impressions matter. A visually rich interface can elevate brand perception, enhance engagement, and create joy.</p><p>But this has to be paired with UX discipline:</p><ul><li><strong>Contrast ratios must remain accessible.</strong></li><li><strong>Motion should guide, not distract.</strong></li><li><strong>Focus should be contextual, not ornamental.</strong></li><li><strong>Users should feel clarity, not awe.</strong></li></ul><p>If Apple — and we, as designers — treat Liquid Glass as a system, not just a skin, there’s potential. The harmony across platforms is a worthy goal. The vitality of motion can support spatial navigation. But it will take deliberate craft to ensure this doesn’t become a case of <em>design for admiration</em> over <em>design for action</em>.</p><p>Liquid Glass reflects more than light. It reflects a philosophical divide in design itself: <strong>Do we design for delight or design for purpose?</strong> The answer, as always, should be both — but not at the cost of the user.</p><p>In an age where interface beauty is easier than ever to fake, <em>true design leadership lies in invisible sophistication</em>: making things work intuitively, inclusively, and beautifully — in that order.</p><p><em>If you’re a designer exploring the balance between aesthetics and usability, this isn’t just about Apple — it’s about where we’re all headed next.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c01930e41eec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design That Performs: KPIs, OKRs & Metrics Every Product Designer Should Know]]></title>
            <link>https://fabriciorecman.medium.com/keep-strugling-with-metrics-61201798d5d9?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/61201798d5d9</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Sun, 15 Jun 2025 20:25:28 GMT</pubDate>
            <atom:updated>2025-06-16T22:09:50.434Z</atom:updated>
            <content:encoded><![CDATA[<p>Because “it looks good” is not a business metric.</p><p>Most designers know how to craft beautiful interfaces or frictionless flows. Fewer know how to measure whether their work actually <em>matters</em>. In an era where design isn’t just visual but strategic, learning how to speak in <strong>data</strong> — not just pixels — is a superpower.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*vnONSCZk572mib2Uq_RSrw.png" /></figure><p>Yet, many Product Designers still float in an aesthetic bubble, disconnected from the <strong>business impact</strong> of their work. And here’s the truth:</p><blockquote><strong><em>If you can’t measure it, you can’t improve it.</em></strong><em><br> — </em>Peter Drucker</blockquote><p>This article is your fast-track into the world of <strong>KPIs, OKRs</strong>, and <strong>Product Design metrics</strong> — with real context, clear definitions, and references from the best minds in product and design.</p><h3>KPIs (Key Performance Indicators)</h3><p>These are the <strong>vital signs</strong> of your product or feature. KPIs track <em>how well</em> you’re doing against a goal. In design, KPIs can be qualitative or quantitative.</p><p><strong>Examples for Designers:</strong></p><ul><li>Conversion Rate (from sign-up to first action)</li><li>Time on Task (how long it takes to complete a key action)</li><li>Error Rate (in critical user journeys)</li><li>Net Promoter Score (NPS) or Customer Satisfaction (CSAT)</li></ul><blockquote><strong><em>Design KPI Tip</em></strong><em>: Always link your design decision to a KPI. If you’re redesigning onboarding, ask: </em>What metric am I improving?</blockquote><h3>OKRs (Objectives and Key Results)</h3><p><strong>OKRs</strong> are strategic. They answer:<br> <strong>Where are we going, and how will we know we’re there?</strong></p><ul><li><strong>Objective</strong>: a big, qualitative goal. (e.g., <em>“Improve onboarding experience.”</em>)</li><li><strong>Key Results</strong>: measurable outcomes that prove success. (e.g., <em>“Increase new user activation by 25%.”</em>)</li></ul><p>OKRs align <strong>design with business</strong>, giving your team direction beyond UI.</p><p><strong>Design Example:</strong></p><p><strong>O</strong>: Reduce friction in checkout process.<br> <strong>KR1</strong>: Decrease drop-off rate from 30% → 15%.<br> <strong>KR2</strong>: Increase mobile conversion by 20%.<br> <strong>KR3</strong>: Maintain satisfaction score &gt; 85%.</p><h3>How to Apply Metrics Without Losing Your Soul</h3><p>Metrics shouldn’t kill creativity — they should <strong>guide it</strong>.</p><ol><li><strong>Start with a question</strong>: “What do I want to learn or prove?”</li><li><strong>Pick the right metric</strong> for the journey you’re designing.</li><li><strong>Track behavior, not just clicks</strong>: Analytics tools (like Hotjar, Mixpanel, Amplitude) reveal user intentions.</li><li><strong>Design with feedback loops</strong>: Use data to <strong>iterate</strong>, not validate a hunch.</li></ol><h3>Closing Note</h3><p>Being a modern designer means <strong>knowing what your work actually does</strong>.</p><p>Design isn’t only about emotion or usability — it’s about performance, retention, delight, and growth. <strong>KPIs and OKRs are your creative constraints</strong>, not your prison.</p><blockquote><em>You’re not just a designer.<br> You’re a product thinker. A strategist. A change agent.</em></blockquote><p>Know your numbers. Shape the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61201798d5d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Product Designers to Experience Designers: Is a gap on there?]]></title>
            <link>https://fabriciorecman.medium.com/from-product-designers-to-experience-designers-bridging-the-gap-de8f0be3f6d0?source=rss-97f3aacd606b------2</link>
            <guid isPermaLink="false">https://medium.com/p/de8f0be3f6d0</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[services]]></category>
            <dc:creator><![CDATA[Alan Ortiz]]></dc:creator>
            <pubDate>Sun, 15 Jun 2025 01:06:11 GMT</pubDate>
            <atom:updated>2025-06-15T01:07:12.304Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s design-driven world, roles are continuously evolving. One of the most telling shifts is the emergence of the <strong>Experience Designer</strong> — a role that expands beyond the traditional scope of a Product Designer. While both contribute value to building better solutions, the difference lies in where they focus their vision and how they connect the dots across disciplines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*n9sjayXzozQMozIwvdgQGg.png" /></figure><h3>The Product Designer: Precision in Execution</h3><p>Product Designers are often at the intersection of <strong>user needs, business goals, and technology feasibility</strong>. They dive deep into shaping digital products — refining wireframes, designing UI systems, and aligning with development teams and operations. Their strength is in solving specific problems with measurable outcomes. They may also contribute to UX and UI processes and collaborate cross-functionally with stakeholders from Marketing, Growth, or Engineering. This role is pragmatic, execution-oriented, and focused on <strong>“making it work and scale.”</strong></p><p>But while Product Designers touch many areas, their lens is often scoped toward <strong>solving isolated challenges</strong> within the product’s journey. They ensure the product is useful and usable, but not necessarily that the broader experience is meaningful.</p><h3>The Experience Designer: Weaving Holistic Journeys</h3><p>Enter the <strong>Experience Designer</strong> — someone who designs not just the product, but the <strong>environment where the product lives and breathes</strong>. Experience Designers orchestrate <strong>Customer Experience (CX), Brand Experience (BX), User Experience (UX)</strong>, and <strong>Interface Design (UI)</strong> in unison. They zoom out to see how each interaction stacks up to form a cohesive, emotionally resonant experience.</p><p>Think of them as <strong>ecosystem thinkers</strong>. They aren’t just shaping screens — they’re crafting rituals, touchpoints, and transitions. They ask:</p><ul><li><em>How does the service feel end-to-end?</em></li><li><em>What’s the emotional narrative the user walks away with?</em></li><li><em>Where does the brand promise show up in the details?</em></li></ul><p>Their tools may include journey maps, service blueprints, spatial or sensorial design, storytelling, and systems thinking. They may collaborate with Product Designers, but their lens is layered: <strong>experience as architecture</strong>, <strong>emotion as material</strong>, and <strong>consistency as design currency</strong>.</p><h3>Design in Layers, Not Silos</h3><p>To simplify:</p><ul><li>A <strong>Product Designer</strong> might ask, <em>“How do we make this feature intuitive and efficient?”</em></li><li>An <strong>Experience Designer</strong> would ask, <em>“How does this moment feel within the larger journey, and how do we make it memorable?”</em></li></ul><p>The Experience Designer builds on the foundations laid by UX and Product disciplines but extends it into <strong>multi-sensory, cross-channel, and service-aware territories</strong>. They make sure that what’s being built <strong>feels alive and interconnected</strong> — from the brand’s first touch to the aftercare experience.</p><h3>Toward a Converging Future</h3><p>These roles are not in competition — they are complementary. In fact, the best design teams are composed of <strong>specialists and synthesizers</strong>. Product Designers can grow into Experience Designers, and vice versa. What matters is a <strong>shared commitment to coherence</strong>, <strong>empathy</strong>, and <strong>intentional design</strong> at every level.</p><p>The future of design is not just about building better products. It’s about <strong>crafting experiences that resonate</strong>, systems that flow, and <strong>brands that remember who you are long after the screen goes dark</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de8f0be3f6d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>