<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Artifacts on Fernando Ruiz</title><link>https://www.fernandoux.com/en/wiki/artifacts/</link><description>Recent content in Artifacts on Fernando Ruiz</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.fernandoux.com/en/wiki/artifacts/index.xml" rel="self" type="application/rss+xml"/><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>Design Specifications</title><link>https://www.fernandoux.com/en/wiki/artifacts/design-specs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/design-specs/</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;
 Detailed documentation that translates designs into development instructions—the bridge between design and code.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-design-specifications"&gt;What are Design Specifications?&lt;/h2&gt;
&lt;p&gt;Design specifications are detailed documents that describe design intent precisely enough that developers can implement it without returning to designers for clarification. Specs cover everything: spacing (the button has 16px padding), colors (the primary blue is #0066FF), interactions (on hover, the button becomes 2% darker), and edge cases (disabled state shows 50% opacity).&lt;/p&gt;</description></item><item><title>Empathy Maps: Understanding Users at a Deeper Level</title><link>https://www.fernandoux.com/en/wiki/artifacts/empathy-maps/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/empathy-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;
 An empathy map is a visual framework for understanding a user&amp;rsquo;s needs, feelings, and environment by exploring what they think, feel, see, say, do, and hear.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-an-empathy-map"&gt;What is an Empathy Map?&lt;/h2&gt;
&lt;p&gt;Imagine sitting with a user for a day, observing everything they do, listening to everything they say, noticing what frustrates them, what excites them, what others influence their decisions. An empathy map is that day of observation, organized visually. You divide a page into sections: What does the user think? What do they feel? What do they see around them? What do they say to others? What actions do they take? Who influences their decisions? By systematically exploring each dimension, you move beyond assumptions into genuine understanding of what users actually need, what obstacles they face, and what drives their decisions. It&amp;rsquo;s not about data—it&amp;rsquo;s about meaning. Data tells you how many users abandoned at checkout; empathy mapping tells you why they abandoned and what would make them stay.&lt;/p&gt;</description></item><item><title>Mockups</title><link>https://www.fernandoux.com/en/wiki/artifacts/mockups/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/mockups/</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 mockup is a static, high-fidelity representation of a product&amp;rsquo;s interface. Unlike wireframes, mockups focus on the visual and aesthetic aspects, including colors, typography, images, and other graphic elements to simulate the final product&amp;rsquo;s appearance.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-mockups"&gt;What are Mockups?&lt;/h2&gt;
&lt;p&gt;If a wireframe is the blueprint of a house, a mockup is the color model or 3D render that shows how the finished house will look. It&amp;rsquo;s a static (non-interactive) design that communicates the art direction and visual design of the product.&lt;/p&gt;</description></item><item><title>Personas</title><link>https://www.fernandoux.com/en/wiki/artifacts/personas/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/personas/</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 Persona (or User Persona) is a fictional user archetype based on real research data that represents a group of users with similar behaviors, goals, and motivations. It is used to humanize users and keep the design team focused on their needs.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-personas"&gt;What are Personas?&lt;/h2&gt;
&lt;p&gt;Imagine you&amp;rsquo;re designing a backpack. You could design it for &amp;ldquo;everyone,&amp;rdquo; but you&amp;rsquo;d probably end up with something generic that nobody loves. Instead, you could design it for &amp;ldquo;Ana, a 20-year-old university student who commutes to campus by bike, needs to carry her laptop and books, and values sustainability and style.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Prototypes</title><link>https://www.fernandoux.com/en/wiki/artifacts/prototypes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/prototypes/</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 prototype is an interactive simulation of a final product used to test and validate design concepts before development. Unlike mockups (which are static), prototypes are &amp;ldquo;clickable&amp;rdquo; and allow users to experience the flow of an application.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-prototypes"&gt;What are Prototypes?&lt;/h2&gt;
&lt;p&gt;If a mockup is the color model of a house, a prototype is a virtual guided tour through that model. It allows you to open doors, turn on lights, and move between rooms to understand what it feels like to live in it.&lt;/p&gt;</description></item><item><title>Red Routes</title><link>https://www.fernandoux.com/en/wiki/artifacts/red-routes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/red-routes/</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 top 5 user journeys your product must support flawlessly—identify these and everything else is secondary.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-red-routes"&gt;What are Red Routes?&lt;/h2&gt;
&lt;p&gt;Red routes are the core user journeys your product must support perfectly. The term comes from London&amp;rsquo;s Underground—red routes are the main lines that carry the most traffic. Everything else is secondary.&lt;/p&gt;
&lt;p&gt;For an e-commerce site, red routes are: browsing products, reading reviews, adding to cart, checking out, and contacting support. Everything else (wishlists, recommendations, social sharing) is nice-to-have.&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>Site Maps</title><link>https://www.fernandoux.com/en/wiki/artifacts/site-maps/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/site-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 hierarchical diagram showing all pages and how they relate—the blueprint before you design a single page.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-is-a-site-map"&gt;What is a Site Map?&lt;/h2&gt;
&lt;p&gt;A site map is a visual representation of a website&amp;rsquo;s structure. It shows every page and how they connect. The homepage sits at the top. Product pages branch down. Support pages branch separately. Each page has a clear parent and siblings.&lt;/p&gt;
&lt;p&gt;A site map answers: &amp;ldquo;Where does this page live? What pages are at the same level? What pages are nested inside?&amp;rdquo; Without a site map, designers design pages in isolation. Pages feel disconnected. Navigation feels random.&lt;/p&gt;</description></item><item><title>User Flows</title><link>https://www.fernandoux.com/en/wiki/artifacts/user-flows/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/user-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;
 A User Flow is a diagram that visualizes the complete path a user follows through a digital product to complete a specific task. It shows the screens, actions, and decisions the user makes from start to finish.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-user-flows"&gt;What are User Flows?&lt;/h2&gt;
&lt;p&gt;If a wireframe is the blueprint of a room and a sitemap is the blueprint of the entire building, a User Flow is the fire evacuation route. It doesn&amp;rsquo;t show all the rooms, just the specific sequence of steps to get from point A (e.g., &amp;ldquo;being in the hallway&amp;rdquo;) to point B (e.g., &amp;ldquo;being safely outside the building&amp;rdquo;).&lt;/p&gt;</description></item><item><title>Wireframes</title><link>https://www.fernandoux.com/en/wiki/artifacts/wireframes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/artifacts/wireframes/</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 wireframe is a low-fidelity visual schematic of an interface, similar to an architect&amp;rsquo;s blueprint. It focuses on structure, content hierarchy, and functionality, deliberately ignoring visual elements like colors, typography, or images.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-are-wireframes"&gt;What are Wireframes?&lt;/h2&gt;
&lt;p&gt;Imagine you want to build a house. Before deciding on wall colors or furniture types, you need a blueprint that defines where the rooms, doors, and windows will be. That is exactly what a wireframe is for a digital product.&lt;/p&gt;</description></item></channel></rss>