<?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 Alex Gomez Perea on Medium]]></title>
        <description><![CDATA[Stories by Alex Gomez Perea on Medium]]></description>
        <link>https://medium.com/@alexgomezperea?source=rss-33af95ca060b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_7iGTpORnYDj8eojO04UFg.jpeg</url>
            <title>Stories by Alex Gomez Perea on Medium</title>
            <link>https://medium.com/@alexgomezperea?source=rss-33af95ca060b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:21:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexgomezperea/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[Dataroom by Flinco]]></title>
            <link>https://medium.com/@alexgomezperea/dataroom-by-flinco-844698938d7e?source=rss-33af95ca060b------2</link>
            <guid isPermaLink="false">https://medium.com/p/844698938d7e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Alex Gomez Perea]]></dc:creator>
            <pubDate>Wed, 20 Apr 2022 14:37:33 GMT</pubDate>
            <atom:updated>2022-04-20T14:37:33.132Z</atom:updated>
            <content:encoded><![CDATA[<h4>A product developed to help StartUps manage the necessary resources during the fundraising phase</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D2nFLr8JWnmeV7jmTPiLwQ.png" /></figure><p>From a very raw initial product, we deliver an improved proposal to our customers within 4 weeks, with which they are fully satisfied and which we propose to implement as the next stage of the product</p><p><em>Briefing — Challenge 1</em></p><h4>Understand the value of the product and the goals of the project as a starting point.</h4><p>The DataRoom is a product developed by Flinco to help startups improve the relationship between foundersand investors during the fundraising process by making it easier for investors to visualize and check critical documents <br> <br>Flinco relied on Ironhack to identify the project’s needs and create a user-centric, customizable offering</p><p><em>ReBriefing — Challenge 2</em></p><h4>Direct the focus of the project to the real needs of the stakeholders.</h4><p>At the team’s first meeting with the product’s founders, we did not see the task statement reflect the needs on which we should focus our work <br> <br>For this reason, based on the information we deepened during this meeting, we reconsidered the focus of the problem raised in the document and received satisfactory feedback from the stakeholders</p><blockquote>To find a real solution, you need a real need</blockquote><p><em>Roadmap — Challenge 3</em></p><h4>Delimiting each phase of the project in just 4 weeks</h4><p>To define the project resources within the established timeframe (4 weeks), we plan each phase with a roadmap <br> <br>Thanks to this planning, we were able to define the necessary availability of users for primary research, as well as the availability of stakeholders to receive feedback on the progress of the project<br> <br>On the other hand, we define Design Thinking as the working method intended for this project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Mem8mNsHGyuOIqLFANFhg.png" /></figure><p><em>Research Scope — Challenge 4</em></p><h4>Knowing the context of the product and define the path of research</h4><p>No one on the team knew anything about the startup world, and in order to direct the research toward valuable insights for the customer, it is necessary, as with all projects, to “soak up” information about the context of the product<br> <br>Given the stage the startup product is at, we decided to conduct exploratory research and defined the following hypotheses and objectives</p><h4><strong>Hypothesis</strong></h4><ol><li>It is a problem for users to share documentation by mail</li><li>Users (founders) have no way to manage the status of documentation</li></ol><h4><strong>Objectives of the investigation</strong></h4><ol><li>Determine the key issues in the founder-investor relationship in fundraising</li><li>Identify the level of privacy in the documents exchanged between founders and investors</li><li>Detail information management to facilitate the process of raising investment</li><li>Capture improvements in the usability of the product</li></ol><p>Secondary Research — Challenge 5</p><h4>Findings from the investigation</h4><p><strong>Understanding the niche in which the product is located.</strong></p><p>Let us put ourselves in context for those who, like us, are unfamiliar with the world of startups, investors, etc…<br> <br>StartUp: These are emerging companies that usually have a high technological component that generally supports an innovative idea</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Gx9piuJb8mD1autiNMKqQ.png" /></figure><p>After explaining the phases of StartUps, DataRoom by Flinco tries to solve the difficulties that arise in the first two phases (Seed/Pre-Seed)</p><h4>We apply benchmarking to understand what other products do</h4><p>After applying the benchmark to products like Google Drive, Ideals, Gitbook, and Readme, we found the following:</p><ul><li>Other products allow the user to know who viewed the content</li><li>The ease with which the user can customize the visualization of the space</li><li>One of the differentiating elements of the data room is how this information is displayed</li></ul><h4>Understanding users’ needs and concerns through interviews</h4><p>We conducted video interviews with 6 startup founders and learned a lot:</p><ul><li>What is your process for finding investors for your company?</li><li>We determine your main problems</li><li>What channels were used to cultivate relationships with potential investors?</li></ul><h4>Quotes:</h4><p>These are some phrases:</p><blockquote>Using email is a bit messy because context is lost in the long run, especially when multiple people are involved. Roberta Howe</blockquote><blockquote>We try to contact investors from the beginning, up to 6 months or until we get the investment we want. Javier Arias</blockquote><blockquote>It is very important to maintain communication between foundersand investors. The process has a human factor when you know the person. Daniela Limia</blockquote><h4>Context of this</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ENBYImb7UHrIrhnZI7Edag.png" /></figure><p>Thanks to the information obtained at this stage, we can create a profile that meets the needs of the investigation</p><h4>Research Conclusion</h4><p>We found out the user’s needs and made some suggestions so that the design meets those needs. <br>Find out the results (🔴) and suggestions (🔵)</p><p>🔴 Lack of centralization in documentation sharing.</p><p>🔵 Centralized location where users have access to documentation.</p><p>🔴 Lack of version control of documentation</p><p>🔵 Only the most recently uploaded version of the document can be accessed</p><p>🔴 Need to know if investors have seen updated documentation</p><p>🔵 Metric that indicates whether investors have seen the most recently uploaded document</p><h4>To present these results in a format that facilitates empathy with the user, we create the following user persona:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CfyzHtBxr8MvBsPL7Plemg.png" /></figure><p><strong>After the research, we defined a pattern of concerns that users shared and that we specified in the following problem statement:</strong></p><blockquote><em>Startup founders in the pre-seed/seed phase need a place to centralize a set of predefined information to facilitate information and communication with the potential investor</em></blockquote><p><strong>If we had to put into words the value that the product offers, we would say that:</strong></p><p><em>“Dataroom by flinco is a centralized space where you can manage the documentation of seed/pre-seed stage startups and make it accessible to investors. You can also establish communication and keep platform users updated, which facilitates the process of attracting investors”</em></p><p>We have found that the user needs a central location for sharing documentation where they can control access, know what the investor has seen, and update the information to keep the investor informed</p><p>For this we have defined the following functions:</p><ul><li>Dataroom</li><li>Updates control</li><li>Roles management</li><li>Notifications generator</li><li>Send emails</li><li>Roles and acces management</li><li>KPI’s</li><li>Documents management ( CRUD )</li><li>Initial set up</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZXs7VosysAObIsGM9y3zqA.png" /><figcaption>User Flow</figcaption></figure><h4>In the end, we defined an interactive product that met their needs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*OkRn8hawg-bfvd51mxedaA.gif" /><figcaption>Prototype</figcaption></figure><h4>Like any product, it needs a continuous improvement strategy</h4><ul><li>Research the user profile of investors to define the needs of those users</li><li>Run tests with users to validate and iterate the proposal</li><li>Generate notifications to inform users of changes to documentation</li><li>Develop a feature that allows investors to invite other investors</li></ul><h4>This is what we have learned as a team in this project</h4><ul><li><strong>Become knowledgeable about the market</strong> in which the product is located in order to guide the project to the best possible result</li><li><strong>Align the project with the actual needs of the customer</strong> rethinking the brief</li><li><strong>Ensure availability of (very busy) users,</strong> and make the most of time to secure research insights</li><li><strong>Bring the greatest possible value to the client,</strong> knowing how to guide the research with the available resources</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=844698938d7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ux/Ui Case Study: Kahoot!]]></title>
            <link>https://medium.com/@alexgomezperea/ux-ui-case-study-kahoot-cd13f57d6f35?source=rss-33af95ca060b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd13f57d6f35</guid>
            <category><![CDATA[add-a-feature]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <dc:creator><![CDATA[Alex Gomez Perea]]></dc:creator>
            <pubDate>Wed, 20 Apr 2022 12:39:40 GMT</pubDate>
            <atom:updated>2022-04-20T12:39:40.127Z</atom:updated>
            <content:encoded><![CDATA[<h4>The possibility that users belonging to a Kahoot! can react in it</h4><blockquote>An Ironhack learning project attempting to add a feature to Kahoot! that would allow participating users to react while participating in the activity</blockquote><h4>The Goal</h4><p>Analyze Kahoot! and integrate the new features without changing the experience of these users.<br>Study the market in which it competes and its users so that the new feature is integrated into the app environment without affecting the experience of those users.</p><h4>The Target</h4><p>Any user of Kahoot! but I focused on high school students between the ages of 16 and 18.</p><h3>Design Process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y7d8_0PIgE5j7wGFLs3CLw.png" /></figure><p>I used design thinking as a design method to get to know the user (their concerns and fears) through interviews and usability testing. Thanks to the information gathered, I was able to define user personas, user flow and the main problem, which helped me get closer to the solution in the ideation phase, since the user was always in the center. Finally, a prototyping and testing phase, where I will later show the iterations I made thanks to the feedback from the users and the team of teachers and classmates.</p><h4>Research Goals</h4><p>Learn how the user uses the application, what flows they use, and what frustrations they have when they want to show their feelings and emotions in a Kahoot! <br>Since the application is about teaching concepts in a dynamic and fun way, I proposed to study the user profile of high school students between the ages of sixteen and eighteen.</p><h3>Secondary Research</h3><h4><strong>Desktop Research</strong></h4><p>After exploring, I learned that Kahoot is a very useful tool for teachers and students to learn and review concepts in a very fun way because it works like a competition.</p><h4><strong>Benchmark</strong></h4><p>On the other hand, I did a competitor analysis with the Kharty and Quizizz apps to learn from them the visual language and tone of the message, and came to the following conclusions. Both are more educational and less playful in tone.</p><h3>Primary Research</h3><h4>Interviews</h4><p>I did six semi structured interviews to learn:</p><p>The frustration was that they did not have the opportunity to show their emotions in said application due to the lack of a resource to do so. This frustration was easily resolved by understanding the flow that the user displayed when using the application, as this was the key to discovering the exposed entry point later.</p><h4>Discoveries and recommendations</h4><p>After researching, I found that users want to show their emotions in the form of emojis because they are part of an activity and since they are competing, they want to show the reactions they have at that moment.</p><p>To this finding, it is recommended to set up an emoji keyboard in the app and an area on the desktop that resembles a chat where users can respond and see the reactions of other participants</p><h3>Define</h3><p>After the research phase, I filtered the information through an affinity diagram that helped define the following methods.</p><h4>Problem statement</h4><p>Students between 16 and 18 years old (teenagers) who want to show their emotions and feelings when participating in a Kahoot! do not have the opportunity to show how they feel after each question in the application</p><h4>HMW</h4><p>How can I help high school students show their emotions and feelings when they give a response and see their outcome if they do not have that resource/opportunity?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPnLoksD2ud0J570xfIGSw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8DPpD2THn3Qg2t9iKgJ55g.png" /></figure><h4>User Flow</h4><p>The next step was to give users a usability test to learn where to insert the resource to display emotions. <br>Considering the problem and knowing where the solution should be used, I moved to the third phase, where I developed the function and inserted it into the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*fbb2aZyUibkpT1ZB.png" /></figure><p><strong>Discovery of the entry point </strong><br>After analyzing the information from the research and using the flow described by the user actions, I discovered the entry point of the function I needed to add later. This was located: on the page corresponding to the mobile app, on the screen displaying the correct or not correct result of the answer. As for the page that corresponds to the view of the PC, it is on the screen that displays the graph of the results for the question that was answered by all or most of the participants.</p><h3>Ideate</h3><p>On the one hand, I addressed various use cases. Among them was the ability to respond to make fun of a partner, to express my emotions or sadness by responding in the final ranking, but the one that best suited my user as an M.V.P. was this: I want to respond as many times as I want, regardless of whether I had the answer right or wrong, until the next question begins.<br>This use case was optimal because it allows the user to respond (with the emojis previously suggested) at the end of each answer, both happy and sad in relation to their answer to the question. <br>Considering this concept, I developed possible solutions better associated with an emoji keyboard with eight possible responses mentioned by the five users, four of which were positive and the other four negative, as they all agreed that they only responded positively or negatively and they wanted a balance of responses. <br>Also mention that one of the interview questions was <em>‘’How would you translate your emotions into emojis?’’</em>. With that, they pointed out what emojis they would like to see in the functionality I would implement next.</p><h3>Design Evolution</h3><h4>First Design</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*k8lv3UPN5yScsDmY.png" /></figure><p>This was the first concept that went into the prototype as an idea: the ability to display the eight responses that users named as best describing their emotions before the results of the Kahoot! and a column showing each student’s response. After testing it with the five users, they suggested me to reform the elements because there was a lot of information presented and many elements together that made it difficult to understand.</p><h4>Second Design</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*sfYftgflNa76tYzX.png" /></figure><p>After consulting with a team of classmates and teachers, I concluded to propose another idea to improve on the previous one. In a second iteration, I removed the speech bubble element to increase the user’s expression and decided to place the user’s name next to the reaction emoji to create a visual hierarchy. After testing with the five users who joined me for the project testing, two issues arose. First, there were still too many elements in the reaction column, and second, the name could not be very long because it was truncated when placed next to it</p><h3>Last Desing and Implementation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ho8x58mliKk9tBNjDr4fUQ.png" /></figure><p>As a final and satisfactory idea for the five users, and having previously tested the idea twice with them, the following emerges: <br>It is a slightly minimalist column that satisfies the five users because it contains the necessary elements to satisfy their frustration. Users will find a button that allows them to display their emotions in a uniform size, and below it is their name, which can be as long as the characters that the app agrees to place on top. <br>On the other hand, it finds a harmony in the components that the solution includes, making it effective and with the possibility of execution by the Kahoot! team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*1c3Ni8C0bOL518YoaGw5kg.png" /></figure><h3>Conclusion</h3><p>What I have learned in this project is to always have the user and their concern by their side to move the project forward step by step. Thanks to them, the development that has acquired this feature is passed on until the final idea has adequately solved the frustration of the user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd13f57d6f35" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wellness project — Pregnancy app Case Study]]></title>
            <link>https://medium.com/@alexgomezperea/wellness-project-pregnancy-app-case-study-5bdf8adfde27?source=rss-33af95ca060b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bdf8adfde27</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <dc:creator><![CDATA[Alex Gomez Perea]]></dc:creator>
            <pubDate>Wed, 20 Apr 2022 11:58:39 GMT</pubDate>
            <atom:updated>2022-04-25T18:52:44.542Z</atom:updated>
            <content:encoded><![CDATA[<h3>Wellness project — Pregnancy app Case Study</h3><h4>Pregnancy 2: an app for a pregnant woman’s partner that address her needs.</h4><h3><strong>Project Overview</strong></h3><h4><strong>The Goal</strong></h4><p>This project consists of performing a complete UX/UI design process to design a mvp. The theme must cover an aspect of wellbeing that the team deems important (supported by user research). The design must meet the following objectives:</p><ol><li>Basic functions to log in/register, set the profile and the goal to reach</li><li>Visualization of progress</li><li>The user flow for the main function of the app.</li></ol><h4><strong>The Context</strong></h4><p>As a team, we chose the theme of pregnancy and fetal development, which we eventually specified as the design for an app for a pregnant woman’s partner, regardless of her gender. We found it interesting to develop an app where the user is the other side of the coin, namely the partner of the pregnant woman. With this unusual objective, we covered the needs of two users when it came to tracking the pregnancy process of their future baby.</p><h4>The Target</h4><p>Pregnant couples between the ages of 30 and 36 who want to become parents.</p><h4>Design process</h4><p>I followed an interactive user-centered design approach in which we have to focus on the users and their needs in every steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oP-9NxRouNrlrAp_utCSew.png" /><figcaption>Design Thinking Process</figcaption></figure><h4><strong>Research Goals</strong></h4><p>To approach the study, we set some goals that reflect what we want to learn from it and what we want to recognize in it:</p><ol><li>To understand the needs and concerns of the pregnant person</li><li>Know the development of the fetus and the stages of pregnancy</li><li>Recognize hormonal changes and mood swings in the pregnant person</li><li>To understand the fears and concerns of the pregnant woman’s partner</li></ol><p><strong>The Hiphotesis</strong></p><p>When it comes to narrowing down the topic, we specify the why through hypotheses, which we then contrast through research:</p><ol><li>There are few products on the market that focus on the person accompanying the pregnant woman during the process.</li><li>The pregnant person is concerned about the development of the fetus, as well as the development of the family and the relationship with her partner.</li><li>Pregnancy is a matter of two people.</li><li>When the pregnant woman’s partner is more involved during pregnancy, the family grows on a solid foundation and the couple’s bonds become stronger.</li></ol><h3><strong>Discover</strong></h3><p><strong>Desktop research</strong></p><p>We conduct exploratory desktop research to learn more about pregnancy, its stages, and the development of the pregnant person’s body and mind.</p><p><strong>Benchmarking</strong></p><p>We looked at competitors like Pregnancy + and Daddy up, which we learned presented information in a visual way and lacked tips to help a woman during pregnancy and things to consider during childbirth and postpartum</p><p><strong>Qualitative research</strong></p><p>We interviewed around 11 people who were pregnant or be the couple of this pregnant to understand what difficulties they came across while pregnancy.</p><p><strong>Interviews conclusion:</strong></p><p>As a conclusion of this investigation, we note that:</p><ul><li>The pregnant woman tries to give her partner all the information she can find, and this disturbs her</li><li>The pregnant woman’s partner feels excluded from the relationship because he thinks that the pregnant woman only cares about her pregnancy</li><li>The pregnant woman wants her partner to be more involved because it frustrates her that she has to manage the pregnancy process alone</li></ul><p><strong>Discoveries and Recommendations</strong></p><p>Pregnant women need company and moral support during pregnancy <br>The couple of pregnant women do not have enough information about pregnancy because they do not do research.</p><p>When creating the design, it is advisable to include a section that clearly informs the couple on how to accompany the pregnant woman during pregnancy, as well as advice so that she can help her partner.</p><h3><strong>Define</strong></h3><p>After the research phase, the information was filtered through an affinity diagram that facilitated the definition of the following methods.</p><p><strong>Problem Statement</strong></p><p>People between 30 and 36 who become parents need information on how to be more involved in the pregnancy process, because their partner needs to feel accompanied (not alone).</p><p><strong>HMW</strong></p><p>What can we do to ensure that men between the ages of 30 and 36 who are going to be parents have information about how to support their partner in pregnancy so that she feels accompanied?</p><p><strong>Value Proposition</strong></p><p>Pregnant2 is an assistant for users whose partner is pregnant. It helps them to know what is happening with their partner and gives them advice so that they feel supported.</p><p><strong>Empathy map</strong></p><p>We used the empathy map to understand and prioritize user needs. It helps me get closer to what he is thinking and feeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q5ESJaXqybZJ-r1DBAuwWw.png" /></figure><h3><strong>Ideate</strong></h3><p><strong>Site map</strong></p><p>For this MVP, we create a simple site map that contains all the pages that this app needs to contain all the information and features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*jxrF-LJyszvFlS0KTRsaPg.png" /></figure><p><strong>User Flow</strong></p><p>On the other hand, we define a user flow, which is the path a typical user takes on a website or in an application to complete a task. The user flow consists of the point at which he enters and adds the steps he performs until he completes the task with a successful result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RtIWVXrlRyAy_o39jOMctQ.png" /></figure><h3><strong>Design Evolution</strong></h3><p><strong>Low / Mid-fi</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*8Kiv6yFiAInRthHjMwOcUQ.png" /></figure><p>This was the skeleton proposed to meet the needs of users and structure the functions that the product should have as an MVP. The first part consists of a prompt for the user to create an account or log in to fulfill one of the requirements. <br>Next, the progress is displayed as a percentage of the pregnancy your partner is carrying (according to the delivery date information you entered). Among other things, we thought it would be useful to have a visual representation of the fetus, as well as height and weight, and one or more curiosities of the fetus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*DXyiYKPEKvPXa9ir0l4HDg.png" /></figure><p>We also considered (based on the information provided by the research) adding a calendar to record doctor’s appointments in addition to other activities. <br>Finally, we needed a profile area to enter the necessary data and an area to give the pregnant woman’s partner the much needed advice to help her with the pregnancy.</p><p><strong>High-fi</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*vY-CD2UL14LUYTCBAhDYtw.png" /></figure><p>The next step was to add the visual elements that completed the interface (colours, logo, and information) that resulted from the research and style tile. Once the first design was ready, it could be tested with users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*RerqoydWGUXoTmYbQ5UmpQ.png" /></figure><p><strong>Conclusion of the test</strong></p><p>After an initial test, we found that:</p><ul><li>There were elements that were confusing because they seemed attackable (length and mass).</li><li>The hierarchy of the elements did not have the right order, which confused users when searching for information</li><li>And another very valuable feedback we received on the logo and colors is that it is not suitable for all users we are targeting.</li></ul><p><strong>Last Design and Implementation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LRlL4NsmbY0ph0PN9gyW2g.png" /></figure><p>After receiving feedback from users, classmates, and teachers, we moved to a second iteration to address the issues raised. We changed the logo and colors to be inclusive. First, the logo does not represent gender and the purple color represents the union of men and women. Also note that we changed the layout of the elements to make it easier to search for information as well as navigate by week at the top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rTZFF9CYzKqNkUjNe77kyA.png" /></figure><p>Finally, we added some modal windows as notifications that remind users of interests or appointments they have in their calendar.</p><h3><strong>Next Steps</strong></h3><ul><li>Retest the app with users and iterate, taking their feedback into account.</li><li>Add another feature (to include after birth) that solves another user concern.</li></ul><h3>Conclusion of The Project</h3><p>I have divided the learning I have received in this project into two types, personal learning and professional learning. Regarding personal learning, I can say that I have developed as a person because I have been able to break with the labels that exist today regarding gender.</p><p>This application is not about gender, it is about a pregnant person and another accompanying them in the process to engage and grow as a family and as a couple. On the other hand, the professional insights were the following: <br>To create the design of an application that not only focuses on the user, but also covers a very important topic such as health. <br>And finally, pointing out the importance of the information hierarchy to help the user navigate the app and find information.</p><h4>My role</h4><ul><li>Design Strategy</li><li>Problem Solution</li><li>Users Interviews</li><li>Competitive analysis</li><li>User Research</li><li>Affinity Diagram</li><li>User Persona</li><li>Empathy Map</li><li>User Flow</li><li>Information Architecture</li><li>Wireframes</li><li>Visual Design</li><li>Prototype</li><li>Improve the design considering user feedback</li><li>Usability testing</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bdf8adfde27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ux/Ui Case Study: Kahoot!]]></title>
            <link>https://medium.com/@alexgomezperea/ux-ui-case-study-kahoot-bab1e5dec1fb?source=rss-33af95ca060b------2</link>
            <guid isPermaLink="false">https://medium.com/p/bab1e5dec1fb</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <dc:creator><![CDATA[Alex Gomez Perea]]></dc:creator>
            <pubDate>Sun, 20 Feb 2022 11:35:44 GMT</pubDate>
            <atom:updated>2022-03-04T18:26:28.636Z</atom:updated>
            <content:encoded><![CDATA[<h4>La posibilidad de que los usuarios que pertenecen a un Kahoot!, puedan reaccionar dentro del mismo.</h4><blockquote>Un proyecto individual de Ironhack en el camino formativo para ser Ux/Ui Designer, que exprime lo mejor de mí y lo aprendido hasta la fecha.</blockquote><p>Después de encontrar la armonía del trabajo en grupo, llega ese gran día el cual el profesor notifica que el siguiente proyecto se efectuará de manera individual. Asombrado y aterrado por la situación que se me planteaba, decidí coger las riendas de mi ser y afrontar con honor un reto de tan enorme responsabilidad. <em>Ha llegado la hora de demostrar lo que hemos aprendido. — </em>Me dije. Así que empecé por organizarme mediante un roadmap y en éste dividirme el proceso en dos: por un lado investigación y por otro diseño e implementación de la solución. Este sistema de organización facilitaría el entendimiento y desarrollo de la funcionalidad que implementaría más adelante: hacer que los usuarios que participan en un Kahoot puedan reaccionar en él. Con el usuario en mente empecé el proceso por investigar la plataforma Kahoot y todo lo que el usuario puede hacer en ella.</p><h4>Objetivo</h4><p>En primer lugar me propuse como objetivo de investigación aprender cómo el usuario usa la aplicación, saber qué flujo utiliza y cuáles son las frustraciones de éste a la hora de querer mostrar sus sentimientos y emociones mientras forma parte de un Kahoot!.<br>Puesto que la aplicación trata sobre la enseñanza de conceptos de forma dinámica y divertida, el perfil de usuario que planteé investigar fueron los alumnos de bachillerato entre dieciséis y dieciocho años.</p><h4>Investigación y aprendizajes principales</h4><p>Seguidamente mediante entrevistas a cinco usuarios pude concluir que la frustración se hallaba en no tener la oportunidad de mostrar sus emociones en dicha aplicación puesto que esta carece de un recurso para poder hacerlo.</p><p>Dicha frustración fue fácil de resolver entendiendo el flujo que mostraba el usuario al usar la aplicación ya que esto fue la clave para descubrir el entry point expuesto más adelante.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hb8oCnuM-f8vPBbPPLzug.png" /><figcaption>User flow</figcaption></figure><p>El siguiente paso fue hacer a los usuarios un test de usabilidad para aprender dónde introducir el recurso para mostrar las emociones.</p><p>Teniendo en cuenta el problema y saber dónde aplicar la solución entré en la segunda fase, idear y añadir la característica a la aplicación.</p><h4>Descubrimiento del Entry Point</h4><p>Tras el análisis de la información proveniente de la investigación, y con la ayuda del flujo descrito por las acciones del usuario, descubrí el punto de entrada de la característica que tendría que añadir posteriormente. Esta se situaba: por el lado que corresponde a la app en móvil en la pantalla donde se muestra el resultado acertado o fallido de la respuesta; en cuanto al lado que corresponde a la vista del pc éste se encuentra en la pantalla donde se muestra la gráfica de resultados a la pregunta contestada por todos o la mayoría de los participantes.</p><h4>Ideación</h4><p>Por un lado, planteé diferentes casos de uso. Entre los cuales se encontraba la posibilidad de reaccionar para mofarse de un compañero, expresar mi emoción o tristeza reaccionando en el ranking final, pero el que se ajustaba mejor a mi usuario como M.V.P. fue el siguiente: <em>Quiero reaccionar las veces que quiera, tanto si he acertado o he fallado en la respuesta, hasta que empiece la siguiente pregunta. </em>Ese caso de uso era óptimo ya que le da la oportunidad al usuario de reaccionar ( con los emojis propuestos anteriormente ) al final de cada respuesta, tanto feliz como triste en relación a su contestación a la pregunta.</p><p>Teniendo este concepto en cuenta, ideé posibles soluciones la cual se vinculaba mejor el hecho de tener un teclado emoji con ocho posibles reacciones mencionadas por los cinco usuarios, cuatro de las cuales positivas y las otras cuatro negativas, ya que todos coincidían que solo reaccionaban positiva o negativamente y querían un equilibrio de reacciones. También mencionar que una de las preguntas de la entrevista era: ‘‘<em>¿ Cómo traducirías tus emociones en emojis ?</em>’’. Con ella me hacían conocedor de qué emojis querrían ver en la funcionalidad que implementaría seguidamente.</p><h4>Primer Diseño</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y8wgUIp7oTbq1S0h8Og63A.png" /></figure><p>Este fue el primer concepto plasmado en el prototipo como idea, la posibilidad de tener las ocho reacciones mencionadas por los usuarios como las que mejor definían sus emociones antes los resultados de las respuestas del Kahoot! y una columna donde ésta muestra la reacción de cada alumno. Tras probarla con los cinco usuarios me plantearon la reforma de los elementos, ya que se presentaba mucha información y muchos elementos juntos que dificultaban el entendimiento.</p><h4>Segundo Diseño</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fp4avjWaKlQWKb5aYvuNiw.png" /></figure><p>Tras alinearme con un equipo de compañeros y profesores llegué a la conclusión de plantear otra idea para mejorar la anterior. Como segunda iteración, quité el elemento bocadillo para poder agrandar la expresión de los usuarios y decidí ubicar el nombre del usuario al costado del emoji de reacción para que adquiriera mayor jerarquía visual. Tras el testeo con los cinco usuarios que me acompañaron en los tests del proyecto, surgieron dos problemas, por un lado seguían sobrando elementos en la columna de reacciones y por otro lado al poner el nombre al lado, éste no podría ser muy largo puesto que quedaba cortado.</p><h4>Último Diseño e Implementación</h4><p>Como idea final y satisfactoria para los cinco usuarios, y tras anteriormente testear dos veces la idea con ellos, surge lo siguiente: <br>Se trata de una columna ligeramente minimalista que satisface a los cinco usuarios puesto que tiene los elementos necesarios para satisfacer su frustración. Los usuarios encuentran un botón con el cual pueden mostrar sus emociones de un tamaño coherente, y debajo se muestra su nombre, que puede ser tan largo como los caracteres la aplicación acepta poner al inicio. <br>Por otro lado encuentra una armonía en los componentes que la solución comprende, haciendo que la solución sea efectiva y con posibilidad de que sea llevada a cabo por el equipo de Kahoot!.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*CNxGF3oVmMObYz1EoxVvRw.png" /></figure><h4>Conclusión</h4><p>Lo que he aprendido de este proyecto es tener siempre al lado al usuario y su preocupación para que pueda avanzar el proyecto paso a paso. Gracias a ellos se transmite la evolución que esta característica ha ido adquiriendo hasta que la idea final solucionaba perfectamente la frustración del usuario.<br>Finalmente, expresar lo orgulloso que estoy de este proyecto porque he podido demostrarme a mí mismo todo lo aprendido hasta el día de hoy, mostrando las capacidades adquiridas y desarrolladas en el corto camino que ha durado este proyecto.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bab1e5dec1fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Challenge 2: Wire framing]]></title>
            <link>https://medium.com/@alexgomezperea/ironhack-challenge-2-wire-framing-15cb963ea89c?source=rss-33af95ca060b------2</link>
            <guid isPermaLink="false">https://medium.com/p/15cb963ea89c</guid>
            <dc:creator><![CDATA[Alex Gomez Perea]]></dc:creator>
            <pubDate>Thu, 16 Sep 2021 13:46:15 GMT</pubDate>
            <atom:updated>2021-09-16T13:46:15.078Z</atom:updated>
            <content:encoded><![CDATA[<p>An experience making wireframes and designing prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*nvaPwOww18jSCE0zrDesUw.png" /><figcaption>Twitch.tv</figcaption></figure><h3>Why twitch.tv?</h3><p>First I’d like to say that I choose Twitch.tv to work with because it’s a platform what is permanent evolution and have a lot of users of all ages. Twitch is a video live streaming service that focuses on videogames but now is working on more important thinks like creative content or music lives. Therefore, its becoming a way to reach all the users.</p><h4>Pathing of the wire framing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YletYlkmj777U8Mex5O80Q.png" /></figure><p>On the one hand I prepare a low-fidelity wireframes with pen and sheet of paper. It was an easy work because it’s understandable on the explained ironhack lessons. On the other hand I worked with a little FigJam file to do a brainstorm for study the layout of my wireframes. Hope you don’t judge me because it’s my first time doing this kind of draws.</p><p>According to the next step and using this little sketch, I get to work to mid-fidelity wireframes. Fortunately I had some help with wireframe kit, this made the work easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CoMYLHlM4-S4mrxPq0vOEg.png" /></figure><p>In my opinion it was a funny design method, laborious but entertaining. As you can appreciate I used some UI elements like buttons, drop-down buttons, text fields and icons among others.</p><p>High-fidelity:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqjvJGj0ykk0mSZErSyJ8Q.png" /></figure><p>Prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hfKq7Ft-qCxu9hHefgmnVQ.png" /></figure><p>Finally I’d like to say that I’m proud of my work and hope you can enjoy it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15cb963ea89c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework UrbanGo_Challenge1]]></title>
            <link>https://medium.com/@alexgomezperea/why-urbango-could-be-the-best-public-transport-company-17b2133eb717?source=rss-33af95ca060b------2</link>
            <guid isPermaLink="false">https://medium.com/p/17b2133eb717</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Alex Gomez Perea]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 09:52:30 GMT</pubDate>
            <atom:updated>2021-09-08T09:57:52.136Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why UrbanGo could be the best public transport company?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*oSY56iCEki4GYzx0_S2TQQ.png" /></figure><p><em>UrbanGo is a public transit and mapping startup based in Silicon Valley. As a company, they are helping people who need to take some kind of transport, public (underground, train, trolley car) or private ( taxi, electric motorcycle or bikes). They are enviromentally sound, therefore they want to search the most sustainable way to travel.First at all we interviewed a number of people who often took the public transport to listen which were their experience taking transport. They told us that expend lot of time buying tickets and the other problem were lot of kinds of tickets.</em></p><p>First of all, we interviewed a number of people who usually take public transportation, to listen which was their experience. They told us that spend a lot of time buying tickets and the other problem was the amount of different tickets available.</p><p>So, how to solve this …</p><h3>We started with a research to understand what’s the main problem, and then, we used brainstorming make a prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SiSmQH-CV_jPZL0LZ5ietA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3kMhWjYyFUqkIg8Y7rbdSw.png" /></figure><p><strong>Solution …</strong></p><p>We designed a feature for their app to facilitate the ticket purchasing procedure. We took into account all kinds of people who take public transport abroad, and also the length of their stay. Once bought your ticket, you must sing up for own your QR code. You can obtain it from multiple ways, downloading it into your phone’s wallet or from an e-mail receipt ( thinking on people who have their screen broke or people who prefer have this document printed ). Finally I thought of the possibility of making a recycled plastic card available for free if you choose the complete package.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17b2133eb717" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>