<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strategy on Fernando Ruiz</title><link>https://www.fernandoux.com/tags/strategy/</link><description>Recent content in Strategy on Fernando Ruiz</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.fernandoux.com/tags/strategy/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a UX Team from Scratch</title><link>https://www.fernandoux.com/en/wiki/strategy/building-ux-team/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/building-ux-team/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 How to establish a UX function in an organization without UX—from first hire to mature team structure.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="starting-from-scratch"&gt;Starting from Scratch&lt;/h2&gt;
&lt;p&gt;Most organizations start with no UX. Engineers build features. Marketing sells them. Users struggle. Growing a UX function requires strategy, hiring, and culture change.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Phase 1: Hire First Designer&lt;/strong&gt; (0-6 months)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Find senior designer (not junior—you need leadership)&lt;/li&gt;
&lt;li&gt;Role: Establish UX thinking, run first user research, begin design documentation&lt;/li&gt;
&lt;li&gt;Wins: One feature redesigned based on research&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Phase 2: Build Small Team&lt;/strong&gt; (6-18 months)&lt;/p&gt;</description></item><item><title>Competitive Analysis</title><link>https://www.fernandoux.com/en/wiki/research/competitive-analysis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/research/competitive-analysis/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A competitive analysis is a strategic research process that involves identifying your competitors and evaluating their products, strategies, strengths, and weaknesses. In UX, it focuses on understanding how others solve similar problems for the same target audience.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-a-competitive-analysis"&gt;What Is a Competitive Analysis?&lt;/h2&gt;
&lt;p&gt;Imagine you want to open a new coffee shop in your neighborhood. The first thing you would do is visit all the other coffee shops in the area. You would try their coffee, check their prices, observe the atmosphere, see what kind of customers they have, and listen to what they complain about or love. You are not doing this to copy them exactly, but to understand the landscape: what works, what does not, and where there might be a gap for your coffee shop to offer something unique and better.&lt;/p&gt;</description></item><item><title>Competitive Analysis</title><link>https://www.fernandoux.com/en/wiki/techniques/competitive-analysis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/techniques/competitive-analysis/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A competitive analysis (or benchmarking) is a research process that involves identifying your competitors and evaluating their products, strategies, strengths, and weaknesses in comparison to your own product or idea.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-a-competitive-analysis"&gt;What Is a Competitive Analysis?&lt;/h2&gt;
&lt;p&gt;Imagine you are the coach of a soccer team. Before an important match, you do not just train your team; you also study recordings of your rival&amp;rsquo;s games. You analyze their playing style, who their star players are, what their usual tactics are, and where they make mistakes. You are not doing this to copy them, but to prepare a counter-strategy that exploits their weaknesses and neutralizes their strengths.&lt;/p&gt;</description></item><item><title>Customer Journey Maps</title><link>https://www.fernandoux.com/en/wiki/artifacts/customer-journey-maps/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/customer-journey-maps/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A Customer Journey Map (CJM) is a visualization of the complete story of a user&amp;rsquo;s interaction with a product or service over time and across different channels. It narrates the experience from the user&amp;rsquo;s perspective, highlighting their actions, thoughts, feelings, and pain points at each stage.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-customer-journey-maps"&gt;What are Customer Journey Maps?&lt;/h2&gt;
&lt;p&gt;If &lt;a href="https://www.fernandoux.com/en/artifacts/personas/"&gt;Personas&lt;/a&gt; are a photo of your user, a Customer Journey Map is a movie about them. It doesn&amp;rsquo;t focus on a single moment, but maps the entire experience of a user as they try to achieve a goal, from the moment they realize they have a need until they resolve it and beyond.&lt;/p&gt;</description></item><item><title>Data-Driven Design Decisions</title><link>https://www.fernandoux.com/en/wiki/processes/data-driven-design-decisions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/processes/data-driven-design-decisions/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Making data-driven design decisions is an approach that uses concrete evidence and data, both qualitative and quantitative, to inform and justify design choices, rather than relying solely on intuition, personal opinions, or aesthetic trends.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-data-driven-design"&gt;What Is Data-Driven Design?&lt;/h2&gt;
&lt;p&gt;Imagine a doctor. A good doctor does not prescribe a treatment based on &amp;ldquo;a hunch&amp;rdquo; or &amp;ldquo;what worked for another patient.&amp;rdquo; A good doctor combines different types of data: listens to your symptoms (qualitative data), orders blood tests (quantitative data), and reviews your medical history to make an informed diagnosis.&lt;/p&gt;</description></item><item><title>Design Culture</title><link>https://www.fernandoux.com/en/wiki/strategy/design-culture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/design-culture/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Creating an organizational culture where design thinking is the default—requires leadership, education, and systematic reinforcement.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-design-culture"&gt;What is Design Culture?&lt;/h2&gt;
&lt;p&gt;Design culture is when an organization naturally thinks about users. Design isn&amp;rsquo;t siloed; it&amp;rsquo;s how everyone works. Engineers design code for humans. PMs design processes for clarity. Leadership designs strategy around user needs.&lt;/p&gt;
&lt;p&gt;Design culture doesn&amp;rsquo;t happen by accident. It requires leadership commitment, continuous education, and systematic reinforcement.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;One sentence punch:&lt;/strong&gt; Design culture is when &amp;ldquo;what do users need?&amp;rdquo; becomes the default question, not the exception.**&lt;/p&gt;</description></item><item><title>Design Evangelism</title><link>https://www.fernandoux.com/en/wiki/strategy/design-evangelism/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/design-evangelism/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Design evangelism (or Design Advocacy) is the continuous process of promoting the value of user-centered design throughout an organization. It involves educating, persuading, and inspiring non-designer colleagues (engineers, product managers, marketing, sales, executives) to understand, value, and integrate design principles into their own work.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-design-evangelism"&gt;What Is Design Evangelism?&lt;/h2&gt;
&lt;p&gt;Imagine you are a nutrition expert at a company. You don&amp;rsquo;t just create a healthy menu for the cafeteria. You give talks about the benefits of good nutrition, put up informative posters, offer consultations, and encourage your colleagues to make healthier choices on their own. You don&amp;rsquo;t impose a diet; instead, you foster a culture of wellness.&lt;/p&gt;</description></item><item><title>Design Principles</title><link>https://www.fernandoux.com/en/wiki/concepts/design-principles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/concepts/design-principles/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Design Principles are a set of brief, clear, and memorable guidelines that articulate the core values that should guide a team&amp;rsquo;s design work. They serve as an internal compass for making consistent, high-quality decisions, especially when there is no specific rule to apply.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-design-principles"&gt;What are Design Principles?&lt;/h2&gt;
&lt;p&gt;They are not prescriptive rules like &amp;ldquo;all buttons must be blue.&amp;rdquo; They are high-level values that help a team define what &amp;ldquo;good design&amp;rdquo; means for their specific product. They are the design team&amp;rsquo;s constitution.&lt;/p&gt;</description></item><item><title>Design Roadmap</title><link>https://www.fernandoux.com/en/wiki/strategy/design-roadmap/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/design-roadmap/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A Design Roadmap is a strategic artifact that visualizes the design team&amp;rsquo;s priorities and work plan over the medium and long term. It aligns design initiatives with product and business objectives and communicates to the entire organization what the design team will focus on and why.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-a-design-roadmap"&gt;What Is a Design Roadmap?&lt;/h2&gt;
&lt;p&gt;Imagine a subway network map. It doesn&amp;rsquo;t show every street in the city, but it does show the main lines, key stations, and important connections. It gives you an overview of how to get around the city and the major future expansion projects. A Design Roadmap is that map for your product: it doesn&amp;rsquo;t detail every task, but it does show the major initiatives and how they connect to overall objectives.&lt;/p&gt;</description></item><item><title>Design Sprints</title><link>https://www.fernandoux.com/en/wiki/processes/design-sprints/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/processes/design-sprints/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A Design Sprint is a five-day process, with a defined step-by-step approach, for answering critical business questions through design, prototyping, and testing with real customers. It is a method for compressing months of debate and development into a single week of focused work.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-a-design-sprint"&gt;What Is a Design Sprint?&lt;/h2&gt;
&lt;p&gt;Imagine you have an idea for a new product. The traditional path would be to spend months researching, designing, developing, and launching to see if people like it. A Design Sprint is like a time machine: it allows you to jump into the future and see how customers react to your finished product, but without having to build it. In just five days, you go from an idea to a realistic prototype and real user feedback.&lt;/p&gt;</description></item><item><title>Design Strategy and Vision</title><link>https://www.fernandoux.com/en/wiki/strategy/strategy-and-vision/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/strategy-and-vision/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Design Strategy (or UX Strategy) is the long-term plan that defines how the user experience will contribute to business objectives. The Design Vision is the inspiring picture of the future that the strategy aims to achieve. Together, they answer the questions: &amp;ldquo;Where do we want to go?&amp;rdquo; (Vision) and &amp;ldquo;How will we get there?&amp;rdquo; (Strategy).
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-design-strategy-and-vision"&gt;What Are Design Strategy and Vision?&lt;/h2&gt;
&lt;p&gt;Imagine you are the captain of a ship. The &lt;strong&gt;Vision&lt;/strong&gt; is your final destination, that paradise island you have in mind that motivates the entire crew. The &lt;strong&gt;Strategy&lt;/strong&gt; is your navigation plan: the route you chart on the map, the currents you will leverage, the supplies you need, and the key ports where you will stop. Without the vision, you sail aimlessly. Without the strategy, the vision is just a dream.&lt;/p&gt;</description></item><item><title>Latency Budgets in UX: Response Times</title><link>https://www.fernandoux.com/en/wiki/strategy/interaction-latency-budgets/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/interaction-latency-budgets/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A &lt;strong&gt;Latency Budget&lt;/strong&gt; is the maximum time allowed (in milliseconds) for a user action to produce a visible response in the interface. It is not a technical metric; it is a design commitment to ensure experience fluidity.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="why-the-designer-should-establish-latency-budgets"&gt;Why the Designer should establish Latency Budgets?&lt;/h2&gt;
&lt;p&gt;Often, designers create complex flows and heavy interactions without considering the technical cost. If an opening animation of a menu takes 500ms and the server another 1000ms to return data, the user will feel the application is a heavy boat.&lt;/p&gt;</description></item><item><title>Modelo de Madurez UX</title><link>https://www.fernandoux.com/es/wiki/estrategia/ux-maturity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/es/wiki/estrategia/ux-maturity/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Definición Rápida&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Un marco para evaluar la madurez de UX de la organización y planificar el viaje de diseño ad-hoc a estrategia dirigida por diseño.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="qué-es-madurez-de-ux"&gt;¿Qué es Madurez de UX?&lt;/h2&gt;
&lt;p&gt;La madurez de UX es cuán sistemáticamente una organización integra UX en la toma de decisiones. La madurez va desde Nivel 0 (sin UX) a Nivel 4 (organización dirigida por diseño).&lt;/p&gt;
&lt;p&gt;Nivel 0: Sin pensamiento de UX. Decisiones basadas en intuición.
Nivel 1: UX ad-hoc. Los diseñadores reaccionan a crisis. Sin estrategia.
Nivel 2: UX emergente. Los procesos existen. Se consulta al diseño, no lidera.
Nivel 3: UX estratégico. El diseño es fundacional. Las métricas guían decisiones.
Nivel 4: Dirigida por diseño. La organización prioriza UX. Cada decisión es centrada en el usuario.&lt;/p&gt;</description></item><item><title>Modelo de Madurez UX</title><link>https://www.fernandoux.com/es/wiki/strategy/ux-maturity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/es/wiki/strategy/ux-maturity/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Definición Rápida&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Un marco para evaluar la madurez de UX de la organización y planificar el viaje de diseño ad-hoc a estrategia dirigida por diseño.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="qué-es-madurez-de-ux"&gt;¿Qué es Madurez de UX?&lt;/h2&gt;
&lt;p&gt;La madurez de UX es cuán sistemáticamente una organización integra UX en la toma de decisiones. La madurez va desde Nivel 0 (sin UX) a Nivel 4 (organización dirigida por diseño).&lt;/p&gt;
&lt;p&gt;Nivel 0: Sin pensamiento de UX. Decisiones basadas en intuición.
Nivel 1: UX ad-hoc. Los diseñadores reaccionan a crisis. Sin estrategia.
Nivel 2: UX emergente. Los procesos existen. Se consulta al diseño, no lidera.
Nivel 3: UX estratégico. El diseño es fundacional. Las métricas guían decisiones.
Nivel 4: Dirigida por diseño. La organización prioriza UX. Cada decisión es centrada en el usuario.&lt;/p&gt;</description></item><item><title>Reduced Motion Strategies: Motion and Accessibility</title><link>https://www.fernandoux.com/en/wiki/strategy/reduced-motion-strategies/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/reduced-motion-strategies/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 &lt;strong&gt;Reduced Motion&lt;/strong&gt; is an accessibility preference that users can activate in their operating systems (Windows, macOS, iOS, Android). When activated, it tells applications to remove or simplify unnecessary animations (&lt;code&gt;prefers-reduced-motion&lt;/code&gt;) to prevent nausea, dizziness, or distraction for people with vestibular disorders or ADHD.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="why-the-designer-should-manage-motion"&gt;Why the Designer Should Manage Motion?&lt;/h2&gt;
&lt;p&gt;As designers, we love animations: zooms, parallax, bounces, and smooth transitions. However, for millions of people, these animations are not &amp;ldquo;pretty&amp;rdquo;; they are physically painful. Excessive movement can cause migraines, disorientation, and vestibular discomfort.&lt;/p&gt;</description></item><item><title>ROI del UX</title><link>https://www.fernandoux.com/es/wiki/estrategia/roi-ux/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/es/wiki/estrategia/roi-ux/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Definición Rápida&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Cómo medir y comunicar el valor empresarial de UX—esencial para el buy-in de stakeholders y asignación de presupuesto.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="qué-es-roi-del-ux"&gt;¿Qué es ROI del UX?&lt;/h2&gt;
&lt;p&gt;ROI (Retorno de Inversión) mide retorno financiero de inversión. ROI de UX cuantifica: &amp;ldquo;Por cada dólar que gastamos en UX, ¿cuánto ganamos?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;UX no es un centro de costos; es un centro de ganancias. Buen UX aumenta conversión, reduce costos de soporte, mejora retención. Mal UX disminuye los tres. Probando esto al liderazgo requiere métricas.&lt;/p&gt;</description></item><item><title>ROI del UX</title><link>https://www.fernandoux.com/es/wiki/strategy/roi-ux/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/es/wiki/strategy/roi-ux/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Definición Rápida&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Cómo medir y comunicar el valor empresarial de UX—esencial para el buy-in de stakeholders y asignación de presupuesto.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="qué-es-roi-del-ux"&gt;¿Qué es ROI del UX?&lt;/h2&gt;
&lt;p&gt;ROI (Retorno de Inversión) mide retorno financiero de inversión. ROI de UX cuantifica: &amp;ldquo;Por cada dólar que gastamos en UX, ¿cuánto ganamos?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;UX no es un centro de costos; es un centro de ganancias. Buen UX aumenta conversión, reduce costos de soporte, mejora retención. Mal UX disminuye los tres. Probando esto al liderazgo requiere métricas.&lt;/p&gt;</description></item><item><title>ROI of UX</title><link>https://www.fernandoux.com/en/wiki/strategy/roi-ux/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/roi-ux/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 How to measure and communicate the business value of UX—essential for stakeholder buy-in and budget allocation.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-roi-of-ux"&gt;What is ROI of UX?&lt;/h2&gt;
&lt;p&gt;ROI (Return on Investment) measures financial return from investment. UX ROI quantifies: &amp;ldquo;For every dollar we spent on UX, how much did we gain?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;UX isn&amp;rsquo;t a cost center; it&amp;rsquo;s a profit center. Good UX increases conversion, reduces support costs, improves retention. Bad UX decreases all three. Proving this to leadership requires metrics.&lt;/p&gt;</description></item><item><title>Service Blueprints</title><link>https://www.fernandoux.com/en/wiki/artifacts/service-blueprints/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/service-blueprints/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A Service Blueprint is a diagram that visualizes the relationships between different components of a service (people, processes, and objects) across the different stages of customer interaction. It&amp;rsquo;s like a [[Customer Journey Maps|Customer Journey Map]] with superpowers, as it not only shows what the customer sees, but also everything that happens &amp;ldquo;behind the curtain&amp;rdquo; to make that experience possible.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-service-blueprints"&gt;What are Service Blueprints?&lt;/h2&gt;
&lt;p&gt;Imagine that a [[Customer Journey Maps|Customer Journey Map]] is the view a diner has at a restaurant: they see the menu, talk to the waiter, receive their food. A Service Blueprint is the complete blueprint of the restaurant: it shows the diner, the waiter, but also the cooks in the kitchen, the ordering system, the suppliers who bring the ingredients, and the cleaning processes.&lt;/p&gt;</description></item><item><title>Strategic Workshops</title><link>https://www.fernandoux.com/en/wiki/processes/strategic-workshops/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/processes/strategic-workshops/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 Strategic workshops are high-level collaborative work sessions, designed and facilitated by design leaders, to align a diverse group of stakeholders (product, business, and technology leaders) around a shared vision, strategy, and long-term priorities. The most common examples are [[Design Sprints]], product vision workshops, and roadmap planning workshops.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-a-strategic-workshop"&gt;What Is a Strategic Workshop?&lt;/h2&gt;
&lt;p&gt;Imagine a summit of world leaders. They do not meet to discuss the color of flags. They meet to address complex problems like climate change or the global economy. They need an expert facilitator (like a UN diplomat) who structures the conversation, ensures all voices are heard, and guides the group toward an agreement or a joint action plan.&lt;/p&gt;</description></item><item><title>Tab Order Strategy: The Keyboard User's Path</title><link>https://www.fernandoux.com/en/wiki/strategy/tab-order-strategy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/tab-order-strategy/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 &lt;strong&gt;Tab Order&lt;/strong&gt; is the exact sequence in which a keyboard user (pressing &lt;code&gt;Tab&lt;/code&gt; and &lt;code&gt;Shift + Tab&lt;/code&gt;) traverses an interface&amp;rsquo;s interactive elements. A good tabbing strategy ensures that the user doesn&amp;rsquo;t get lost, doesn&amp;rsquo;t have to perform unnecessary clicks, and can complete their tasks quickly and logically.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="why-the-designer-should-decide-the-tab-order"&gt;Why the Designer Should Decide the Tab Order?&lt;/h2&gt;
&lt;p&gt;Although tab order is usually an automatic consequence of the order in the HTML code (the DOM), visual design can be much more complex. As designers, we sometimes create layouts with columns, grids, or floating elements that don&amp;rsquo;t follow a pure linear order.&lt;/p&gt;</description></item><item><title>UX KPIs</title><link>https://www.fernandoux.com/en/wiki/strategy/kpis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/kpis/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A UX KPI (Key Performance Indicator) is a quantifiable metric that a team uses to measure and evaluate the success of the user experience over time. They help teams understand whether their design efforts are achieving the desired outcomes.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-ux-kpis"&gt;What Are UX KPIs?&lt;/h2&gt;
&lt;p&gt;Imagine you are driving a car. The dashboard gives you vital information: the speedometer (speed), the fuel gauge (range), the engine temperature. You could not drive safely or efficiently without them. UX KPIs are the dashboard of your product: they are the indicators that tell you whether the user experience is on track or whether there are problems that need your attention.&lt;/p&gt;</description></item><item><title>UX Maturity Model</title><link>https://www.fernandoux.com/en/wiki/strategy/ux-maturity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/ux-maturity/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A framework for assessing organizational UX maturity and planning the journey from ad-hoc design to design-led strategy.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-ux-maturity"&gt;What is UX Maturity?&lt;/h2&gt;
&lt;p&gt;UX maturity is how systematically an organization integrates UX into decision-making. Maturity ranges from Level 0 (no UX) to Level 4 (design-driven organization).&lt;/p&gt;
&lt;p&gt;Level 0: No UX thinking. Decisions based on gut feel.
Level 1: Ad-hoc UX. Designers react to crises. No strategy.
Level 2: Emerging UX. Processes exist. Design is consulted, not leading.
Level 3: Strategic UX. Design is foundational. Metrics guide decisions.
Level 4: Design-led. Organization prioritizes UX. Every decision is user-centered.&lt;/p&gt;</description></item><item><title>UX Strategy Document</title><link>https://www.fernandoux.com/en/wiki/strategy/ux-strategy-document/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/ux-strategy-document/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 A UX Strategy Document is an artifact that articulates the [[Strategy and Vision|design strategy and vision]] of a product or service. It connects business goals with user needs and establishes a high-level plan for how design will help close the gap between where the product is now and where it wants to be in the future.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-a-ux-strategy-document"&gt;What Is a UX Strategy Document?&lt;/h2&gt;
&lt;p&gt;Imagine you are going on a road trip across a country. You don&amp;rsquo;t just get in the car and start driving. First, you create a travel plan: you define your final destination (the vision), the route you will follow, the key stops you will make (the strategic pillars), the budget you need, and how you will know you are on the right track. A UX Strategy Document is that travel plan for your product&amp;rsquo;s user experience.&lt;/p&gt;</description></item></channel></rss>