<?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 Javier Escobedo  on Medium]]></title>
        <description><![CDATA[Stories by Javier Escobedo  on Medium]]></description>
        <link>https://medium.com/@javier.escobedo.91?source=rss-17d6c8007de8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-l8pwUtGLinBIoD0l90YDA.jpeg</url>
            <title>Stories by Javier Escobedo  on Medium</title>
            <link>https://medium.com/@javier.escobedo.91?source=rss-17d6c8007de8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:12:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@javier.escobedo.91/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[Project 4 — Wellness App for the Daily Health Conference]]></title>
            <link>https://medium.com/@javier.escobedo.91/project-4-wellness-app-for-the-daily-health-conference-dfe138f911dc?source=rss-17d6c8007de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfe138f911dc</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[aging-well]]></category>
            <category><![CDATA[collaborative-learning]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <dc:creator><![CDATA[Javier Escobedo ]]></dc:creator>
            <pubDate>Sun, 04 Aug 2024 22:26:09 GMT</pubDate>
            <atom:updated>2024-09-20T10:51:27.857Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Project 4 — Wellness App for the Daily Health Conference</strong></h3><figure><img alt="Image hero showing the logo of Everwell’s app, along with two mobiles displaying two different pages of Everwell; as a background there is a valley." src="https://cdn-images-1.medium.com/max/1024/1*kuW9F4_0l2hHR4jZA_e14g.jpeg" /><figcaption>Welcome to Everwell’s case study</figcaption></figure><h3>Introduction</h3><p>As part of IronHack’s bootcamp, the fourth project was to develop a wellness app for the Daily Health Conference. The brief was as follows:</p><p><em>The Daily Health Conference, facing declining memberships due to slow tech adoption, seeks to develop innovative wellness apps. Designers will research user habits, create an MVP of a disruptive wellness tool, and pitch ideas to a jury. The winning concepts will be integrated into their offerings and unveiled at the annual conference, aiming to enhance member value with digital health services like diet plans, fitness programs, addiction management, and water intake tracking.</em></p><p>Once the brief and groups were defined, Elvira Infante and I set a to-do list for our team: introduce our weaknesses and strengths since it was our first time working together, define a roadmap with a timeline displaying the tasks to achieve, and define the area we wanted to work on for the app. This proved particularly challenging given the broad wellness topic; we conducted initial secondary research to identify possible unattended niches.</p><p>After discussions, we found two possibilities: in-home care (related to healthy aging, as articles like one from <a href="https://www.mckinsey.com/industries/consumer-packaged-goods/our-insights/whats-new-in-consumer-wellness-trends">McKinsey</a> indicated an increasing trend among millennials to look after their own health) and women facing menopause. Although the second topic was more interesting to me, we decided to avoid it due to time constraints and the difficulty of finding a user pool for our research.</p><h3>User Research Strategy</h3><p>With a defined topic, we were ready to begin the process and crafted our Lean UX Canvas. This step was challenging since neither of us had previous experience creating one. We were unaware of the required precision or depth needed to describe our market research fundamentals, along with hypotheses and riskiest assumptions. However, with time and lectures, we completed it and crafted our survey to gather quantitative data.</p><p>We launched the survey and received 50 responses, providing valuable information as you can see in the image below:</p><figure><img alt="Image with five different research results: 84% of respondents aged 30–45 measure their health data at home; 96% considered regular exercise the most important routine, followed by good nutrition; 65% stated preventing health issues as their main motivation; 60% document their health metrics on an app; 74% visit the doctor at least once a year for general check-ups" src="https://cdn-images-1.medium.com/max/1024/1*uRrSZq_0pC3Zq1r-PZvj9g.jpeg" /></figure><p>Following our converging approach, we conducted qualitative research to gain insights that would help us orient our project more tangibly. The insights were classified by trends such as healthy aging perceptions, search-data-documenting, healthy self-done habits, lifestyle change motivations, and achievement/goals/new habits setting. The last category aligned with our secondary research, highlighting the challenge of setting and maintaining long-term goals.</p><h3>Empathy to Our Users</h3><p>With the first part of our research complete, our next task was to create a <em>Persona</em> representing our interviewees. Below you can find his graphic, as well as his painful story:</p><figure><img alt="Image displaying the Persona; his name is Paco aka Pancho. The imae shows as well details such as his age, occupation, about, behaviours, goals and frustrations." src="https://cdn-images-1.medium.com/max/1024/1*vnOaRYuMi4ezXH0qJ_LBYg.jpeg" /><figcaption>Paco aka Pancho: our persona, based on our research</figcaption></figure><blockquote>Pancho, a 32-year-old Mexican software developer living in Madrid, spends most of his day in front of a computer. Recently, he started experiencing back pain due to long hours of poor posture at work. One evening, he opted to walk instead of taking the subway, only to suffer from a recurring leg cramp. Determined to find relief, he tried home exercises and balms, which helped temporarily. However, job stress prevented him from maintaining these positive changes, and the pain returned.</blockquote><blockquote>After visiting a doctor, Pancho was advised to change his habits or face serious health issues. Despite his determination, Pancho struggles to turn new routines into lasting habits without a specific goal. Desperate for a solution, he searched for motivation tools on his phone but found nothing effective. Pancho needs a way to stay motivated and consistent in adopting healthier habits to avoid future health problems.</blockquote><p>With Pancho’s situation in mind, we defined our problem statement:</p><p><em>Millennials who are concerned about their long-term health need to find a way to take steps to improve their long-term trajectory because maintaining a healthy lifestyle is currently challenging for them.</em></p><p>Alongside the problem statement, our team formulated the How Might We (HMW) statement to address Pancho’s problem:</p><p><em>HMW help users set and achieve goals, stay motivated and consistent with new habits, and make the process enjoyable and rewarding?</em></p><h3>Ideation</h3><p>With exercises such as Crazy 8s and MoSCoW, our project began to take shape. We developed ideas and voted for the most interesting ones, establishing our Minimum Viable Product (MVP): At a bare minimum, users should establish consistent habits, track activities, and record metrics. Users can set goals, track progress, learn about their progress on relevant pages, and manage their privacy data, including export or deletion options.</p><p>Next, we defined our User Flow to understand the sequence of steps Pancho would take to use our product. We struggled with how broad or narrow to develop the user flow, ultimately focusing on paths we could develop into Hi-Fi wireframes. In the image below, there’s only one input, while there are two different outputs; the one on top refers to account settings, which was not part of the deliverables’ scope.</p><figure><img alt="The image shows a user flow with one input, two different outputs" src="https://cdn-images-1.medium.com/max/1024/1*8TAkF1uYPOcp9D3ZIWT6ug.jpeg" /><figcaption>The user flow depicts one entry point, and three different outputs</figcaption></figure><h3><strong>Execution: Low-Fi &amp; Mid-Fi Wireframing</strong></h3><p>In this phase, I felt more confident as developing sketches and proposals is my strength. We sketched up to two suggestions for each page, explained them to the team, and voted on the most suitable options, including comments and additions. This process was smooth, allowing us to fast-track and compensate for extra time spent on research.</p><p>Generating Mid-Fi wireframes and prototypes was a team effort. We quickly had the wireframes ready, with only the prototype missing before user testing. I volunteered to build the prototype and polish details, while Elvira created the Moodboard and Busola scheduled testing sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oM8ykhbenAo7JOPwsz0KoQ.jpeg" /><figcaption>Mid-Fi wireframes showcasing the steps to create a new goal within the app</figcaption></figure><p>User testing revealed areas for improvement. Modifications were made at a Mid-Fi level to discuss them before creating Hi-Fi wireframes.</p><h3><strong>Style Tile &amp; Hi-Fi Wireframing</strong></h3><p>The previously created Moodboard saved time by aligning on images and desired emotions. Using the Moodboard, we developed a chosen page on Hi-Fi level individually, compared them, and chose the best features and visual elements.</p><p>Finally, we split the work due to time constraints: I focused on Hi-Fi wireframes and prototype (given my Figma experience), while Elvira worked on the Style Tile (image below) and presentation with Busola. The team worked functionally, everyone felt heard, and we achieved a collaborative synergy in the final product.</p><figure><img alt="Image showing the style tile of the prject including the logo, typography, colours, iconography, and UI elements." src="https://cdn-images-1.medium.com/max/1024/1*32QYwXxqmcCTa8XUG2hkxw.jpeg" /><figcaption>Style tile for our project — while I was working on the Hi-Fi wireframes, I was providing the elements while Elvira would complete the tile and add them</figcaption></figure><h3>Final Product and Takeaways</h3><p>With Everwell, users like Pancho can set new short- or long-term goals. The app provides a form to fill in requirements such as type of activity, desired age for achieving the goal, and time availability. It will also sync medical data or allow users to enter it manually and will provide a weekly list of activities to complete. For example, if Pancho wants to hike Mount Fuji at 65, he will receive a list of tasks to perform weekly to achieve that goal.</p><p>I’m glad to say this project was a great learning experience that really sharpened my skills in user research, collaboration, and design. We faced some challenges, like narrowing down our focus and perfecting our user flow, but it taught me how to adapt and work effectively with a team. Balancing creativity with practicality was key, and I realized just how powerful a user-centered approach can be. Overall, it was a rewarding journey that highlighted the importance of teamwork and innovative thinking.</p><figure><img alt="Image showing the hi-fi wireframes, organised in tiles" src="https://cdn-images-1.medium.com/max/1024/1*bK2pedU92N7OwiIrVB87bQ.jpeg" /><figcaption>These are the final hi-fi wireframes.</figcaption></figure><p>And of course, if the project continues, further iterations would involve plenty of fixes, testing, and deployment, all over again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfe138f911dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project 3: Redesigning an App]]></title>
            <link>https://medium.com/@javier.escobedo.91/project-3-redesigning-an-app-03ec0b609aef?source=rss-17d6c8007de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/03ec0b609aef</guid>
            <category><![CDATA[softskillsimprovement]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Javier Escobedo ]]></dc:creator>
            <pubDate>Sun, 28 Jul 2024 18:14:31 GMT</pubDate>
            <atom:updated>2024-07-28T18:25:35.030Z</atom:updated>
            <content:encoded><![CDATA[<p>After the eventful experience I had in the second project of the bootcamp, my inner designer was craving a new challenge and the chance to work with skilled and talented people to redeem the previous outcomes. Therefore, I was more than honored to team up with my colleague <a href="https://medium.com/@niamh.ac">Niamh Akiboye</a> for this short, yet intriguing project.</p><figure><img alt="An image showcasing three high fidelity mock ups in a dark, abstract background" src="https://cdn-images-1.medium.com/max/1024/1*u_3fdV1dKllq7CYRssuBmw.jpeg" /></figure><h4><strong>Introduction</strong></h4><p>The brief was simple yet challenging: redesign an existing app, focusing on 2–4 pages, and justify our changes. It sounded relatively easy, especially since no user research was required within the two-day timeframe.</p><p>Like any professional team, Niamh and I quickly decided on an app to work on. Honestly, I had no specific apps in mind. My reasoning was:</p><ul><li>We could work on a random app that functions decently well, or</li><li>We could find a problematic app, where our improvements would stand out even more, given our combined six years of experience in UI design.</li></ul><p>Initially, I thought of Grindr, notorious for its toxic user environment, as an interesting challenge. However, Niamh had a trump card: the Uniqlo app. Though I had only seen the store in some malls in other countries, the moment I downloaded and tried to use the app, I knew this was our golden ticket to success. More on that later…</p><h4><strong>Project Material: Uniqlo’s App</strong></h4><p>For those unfamiliar with Uniqlo, it’s a Japanese casual wear designer, fast-fashion manufacturer, and retailer with stores throughout Europe. The app, launched in the App Store several years ago, offers benefits like exclusive promotions and shopping history. However, it provides little value to customers. The e-commerce elements are not built into the app, and the navigation of existing features is confusing and convoluted.</p><figure><img alt="An overview of five different screenshots of the current Uniqlo app, with a dark, abtstract background" src="https://cdn-images-1.medium.com/max/1024/1*HAD3TcQRkMnEgDiUYgE9Lw.jpeg" /><figcaption>In the image above, we can see a quick overview of the so unhappy path users have to go through when trying to search for an store with the existing app.</figcaption></figure><p>We had our work cut out for us. We knew this app needed urgent changes on many levels. The next step was to conduct a detailed heuristic analysis using the Norman Nielsen 10 usability principles, examining not only the negative aspects but also the positive ones.</p><p>This activity gave us a comprehensive overview of the app’s situation, highlighting the most pressing issues needing immediate action and allowing us to align on the problems we wanted to tackle. Although it’s not part of the “playbook,” one of us suggested generating “How Might We” statements, both on a general and consolidated level. This new approach fueled our creative process — sometimes bending the rules can be beneficial.</p><p>After analyzing the few elements within the app, our dynamic duo agreed to focus on two main pages: the welcome page and the store finder page. We then worked directly on lo-fi mockups to compare our solutions.</p><p>With our combined expertise, the process went relatively quickly. By explaining our design ideas to each other, some elements or features were immediately accepted, while others required further discussion. However, with a clear goal and proper communication, potential designer ego conflicts were replaced by solutions. We each developed hi-fi mockups to ensure no one felt their ideas were disregarded.</p><p>With the goals clear, we split the work: while both of us contributed to the components, Niamh worked on the home page and elements like dropdown menus and info modals, while I focused on the store finder page. Once the hi-fi mockups were completed, the next steps involved refining the prototype, consolidating other deliverables such as the style tile, and tidying up the design file.</p><p>I must admit that tidying up files and following naming conventions is one of my weaknesses. This project definitely helped me improve in this area, as we finished well before the end of the day, allowing us to allocate the remaining hours to perfecting our work.</p><figure><img alt="A screenshot of a figma file containing ten different sections, each one with multiple details, assets and texts." src="https://cdn-images-1.medium.com/max/1024/1*8Bw6A_Gokp1PmrkpWbsyCA.png" /><figcaption>Learning how to document all the assets and the process is as important as presenting the project itself, particularly when it has the potential to be scaled up.</figcaption></figure><h4>Results</h4><p>As part of the improvements, the home page’s content was reorganized and reduced. In the original page, too many elements were duplicated (e.g., the “Home” item appeared twice), and the hamburger menu had little value since almost all options linked to an embedded website. Additionally, the icons were misaligned in purpose, and Uniqlo’s logo was nowhere to be seen.</p><p>For the original store finder page, the magnifying glass icon appeared up to four times, the search options labels mismatched their purposes (e.g., selecting “city” displayed a list of all federal states in Germany), and no results were provided after selecting the options.</p><p><strong>In our improved version, the following changes were made:</strong></p><p><strong>Homepage:</strong></p><ul><li>Added logo and page title to orient users.</li><li>Removed “Cart” icon and added a clear “SHOP” label with an icon indicating behavior.</li><li>Eliminated the hamburger menu and search bar to avoid duplicated content.</li><li>Moved marketing copy up on the hero banner so the button is not hidden on smaller devices.</li><li>Moved pagination to the top of the image.</li><li>Redesigned the footer/nav bar to include key app features like coupons and news. Also, renamed the items for clarity.</li></ul><figure><img alt="Image with two versions of the homepage, showing the before and after state after redesigning." src="https://cdn-images-1.medium.com/max/1024/1*X_Buuii6laQvoqQwDo5Pwg.jpeg" /><figcaption>In the image above, the changes on the homepage are visible by comparing both versions</figcaption></figure><p><strong>Store Finder:</strong></p><ul><li>Prioritized search and filter as the first action (in the original screenshot, the map is calculated based on unknown information since the user location is not shared). The redesign shows a broader range of options for users who do not share location.</li><li>Condensed search and filter items slightly.</li><li>Added a country selector.</li><li>Updated the city selector to show only cities with Uniqlo stores.</li><li>Added filters as pills to allow more options.</li><li>Included more filter options.</li><li>Added a help icon and overlay.</li><li>Updated the search button to look more like a button.</li></ul><p><strong>Store Finder after selecting a country and a city:</strong></p><ul><li>Added numbered pins on the map to help users identify locations on the list below.</li><li>Added a chevron to close the list and reveal the map and search filters.</li><li>Increased font sizes and set them in black for better contrast.</li><li>Included store features as recognizable pills, with additional services also listed.</li><li>Tidied and compressed text alignment for better balance.</li></ul><figure><img alt="Image with two versions of the store finder, showing the before and after state after redesigning, each state with two different screenshots." src="https://cdn-images-1.medium.com/max/1024/1*3-AK7H8-po3LtUbofSDjoA.jpeg" /><figcaption>In the image above, the changes on the store finder pages are visible by comparing both versions</figcaption></figure><h4>Conclusion</h4><p>The main takeaway from this project is that, regardless of the technical skills and hard studies developed over the years, soft skills play a crucial role in the success of a team project. Effective communication, valuing others’ ideas, and being able to see the value in them, among other social capabilities, can clearly influence the result of a project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03ec0b609aef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The case study of how to design an e-commerce website when dealt a good hand and still fail.]]></title>
            <link>https://medium.com/@javier.escobedo.91/the-case-study-of-how-to-design-an-e-commerce-website-when-dealt-a-good-hand-and-still-fail-bdf644df3fe0?source=rss-17d6c8007de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdf644df3fe0</guid>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Javier Escobedo ]]></dc:creator>
            <pubDate>Mon, 22 Jul 2024 00:18:20 GMT</pubDate>
            <atom:updated>2024-07-28T16:22:49.958Z</atom:updated>
            <content:encoded><![CDATA[<p>Usually, when writing a case study, designers try to show how successful their product or project was and how they did the whole process to get to that point. And, while this writing will have some similarities to the aforementioned features, it will definitely differ by showing how a bad combination of elements can turn a project set to succeed into a failure.</p><figure><img alt="Hero image displaying a portable computer, showing a mexican restaurant website. Background is a mesh of mid fidelity wireframes at 45 degrees." src="https://cdn-images-1.medium.com/max/1024/1*LxPFi4eYqDEWNj0bAKDuVQ.jpeg" /></figure><p><strong>Stakeholder Choice</strong></p><p>For this project, we were given the brief and the team members: to design a responsive e-commerce website.</p><p>We then had to choose a stakeholder: I already had in mind a friend of mine who owns three restaurants in Munich; I also considered that another team member lives in Munich too, meaning we could do deeper research and take a more realistic approach for this project.</p><p>When I pitched the idea, somehow they were both happy with it, and even the third member, who lives in another city, offered to travel to Munich just for the interview. With all of this, I thought this was going to be an exciting project.</p><p>And so, our chosen stakeholder was Condesa: a Mexican restaurant with three branches located in Munich. What sets Condesa apart from its competitors is their commitment to quality above anything, meaning an honest, loyal relationship with its clients. Being the most successful Mexican restaurant in Munich, we could not ignore the fact that their e-commerce was simply non-existent; this translated into an exciting challenge.</p><figure><img alt="An internal view of the branch of Condesa Mexican Authentic Food in Munich" src="https://cdn-images-1.medium.com/max/1024/1*pEEt9Ckz9NNFWcxe-Eav9g.jpeg" /><figcaption>This is their most successful branch located right at the Münchner Freiheit square in Munich</figcaption></figure><h3>Act I: The beginning of the end</h3><p>I believe most people do not really intend to create problems to others intentionally — right, this sounds ok. But what happens when we start off on the wrong foot when working in a new team?</p><p>My purpose with the case study is to explain the things I learned I should avoid for any future project. When working in a team with a horizontal hierarchy, some people might take the lead, and some might not. But regardless of it, there must be a consensus on what strengths and weaknesses each member can bring to the table — that way, it will be easier to organize the work and delegate tasks accordingly. Well, you guessed it, we didn’t do it. I can only assume <strong>the error here was not doing it</strong> right at the beginning.</p><p>Once the stakeholder was defined, I suggested doing a competitive audit, and here is where the problems began. No consensus on leadership, misalignments on ideas, lack of soft skills, all of this made each task harder than it should have been. The same issue occurred with the interview script for our stakeholder; the tasks we needed to complete in the first two days right before the weekend were a disaster.</p><p><strong>Interview Onsite</strong></p><p>As the new week started, our first task on our list was to meet before visiting the stakeholder’s business in Munich. And it’s because of this that our team didn’t break entirely at the beginning; having the chance to meet physically and have some chitchat allowed us to empathize with one another, and somehow, gave us hope in thinking everything was going to be alright.</p><figure><img alt="An image depicting 4 people behind a table; they just had an interview and are smiling." src="https://cdn-images-1.medium.com/max/1024/1*ZKsCRwUhLTtCE9iFJc1EMw.jpeg" /><figcaption>Interview in the basement of the Condesa branch located next to Central Station, Munich</figcaption></figure><p>As per the interview, I conducted it and experienced again that the script is merely a guide, that an interview should feel more like a conversation that can easily change the order of the questions; and that sometimes, the answers will not be at all what one can expect.</p><p><strong>Quantitative/Qualitative Research</strong></p><p>The following couple of days, our task was to get insights from our stakeholder’s interview, as well as conducting quantitative research with a survey so we could better understand the existing problems. Combining these pieces to craft an interview for qualitative research proved to be challenging. Having constant disagreements and the famous <em>designer ego</em> inside the team delayed us significantly; as I’m writing this, I believe that <strong>whenever this issue arises, it must be called out immediately in a polite, constructive way,</strong> instead of being belittled. This is another learning.</p><p><strong>Post Research</strong></p><p>For the next steps that followed the qualitative research data (from Problem Statement to Mid-Fi prototype testing), the team dynamics somehow got better, maybe because by following the process in the way we had learned, we knew that each member should propose a solution and then, we vote for the best features as a team.</p><p><strong>Persona and User Journey Map</strong></p><p>Once the problem statement was cleared and set, creating the Persona and User Journey Map was easier for all of us; at this point, it was clear that these deliverables would serve as support for our final product.</p><figure><img alt="A persona file that contains a photograph of a man, and on the right side multiple features such as demographics, about, goals, frustrations and behaviours." src="https://cdn-images-1.medium.com/max/1024/1*mVYKWG4LUTpSpOdWVbxq5Q.jpeg" /><figcaption>Developing the Persona after the research was a process we didn’t struggle with, and I feel honored to show it in this case study.</figcaption></figure><p><strong>Ideation</strong></p><p>For this, we decided to go with Crazy 8s and HMW statements; allowing each member to present their ideas and vote for the best ones enabled us to keep on working faster than at the beginning. And once we voted, I suggested doing the MoSCoW method too, explaining that in our previous project, not doing it cost us 4–6 hours of extra work as the internal discrepancies arose almost at the end of that project.</p><p><strong>Sitemap and User Flow</strong></p><p>By running against the clock and willing to start working on the Mid-Fi prototypes as soon as possible, we began right away with the sitemap. And yet,<strong> another learning is not to rush the processes</strong>: while the three of us could not work as a team most of the time, it’s true that in constellations of two members, things would be smoother. And that day, one member was not available, so the remaining two of us took on the sitemap immediately.</p><p>By rushing it, we created a weird mix of a sitemap/user flow; thankfully, after receiving feedback and some further help, we were able to work on it one more time and understand the differences clearly between a sitemap and a user flow.</p><p>By the time of creating the user flow, the three of us were working together again, coming up individually with proposals. At the time of reviewing them, most likely because it was Friday evening, we didn’t struggle in choosing how to proceed, and even doing the edits was relatively an easy process.</p><figure><img alt="An image showing a user flow. This consists in multiple steps depicting the redesigned experience of a user when ordering at Condesa." src="https://cdn-images-1.medium.com/max/1024/1*NbcWbxXsWB1D5fyTxhp_-Q.jpeg" /><figcaption>The User Flow is another deliverable that is worth showing, mainly because it is one of the few items where we all aligned as a team.</figcaption></figure><h3>Act II: Implosion</h3><p>As every storytelling piece has a climactic moment, this has finally come. And so, previous to the presentation day, tensions were high due to the number of deliverables to conclude. At least it was clear to all of us:</p><ul><li>Mid-Fi prototype</li><li>User Testing</li><li>Hi-Fi Prototype</li><li>Presentation</li></ul><p>In a functional team, this can be easily done within 8 hours. Exactly, in a functional team.</p><p>As I’m the one with more Figma experience, I voluntarily offered to do the mock-ups for the Mid-Fi prototype while receiving input from both members; however in real-life projects, once the members are aligned on the ideas and to-dos, each one usually takes full responsibility/leadership roles for each of the deliverables. It’s a matter of trust.</p><p>Unfortunately, this didn’t happen while constructing the Mid-Fi prototypes, as it was hard for me to work while getting simultaneously more than five suggestions per minute. Another <strong>lesson learned is to clarify the value of trust in each member</strong>.</p><p>Once the Mid-Fi prototype was done, we proceeded to testing it — a smooth process with five different people; we took the feedback and decided to implement it in the final Hi-Fi prototype.</p><p>And here is where things imploded:</p><p>Working after hours has never been a problem for me as long as it makes sense. And even if it does not, I can still collaborate as I firmly believe that providing the best efforts each member has can result in a successful experience.</p><p>Before we started, I tried to take one more time the role of leadership by delegating the presentation task to a member, the redefined moodboard task to another; this by explaining I can start creating the design system. Another lesson learned:<strong> </strong>while it is not my intention to come to this bootcamp and tell everyone right away that I already have experience in the UI field, at least it is something I should share, along with the strengths and weaknesses.</p><p>The moodboard went well and the presentation was somehow being created; I understood the importance of trusting the members as an individual simply cannot make all the deliverables when the project has been framed to be conducted in teams. And even though there were things I did not like, I prioritized finalizing things unless something was definitely a no-go.</p><p>When it came to the design system, while I was creating it, I also found it important to ask for opinions and even delegate tasks, such as picking the typeface for the project (particularly not my strongest suit). In the end, coming up with a design between more than two people includes a compromise, meeting halfway especially when ideas that are based solely on subjective taste are at discussion.</p><p>But as I mentioned before, seeing a no-go taking place, something that I know based on my experience would not work, makes me point it out and get it changed, especially if there is objective criteria to prove the point. In this case, accessibility plays a big role for me since I personally know and have worked with people with disabilities and am aware of the struggles they have when accessibility is disregarded for a “creative whim”.</p><figure><img alt="A homepage of a Mexican restaurant. It depicts accessibility problems that must be addressed to benefit users with visual impairments." src="https://cdn-images-1.medium.com/max/1024/1*hAVItnhpx7MAXyIiu04CeA.jpeg" /><figcaption>With the current prototype, the text on the left hand side doesn’t make enough contrast with the background, leading to readability issues. Additionally, the items on the nav bar need some work to generate a bigger contrast. A simple solution could be to change the font to bold.</figcaption></figure><p>But when debating in an argument and dealing with statements that are crafted with language that is unprofessional carried by the insistency of the designer ego, the project will inevitably become never-ending and stressful.</p><p>At some point, I knew I had to make a decision: on one hand, I felt the responsibility for making this a successful project since the stakeholder is also a close friend of mine. On the other hand, I realised it is not worth the stress, especially if I can rework it at a later point. With that last thought in mind, I stepped back on giving any design decisions; I made that clear to my colleagues, explaining that I would continue working on the Hi-Fi prototype and that they could proceed with any changes anywhere without my opinion, be it color or fonts.</p><p>Thinking in retrospect, that was a hard decision for me, as I have never before done such a thing; but yet <strong>another learning is to take a step out of the picture for a moment and ask ourselves what is worth and what is not.</strong></p><h3>Epilogue</h3><p>Even though this is a project I will rework on my own individually to be able to present it to the stakeholder, it was definitely full of learnings. In real life, most of the time we can’t simply choose who we have to work with, hence the need to develop soft skills to get a better understanding and empathy.</p><p>And of course, regardless of the dynamics we had, the research work we did will be fully credited accordingly, as it would have not been possible without a team effort.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdf644df3fe0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project 1 — Wicked Problems Case Study: Immigration]]></title>
            <link>https://medium.com/@javier.escobedo.91/project-1-wicked-problems-case-study-immigration-6aced037408d?source=rss-17d6c8007de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6aced037408d</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[immigration]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Javier Escobedo ]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 22:59:38 GMT</pubDate>
            <atom:updated>2024-07-07T22:59:38.083Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Project 1 — Wicked Problems Case Study: Immigration</strong></h3><h3><strong>Introduction</strong></h3><p>As part of the first project of the UX/UI Ironhack’s bootcamp, we were given the task to select one out of five different topics under the not-so-revealing name of wicked problems. I felt attracted to the topic of Immigration, mainly out of personal interests and experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9nZzH_aPb8Jmxaz6" /><figcaption>Photo by <a href="https://unsplash.com/@schluditsch?utm_source=medium&amp;utm_medium=referral">Daniel Schludi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Briefing for the topic:</p><p><em>People’s mobility has increased exponentially all around the world in recent years. Even though migration has always been a common phenomenon throughout history, humankind has never seen such a wide variety of destinations, motivations, and configurations.</em></p><p><em>The experience of migrating to a new country and having to adapt to a different culture or language comes with a number of bureaucratic duties that must be completed within a particular timeframe to validate the journey in the host country. </em><strong><em>How Might We Help migrants find information, complete tasks, and get their paperwork done to start their life in a new city</em></strong><em>?</em></p><p>The next step was to define the teams. Given that not everyone in the bootcamp shares similar backgrounds or the same level of soft skills development, I knew this would play a role in the team’s dynamics. Our team was formed by Anastasia Rozkhova, Felix Blanc, Niamh Akiboye, and myself.</p><p><strong>Project specifics:</strong></p><ul><li><strong>Goal:</strong> Propose a solution to the problem using Design Thinking methodology.</li><li><strong>Timeline:</strong> 8 working days.</li><li><strong>Deliverables:</strong> A presentation and case study showcasing multiple methodologies such as research, user interviews, affinity diagrams, etc.</li></ul><p>The result is an app that simplifies and consolidates all the necessary information for new immigrants moving to Germany as high-skilled workers. Its main feature is a Timeline that provides a clear visualization of all the required steps before and after arrival in Germany, including specific details per step, as well as support sections with multiple sources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r3zd9e40wFqJFlJ6nPFnVw.png" /></figure><h3><strong>Process</strong></h3><p>Once the project kicked off, we began working with a list of methodologies that are part of the Design Thinking process. The first one was Secondary Research.</p><p><strong>Secondary Research</strong></p><p>Aligned on our topic, we individually conducted secondary research. Internal differences became clear as each of us focused on specific topics within the immigration spectrum. This led to an internal debate where we understood the need to narrow down our scope to offer a solution. Initially, we decided to focus on volunteers helping migrants with their process after arriving in Germany, particularly those involved with Ukrainian refugees. However, the constraints of the next step (user interviews) required us to change our target audience to find available users. This was a necessary adjustment in line with the iterative nature of Design Thinking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oJCaMpfKPKmZ3GWx" /><figcaption>Photo by <a href="https://unsplash.com/@glenncarstenspeters?utm_source=medium&amp;utm_medium=referral">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>User interviews</strong></p><p>With a positive attitude after the initial hiccup, the next step was to understand more about our user, so we drafted an interview guide. This was crucial for understanding primary research, uncovering opportunities, and generating insights. We conducted four interviews, which provided interesting information that helped us converge the secondary research findings. Key quotes included:</p><blockquote>“I wouldn’t move somewhere else, don’t want to go through all of that again.”</blockquote><blockquote>“You realize you’re on your own.”</blockquote><p><strong>Affinity Diagram</strong></p><p>After the interviews, we clustered and classified the data. We created tags along the process, allowing for a comprehensive overview at the end. Through democratic voting, we identified the most relevant insights:</p><ol><li>Information about the process is scattered across multiple official and unofficial channels.</li><li>Lack of consistent, official support groups for socializing.</li></ol><p>This led to our problem statement: <em>Highly-skilled non-EU professionals need to find a way to successfully complete their migration process within a set timeframe because currently the information about immigration is scattered and inconsistent across multiple sources, and support is limited.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FXod0l6D15XGgF10DtBFdQ.png" /><figcaption>Up to this point, even the notes were categorized by color, indicating whether they represented a motivation, behavior, or pain point (in red)</figcaption></figure><p><strong>User Persona</strong></p><p>One of my favorite parts of the process was creating the User Persona. This consolidated all our research into an imaginary user representing many others. Our Persona is Karthik, a recent computer science graduate from India in his late 20s who wants to relocate to Germany for a high-paying job and a better standard of living. Karthik’s primary needs are to apply for a visa and a work permit. He struggles to decipher all the information available on governmental sites and social media, feeling stressed about meeting documentation requirements within his timeframe. Karthik represents the voices of everyone we spoke to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*plJWqb1f9DWa3tGOQ2MCcw.png" /></figure><p><strong>User Journey Map</strong></p><p>We designed a user journey map representing Karthik’s steps to achieve his primary needs. The map shows the emotional ups and downs in Karthik’s journey, emulating an emotional roller coaster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Q9-AWxRlE_YhP19URjQ-g.png" /></figure><p><strong>Ideation</strong></p><p>For the ideation phase, our team generated multiple ideas to solve Karthik’s goals. We clustered these ideas by affinity and identified six different trends, agreeing to focus on the most appealing one: the Timeline. This visual map shows the list of steps required before and after arrival.</p><p><strong>User Flow</strong></p><p>After completing the previous steps, we worked on the user flow. Here, we noticed discrepancies reflecting individual outcomes. We discussed and reviewed the generated flows, arriving at a final version after more than three iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uLleIoYmeD4wp11NCx88Ng.png" /></figure><p><strong>Lo-Fi Wireframing</strong></p><p>Prior to the presentation, we concluded with Lo-Fi wireframing. Discrepancies surfaced again, necessitating a step back to realign our goals. This highlighted the iterative nature of the process.</p><p>After testing the first version of the Lo-Fi prototype with three target audience users, we applied further changes based on our observations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_AO_cAqMK5rfdXxoGgrogw.png" /><figcaption>You can explore yourself the prototype <a href="https://www.figma.com/proto/KQ51jlUZDthoNyul8xOfsz/%5B-P1-Team-1-%5D-Design-File---The-Arrival-Alliance?page-id=16%3A321&amp;node-id=3598-2499&amp;viewport=1629%2C678%2C0.44&amp;t=Pugqn7rIfm7jxcI7-1&amp;scaling=min-zoom&amp;content-scaling=fixed">here</a>.</figcaption></figure><p><strong>Presentation</strong></p><p>As a deliverable, our team prepared an 8-minute presentation for the class. It covered:</p><p><strong>- Project Overview (pitch)</strong></p><ul><li>The current situation (problem)</li><li>The solution</li></ul><p><strong>- The problem</strong></p><ul><li>Main discoveries through the empathy and affinity processes</li><li>Persona</li><li>User Journey Map</li></ul><p><strong>- Problem Definition</strong></p><ul><li>How Might We</li><li>Problem Statement</li><li>Ideation</li></ul><p><strong>- Solution Demo</strong></p><p><strong>- Further Steps</strong></p><p>Overall, the presentation went well. Most of us had previous experience with presenting and pitching products, although we treated it more as a formal pitch than an explanatory classroom talk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g2ena6MJmyn_tc6NRGtkgg.png" /></figure><h3><strong>Next Steps</strong></h3><p>Given more time, the next steps would include developing additional features, like a mentoring/peer-to-peer feature for connecting users undergoing the immigration process. UI development would also be crucial, focusing on a design system that allows scalability.</p><p><strong>Conclusion</strong></p><p>Although Design Thinking and user research processes are not new to me due to my background as a former industrial designer, I find working with people from different backgrounds fascinating. This upskilling process improves not only our hard skills but also our soft skills. It is essential to develop empathy, as we will not always be paired with similar minds in the work environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aced037408d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IronHack’s Pre-work — Challenge 2: Wireframing a user flow.]]></title>
            <link>https://medium.com/@javier.escobedo.91/ironhacks-pre-work-challenge-2-wireframing-a-user-flow-b8850469b17b?source=rss-17d6c8007de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8850469b17b</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-journey]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[wireframe]]></category>
            <dc:creator><![CDATA[Javier Escobedo ]]></dc:creator>
            <pubDate>Mon, 17 Jun 2024 15:53:57 GMT</pubDate>
            <atom:updated>2024-06-17T15:53:57.068Z</atom:updated>
            <content:encoded><![CDATA[<h3><a href="https://medium.com/@javier.escobedo.91/ironhacks-pre-work-challenge-1-citymapper-s-way-to-an-upgraded-experience-a92b2b27334f?source=your_stories_page-------------------------------------">IronHack’s Pre-work — Challenge 2: Wireframing a user flow.</a></h3><h3>Deconstructing an app to understand its fundamentals, from a dot to a user flow.</h3><p>As part of the prework to enroll in Ironhack’s UX/UI bootcamp, we were tasked with analyzing an existing app and, by choosing one user journey, deconstructing the mock-ups to a lo-fi wireframe level.</p><p>Based on previous challenges, I decided to work with the Airbnb app for a couple of reasons:</p><ul><li>The app’s design is not only visually appealing but also intuitive and logical.</li><li>The main purpose of the app is to book accommodation; this user journey involves multiple steps and, if not designed correctly, might end up in failures most of the time.</li><li>I find the design system of the company fascinating, especially knowing that they designed their own font and icons.</li></ul><p>Once the decision was made, I started working directly on Figma to produce the multiple screens before building the prototype.</p><figure><img alt="Set of 8 wireframes describing the main user journey to book accommodation using Airbnb." src="https://cdn-images-1.medium.com/max/1024/1*XDYO4rk6UHE5vZNwXeb_JA.png" /></figure><p>The user journey depicted above shows the simplicity of booking accommodation with Airbnb. The steps are as follows:</p><ol><li><strong>Entering the destination place</strong> (screens 1–3).</li><li><strong>Selecting the dates</strong> (screen 4).</li><li><strong>Selecting the number of guests</strong> (screen 5).</li><li><strong>Selecting a place from the results</strong> either by using the map or by scrolling down and previewing the options (screen 6).</li><li><strong>Reading the place’s information and features</strong> prior to proceeding to the next step in the booking process (screen 7).</li><li><strong>The final step</strong>, similar to a shopping cart, contains all the information of the accommodation, including policies and rules. Unlike the previous steps, in order to submit the booking request, the user must scroll down through all the information (screen 8).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BC_5-z7ZitSp5Vz389ISPw.gif" /></figure><p>This exercise provides amazing insights to everyone, whether beginners or experienced UX designers, to understand the logic behind user journeys on apps that we use in our everyday lives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8850469b17b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IronHack’s Pre-work — Challenge 1: CityMapper’s way to an upgraded experience.]]></title>
            <link>https://medium.com/@javier.escobedo.91/ironhacks-pre-work-challenge-1-citymapper-s-way-to-an-upgraded-experience-a92b2b27334f?source=rss-17d6c8007de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a92b2b27334f</guid>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Javier Escobedo ]]></dc:creator>
            <pubDate>Sat, 15 Jun 2024 15:34:58 GMT</pubDate>
            <atom:updated>2024-06-15T15:36:32.848Z</atom:updated>
            <content:encoded><![CDATA[<h3>IronHack’s Pre-work: Javier Escobedo_Challenge1.</h3><h3>How little changes can have tremendous impacts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5OrcM17TZb8b07q1ldXzA.png" /></figure><p>Citymapper is a dynamic navigation app designed to help users travel efficiently within urban environments. What sets Citymapper apart is its ability to offer a highly customizable experience, allowing users to select from various modes of transportation and receive real-time notifications. This combination ensures that users can choose the best possible routes tailored to their specific needs and preferences.</p><p>However, despite its innovative features, Citymapper still faces challenges that need to be addressed, especially if it aims to become the top choice for users over competitors like Google Maps and Transit.</p><p>To gain a better understanding of the existing issues, I conducted interviews with several users. The feedback was particularly critical regarding the ticketing service.</p><blockquote>The app’s interface is nice and all, but why should I use it instead of Google Maps, for example? If I’m gonna end up buying the ticket in a different platform or even at a vending machine, it really doesn’t play a difference at all.</blockquote><p>Citymapper has a valuable niche to explore if it decides to partner with transport associations in each city where it operates. This would create a seamless experience from point A to Z, allowing users to complete their entire journey within the comfort of the app.</p><h3>Enhancing User Experience: A Hands-On Approach</h3><p>With this valuable insight, the next step was to analyze the existing user flow when using Citymapper and identify potential improvements. As with any beneficial process, the first step is to generate multiple ideas, followed by selecting the best among them.</p><p>What if, once the multiple commuting options appear after entering the starting point and destination, the user could see the total cost of the journey, regardless of the different transportation means? Once an option is selected, it could expand to display ticket purchasing options: <br>a. Buy all the required tickets in one purchase, or <br>b. Buy specific segments needed to complete the journey.</p><figure><img alt="Three wireframes on paper displaying the first steps to use Citymapper to navigate from point A to point B" src="https://cdn-images-1.medium.com/max/1024/1*JpEtFI5agge6GH-fZv8P3w.jpeg" /><figcaption>On wireframe #3 (last one on the right), the options show the cost of the journey as a suggested improvement.</figcaption></figure><p>For the option where the user decides to buy all the tickets in one go, the app should still show the price breakdown. Providing information and transparency will generate a tighter bond between the interface and the user.</p><figure><img alt="Three wireframes on paper displaying the steps 4 to 6 to use Citymapper to navigate from point A to point B" src="https://cdn-images-1.medium.com/max/1024/1*f-sTlSHYMffddQYtuie-Nw.jpeg" /></figure><p>Like other e-commerce sites, this overview of the shopping cart will also remind the user of similar products, thereby easing the use of this new feature.</p><p>Finally, once purchased, the app will provide a QR code that can be used as a ticket for each segment of the transportation.</p><figure><img alt="Three wireframes on paper displaying the steps 7 and 8 to use Citymapper to navigate from point A to point B" src="https://cdn-images-1.medium.com/max/1024/1*ullVQKvYHahhy45Hcjxpmg.jpeg" /></figure><p>It is important to remember that, as in any other design process, this is an early stage where many factors have not yet been considered. Some immediate questions might include:<br>1. What if certain transportation means do not yet have an electronic reader, requiring a paper ticket?<br>2. What if the device’s battery runs out?</p><p>Nevertheless, any great idea begins as a small process on paper, and if after multiple iterations the idea has to undergo significant changes, that does not mean the process was useless — quite the opposite.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a92b2b27334f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>