<?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/en/wiki/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/en/wiki/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>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 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 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>Offline-First Flows: Designing for Disconnection</title><link>https://www.fernandoux.com/en/wiki/strategy/offline-first-flows/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/offline-first-flows/</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;
 The &lt;strong&gt;Offline-First&lt;/strong&gt; strategy is a design and development approach that assumes the user will have an intermittent or null internet connection at some point. Instead of treating &amp;ldquo;Offline&amp;rdquo; as an error state, it is treated as a fundamental feature of the product. The goal is for the application to always keep working.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="the-challenge-of-modern-product-applications"&gt;The Challenge of Modern Product Applications&lt;/h2&gt;
&lt;p&gt;Most traditional web apps (like Jira or Gmail) usually break or show a Chrome dinosaur when Wifi is cut. In advanced digital product design, such as Notion, Figma, or Linear, this is no longer acceptable.&lt;/p&gt;</description></item><item><title>People Management (Design Leadership)</title><link>https://www.fernandoux.com/en/wiki/strategy/people-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/strategy/people-management/</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;
 People Management, in the context of design, is the practice of leading, mentoring, and supporting a team of designers so they can do the best work of their careers. It involves shifting from being a &amp;ldquo;doer&amp;rdquo; to being a &amp;ldquo;multiplier,&amp;rdquo; whose success is measured by the success and growth of the team.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-people-management-in-design"&gt;What Is People Management in Design?&lt;/h2&gt;
&lt;p&gt;Imagine a great chef. In their early days, their success was measured by the incredible dishes they cooked themselves. But when they become the executive chef of a Michelin-starred restaurant, their success no longer depends on the dishes they cook, but on their ability to run the kitchen, create an exceptional menu, and train other chefs to cook at a level of excellence. They become a talent multiplier.&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 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>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>