<?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 Pablo Garcia Pedro on Medium]]></title>
        <description><![CDATA[Stories by Pablo Garcia Pedro on Medium]]></description>
        <link>https://medium.com/@pautorre91?source=rss-7bac6d52810c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmiYy07rLo6DJUFjlGGg0g.jpeg</url>
            <title>Stories by Pablo Garcia Pedro on Medium</title>
            <link>https://medium.com/@pautorre91?source=rss-7bac6d52810c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:04:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pautorre91/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[How to get nice insights from a user testing ✨]]></title>
            <link>https://medium.com/design-bootcamp/how-to-get-nice-insights-from-a-user-testing-ebbb76edd1e6?source=rss-7bac6d52810c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebbb76edd1e6</guid>
            <category><![CDATA[search]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[insights]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Pablo Garcia Pedro]]></dc:creator>
            <pubDate>Thu, 15 Sep 2022 11:04:44 GMT</pubDate>
            <atom:updated>2022-09-17T07:31:36.186Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*N-wp0O1APfKO4UfGR73bIA.gif" /><figcaption>Pikachu searching experience</figcaption></figure><p>In this article, we are going to discuss a case of improving the search experience of a specific brand or model of users on a website for buying used and semi-new cars.</p><p>First of all, we analyze the system that currently exists to perform this search, which consists (of desktop and mobile versions) of a dropdown to first select the brand and then the model of the car. We have to take into account the limitation that without a previous brand selection, the search by the model is not active. This happens in all displays.</p><p>We understand that limiting the user options can have its advantages (agility, error prevention) and also its disadvantages (more actions, more time to perform them…).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UJ1AVApWKt_qx77pbPG4rw.png" /><figcaption>Current desktop (left) and mobile (right) search method</figcaption></figure><p>It is then that a possible alternative is proposed through a search style based on the autocomplete function.</p><p>Therefore, we decided to conduct a usability test with users and stakeholders to assess the impact of this possible solution to improve the search experience.</p><p>The test, which we will perform with <a href="https://maze.co/">Maze</a>, consists of 2 missions, a simple question, and an optional answer justification.</p><p>To complete the first mission, the user must search for the “Hyundai Hb20” model using an autocomplete system. In this mission, there are 6 different paths to obtain the result (model, brand, number, letter…). While the second mission has only 1 path to complete, as it is the current experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0AbwmKtdHLM7PzfCaSq0vQ.png" /><figcaption>Autocomplete search (left) and dropdown list selection (right)</figcaption></figure><p>Once the 2 missions were completed, we asked the users which one they thought was the simplest to use. We then optionally ask them why they gave this answer.</p><p>In this way, we obtain two types of answers: quantitative and qualitative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7PAHjzjDtiSAM3xLFu63ow.png" /><figcaption>Data from Maze about the missions and the quantitative question</figcaption></figure><p>Users responded by leaving feedback in the answers and providing value for their experience. With this data and the analysis of the Maze metrics, we can generate our conclusions from the test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A32IvD4uuzRucrZrjyDDwA.png" /><figcaption>Feedbacks from users</figcaption></figure><h3>Conclusions</h3><p>1. <strong>Depending on the users’ level of product knowledge, the predisposition towards one type of search varies</strong>. Users with less knowledge opt for the “dropdown list” option, while more advanced users prefer to autocomplete as it helps them find the car with fewer actions and faster.</p><p>2. <strong>Users can make mistakes.</strong> In an “open field” option the % of errors made may increase and lead some users to feelings of frustration. Whereas a search “limited” to the selection of a predefined list of make and model greatly reduces the possible % of errors made.</p><p>3. <strong>Search times are usually low </strong>(between 2–4 s approx) so the results are the data that will have more relevance when decided by the user.</p><p>4. <strong>Achieving a “Hybrid” search model can improve the experience of the two types of users we have differentiated</strong>, thus helping us to diversify user journeys and lead them down different paths according to their level of knowledge and urgency to buy. In addition, the data we would obtain from the search fields will help us to better understand which models users are looking for the most.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebbb76edd1e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-get-nice-insights-from-a-user-testing-ebbb76edd1e6">How to get nice insights from a user testing ✨</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to manage the change of the objective for the quarter]]></title>
            <link>https://medium.com/design-bootcamp/how-to-manage-the-change-of-the-objective-for-the-quarter-c96b2fe54e41?source=rss-7bac6d52810c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c96b2fe54e41</guid>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[ideation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Pablo Garcia Pedro]]></dc:creator>
            <pubDate>Thu, 07 Jul 2022 11:24:38 GMT</pubDate>
            <atom:updated>2022-07-15T05:17:53.267Z</atom:updated>
            <content:encoded><![CDATA[<p>ideation — brainstorming</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*BkuHpF1h0KloqQ2zFXUqHg.gif" /><figcaption>Thinking about it…</figcaption></figure><p>How can we deal with the change of an OKR once the quarter has started? Which people should we involve in this modification? How much time do we have to do it in an agile way?</p><p>I will try to solve all these questions by means of a practical example of a real situation at work ;)</p><p>To start, we must know where this change comes from and its reasons, which in our case is a question of the time and scope of the team.</p><p>Once we have the information about the change, we proceed to perform a brainstorming exercise on the new OKR with the whole squad (this is the term we use to refer to the PD + PM + Devs team) and the different stakeholders (business and marketing people). This session will take about 1h 30min.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A0Wvu50hxKGVEhCcLPJNRw.png" /><figcaption>Exercise introduction</figcaption></figure><p>After this session, we will make a presentation of the final Outcome with its opportunities. So within 2–3 days, we can have our new target.</p><p><strong>How does it work? This exercise consists of 4 phases:</strong></p><p><strong>Phase 1 — Thinking ideas</strong></p><p>We will divide into groups of 2 people for the generation of ideas. In this way we will be able to generate 4 ideas to start working on the exercise. Each group will have 5 minutes (with the possibility of extending for more time if necessary). In this first phase, the participants of each group will discuss in a separate area in gather to be more concentrated.</p><p><strong>Phase 2 — Ideas improvement</strong></p><p>When the timer rings, participants can pass their ideas to the group on the right. Start the timer again and ask participants to add suggestions that complement or improve the ideas already on the template. Each group should contribute to the rest of the ideas. Then the group has to define their idea with the improvements of the other partners ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wG6s0e45360-8OZ84s2guw.png" /><figcaption>The different steps of the exercise</figcaption></figure><p><strong>Phase 3 — Voting</strong></p><p>Each participant will have 2 votes to distribute among the 4 final ideas (ideas with all the improvements proposed in the previous exercise).</p><p>Once we have all the votes cast, we will proceed to the next step</p><p><strong>Phase 4 — Effort Matrix</strong></p><p>With the votes cast, all the participants will evaluate the effort and impact that these ideas can have in a matrix exercise.</p><p>Afterward, we will validate which idea or ideas we can carry out and we will finish the exercise, having a clear solution on how we can achieve our objective.</p><p>The final step, we will carry out to finalize the exercise will be a mapping of the final outcome with the opportunities and feasibility that it entails so that we can achieve our objective within the quarter. This exercise will be carried out entirely with the components of the squad.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GEg4Ek3krqQ9SKSzawRp4g.png" /></figure><p>and … that’s all folks!</p><p>I decided to share this information because it worked quite well for us within the team and it helped us to keep moving forward in order to achieve the new objectives involving all the people to have a better alignment between all the people.</p><p>I hope it can help you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c96b2fe54e41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-manage-the-change-of-the-objective-for-the-quarter-c96b2fe54e41">How to manage the change of the objective for the quarter</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Facilitator role: rules and scope]]></title>
            <link>https://medium.com/@pautorre91/facilitator-role-rules-and-scope-b66b1ce912bb?source=rss-7bac6d52810c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b66b1ce912bb</guid>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[methodology]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[organization]]></category>
            <dc:creator><![CDATA[Pablo Garcia Pedro]]></dc:creator>
            <pubDate>Wed, 04 May 2022 14:56:53 GMT</pubDate>
            <atom:updated>2022-05-04T17:21:23.142Z</atom:updated>
            <content:encoded><![CDATA[<p>You know when your team/squad wants to have more ownership and encourage everyone’s participation? This is for you mah buddy!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*N9_qIecXt-SWdF1ewqnpsw.png" /><figcaption>Homer thinks about how to improve…</figcaption></figure><h3>Description</h3><p>In order to distribute the squad organization to all its members and not delegate excess of responsibility to the product or engineering managers and have more ownership the entire team, we introduced the figure of the facilitator. The initiative consists of having a different person from the squad each week who is in charge of organizing and facilitating certain tasks, helping the squad to function properly. This initiative also helps all squad members improve their communication, organization and leadership skills.</p><h3>Rules</h3><blockquote>1.Each week there will be a new facilitator who will change on a rotating basis.</blockquote><blockquote>2. If the facilitator is absent (illness, vacation, etc.), the facilitator from last week will be in charge of substituting him/her.</blockquote><blockquote>3. People who are eligible to be the facilitator are all crew members except the engineering manager.</blockquote><h3>Tasks</h3><p>🫶🏻 <strong>Organize the daily</strong></p><ul><li>Ensure that all the crew members of the squad have joined and will notify the crew members who are missing to join.</li><li>The facilitator will be responsible for ensuring that all defined standard procedures are complied with.</li><li>Ensure that the language in which it will be carried out is the agreed one.</li><li>The facilitator will be in charge of indicating when the meeting starts and ends.</li><li>The facilitator will place greater emphasis on the board, warning of cases in which inconsistencies occur, such as tasks without a description, board columns in which the minimum and maximum established tasks are not met, etc.</li><li>The facilitator will ensure that the distribution of work is balanced between delivery and discovery procedures, always taking into account the squad priorities and objectives at the moment.</li></ul><p>👀 <strong>Check the meetings of the day. <br></strong>Starting the day, the facilitator will make sure that the meetings scheduled for the day make sense and make sure to cancel, change times or notify the organizer of the meeting to do that if needed.</p><p>📃 <strong>Summary of meetings with the client.<br></strong>The facilitator will make a summary detailing all important points of the meetings with the client and will share this summary in the corresponding channel if necessary.</p><p>⏱ <strong>Notices about overtime in internal team meetings.<br></strong>In the cases where the internal team meetings exceed the scheduled time, the facilitator will indicate this during the meeting and suggest the possibility of scheduling a second meeting.</p><p>🗣 <strong>Conversations about the product in public channels.<br></strong>In the cases where the conversations about product doubts and implementations take place in private channels, the facilitator will suggest transferring that conversation to public channels.</p><p>✍🏽 <strong>Retrospective actions<br></strong>Once the squad retrospective is finished, the facilitator will complete the document provided by the engineering manager and add the decision and action sections following the same format as the previous retrospectives. Once this is done, he will share the document with the rest of the squad.</p><blockquote>I hope that if you have come this far it has helped you! If you have any questions or suggestions you can make them in the comments, I will be happy to answer and discuss✌🏼</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b66b1ce912bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to prioritize tasks to make an MVP]]></title>
            <link>https://medium.com/@pautorre91/how-to-prioritize-tasks-to-make-an-mvp-93512efb038a?source=rss-7bac6d52810c------2</link>
            <guid isPermaLink="false">https://medium.com/p/93512efb038a</guid>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Pablo Garcia Pedro]]></dc:creator>
            <pubDate>Fri, 07 Jan 2022 13:19:39 GMT</pubDate>
            <atom:updated>2022-01-07T13:19:39.004Z</atom:updated>
            <content:encoded><![CDATA[<p>We had a situation to solve: as a team we had to be able to generate an MVP in a period of 2 weeks. The product area, specifically the product designer (a.k.a “me”) was in charge of helping the team with a prioritization and task organization exercise. I am going to tell you how my experience was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*J_1yHebQgo_wedrg9DL-ig.jpeg" /></figure><p>First of all, we did an internal brainstorming exercise to see what kind of framework we could generate to solve this casuistry. Then we decided to structure the exercise in 3 phases: Ideation, prioritization and organization. We decided to use MIRO to carry out the session… and here we started!</p><h3>Context</h3><p>Houston, we have a problem to solve in <strong><em>Our Squad</em></strong> to <strong>generate an MVP for the lifetime warranty</strong></p><p>To generate this MVP, we must discover which components are necessary to support a warranty process identifying the building blocks that make it possible.</p><p>The goal we want to achieve is the generation of the minimum necessary features to be able to get the job done, subdividing the work in tasks to be able to face it in a better way.</p><p>In order to have a better capacity to solve the exercise we must think at all times who our stakeholders are and how the different proposals may affect them.</p><p><strong>Let’s get started! this is the first time we are going to create a product from scratch</strong></p><h3>How does this activity works?</h3><p><strong>This workshop consists of 3 phases.</strong> The first phase is the ideation phase. In it we will leave our comments, which we will then validate all together to move to the next step.</p><blockquote><strong>Phase 1 — Ideation</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*CwyCpILQH2yQT0EvPLFoQg.png" /><figcaption>The ideation phase</figcaption></figure><p><strong>First part <em>The dreamer. </em></strong>Unleash your creativity. Concentrate on letting ideas flow without criticism or restrictions. Then we will group the ideas by related themes and write a post-it as a summary that represents them.</p><p><em>— Ask yourself: what do we want, what are the potential benefits of this solution?</em></p><p><strong>Second part <em>The realistic. </em></strong>The dream is possible. Assuming we can achieve it, figure out what steps you would have to take to get there.</p><p><em>— Ask yourself: How can we implement this idea? What resources would we need?</em></p><p><strong>Third part <em>The critique. </em></strong>In order to approach this phase, we will filter the ideas beforehand in the “realistic” section and then it is time to discover the possible obstacles.</p><p><em>— Ask yourself: What could go wrong with this idea? What is missing? What are the possible weaknesses?</em></p><blockquote><strong>Phase 2— Prioritization</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SfB2x31uzoNrmXRpZkgZjg.png" /><figcaption>The prioritization phase</figcaption></figure><p><strong>The second phase</strong> is the prioritization phase. According to the results obtained from the first exercise, we will rate them according to their impact on the MVP</p><p>We will perform a bull’s eye exercise, which consists of 3 circles. The inner circle contains the elements of highest priority, the middle circle contains the elements of medium priority and the largest circle contains the elements of lowest priority.</p><p>In the corners of the bull’s eye we will have the stakeholders so that we always have a mentality of which profiles are involved in the assurance from its creation to its follow-up.</p><blockquote><strong>Phase 3— Organization</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zdI8Xs0HS7bh34_lgA6FoA.png" /><figcaption>The organization phase</figcaption></figure><p><strong>The last phase</strong> will consist of a selection and description of the items with the highest priority as a result of the previous exercise in order to generate our MVP.</p><p>In this exercise we are going to divide the characteristics that we have obtained in the previous exercise in the possible subtasks and dependencies with other areas that it may contain.</p><p>In this way we will get a better organization and structuring of the tasks to be able to work in a more agile way and thus be able to obtain a solution for our MVP.</p><h3>Learnings 📔</h3><blockquote>One of the most important things I learned was that the same person having the role of session director and participant at the same time is counterproductive and not very agile because it makes the session take too long.</blockquote><blockquote>Another thing I learned is that feedback is very important and in each and every one of the exercises we do as a team there should be a section for it. Thanks to this practice I was able to get inputs in an easier way to improve future sessions.</blockquote><blockquote>It is very important to involve stakeholders, it makes us have a much broader and more realistic vision to face these exercises.</blockquote><blockquote>Time is gold. We must speed up the exercises as much as possible by working remotely, and having a first phase to be performed asynchronously helps participants to have more context to then focus better on the exercise.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93512efb038a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[El análisis heurístico]]></title>
            <link>https://medium.com/@pautorre91/el-an%C3%A1lisis-heur%C3%ADstico-2b5c7d328ed3?source=rss-7bac6d52810c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b5c7d328ed3</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[heuristic-evaluation]]></category>
            <category><![CDATA[dci]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Pablo Garcia Pedro]]></dc:creator>
            <pubDate>Fri, 22 Oct 2021 18:53:24 GMT</pubDate>
            <atom:updated>2021-10-22T18:53:24.357Z</atom:updated>
            <content:encoded><![CDATA[<p>Hola! Soy Troy McClure, quizá me recuerden de otros posts cómo… En realidad no soy Troy sólo un diseñador dando sus primeros pasos en medium y estaba buscando una manera distinta de empezar mi primer post sobre el análisis heurístico ;)</p><blockquote>El objetivo principal de ésta prueba de usabilidad es el de <strong>medir la calidad de uso de una interfaz</strong>, al igual que los Walkthroughs (recorrido/ paseo cognitivo); pero a diferencia de ésta, la EH se centra en <strong>inspeccionar los problemas</strong>.</blockquote><p>Ahora que tengo toda vuestra atención, vamos a tratar los 10 principios de heurística de Nielsen acompañados de buenas y malas prácticas analizando la interfaz de la página de la liga española de baloncesto ACB, ya que es una web que ha dado mucho que hablar y ha tenido un rediseño interesante(de marca incluido) recientemente.</p><p>Éstos principios de Nielsen una vez explicados, los priorizaremos según el grado de importancia en cuanto a la experiencia de usuario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*4op6sBGh72RqF9AtFqCEHA.gif" /></figure><h3>1— Visibilidad del estado del sistema</h3><p><em>El diseño debe mantener siempre informados a los usuarios sobre lo que está ocurriendo en todo momento mediante una retroalimentación.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*CSo5Jj_am84HXxpp2Bp7iA.png" /><figcaption>Fuente: screenshot propio sección valencia basket en www.acb.com</figcaption></figure><h4>❌ Mala práctica</h4><p>Vemos que existen <strong>3 menús diferentes en la página</strong>. Uno en forma de listado de clubes con su escudo, el segundo menú aparece debajo del logo de la liga, y por último unas <em>tabs </em>a modo de menú dentro del equipo que hemos seleccionado.</p><p>Sólo tenemos una referencia en el tercer menú, en el resto <strong>no observamos ningún distintivo que nos indique cómo hemos llegado hasta ahí ni en qué nivel menú superior nos encontramos.</strong></p><h3>2 — Coincidencia entre el sistema y el mundo real</h3><p><em>El diseño debe hablar el idioma de los usuarios. Utilizar palabras, frases y conceptos familiares para el usuario, en lugar de jerga interna.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*HRwwSyGBNFrBC2epSBq6zA.png" /><figcaption>Fuente: screenshot propio sección resultados en <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>❌ Mala práctica</h4><p>Los desplegables <strong>no sabemos si están activados o no</strong> ya que todos poseen la misma apariencia. Además dentro del desplegable <strong>tampoco tenemos manera de saber qué opción estamos seleccionando.</strong></p><h3>3 — Control y libertad del usuario</h3><p><em>Los usuarios suelen necesitar una “salida de emergencia” claramente marcada para abandonar la acción no deseada sin tener que pasar por un proceso prolongado.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*m7sJPvMFLLduIarTk0ZY_Q.png" /><figcaption>Fuente: screenshot propio sección artículos en <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>🤔 ¿? práctica</h4><p>Es una actividad común el uso del logo dela web a modo de volver siempre a la página de inicio. En muchos casos, no es entendible por parte de una gran mayoría ya que algunas páginas requieren de un login previo, por lo que puede resultar confuso dependiendo del nivel del usuario en la página.</p><h3>4 — Consistencia y normas</h3><p><em>Los usuarios no deberían tener que preguntarse si diferentes palabras, situaciones o acciones significan lo mismo. Es importante mantener la misma consistencia a lo largo de todo la experiencia.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*F_8akzGRnbaaKoR6t7y24w.png" /><figcaption>Fuente: screenshot propio homepage <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>✅ Buena práctica</h4><p>La consistencias entre todas las secciones de la homepage y el uso del mismo tono de comunicación con un diseño totalmente estático reflejan una sensación de coherencia que nos permite tener una navegación sencilla.</p><h3>5 — Prevención de errores</h3><p><em>Los buenos mensajes de error son importantes, pero los mejores diseños evitan cuidadosamente que los problemas se produzcan en primer lugar. Debemos ayudar al usuario a equivocarse antes de que cometa el error.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*_tRSeDGfzJtZehK6K_aIKQ.png" /><figcaption>Fuente: screenshot propio sección aviso legal en <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>❌ Mala práctica</h4><p>Al clicar en el enlace sobre el aviso legal, se nos abre un documento en una pestaña nueva directamente, sin pasar por una página previa con información previa y un enlace explícito al documento ni con ninguna información sobre la acción que se va a realizar es diferente a el resto.</p><blockquote><em>Bueno, ya estamos en la mitad, solo queda el resto :)</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/292/1*irCCWoOpCXPY0JG-8AHPzg.gif" /></figure><h3>6— Reconocer más que recordar</h3><p><em>Aliviar la carga de memoria del usuario haciendo visible objetos, acciones y opciones. Siempre se deben indicar los campos por los cuales se ha realizado la búsqueda.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*D4FBYkY4MaWRRgRPuYevxA.png" /><figcaption>Fuente: screenshot propio menú principal <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>✅ Buena práctica</h4><p>Consideraremos este ejemplo como <em>bueno</em> debido a que lo analizaremos desde el punto de vista de la estructura y organización de la información, por lo que la UI en este caso no lo valoraremos. Observamos una diferenciación de los niveles en los que estamos adentrados del menú, sabemos en todo momento el elemento seleccionado donde se encuentra.</p><h3>7— <strong>Flexibilidad y eficiencia en el uso</strong></h3><p><em>Permitir que los usuarios adapten las acciones frecuentes. Los procesos flexibles pueden llevarse a cabo de diferentes maneras, de modo que los usuarios puedan elegir el método que más les convenga según su nivel de experiencia.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-XKPCLDO3cBf0ynY-EFYrA.png" /><figcaption>Fuente: screenshot propio página de resultados y ficha de un partido concreto <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>✅ Buena práctica</h4><p>Observamos 3 maneras diferentes de poder acceder al artículo del partido seleccionado. Un usuario con mas experiencia es consciente de que si prefiere ver las estadísticas lo primero irá al icono superior de la derecha y accederá a esa información y posteriormente mediante las tabs del menú del partido podrá ver todo lo relacionado con él. Mientras que un usuario no tan experto puede no conocer ese atajo de información.</p><h3>8 — Diseño estético y minimalista</h3><p><em>Las interfaces no deben contener información irrelevante o que rara vez se necesite. Cada unidad de información adicional en una interfaz compite con las unidades de información relevantes y disminuye su visibilidad relativa.</em></p><p><em>Esta heurística no significa que haya que utilizar un diseño plano: se trata de asegurarse de que el contenido y el diseño visual se centran en lo esencial.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*wTosF8Jk-ENdGdQJmeGkYA.png" /><figcaption>Fuente: screenshot propio homepage <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>❌ Mala práctica</h4><p>Vemos la aparición de dos banners de tamaño y estética similar a los bloques de información de la homepage, por lo tanto pueden conducir a error y distraer al usuario.</p><h3>9 — Ayudar a reconocer, diagnosticas y recuperarse de errores</h3><p><em>Debemos comunicar errores con facilidad al usuario, le proporcionamos una solución o camino a seguir y proponemos una alternativa.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*cT5wzDYhnCN9drzaB1_fdw.png" /><figcaption>Fuente: screenshot propio invalid URL <a href="http://www.acb.com/">www.acb.com</a></figcaption></figure><h4>❌❌❌ Malísima práctica</h4><p>No aparece ningún mensaje indicando ninguna información sobre lo que ha ocurrido, ni tampoco tenemos posibilidad de realizar ninguna acción ya que la web se ha quedado solo con el header y el footer.</p><h3>10— Ayuda y documentación</h3><p><em>Es deseable que que el sistema no necesite ninguna explicación adicional. Sin embargo, puede ser necesario proporcionar documentación para ayudar a los usuarios a entender mejor las funcionalidades. El contenido de la ayuda y la documentación debe ser fácil de buscar y centrarse en la tarea del usuario.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*iusQL_UIQggNKeMOnS7K3w.png" /></figure><h4>🔮 Misteriosa práctica</h4><p>Como dice Phineas <em>“descubramos algo que nunca existió”, eso le ocurre a la página de la acb, no dispone de ningún buscador, ni sección de ayuda, ni ningún tooltip. Resolvamos el misterio calificándola como mala práctica por su ausencia.</em></p><blockquote>Pues el resto terminó ;) ahora, vamos a la segunda parte</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*qYmVuhy0ObLUQk-9kZmK_g.gif" /></figure><h3>Listado de problemas encontrados en los principios analizados:</h3><blockquote>En total encontramos <strong>6</strong> ejemplos de malas prácticas dentro de la web de la ACB La siguiente lista mostrará éstos principios en orden de mas a menos graves con soluciones propuestas para cada uno de ellos.</blockquote><p><strong>P 2 — Coincidencia entre el sistema y el mundo real</strong></p><p>Lo esencial es que el usuario pueda relacionar conceptos aprendidos previamente a las acciones a realizar en su experiencia en nuestra web. Debemos facilitar siempre el uso de nuestro producto al usuario.</p><p><em>Éste caso se podría resolver mediante animaciones en la UI para informar al usuario de que se ha realizado la acción, o una mayor consistencia entre los iconos usados, sus estados y sus colores.</em></p><p><strong>P 9 — Ayudar a reconocer, diagnosticas y recuperarse de errores</strong></p><p>Somos conscientes de que todos nos equivocamos, y todos hemos sido principiantes alguna vez. Por lo que es de vital importancia para el usuario sentirse capaz de resolver cualquier problema mediante las herramientas y comunicaciones que le proporcionemos</p><p><em>Para esta situación bastaría con tener ALGO en la web para ayudar al usuario, al menos una acción que te permita salir de ahí o una dirección de contacto para comunicar el error.</em></p><p><strong>P 1—Visibilidad del estado del sistema</strong></p><p>Es muy importante mantener informado al usuario sobre dónde se encuentra en el momento, o cómo ha llegado a hasta allí para no generar una sensación de estar perdido en la web.</p><p><em>Mediante migas de pan, o algún elemento distintivo dentro de la pestaña del menú accionada podríamos solventar los problemas que presenta la web.</em></p><p><strong>P10 — Ayuda y documentación</strong></p><p>Como hemos mencionado anteriormente algunas veces el usuario puede necesitar ayuda en momentos determinados y nosotros debemos proporcionársela, algunas veces como documentación extra. Para la experiencia del usuario es importante disponer de la información necesaria para entender las funcionalidades en el caso que las necesite.</p><p><em>Teniendo un repositorio de información acompañado de una batería de preguntas frecuentes, e incluso un apartado de soporte resolveríamos esta problemática. La we no posee ningún apartado de ayuda.</em></p><p><strong>P 5 — Prevención de errores</strong></p><p>En los principios previos hemos dado mayor importancia al cometer errores, esto viene dado con la premisa de que si ayudamos a los usuarios para que no erren, no habrá que ser tan incisivo en las prevenciones de los errores. No obstante, es conveniente informar al usuario previo a poder cometer el error.</p><p><em>Con el uso de ventanas emergentes o notificaciones del navegador, estaríamos informando al usuario de la situación en la que se encuentra que le puede llevar a realizar una acción no deseada</em></p><p><strong>P3—Control y libertad del usuario</strong></p><p>Debemos proporcionar una via de salida clara para el usuario en el caso que que haya llegado a un punto en el que no sepa cómo poder salir. Cuando se dan estas situaciones y no hay una acción clara para salir, se puede generar una sensación de agobio y estrés por parte del usuario.</p><p><em>Es habitual tener en los márgenes izquierdo y derecho superiores de la página acciones que te permitan volver al inicio o directamente salir, por lo que con tener habilitada una acción específica y clara para proporcionar la salida, podríamos solventar esta situación.</em></p><p><strong><em>Conclusión: Mediante éste análisis heurístico hemos podido comprobar que si ya esta web en sus versiones posteriores tenía muchos problemas de usabilidad, con este nuevo rediseño de la web no se ha notado ningún tipo de mejoría en cuanto al uso y la navegación de la página.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/84/1*GIVWR1g0h29ZYPy--hYZzA.png" /></figure><h3><strong>Muchas gracias por haber seguido leyendo hasta aquí </strong>👍</h3><blockquote>Referencias</blockquote><ul><li><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">https://www.nngroup.com/articles/ten-usability-heuristics/</a></li><li><a href="https://blog.prototypr.io/evaluacion-heuristica-9c8fce655759">https://blog.prototypr.io/evaluacion-heuristica-9c8fce655759</a></li><li><a href="https://uxplanet.org/an%C3%A1lisis-heur%C3%ADstico-de-la-p%C3%A1gina-web-de-educaci%C3%B3n-de-la-comunidad-de-madrid-cd812cf4e9cd">https://uxplanet.org/an%C3%A1lisis-heur%C3%ADstico-de-la-p%C3%A1gina-web-de-educaci%C3%B3n-de-la-comunidad-de-madrid-cd812cf4e9cd</a></li><li><a href="http://quadern-usabilitat.recursos.uoc.edu/">http://quadern-usabilitat.recursos.uoc.edu/</a></li><li><a href="https://www.uifrommars.com/10-reglas-heuristicas-como-aplicarlas/">https://www.uifrommars.com/10-reglas-heuristicas-como-aplicarlas/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b5c7d328ed3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>