<?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 Cami Marocchi on Medium]]></title>
        <description><![CDATA[Stories by Cami Marocchi on Medium]]></description>
        <link>https://medium.com/@marocchicamila?source=rss-6516c6e1b471------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rRZ_dumbMR5ytjVoW7fqOg.jpeg</url>
            <title>Stories by Cami Marocchi on Medium</title>
            <link>https://medium.com/@marocchicamila?source=rss-6516c6e1b471------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:09:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marocchicamila/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[From MVP to 2.0: Designing a Banking Login That Users Actually Trust]]></title>
            <link>https://marocchicamila.medium.com/from-mvp-to-2-0-designing-a-banking-login-that-users-actually-trust-5ce382bd3091?source=rss-6516c6e1b471------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ce382bd3091</guid>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[mobile-design]]></category>
            <dc:creator><![CDATA[Cami Marocchi]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 02:15:33 GMT</pubDate>
            <atom:updated>2026-09-02T19:53:50.246Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A visual designer’s perspective on iterating a high-stakes authentication flow across 6 countries.</em></p><p>When I joined the <strong>BAC Credomatic -</strong>largest financial networks over 4 million users across 6 countries, mobile banking redesign, the login screen looked like most banking apps from five years ago: a white card, two input fields, a blue button. It worked. But <strong>it didn’t feel like a bank you could trust with your savings</strong>.</p><p>This is the story of how <strong>I designed the MVP login from scratch</strong>, incorporated insights from usability testing with real users across the region, and iterated toward a biometric-first experience that felt as secure as it actually was. <strong>I worked within a multidisciplinary team, with a UX Lead from the client side validating direction</strong>. But the visual design decisions were mine to make.</p><h3>The Problem</h3><p>The old app had all the functional pieces in place: username field, password field, a “forgot password” link, a token input. But everything lived on a single screen, competing for attention at the same time.</p><p>The token input was always visible even for users who didn’t need it. The biometric option was an afterthought, tucked below the form as a small fingerprint icon. There was no personalization, no context. Every time you opened the app, it greeted you the same way it would greet a stranger.</p><p>For a bank serving millions of users across six different countries, with different levels of digital literacy, different devices, different habits, that one-size-fits-all approach wasn’t scaling. And the usability data would later confirm what the design already suggested: users were hesitating, second guessing, and in some cases, failing to complete basic authentication tasks.</p><figure><img alt="Two screens of the BAC Credomatic old app side by side. Left: empty login form with username and password fields, token checkbox, and a blue ‘Ingresar’ button. Right: the same screen with a username entered, showing Face ID as a small, low-contrast option below the field — an afterthought rather than a feature." src="https://cdn-images-1.medium.com/max/1024/1*j9d1RZBqWKSBpcCYzq-l4g.jpeg" /><figcaption><em>The old login experience: token always visible, biometrics buried. Every user, same screen.</em></figcaption></figure><h3>The Process</h3><p>My scope covered the end-to-end visual design of the login flow from the first MVP screens to the iterative work that became Login 2.0.</p><p><strong>Benchmark</strong></p><p>Before starting with Figma, I researched how other banking apps handled login. I looked at authentication patterns, how biometrics were shown to users, how apps communicated trust visually, and how they handled the “remembered user” state.</p><p>Two things stood out: the best apps made biometrics feel like a feature, not a fallback. And the ones users trusted most were the ones that greeted them by name.</p><p><strong>MVP</strong></p><p><strong>The MVP was the first real departure from the old app</strong>. I removed the Token checkbox from the main screen it was creating noise for the majority of users who never used it. I added “Recordar usuario” as a checkbox that would become the biometric first experience. The layout was cleaner, the hierarchy clearer. But it still felt like a form.</p><p><strong>Phase 3: Login 2.0</strong></p><p>The <strong>usability testing</strong> results gave us something usefull to work with. Users hesitated on terminology “token”, “recordar usuario” especially users over 40, who represented 44% of the test group. The old model was asking users to think too much at the moment they most needed to feel secure.</p><p>For Login 2.0, I explored multiple visual directions. The breakthrough came when I shifted the question from “how do I display these fields?” to “what should the user feel when they open this app?”.</p><p>That shift drove three key decisions: putting the user’s name front and center, making the biometric icon the visual protagonist of the screen, and committing to a fully red interface removing the blue that came from the broader Design System to<strong> create a login experience that felt distinctly BAC, and distinctly trustworthy.</strong></p><figure><img alt="Left screen: the old app with a white card on a grey background, mixed blue and red colors, token checkbox visible, and biometrics absent. Center screen: the MVP with a cleaner white card layout, ‘Recordar usuario’ checkbox introduced, and a more consistent visual hierarchy. Right screen: Login 2.0 with a fully red screen, username and password fields integrated into the brand color, and ‘Recordar usuario y registrar Face ID’ as a single action" src="https://cdn-images-1.medium.com/max/1024/1*dxHH-7tAncOS1zxXYSfwlw.jpeg" /><figcaption><em>Old App &gt; MVP &gt; Login 2.0. Three phases tomake authentication feel like trust.</em></figcaption></figure><h3>Key Design Decisions</h3><p>Every change between the old app and Login 2.0 had a reason.</p><p><strong>1. Biometrics as the protagonist, not the fallback</strong></p><p>In the old app, the biometric option appeared only after the user typed their username, small, low contrast, easy to miss.<strong> In Login 2.0, Face ID and Touch ID became the centerpiece of the screen</strong>. The password option was still there, but as a secondary action. This hierarchy change wasn’t cosmetic: it was a statement about how users should authenticate in 2024.</p><p><strong>2. Personalization as a trust signal</strong></p><p>“Buenos días, Miguel” isn’t just a greeting. In a banking context, seeing your own name before you authenticate tells you: <strong>this app knows who you are, and it’s ready for you</strong>. It reduces the cognitive load of the login moment and replaces the feeling of filling out a form with the feeling of being recognized.</p><p><strong>3. One color, one message</strong></p><p>The MVP used both red and blue both valid within BAC’s Design System. But for Login 2.0, I explored proposals that used only red. <strong>The result felt more cohesive, more corporate, more trustworthy</strong>. In a screen where the user is about to hand over their credentials, visual consistency isn’t just a detail.</p><p><strong>4. Pre-login quick actions</strong></p><p>Users who aren’t logged in still need things: exchange rates, help, product information. So for the Login 2.0, I surfaced them as icon-based quick actions at the bottom of the screen visible before authentication, without cluttering the main login area.<strong> A small decision with a real impact on how non-clients and first-time users experience the app.</strong></p><figure><img alt="Left &amp; Center: biometric login with Face ID or Touch ID — fully red screen, user greeted by name ‘Buenos días, Miguel’, face recognition icon as the visual centerpiece, and a secondary ‘Ingresar con contraseña’ option below. Right: the password login state — fully red, clean form with username and password fields, and ‘Recordar usuario’ checkbox to enable biometrics on next login." src="https://cdn-images-1.medium.com/max/1024/1*wOvlFr-sqbNiQ41AZBMxZQ.jpeg" /><figcaption><em>Face ID, Touch ID, password — three ways in, one consistent experience. Designed to feel like the same app, regardless of how you authenticate.</em></figcaption></figure><h3>Reflection</h3><p>I learned that in banking, <strong>the login is the handshake the very first impression</strong>. It’s the moment a user decides whether they trust you with their money. Every pixel, every label, every hierarchy decision carries weight that most interfaces don’t have to bear.</p><p><strong>Working on BAC taught me that defensive design isn’t about adding warnings it’s about removing doubt</strong>. The best security UX is the kind users don’t have to think about.</p><p>If I were to do it again, I’d push earlier for user testing on the MVP, before the patterns got established. The insights we gathered validated decisions already made, useful, but less powerful than insights that shape the first proposal.</p><p>That’s the thing about iterative design: the earlier you learn, the more freedom you have to change.</p><h3>Thanks for reading!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ce382bd3091" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for the Arab World: What I Learned Localizing a Health App for Oman]]></title>
            <link>https://marocchicamila.medium.com/designing-for-the-arab-world-what-i-learned-localizing-a-health-app-for-oman-57745f22b7ca?source=rss-6516c6e1b471------2</link>
            <guid isPermaLink="false">https://medium.com/p/57745f22b7ca</guid>
            <category><![CDATA[rtl-design]]></category>
            <category><![CDATA[accesibility]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <dc:creator><![CDATA[Cami Marocchi]]></dc:creator>
            <pubDate>Fri, 29 May 2026 20:40:14 GMT</pubDate>
            <atom:updated>2026-05-29T20:40:14.035Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Beyond flipping the layout: how real research with users, Apple experts, and a translation agency — with no AI tools to rely on — changed how I think about cross-cultural design.</em></p><h3>Where It Started</h3><p>When the B-Healthy App team got the opportunity to expand the product into the Oman market, the first instinct might have been technical: <em>“we need to implement all the UI to RTL and translate the copies.”</em></p><p>As the visual designer on the project, I took the initiative to understand first — before changing a single pixel — what it actually meant to design for an Arab user. This was my first time working for this region!</p><h3>But first, research: Three Sources, Three Kinds of Knowledge</h3><h4>1. Expert Voices Before a Single Screen</h4><p>The first step was talking to people who lived the experience from the inside — before touching any design.</p><p>The first contact was a Globant colleague based in the Middle East, specializing in the gaming industry. She was attending an egames conference at the time and brought a sharp perspective on how Arab users engage with digital products: interaction patterns, visual expectations, and the nuances of designing for a region that the Western tech world often treats as a monolith.</p><p>The second contact was a native Arabic speaker, who we brought in specifically to review copy. What started as a translation check turned into something more valuable: she caught grammatical gender inconsistencies in Arabic that looked correct to an external translator but would sound unnatural to a native speaker. That level of nuance doesn’t appear in any style guide — it only comes from someone who actually lives the language.</p><h4>2. Apple WWDR: The Most Direct Technical Source</h4><p>One of the first technical questions that came up was deceptively simple: should the calendar week view start on Monday or Saturday?</p><p>In Oman, the working week runs Sunday through Thursday — Friday and Saturday are the weekend, a change that has been in place since 2013. That’s not just a cultural footnote — it directly affects how a user reads their weekly activity progress.</p><p>The team escalated the question directly to Apple WWDR (Worldwide Developer Relations), who connected us with their localization evangelist and t the recommendation was to evaluate adapting the calendar view to the user’s regional preferences. An elegant technical solution that required a product decision: standardize or personalize?</p><p>That conversation with Apple also led us to review their Human Interface Guidelines for RTL in depth, and a WWDC 2022 video specifically on designing for right-to-left languages. Not as optional reading — as a design brief.</p><h4>3. The Translation Agency: Real Process with Real Friction</h4><p>For the final app copy, we worked with a specialized Arabic translation agency. The process involved preparing structured spreadsheets with every string of text organized by section and flow: Homepage, Enrollment page, Progress, Badges, Notifications, Transactional Emails.</p><p>Each row had the English text, the Arabic translation, a feedback column for revisions, and the development key. A system designed to ensure nothing was lost between design, translation, and implementation.</p><figure><img alt="Screenshot of a spreadsheet with columns for Screen/Section, English, Arabic, Feedback, Spanish and Portuguese. A comment bubble from a revieweris visible, noting a terminology inconsistency in the Arabic translation of the word “Exercise”, suggesting to use the singular format following Apple’s naming conventions." src="https://cdn-images-1.medium.com/max/1024/1*7jxLn6yYPdKM7DEuqLZQ9A.png" /><figcaption>Copy review spreadsheet showing English, Arabic, and feedback columns. A comment from our native Arabic reviewer questioning terminology consistency — the kind of nuance no style guide covers.</figcaption></figure><p>What nobody anticipates in a localization brief: the working week in Oman runs Sunday through Thursday — Friday is both the Islamic day of prayer and the official day off. That meant the translation agency was unavailable on Friday, creating gaps in the reviews that we hadn’t included into the original timeline. A small cultural detail with a real impact on delivery.</p><h3>The RTL Design Decisions</h3><p>With the context understood, the visual side had its own complexity. These were the most significant decisions:</p><h4>Direction and Iconography</h4><p>The most obvious change — and the most treacherous — is directionality. In Arabic, everything flows right to left. But it’s not just flipping the layout with an automatic mirror.</p><figure><img alt="Side by side comparison of the same app screen in English and Arabic. The English version reads left to right with the title “Progress” on the left. The Arabic version mirrors the layout right to left, with the title “التقدم” on the right and all navigation elements flipped accordingly." src="https://cdn-images-1.medium.com/max/1024/1*6WUpJ9LLS9ON6Q23LKFGLA.png" /><figcaption>The same Progress screen in English (LTR) and Arabic (RTL). Notice the layout direction, text alignment, and navigation arrows — all adapted, not just translated.</figcaption></figure><p>Directional icons are the clearest case: a “go back” arrow in English points left. In Arabic, “go back” means going right. If you simply mirror the interface, the arrow ends up in the visually correct position but pointing in the wrong direction.</p><p>I reviewed every icon in the flow to determine which ones should be mirrored and which shouldn’t. Icons that represent real-world objects (a watch, a person, a heart) don’t get mirrored. Icons that represent direction or navigation do.</p><figure><img alt="Screenshot of a mobile app design in English showing three screens with blue circular annotations. Notes read: “Confirm if rings must be closed CCW”, “Confirm if Health app icon should be reflected”, and “Imagery will require Arabic copy” — indicating design decisions under review for Arabic RTL localization." src="https://cdn-images-1.medium.com/max/1024/1*HfSXwoA3rh96318YNqV8Tw.png" /><figcaption>Design review annotations questioning which elements needed mirroring, direction of ring animations, and icon reflection — decisions that required research, not guesswork.</figcaption></figure><h4>Typography</h4><p>Arabic has its own typographic conventions: font sizes that feel comfortable in English often need to be 20–30% larger in Arabic to maintain the same readability. The reason is structural — Arabic letters are connected, many include dots and diacritical marks, making the script visually denser per character. I worked with typefaces that had robust Arabic support while maintaining consistency with the product’s visual personality.</p><h4>Illustrations and Representation</h4><p>B-Healthy used human illustrations as a core part of its visual identity. For the Oman market, this required careful consideration.</p><p>One of the clearest examples: illustrations showing women in typical Western athletic wear — t-shirts, sleeveless tops, fitted clothing — needed to be adapted. In the Arabic version, women had to be covered more modestly, reflecting cultural and religious norms around dress. The adaptations weren’t about censorship — they were about designing with genuine respect for the people who would actually use the product.</p><figure><img alt="Three pairs of illustrations showing the same female character before and after cultural adaptation for the Arab market. In each pair, the left version shows the character with uncovered hair and Western clothing. The right version shows the same pose and expression with a hijab and more modest clothing, while maintaining the same color palette and energetic style." src="https://cdn-images-1.medium.com/max/1024/1*i7VYPBGOJka-5CpFwdNi5A.png" /><figcaption>Same character, same energy, same brand identity — adapted modestly for the Arab market. Only the clothing and hair covering changed, never the personality.</figcaption></figure><h4>The Calendar and Weekly Goals</h4><p>The week-start decision turned out to be one of the most interesting from a product perspective. The app displayed the user’s weekly progress — a central component of its gamification system. If the week “starts” on Monday for the user but the product shows it from Sunday, the user will never feel like their week and the app are in sync.</p><p>I worked together with the UX team to define how to visually represent this adaptation while maintaining consistency with the existing progress system.</p><figure><img alt="Side by side comparison of Apple’s Calendar app in English and Arabic. The English version shows months arranged left to right with dates reading left to right. The Arabic version mirrors the entire layout, with month names in Arabic script, dates reading right to left, and the overall navigation elements flipped to accommodate RTL reading direction." src="https://cdn-images-1.medium.com/max/1024/1*kig2MhoUiQiqXxBhC5ub8Q.jpeg" /><figcaption>Apple’s Calendar app in English and Arabic — a reference we used to understand how RTL affects date layouts and reading patterns in a familiar context.</figcaption></figure><h3>The old school way — and why it matters</h3><p>Everything I described in this article was researched and coordinated the way designers worked before AI tools existed in our workflows: googling, watching conference videos, reaching out to people one by one, waiting for responses, synthesizing notes manually, presenting findings, refining them, waiting again.</p><p>What took me roughly two weeks — gathering information, coordinating with experts across time zones, preparing the copy spreadsheets, presenting decisions, incorporating feedback, navigating Friday delays — could today be compressed significantly with the right AI tools.</p><p><strong>But here’s what I think about that:</strong> the <em>process</em> of doing it slowly forced a depth of understanding that a faster workflow might have skipped. Every Friday delay made me more aware of the cultural context I was designing for. Every back-and-forth with Nadine taught me something about the language I couldn’t have googled. Every email thread with WWDR made the final decisions feel earned!</p><h3>What Changed in How I Design</h3><p>This experience left me with three lessons I now apply to every project:</p><p><strong>1. Cultural research is not optional in localization. </strong>Translating text without understanding cultural context produces interfaces that are technically correct but humanly hollow. Talking to an expert before designing a single screen was the most important decision in the project.</p><p><strong>2. Cultural constraints are design opportunities.</strong> Fridays without translators, icon directionality, Arabic typography — every “complication” forced me to understand the product better. A designer who only works within their own cultural context knows half the world.</p><p><strong>3. Scale matters</strong> B-Healthy wasn’t just an app — it was a health program with an ecosystem of emails, notifications, enrollment screens, progress tracking, and badges. Localizing all of that into Arabic required thinking in systems, not screens. Every design decision had to work across the entire product, not just the screen in front of me.</p><p><em>I’m a Senior Product Designer specializing in Fintech and HealthTech. See more of my work on</em><a href="https://www.behance.net/camiluxui"><em> Behance</em></a><em> or connect with me on</em><a href="https://www.linkedin.com/in/camilamarocchi-662a76325"><em> LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57745f22b7ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mi experiencia en la Diplomatura de UX RESEARCH]]></title>
            <link>https://marocchicamila.medium.com/mi-experiencia-en-la-diplomatura-de-ux-research-a878f9d164b0?source=rss-6516c6e1b471------2</link>
            <guid isPermaLink="false">https://medium.com/p/a878f9d164b0</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ui-ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[diplomatura]]></category>
            <category><![CDATA[uxr]]></category>
            <dc:creator><![CDATA[Cami Marocchi]]></dc:creator>
            <pubDate>Thu, 17 Dec 2020 14:05:16 GMT</pubDate>
            <atom:updated>2020-12-17T14:05:16.346Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0PvH25Grx9--mIOckykc5Q.png" /><figcaption><a href="http://www.diplomaturauxresearch.com.ar/">http://www.diplomaturauxresearch.com.ar</a></figcaption></figure><h4>Cursé la primer diplomatura universitaria en <a href="http://www.diplomaturauxresearch.com.ar/">UX Research</a> y comparto mi experiencia.</h4><h3>El contexto</h3><p>Luego de haber estudiado en Acámica UX/UI Design, me inscribí en talleres, workshops, y ya no quería repetir lo mismo visto, hasta que…</p><p>A fines de 2019 Eugenia Casabona (Mulesoft) comentó por el canal de Slack UX Argentina, sobre este curso que habían creado. Ingresé en la web para saber más al respecto. La lista de docentes invitados me convencieron enseguida y el temario me interesó, si bien algunos temas ya los había visto muy por arriba en Acámica.</p><p>Pasaron varios meses, analizaba el contenido, fechas, horarios de cursada, precio (para nada costoso respecto a otros cursos sin título universitario) y cómo organizarme con la carga horaria. Sabía que quería seguir capacitándome entonces me decidí.</p><h3><strong>Mi experiencia online</strong></h3><p>La cursada inició en Mayo, plena cuarentena en Argentina. Remarco esto, porque no hubo ni un problema de organización y las coordinadoras (Eugenia y Ángeles Mendoza) supieron amoldar todo el contenido, de manera online en poco tiempo de preparación.</p><h3>Contenidos DIUXR</h3><p>Dentro de los 5 módulos, el contenido abarca desde el Rol del UX Researcher en el desarrollo de productos y servicios, técnicas de investigación, análisis y presentación de resultados, evlauación centrada en las personas y la solución. Por último, un trabajo integrador de investigación para aplicar los contenidos vistos en un caso real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZLZjqtunhogSnL0EGPhUmQ.jpeg" /><figcaption>Roadmap de la cursada</figcaption></figure><p>Algunos temas que destacaron fueron: Jobs To Be done, Mapeo de experiencia, Entrevistas en profundidad y Generación de Insights.</p><p><strong>Docentes invitados</strong></p><p>Además de las clases dadas por Angie y Euge, algunos temas fueron dictados por un docente invitado. Esto estuvo muy bueno porque figuras conocidas del ámbito de UX, vienen a contarte su historia y explicar las metodologías que fueron aplicando en su experiencia.</p><p>Las clases que más aproveché fueron:</p><p>Juan Manuel Carraro (Accenture — Modelos mentales y arquetipos), Helena Polublank (Naranja X- Data Driven Design); Sol Velázquez y Facu Ruiz (Mercado Libre) dieron dos clases dedicadas exclusivamente a pruebas con usuario; Lucrecia Feller (Flux IT — Diseño colaborativo) ejercicios con usuarios, stalkeholders para que sean parte de la solución del problema. Por último como final de cursada, vinieron a dar una clase de armado de Portfolio UXR, Santiago Sanchez y Rodrigo Hurtado (ambos de Naranja X).</p><p><strong>Tutorías y charlas extras</strong></p><p>Las profesoras fijaron un dia de la semana para tutorías, un espacio para reforzar conceptos, aclarar dudas de temas o para presentar avances de las entregas. Y como bonus track, desde la Diplomatura crearon un ciclo de charlas abiertas llamadas <a href="https://www.youtube.com/channel/UC_loEy2Uyx61p-cAieKQc4g"><em>UXR Stories</em></a> dadas por profesionales, en vivo desde YouTube.</p><h3>Trabajo integrador</h3><p>Durante toda la cursada, los trabajos en clase forman parte del trabajo integrador. Con mi equipo “Amarillo post-it”, optamos por volcar todo el material y contenido a Mural. Cada entrega la trabajamos en grupo ahí mismo.</p><p>En este caso, el cliente fue TECHO para mi país (Argentina). Nos presentaron un objetivo de negocio [Aumentar y eficientizar las donaciones para poder generar soluciones concretas que mejoren las condiciones de vida de las personas que viven en asentamientos populares]</p><p>Lo que nos llevó a preguntar, ¿cuáles son las necesidades reales de los usuarios?, ¿cómo podríamos hacer para que personas que nunca donaron empiecen a hacerlo y lo hagan en forma recurrente?</p><p>Nos adentramos al mundo de las donaciones, llevando a cabo, encuestas a usuarios, entrevistas a voluntarios y donantes recurrentes. Llevamos a cabo pruebas de usuario para conocer la usabilidad de la página de Techo, para donar en Argentina. Por último, presentamos nuestros resultados a los stakeholders y profesoras. Pueden ver la misma en <a href="https://docs.google.com/presentation/d/1KhwDZzduRwOWjeXhhY5XfAE8Tn2dQ6qnBU7eK7HKypg/edit?usp=sharing">este link</a>.</p><h3><strong>Takeaway</strong></h3><p><strong>No creí hacer alguna vez una Diplomatura en Investigación. Trabajé desde el rol del Researcher. Todo nuevo para mí, poder conversar con usuarios reales, escuchar sus problemas y necesidades; conocer nuevas herramientas para realizar pruebas de manera remota.</strong></p><p>El proyecto propuesto representó un desafío debido al aislamiento y poder juntarnos con el equipo, por la cantidad de datos que fuimos recabando para resolverlo de manera efectiva.</p><p>Aprender y aplicar todo lo anterior fue parte de un proceso que se iteró y se revisó múltiples veces con mi grupo a lo largo de 6 meses para llegar a un buen resultado.</p><p>Muchas gracias a las profesoras, por la paciencia y ¡dedicación a los alumnos!</p><p>Me sentí acompañada durante toda la cursada, siempre estuvieron a disposición de los alumnos. ¡Lo recomiendo!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a878f9d164b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Caste Study: Parquímetros en C.A.B.A]]></title>
            <link>https://marocchicamila.medium.com/ux-caste-study-parqu%C3%ADmetros-en-c-a-b-a-5bedb7589542?source=rss-6516c6e1b471------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bedb7589542</guid>
            <category><![CDATA[parking-system]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[parquimetro]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Cami Marocchi]]></dc:creator>
            <pubDate>Sun, 05 Jan 2020 00:21:03 GMT</pubDate>
            <atom:updated>2020-01-08T12:31:05.731Z</atom:updated>
            <content:encoded><![CDATA[<p>¿Cómo eliminar la complejidad de su uso?</p><h3>A raíz de la movida contra la iniciativa del gobierno porteño que incrementará a más de 84 mil los estacionamientos tarifados. Se me ocurrió trabajar sobre este <em>issue</em> que afecta a varios usuarios en la Ciudad de Buenos Aires. ¿Cómo mejorar esta experiencia de usuario? ¿Cómo mejorar este servicio impuesto?</h3><h4><strong>Contexto</strong></h4><p>Para quienes no conocen, los parquímetros miden el tiempo de estacionamiento de un vehículo en una zona determinada de la vía pública en que se debe pagar para estacionarse y que cobra al usuario la cantidad debida en base a horas que deje su auto.</p><p>Actualmente el estacionamiento tarifado funciona mediante máquinas tickeadoras, que operan de lunes a viernes de 8hs a 21hs y los sábados de 8hs a 13 hs. Los domingos los espacios son gratuitos. Esto mejora la circulación, mediante un ordenamiento del tránsito en las zonas del micro/macro centro de la Ciudad, estacionados en la vía pública.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E6GvqIND03Xn8jsjSU8sNg.jpeg" /><figcaption>Máquinas de frente, carteles en vía pública, señalética.</figcaption></figure><blockquote>La clave de un producto o servicio que funciona es su ajuste con las necesidades de las personas que lo van a usar</blockquote><h4>La problemática</h4><p>El usuario debe seguir las instrucciones o pasos, indicadas en el frente de la máquina&gt; introducir monedas (sí, monedas) o cospeles necesarios de acuerdo al tiempo estacionado&gt;comprobar los datos de la pantalla y emitir el ticket mediante un botón. Con el ticket en mano, volver a su auto estacionado, y dejarlo dentro en un lugar visible para cuando pase el control.</p><p>Para abonar con cospeles, debe buscar el cartel en la cuadra donde estacionó que indica en que kiosco puede comprar las fichas de acuerdo las horas de estacionamiento. Si la pantalla o el parquímetro tiene problemas, <strong>no debe dejar el auto</strong> estacionado y puede llamar a un número indicado en la tickeadora. Si el plazo venció, el vehículo será removido por la grúa.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CmrSIZvgP-xPV-YW7WF8JQ.png" /><figcaption>Customer Journey</figcaption></figure><h3>¿Con qué herramientas investigo?</h3><p>Encuestas (representatividad)<br>Entrevistas individuales a usuarios (3)<br>Estudios Etnográficos, mediante observación directa presencial.<br>Nro. de Pain points en cada paso <br>Hipótesis<br>Test multivariante de rebote y eficacia sobre las posibles oportunidiades de mejora</p><h3>Mi experiencia usando parquímetro</h3><p>Estacioné mi auto sobre la calle Posadas. Habían dos opciones de puntos de venta de fichas. Pagar en monedas no era posible, ¿quien lleva $30 en monedas de $5, o ahora $10? Fui a la dirección Posadas 1271. Era un local que cerró definitivamente. Ok, vamos a la opción 2) Posadas 1173, a 2 cuadras de donde estacioné. Una ferretería que vende cospeles. Compré 2 y volví al lugar donde estaba mi tickeadora correspondiente.</p><p>Introduje las dos fichas. Me las devolvió. Volví a ingresarlas de a una, presioné el botón ticket pero me entregó uno solo; una de las fichas me fue devuelta. Repetí la operación y recibí el ticket faltante. Caminé hasta mi auto, y dejé los dos comprobantes visibles. FIN.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1MTlvF61GjJWAyql_VD6wg.jpeg" /><figcaption>Los pasos de mi experiencia.</figcaption></figure><h4>Resultados</h4><p>A través de las entrevistas y observaciones, los inconvenientes son: encontrar los puntos de venta de cospeles y comprarlos; olvidarse del tiempo transcurrido de estacionamiento; encontrar las máquinas tiqueadoras en buenas condiciones ya que muchas no tienen buen funcionamiento o legibilidad.</p><h4>Oportunidades de mejora</h4><p><strong>Aclaro, que no tuve el presupuesto ni el tiempo para abordar este desafío, pero en el futuro, se podría volver a visitar el proyecto y centrarnos en los aspectos colaborativos de la gestión de tareas.</strong></p><p>El estacionamiento tarifado, no se puede evitar, es un regimen ya aprobado e impuesto. Entonces, mi pregunta es ¿se puede omitir el paso de la compra de cospel? ¿se puede prescindir de un ticket, volver y dejarlo en el auto?</p><p>Mi <strong>primer</strong> pensamiento: crear una app para realizar el pago que puede ser del Gobierno. Pero implica un costo alto y tiempo para desarrollarla. Además no todos quieren descargar otra aplicación más en el celular.</p><p>Entonces… máquinas que aceptan tarjetas de crédito o débito por contactless. El problema con esta solución, es la logística y altos costos necesarios para implementarlos y reemplazar las viejas máquinas.</p><h4>Mi posible solución</h4><p>Sé que no es ninguna novedad hoy en día. Se puede colocar un calco en cada máquina, con un <strong>Código QR</strong> escaneable que luego se abona desde el celular, puede ser mediante MercadoPago u similar. Los pasos serían: escanear código, ingresar pago correspondiente a la estadía, ingresar el Nro. de terminal en la cual se está pagando y por último el dominio/patente y DNI.<br><strong>¿Y cómo sabe el control que abonamos la tarifa? </strong><em><br></em>Estos datos se pueden cargar en una base a la que tienen acceso los controladores. Cuando pasa el remolque verifica por la patente si abonó o no.</p><p>Para que esta solución sea palpable, fácil de acceder y no haya un <em>gap</em> entre quienes no se familiarizan con este nuevo sistema; el mismo código puede ser un educador de cómo usarlo, como guía de paso a paso. Además los propios parquímetros pueden tener una breve guía de pasos de como abonar.<br>La opción de pago con cospel, puede seguir vigente mientras se ofrece esta alternativa.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CO-WpCEZgUBh5-VAF9s9aQ.jpeg" /></figure><h3>Conclusión</h3><p>De esta forma reducimos el uso de cospel, el tiempo en buscar el kisco, volver al auto para dejar el ticket. Y facilita a los usuarios a tener un seguimiento en su celular, del tiempo que resta de estacionamiento. Como ya mencioné, este caso aún está en revisión. ¡Cualquier aporte es bienvenido!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bedb7589542" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>