<?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 Diego Menezes on Medium]]></title>
        <description><![CDATA[Stories by Diego Menezes on Medium]]></description>
        <link>https://medium.com/@diegomenezesux?source=rss-bb7c91c07189------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Ie3CDX0yLlFOwbEajkLpfA.png</url>
            <title>Stories by Diego Menezes on Medium</title>
            <link>https://medium.com/@diegomenezesux?source=rss-bb7c91c07189------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:12:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@diegomenezesux/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[High-Conversion Landing Pages — Contabilizei (Fintech UX & CRO)]]></title>
            <link>https://diegomenezesux.medium.com/high-conversion-landing-pages-contabilizei-fintech-ux-cro-1653da07525f?source=rss-bb7c91c07189------2</link>
            <guid isPermaLink="false">https://medium.com/p/1653da07525f</guid>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Diego Menezes]]></dc:creator>
            <pubDate>Thu, 26 Feb 2026 20:17:58 GMT</pubDate>
            <atom:updated>2026-02-26T20:21:17.342Z</atom:updated>
            <content:encoded><![CDATA[<p>Visual showcase of the final UI implementation for a high-conversion landing page developed for Contabilizei. The project focused on conversion optimization (CRO), performance-driven UX, layout hierarchy, trust-building elements, and data-informed design decisions. The interface reflects alignment between product strategy, marketing acquisition goals, and measurable business impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9VArnQgmO4UZSPVC39r4Gg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k-LZ-PwsQs7d9cHG.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1653da07525f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ambev AI Products]]></title>
            <link>https://diegomenezesux.medium.com/ambev-ai-products-4a4ec9b39726?source=rss-bb7c91c07189------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a4ec9b39726</guid>
            <dc:creator><![CDATA[Diego Menezes]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 15:13:50 GMT</pubDate>
            <atom:updated>2025-08-02T15:13:50.908Z</atom:updated>
            <content:encoded><![CDATA[<p>I spearheaded a strategic initiative to integrate generative AI into Ambev’s core operations, focusing on both employee efficiency and enterprise security. The project encompassed the end-to-end design of two flagship products: an automated HR assistant to reduce operational overhead, and a secure, in-house conversational AI to protect sensitive company data. Let’s dive in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CfsR3JDaCQpvtPuBywzV3w.png" /></figure><h3>Let’s talk about Stellar</h3><p>Ambev’s HR department faced a significant operational challenge: a high volume of repetitive employee inquiries. This constant stream of tickets about company policies, benefits, and payroll created a bottleneck that delayed response times and, more importantly, prevented the HR team from focusing on more strategic, high-impact work.</p><p>Our solution was <strong>Stellar</strong>, an intelligent virtual assistant designed to be the first point of contact for all HR matters. More than a simple chatbot, Stellar leverages a powerful Large Language Model (LLM) enhanced with custom Retrieval-Augmented Generation (RAG) technology. This allows it to securely access Ambev’s internal knowledge base to provide instant, accurate, and context-aware answers, 24/7.</p><p>By empowering employees with self-service, Stellar successfully offloaded a significant number of tickets from the HR department. This not only accelerated problem resolution but also drastically reduced operational costs, allowing our HR professionals to dedicate their valuable time to more complex human challenges.</p><blockquote><em>“</em>The goal of AI is to empower humans to be better, to be more creative, and to be more productive<em>”<br> — </em><strong><em>Satia Nadella</em></strong><em>, CEO of Microsoft</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFwwGTIayU6Hw41R5KN-TA.png" /></figure><h3>The Challenge</h3><p>To create an assistant that was not just intelligent but also trustworthy and globally effective, we had to overcome two significant and interconnected hurdles:</p><p><strong>1. Creating a Single, Trustworthy Source of Truth</strong></p><p>Stellar’s primary challenge was knowledge. To be useful, it needed to become the single, authoritative source for all HR information across Ambev. This meant ingesting and correctly interpreting a massive, diverse dataset — from complex benefits, salary, and vacation policies to simple employee contact information (“Who is…”).</p><p>The information had to be not only comprehensive but also <strong>100% accurate</strong>. Any error could erode user trust instantly and create serious issues for employees. The central question was: how could we effectively build, manage, and constantly update this vast ‘brain’ to ensure its reliability?</p><p><strong>2. Designing for a Global, Multilingual Workforce</strong></p><p>Ambev’s workforce is global. The second major challenge was to design an experience that felt seamless and natural for employees worldwide, communicating in multiple languages including English, Portuguese, Spanish, and languages used in our Indian operations.</p><p>This went far beyond simple translation. Stellar needed to understand regional nuances in HR policies and provide culturally relevant information. We had to create a system that could not only speak many languages but also understand many different workplace contexts, ensuring every employee, regardless of location, felt equally supported and understood. This required a robust back-end system that someone could easily manage — a challenge that directly led to the design of a custom Admin Portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MI7GSEToj9hKQF4Wqapi7A.png" /></figure><p>Of course. This section is essential to show recruiters your structured thinking and how you apply the user-centered design process to a complex technical product like an AI assistant.</p><p>We will outline each step, explaining the “why” behind your actions to demonstrate strategic intent. Here is a draft for this section, written in English.</p><h3>Our Design Process: Crafting a Human-Centric AI</h3><p>To tackle the complexity of creating a global AI assistant from the ground up, we followed a structured, user-centric design process. This ensured that every decision was grounded in user needs and business goals.</p><p><strong>1. Discovery &amp; Strategy</strong> We began by aligning with key stakeholders from HR and leadership to define the project’s core objectives: reducing operational costs, accelerating response times, and improving the overall employee experience. We analyzed thousands of existing HR support tickets to identify the most frequent and repetitive questions. This data-driven approach was foundational, allowing us to prioritize features and define clear success metrics for Stellar.</p><p><strong>2. User Research</strong> To ensure we were building an assistant that employees would actually use and trust, we conducted in-depth interviews with staff across different departments and global regions. This research helped us create user personas (e.g., “The New Hire,” “The Manager Abroad”) and map their current, often frustrating, journeys for simple HR tasks. We uncovered key pain points and needs, which validated the demand for an instant, centralized, and multilingual solution.</p><p><strong>3. Ideation &amp; Prototyping</strong> Our ideation focused on two parallel streams:</p><ul><li><strong>Conversation Design:</strong> We defined Stellar’s personality: helpful, professional, and clear. We then mapped out conversational flows for key queries, scripting dialogues to feel natural rather than robotic.</li><li><strong>Interface Design:</strong> We created low and high-fidelity prototypes for the chat interface itself, as well as for the crucial <strong>Admin Portal</strong> — the tool that would empower the HR team to manage and update Stellar’s knowledge base without technical help.</li></ul><p><strong>4. Testing &amp; Interviews</strong> We conducted several rounds of moderated usability testing. Employees were given specific tasks to complete using our interactive prototypes (e.g., “Find out the company policy on remote work”). These sessions allowed us to gather direct feedback on the clarity of the interface, the naturalness of the conversation, and the user’s overall trust in the answers provided. Insights from this testing led to crucial refinements in both the conversational scripts and the UI layout, ensuring the final product was truly intuitive and reliable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gCGBHwmu40Z8F3-VG5zoKQ.png" /></figure><h3>Implementation &amp; Results: A Landmark Achievement in Operational Efficiency</h3><p>The rollout of Stellar marked a turning point for Ambev’s internal operations. What began as a strategic initiative to improve HR support quickly became an indispensable, company-wide tool, fundamentally changing how employees access information.</p><p>The results have exceeded all expectations, delivering massive and measurable value.</p><blockquote><strong><em>Over $1.2 Million in Annual Cost Savings</em></strong></blockquote><blockquote><em>By automating responses to thousands of inquiries and enabling instant, 24/7 self-service, Stellar has drastically reduced the operational costs associated with manual HR support. This has resulted in a direct, estimated </em><strong><em>annual saving of more than $1.2 million</em></strong><em> for the company.</em></blockquote><h4>An Evolving, Omnichannel Ecosystem</h4><p>Stellar’s success is also measured by its continuous growth and its expanding reach. The product is constantly evolving to meet employees where they are, ensuring support is frictionless and always accessible.</p><ul><li><strong>Direct WhatsApp Integration:</strong> In a major step forward, Stellar is now integrated with WhatsApp, allowing employees to get instant answers through the world’s most popular messaging app.</li><li><strong>Multi-Platform Presence:</strong> Beyond WhatsApp, Stellar has been seamlessly embedded within key company portals and is also available as both a standalone web application and a convenient widget, ensuring help is always just a click away.</li></ul><h4>A Foundation for Future Innovation</h4><p>Stellar is not a static tool; it’s a constantly learning and evolving platform. The insights gathered from user interactions are fed back into the system to improve its intelligence and expand its capabilities daily. This culture of continuous improvement ensures that Stellar will not only maintain its high performance but also serve as a foundational piece for future AI-driven innovations at Ambev.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-EPARDfux4yHv87kwnNFA.png" /></figure><p>Pioneering in artificial intelligence requires trust, courage, and above all, collaboration. These projects are the result of the joint effort of an exceptional team. I am grateful to the Ambev leadership for their vision for the future, to the engineering and data teams who brought the intelligence to life, and to all the employees who embraced these new tools and helped us evolve. Together, we didn’t just implement a new technology; we took an important step toward making Ambev a more efficient and secure workplace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fGS7xRHG9Lo6BafO87JsIA.jpeg" /></figure><h3>Quick talk about GPTap</h3><h4>Introduction</h4><p>The second pillar of our strategic AI initiative was GPTap, an enterprise-grade conversational AI designed to empower employees while safeguarding Ambev’s most critical asset: its data. As a secure, in-house alternative to public tools like ChatGPT, GPTap provides the full power of a large language model without the risk of exposing sensitive corporate information, fostering innovation with peace of mind.</p><h4>The Challenge</h4><p>The rise of powerful public AI models presented a double-edged sword. Employees were eager to leverage these tools to boost productivity — for tasks like drafting emails, summarizing reports, and generating code. However, using public platforms for work-related tasks created an unacceptable security risk, potentially exposing confidential strategies, financial data, and intellectual property. The challenge was clear: how could we provide our teams with the innovative power of generative AI while ensuring our corporate data remained 100% secure within our own walls?</p><h4>Our Design Process</h4><p><strong>1. Discovery &amp; Research</strong> We began by interviewing employees from various departments (marketing, legal, engineering) to understand their desired use cases for a chat AI. We partnered closely with IT Security and Legal stakeholders to define strict data handling protocols and establish the core requirements for a secure, enterprise-ready platform. This phase was crucial for understanding both user needs and business risks.</p><p><strong>2. Ideation &amp; Prototyping</strong> Our design focused on creating a familiar, intuitive chat interface while building in crucial enterprise-grade features. We prototyped functionalities like conversation history management, clear data usage disclaimers, and a feedback mechanism for improving the model’s responses. The primary goal was to make the secure, internal option the easiest and most trusted choice for employees.</p><p><strong>3. Testing &amp; Interviews</strong> Through moderated testing sessions with our prototypes, we validated the usability of the interface and, more importantly, the user’s understanding of its security benefits. We gathered feedback to refine prompts and ensure GPTap was genuinely useful for the specific tasks identified in our research, confirming it could effectively replace the need for public AI tools for all work-related activities.</p><h4>Implementation and Results</h4><p>GPTap was successfully rolled out across the company, immediately closing a significant security vulnerability and becoming a go-to tool for employees. It has fostered a culture of safe and responsible AI experimentation.</p><ul><li><strong>Strategic Risk Mitigation:</strong> The platform has effectively eliminated the risk of sensitive data leaks to public AI models, protecting Ambev’s intellectual property and ensuring compliance.</li><li><strong>Boosted Productivity:</strong> Teams now leverage GPTap to accelerate a wide range of tasks, from content creation and data analysis to code generation, leading to significant, company-wide efficiency gains.</li><li><strong>High Adoption:</strong> The tool has seen widespread and enthusiastic adoption, demonstrating a clear and previously unmet demand for safe and powerful internal AI solutions.</li></ul><h4>Acknowledgements</h4><p>I want to extend special thanks to Ambev’s IT Security and Legal teams, whose partnership was fundamental to the success of GPTap. Their expertise ensured we built a tool that was not only powerful but also impeccably secure. Thank you also to the development team and to Ambev’s leadership for their deep commitment to proactive and responsible innovation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a4ec9b39726" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ambev Enterprise Design System 2.0]]></title>
            <link>https://diegomenezesux.medium.com/ambev-design-system-66f000a0c2d3?source=rss-bb7c91c07189------2</link>
            <guid isPermaLink="false">https://medium.com/p/66f000a0c2d3</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ambev]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Diego Menezes]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 13:49:10 GMT</pubDate>
            <atom:updated>2026-02-26T19:04:50.209Z</atom:updated>
            <content:encoded><![CDATA[<p>I architected Ambev’s Enterprise Design System to unify brand expression and scale digital products globally. Built as a single source of truth, the system supports multiple products and teams across the organization.</p><p>Structured with scalable components and documented in Storybook, the library includes over 70 reusable components aligned between design and engineering.</p><p>More than a UI library, the system became the foundation for consistent, efficient product development at scale.</p><p>Let’s dive in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCM9lXcD6GKb20v20qlykw.png" /></figure><h3>Building the Enterprise Design System</h3><p>I led the creation of Ambev’s first global Design System, establishing the foundational framework for the world’s largest brewing company. Built as a single source of truth, the system unified a fragmented digital ecosystem, accelerated product development, and strengthened brand consistency at scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*2xBV811Ud_Yl0EhgpyGIdg.png" /></figure><p>Before the system, dozens of teams worked in silos without shared standards, resulting in inconsistencies, duplicated effort, and slower delivery. The challenge was to bring structure, alignment, and scalability — creating a unified foundation capable of supporting multiple products and empowering designers and developers globally.</p><h4>The Goal: Unification, Speed, and Quality</h4><p>The mission was to architect a scalable Design System from the ground up — one that could unify brand expression, streamline workflows, and elevate product quality across the organization.</p><p>The objectives were clear:</p><ol><li><strong>Establish</strong> a unified design language aligned with Ambev’s brand identity.</li><li><strong>Accelerate</strong> and mantain efficiency for design and engineering teams.</li><li><strong>Ensure</strong> consistency and quality across all digital products.</li></ol><p>The outcome was a governed, living system adopted company-wide. With over 70 reusable components documented in Storybook, the Design System became the foundation for new digital products, improving operational efficiency and strengthening cross-team collaboration.</p><blockquote><em>“</em>A design system isn’t a project. It’s a product, serving products.<em>”<br> — </em><strong><em>Nathan Curtis</em></strong><em>, Design System Expert</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pXgHYYlueLWtt4XO0r0fZQ.png" /></figure><h3>The Challenge</h3><p>The project required overcoming two critical challenges: Design System adoption and global governance.</p><h4>1. From Mandate to Movement: Driving Adoption</h4><p>Despite strong executive sponsorship from New York leadership, adoption could not rely on a top-down mandate. Product teams with independent roadmaps and tight deadlines would only integrate the Design System if it clearly improved efficiency, scalability, and component flexibility.</p><p>The challenge was to position the system as a product and a service — not a restrictive rulebook. This required robust documentation standards, clear contribution workflows, scalable component architecture, and responsive support. Governance had to balance consistency with autonomy across multiple digital products.</p><h4>2. Orchestrating a Global Collaboration</h4><p>The system was built across three regions: strategic leadership in New York, design management in Brazil, and engineering in India. This demanded strong stakeholder alignment, cross-functional collaboration, and asynchronous workflows.</p><p>Managing time zones, cultural differences, and English-based communication required structured documentation, transparent decision-making, and clear semantic alignment between design and engineering. Governance and collaboration were as critical as the components themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rpDqfMnBKBibV2EAfv86zA.png" /></figure><h3>The Process</h3><p>To ensure long-term scalability and adoption, the Design System was built on a structured Discovery and validation process. Rather than jumping into component creation, we focused on understanding existing workflows, system failures, and organizational needs.</p><p>The Discovery phase was grounded in UX research, stakeholder alignment, and ecosystem analysis. The objective was to define a scalable architecture, governance model, and contribution framework capable of supporting multiple products and distributed teams.</p><p>Every design decision was based on evidence, operational gaps, and real product team needs — ensuring the system would be technically viable, strategically aligned, and broadly adoptable..</p><h3>The Discovery: Understanding the Ecosystem</h3><p>The Discovery phase focused on one core principle: building a scalable future required understanding past system failures and current operational needs. Our approach combined internal audits, stakeholder research, and competitive benchmarking to define a sustainable Design System architecture and governance model.</p><h4>1. Internal Audit: Learning from Past Failures</h4><p>We conducted a post-mortem analysis of previously attempted Design Systems at Ambev to understand why adoption failed.</p><ul><li><strong>Objective:</strong> Identify structural and governance gaps.</li><li><strong>Process:</strong> Audited legacy system architecture, documentation standards, and interviewed teams who had previously interacted with them.</li><li><strong>Key Insight:</strong> The main failure was not visual inconsistency — it was governance. Lack of ownership, maintenance processes, and a clear contribution model led to outdated components and loss of trust. Without a dedicated team and defined lifecycle management, system maturity quickly deteriorated.</li></ul><h4>2. Stakeholder Interviews: Mapping Real Product Needs</h4><p>We treated product squads as primary users and conducted structured interviews with lead designers and engineers across major digital platforms.</p><ul><li><strong>Objective:</strong> Map workflows, identify bottlenecks, and define priority components.</li><li><strong>Process:</strong> Interviews focused on UI inconsistencies, duplicated effort, delivery friction, and alignment with engineering.</li><li><strong>Key Insight:</strong> Teams were reinventing components repeatedly, creating visual fragmentation and thousands of wasted development hours. There was a strong demand for a centralized, scalable, and trustworthy component library.</li></ul><h4>3. Competitive Benchmarking: Defining Best Practices</h4><p>To ensure enterprise-level maturity, we benchmarked leading Design Systems including Material Design, Polaris, and Carbon.</p><ul><li><strong>Objective:</strong> Identify best practices in documentation, governance, contribution workflows, and white-label scalability.</li><li><strong>Process:</strong> Analyzed architecture patterns, token structures, and documentation ecosystems.</li><li><strong>Key Insight:</strong> This validated our decision to adopt Storybook for interactive documentation and reinforced the need for clear design principles, semantic alignment, and a transparent component contribution framework from day one.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_1-xWj-oE8dz7bfpsZ5ytw.png" /></figure><h3>Implementation and Results</h3><p>The transition from concept to enterprise standard marked a structural shift in how digital products are built at Ambev. Through a phased rollout, defined governance model, and robust Storybook documentation, the Design System evolved from an initiative into a scalable, living framework supporting product teams across the organization.</p><p>Its impact is measurable and continuous.</p><blockquote><strong><em>73% Adoption Rate</em></strong></blockquote><blockquote><em>Today, 73% of all new digital applications are built using the Design System. Adoption continues to grow as teams recognize its operational efficiency, scalability, and structured support model</em>.</blockquote><h4>Acceleration &amp; Operational Efficiency</h4><p>By providing validated, reusable components aligned between design and engineering, the system eliminated redundant work and streamlined the development lifecycle.</p><ul><li><strong>The result:</strong> <strong>an estimated 40% increase</strong> in design and front-end efficiency, reducing rework and enabling teams to focus on high-value problem solving rather than rebuilding foundational UI patterns.</li></ul><h4>Cost Reduction &amp; Business Impact</h4><p>The “build once, use everywhere” model significantly reduced duplicated development effort across projects. Increased time-to-market and workflow optimization translated into tangible cost savings and measurable ROI.</p><p>Beyond efficiency gains, the Design System became a strategic asset — strengthening governance, ensuring brand consistency, and positioning Ambev with greater agility in responding to market demands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XMZi7WL8wfoSRTM5_M5E8w.png" /></figure><h3>Reflection &amp; Key Learnings</h3><p>This project reinforced that a Design System is fundamentally a product — not a deliverable. Its success depends on governance, ownership, a clear roadmap, and continuous iteration. A component library without lifecycle management and structured support will inevitably lose relevance. Treating the system as a service for product teams was critical to achieving sustainable adoption.</p><p>Working across New York, Brazil, and India strengthened my understanding of global collaboration and stakeholder alignment. Clear documentation, asynchronous workflows, and semantic alignment between design and engineering were not optional — they were the foundation of system maturity and scalability.</p><p>Finally, adoption is earned through value, not authority. Executive sponsorship accelerates visibility, but long-term adoption comes from solving real operational pain points. By grounding decisions in research and delivering high-impact components early, we built trust, momentum, and a scalable framework that teams chose to adopt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-EPARDfux4yHv87kwnNFA.png" /></figure><p>This achievement was the result of strong cross-functional collaboration across design, engineering, product, and leadership teams globally.</p><p>I’m grateful to the teams in <strong>New York, Brazil</strong>, and India who contributed to building and evolving a Design System that became a foundational enterprise standard at Ambev.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66f000a0c2d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rede Globo (UX/UI)]]></title>
            <link>https://diegomenezesux.medium.com/rede-globo-ux-ui-50ea5cd1341e?source=rss-bb7c91c07189------2</link>
            <guid isPermaLink="false">https://medium.com/p/50ea5cd1341e</guid>
            <category><![CDATA[product-designer]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Diego Menezes]]></dc:creator>
            <pubDate>Sun, 29 Dec 2024 22:53:25 GMT</pubDate>
            <atom:updated>2024-12-29T22:53:25.936Z</atom:updated>
            <content:encoded><![CDATA[<p>Redesign a communication system for Rede Globo and its affiliates to improve usability and accessibility. The system facilitates scheduling, alerts, and voting for TV awards, focusing on intuitive design and mobile compatibility</p><p>Let’s dive in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B5hTBh2XLtPxYrOowepjxQ.jpeg" /></figure><h3>Introduction</h3><p>This case study focuses on a project undertaken for Rede Globo, one of Brazil’s largest media networks, and its nationwide affiliates.</p><p>The objective was to redesign a complex communication system that handled program scheduling, real-time alerts, and voting for TV awards. The existing system suffered from poor usability, which led users to bypass it entirely and reach out to the team directly for support. The diversity of the users — from tech-savvy professionals to those with limited digital access — added another layer of complexity.</p><p>The challenge was clear: we needed to create an intuitive, mobile-friendly platform that could address these pain points and empower users across varied technical backgrounds. The goal was to improve efficiency while reducing the workload of the support team.</p><p>The result? A highly praised system that increased user adoption by over 30%, significantly reducing the need for support while enhancing the communication process for affiliates nationwide.</p><p>The project was completed in 12 months.</p><blockquote><em>“You can’t design for everyone, but you can design for someone.”</em><br> — <strong>Brian Chesky</strong>, co-fundador do Airbnb</blockquote><h3>The Challenge</h3><p>Rede Globo’s communication system was at the heart of its collaboration with affiliates, yet it faced significant barriers that limited its effectiveness. The platform was outdated and difficult to navigate, leading users to avoid it entirely and rely on direct support from the central team.</p><p>The diversity of the user base posed another layer of difficulty. Affiliates ranged from large, resourceful stations with tech-savvy teams to smaller ones with limited access to modern technology. Many users relied heavily on mobile devices due to outdated computers or their on-the-go work style.</p><p>The system’s primary functionalities — such as handling program scheduling, broadcasting critical alerts, and enabling voting for prestigious TV awards — were crucial but often overshadowed by usability issues.</p><p>The challenge was to transform this fragmented experience into a cohesive, intuitive platform that could address these diverse needs while reducing dependency on support teams. Accessibility, usability, and scalability became the cornerstone of our approach to overcome these hurdles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FF6blqzm_aZwG5q1X2yG_A.png" /><figcaption>Redesigned home page of Rede Globo’s communication system, featuring key messages, program scheduling links, and a user-friendly, intuitive interface.</figcaption></figure><p>Example of the Home Screen above</p><h3>Discovery</h3><p>The discovery phase played a critical role in understanding the unique challenges faced by Rede Globo and its affiliates. We began with a series of interviews and research to dive into the needs, pain points, and goals of the various stakeholders involved.</p><p>A key aspect of the discovery was understanding the business side of the system. This platform not only facilitated communication but also helped Rede Globo increase revenue. By identifying important events such as sooccer matches, novela finales, and successful programs, the broadcaster could strategically sell sponsorships for these key dates, boosting overall earnings.</p><p>Our focus during this phase was to identify the core functionalities of the communication system, understand the frustrations with the previous platform, and clarify the must-have features, secondary improvements, and overall priorities for the new design. We organized discussions with stakeholders to ensure that all voices were heard and that we were aligning on the key areas that required attention.</p><p>To support this process, we used collaborative tools to map out what elements were essential, which could be simplified or removed, and what might be developed in future iterations. This approach helped us prioritize the most pressing needs while creating a roadmap for the next steps.</p><p>The discovery phase was not only essential for gathering valuable insights but also laid the foundation for building a strong, collaborative relationship with Rede Globo’s team. It was the first crucial step in designing a solution that would improve the user experience for all involved.</p><h3>Research</h3><p>Our research phase began with a series of virtual interviews with key stakeholders across different roles within Rede Globo and its affiliates. This included a diverse range of individuals, from operational employees to managers, directors, and teams responsible for communication and broadcasting. These interviews were conducted via video call to ensure we could connect with participants, regardless of their location.</p><p>The objective of these interviews was to collect a wide variety of perspectives on what was most important for the new communication system. By engaging with stakeholders at different levels within the organization, we gained a deep understanding of the users’ needs, frustrations, and expectations for the system.</p><p>The insights we gathered from these conversations were essential in shaping the design approach. Each stakeholder brought forward valuable feedback, helping us to pinpoint critical features, understand existing system bottlenecks, and identify key areas for improvement.</p><p>This user-centered research approach enabled us to develop a design strategy that was grounded in the real needs and preferences of the end-users. It set a strong foundation for the subsequent ideation and prototyping stages, ensuring the system would meet the requirements of all involved.</p><h3>Ideation and Prototyping</h3><p>The ideation and prototyping phase began with the creation of an initial style guide for Rede Globo’s communication system. This guide was developed based on the broadcaster’s established visual identity, ensuring consistency with their official colors, fonts, and other branding elements. We designed key visual components such as icons, color palettes, font sizes, and layout structure, all aligned with the brand’s standards.</p><p>Once the style guide was approved, we proceeded with the prototyping stage, starting with the development of initial wireframes. These wireframes served as a blueprint, outlining the system’s layout, the placement of elements, and the organization of menus and key functions.</p><p>The wireframes provided a tangible representation of our design concepts, enabling us to discuss, test, and refine the system’s structure, navigation, and user flow. This phase was essential for visualizing the project’s overall structure before diving into more detailed design and development work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RExI2l2XYw99h2Madg6CEA.png" /></figure><p>First idea of the Home Screen</p><h3>Testing and Interviews</h3><p>Once the high-fidelity prototype was developed in Figma, we moved on to the crucial testing phase. We conducted interviews with a diverse group of users, presenting the prototype to gather their insights, feedback, and suggestions for improvement. This testing phase proved to be highly valuable, providing us with a wealth of positive responses as well as constructive ideas to enhance the design.</p><p>A key outcome of the testing was the decision to simplify the visualization of the main communication screen. This change was based on user feedback and took into consideration the project’s timeline and available resources. While there were many ideas for the screen’s functionality, the testing process helped us prioritize features that would deliver the greatest value to users while remaining feasible for development within the set timeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tbF5ZTBSt0ZycNIVIiBcfA.png" /><figcaption>List solicitations screen</figcaption></figure><p>This user testing phase was crucial in ensuring that the communication system was intuitive and aligned with the users’ needs. We received valuable real-world insights that directly informed our design adjustments. The feedback from users helped guide us in making refinements that enhanced usability and overall effectiveness.</p><p>Moreover, this phase highlighted the importance of iterative design and the collaboration between designers, developers, and users. By working together, we were able to create a solution that was not only functional and feasible but also user-friendly and effective in meeting the needs of Rede Globo and its affiliates.</p><h3>Implementation and Results</h3><p>After the testing phase, we moved into the implementation stage, turning our validated design into a fully functional communication system. The screens were developed based on user feedback and the design decisions we made during the testing phase, ensuring that the final product was both aesthetically appealing and highly user-friendly.</p><p>The result was a system that successfully met the needs of Rede Globo and its affiliates, offering a significantly improved user experience over the previous platform. The client was extremely satisfied with the outcome, praising the design for its positive impact on their communication processes and overall user satisfaction.</p><p>This project was a hybrid undertaking, where I had the opportunity to contribute as both a UX and UI designer. My work was well-received, earning recognition from senior management and the client team. The project also strengthened the relationship between Rede Globo and the design team, highlighting our ability to deliver high-quality, user-centered solutions that directly addressed the client’s business needs.</p><p>This project was a clear example of how user-centered design, iterative testing, and close collaboration between stakeholders can result in a solution that is both visually appealing and functionally effective. It reinforced the importance of aligning user needs with business goals to create a system that delivers value for all parties involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jeFI5CwKAadyqxlGTLnIDQ.png" /></figure><p>Awards Screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-g3i3Ov7_ez8mn47VLTygQ.png" /></figure><p>CrawlWeb — Another quick system developed</p><h3>Reflection and Learning</h3><p>This project was an incredibly rewarding journey, marked by seamless collaboration and alignment from the start. From day one, the client and stakeholders were fully engaged and supportive, which allowed us to dive straight into solving their challenges with a clear vision and shared goals.</p><p>Empathy and effective communication were key throughout this process. Understanding the client’s needs and staying attuned to the evolving requirements of the users ensured that the design remained user-centered and impactful. Building a strong rapport with the team and stakeholders fostered a positive and productive environment, allowing us to make informed decisions and deliver a solution that exceeded expectations.</p><p>The project was significant not only because of its size and complexity but also because of the meaningful impact it had on the client’s operations. Being involved from the very beginning and working closely with key stakeholders gave me the opportunity to contribute to the project’s success in a way that was both rewarding and educational.</p><p>Flexibility was also essential. As with any large project, adjustments were made along the way, and each challenge presented an opportunity to refine and enhance the design. I’ve learned that adaptability is crucial in delivering solutions that meet both user and business needs effectively.</p><p>I am deeply grateful to the entire team, stakeholders, clients, users, META, and Rede Globo for the trust and collaboration that made this project a success. This experience reaffirmed my belief in the power of empathy, flexibility, and user-centered design in creating truly impactful solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B_5MX2HchAkujmocOltXVg.png" /></figure><p>Thank you to the entire team, stakeholders, clients, users, and to META and Rede Globo for your trust, collaboration, and invaluable contributions. This project wouldn’t have been possible without each of you, and I am truly grateful for the opportunity to work together towards this shared success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50ea5cd1341e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ABI-Inbev (UX/UI)]]></title>
            <link>https://diegomenezesux.medium.com/abi-inbev-69c4a74d77bc?source=rss-bb7c91c07189------2</link>
            <guid isPermaLink="false">https://medium.com/p/69c4a74d77bc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Diego Menezes]]></dc:creator>
            <pubDate>Sat, 24 Jun 2023 17:15:59 GMT</pubDate>
            <atom:updated>2024-12-24T00:57:36.446Z</atom:updated>
            <content:encoded><![CDATA[<p>Design a comprehensive system that would streamline the employee qualification and review process. This would include facilitating meetings, voting, and various other elements that contribute to effective personnel management.</p><p>So, let’s start!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iigON6GpJx9oceubNJU7kA.jpeg" /></figure><h3>Introduction</h3><p>This case study centers around a project undertaken for the People Tech team at ABI-Inbev, a global enterprise with over 200,000 employees.</p><p>The project was a complex one, not only because of the intricate system required but also due to the client’s previous unfavorable experiences with consultancies. The existing system was burdened with a poor user experience (UX) that significantly hampered the review process, leading to skepticism and frustration from the client.</p><p>Thus, the challenge was two-fold: we needed to design a user-friendly, efficient system while rebuilding trust and confidence with the client. It was an incredible journey, one that demanded creativity, empathy, and resilience.</p><p>The outcome? A successful project that left everyone satisfied, paving the way for a stronger relationship with the client and an enhanced review process for the entire organization.</p><p>It was made in 11 months.</p><blockquote><em>“</em><strong><em>For those who don’t know where they are going, any path will do.”</em></strong></blockquote><h3>The Challenge</h3><p>The central challenge of the project involved reconciling the multifaceted needs of both the business and people teams in ABI-Inbev. The employee qualification and review process was a year-long endeavor, punctuated by numerous meetings involving various managers tasked with voting on and discussing employee performance. Scores were recorded, discussions were held about potential promotions, and it was a demanding task that required a robust, efficient system to support it.</p><p>Adding to this complexity was the need for a ‘Talent Card’ — a visual representation of an employee’s professional profile, akin to a resume, that the employees themselves would fill out. This feature added another layer of user interaction to the process and required careful UX consideration to ensure it was both intuitive for the employees to use and useful for the managers reviewing it.</p><p>Lastly, the managers needed access to visual dashboards presenting all the Key Performance Indicators (KPIs) of the employees. This was a critical feature that would enable them to make informed decisions about promotions and other HR actions.</p><p>However, the system that was previously in place had proven inadequate. It provided a poor user experience, which led to inefficiencies and frustrations that complicated an already intricate process. Therefore, the project’s primary objective was to create a new system that would streamline these processes and provide a more user-friendly and effective solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*02_it4hrsDP3_3RoJshr_g.png" /><figcaption><em>Example of the Talent Card Screen</em></figcaption></figure><h3>Discovery</h3><p>The discovery phase was an integral part of the project and provided valuable insights into the needs and pain points of the various stakeholders. The process was kicked off with a three-day on-site workshop at ABI-Inbev, where individuals from around the globe, including Argentina, Belgium, the United States, Canada, and via virtual participation, China and India, came together to discuss the project.</p><p>Our primary goal during this phase was to identify the most crucial sections of the system, understand the issues with the previous system, and define the mandatory improvements, secondary enhancements, and overall critical elements needed in the new design. To facilitate this, we organized stakeholders into groups and topics, working collaboratively to discuss and define the project’s needs and objectives.</p><p>We leveraged the Miro tool to create cards and categorize what was most important, what could be removed, and what could be reserved for a future development phase. This interactive approach allowed us to visualize and prioritize the needs, leading to a comprehensive understanding of what the new system should encompass.</p><p>This workshop not only proved to be a rich source of information but also set the stage for an open, collaborative relationship with the stakeholders. It was a significant first step in our journey to designing a system that would ultimately meet the needs of ABI-Inbev and improve the user experience for all involved.</p><h3>Research</h3><p>Our research phase involved conducting virtual interviews with key individuals from various roles within the organization. This included not just the common employees, but also managers, directors, and personnel from the people and human resources teams. These interviews were conducted via video call, ensuring we could reach stakeholders regardless of their geographical location.</p><p>The purpose of these interviews was to gather a diverse range of perspectives on what was important for the new system. By engaging with stakeholders from different levels and departments within the organization, we were able to gain a comprehensive understanding of the user needs, pain points, and expectations from the system.</p><p>The insights garnered from these discussions were invaluable in shaping our approach to the design. Each stakeholder offered unique viewpoints and experiences, helping us to define the necessary features, understand the bottlenecks in the current system, and identify areas of potential improvement.</p><p>This broad-reaching, user-centered research approach allowed us to create a design strategy that took into account the needs and preferences of all end-users, setting a solid foundation for the ideation and prototyping stages that followed.</p><h3>Ideation and Prototyping</h3><p>The ideation and prototyping stage of the project began with the creation of an initial style guide for the client’s approval. This guide adhered to the company’s standard colors and official fonts as per a guideline previously approved by the client. Elements such as icon designs, color schemes, font choices, and sizes were initially developed for this style guide, serving as the visual foundation for the system we were about to create.</p><p>Upon approval of the style guide, we moved on to the prototyping phase, beginning with the development of initial wireframes. These wireframes served to present our ideas for the layout and positioning of elements, as well as the structure of menus and other components of the system.</p><p>The wireframes provided a visual representation of our solution, allowing us to discuss, iterate and refine the design. This phase was crucial for visualizing the system’s structure, layout, and navigation before moving onto more detailed design and development stages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*-HryIpEuxFcpt4kAWVgp5A.png" /><figcaption>First idea of the Meeting Screen</figcaption></figure><p>All right, this could be more a ScratchFrame, but it’s just the way I like :D</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*mulXZ9odRufv1MhoThJQow.png" /><figcaption>First Style Guide Figma sent to approval</figcaption></figure><h3>Testing and Interviews</h3><p>Once the high-quality prototype was developed in Figma, the next crucial step was to test it with users. We scheduled interviews with a diverse group of users to present the prototype, soliciting their ideas, feedback, and opinions. This testing phase was an enlightening experience, and we received a wealth of positive feedback and invaluable suggestions for improvements.</p><p>One of the significant outcomes of this testing phase was the decision to simplify the meeting screen’s visualization. This adjustment was based on the users’ feedback and also factored in the development timeline and resources available. While we had many ideas for the meeting screen, the testing helped us prioritize and focus on elements that would offer the most user benefit while still being feasible for the development team to implement within the project timeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7WyOQLzXvPdRAsxzk7L9rQ.png" /><figcaption>Final Meeting View Screen</figcaption></figure><p>This user testing phase was instrumental in ensuring the system was intuitive and met the users’ needs, providing us with real-world insights that guided our design adjustments. Moreover, it exemplified the importance of iterative design and collaboration between designers, developers, and users in creating a product that is not only functional and feasible but also user-friendly and effective.</p><h3>Implementation and Results</h3><p>Following the testing phase, we moved onto the implementation stage, turning our validated design into a fully functional system. The screens were developed in line with the user feedback and our streamlined design decisions, carefully maintaining the aesthetics while ensuring functionality and user-friendliness.</p><p>The result was a system that successfully addressed the needs of the ABI-Inbev team, offering a vastly improved user experience compared to the previous system. The client was incredibly satisfied with the outcome, expressing high praise for the design and its impact on their employee qualification and review process.</p><p>The project was a hybrid undertaking in which I had the opportunity to work both as a UX and UI designer. My work received significant recognition, including commendations from the company’s top management. This project bolstered the relationship between ABI-Inbev and Invillia, the consulting firm I was part of, demonstrating our ability to deliver high-quality, user-centered design solutions that meet our clients’ needs.</p><p>(Note: Here, you can showcase the developed screens and other visual elements of the final design.)</p><p>This project was a testament to the power of user-centered design, iterative testing, and close collaboration between various stakeholders. It underscored the importance of understanding user needs and business requirements, translating them into a design that is both aesthetically pleasing and functionally effective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N_z51HX-Upaf-arF5RlLyQ.png" /><figcaption>Home Screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TuHc8s3b7plwsPELTx9ojA.png" /><figcaption>Dashboard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*02_it4hrsDP3_3RoJshr_g.png" /><figcaption>Talent Card</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fQ2UOumtos4zHpkSWtaMCw.png" /><figcaption>Manager Assessment</figcaption></figure><h3>Reflection and Learning</h3><p>This project was a journey marked by initial resistance, evolving into mutual trust and successful collaboration. In the beginning, the client was skeptical due to previous experiences with consulting firms, particularly due to the poor user experience of the prior system. However, as we delivered consistent high-quality work and received positive feedback from the company directors, the client’s attitude began to shift. They became more approachable and confident in our ability to meet their needs.</p><p>Resilience and empathy played key roles in the early stages of this project. It was essential to understand the client’s position and the reasons behind their initial skepticism. This understanding helped us approach the situation with patience and maintain a positive, collaborative relationship even when the going got tough.</p><p>This project was characterized by significant team changes, with me being the only constant from day one until the end. It was undoubtedly the largest project I have ever worked on, both in terms of the company’s size and the system’s complexity. Having the opportunity to participate from the first day, working closely with key stakeholders, allowed me to drive the project’s UX quality.</p><p>Flexibility was another crucial element of this project. Many screens and ideas had to be adapted or changed along the way, but I embraced these challenges as opportunities for growth and learning. This project reinforced my belief in the importance of adaptability in all aspects of life.</p><p>To everyone who has taken the time to read this case study, I extend my sincere thanks. I am available for any questions or further discussions. This project was not just about designing a system; it was a learning journey that reinforced the value of empathy, resilience, flexibility, and user-centered design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nwiVL1-mCKXDQDV5scCO6A.png" /></figure><p>I was one of those honored by Renato Bolzan, CEO of the company! <br>I was very happy with this recognition… I thank everyone here again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69c4a74d77bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serasa Mobile — UX/UI]]></title>
            <link>https://diegomenezesux.medium.com/serasa-mobile-ux-ui-444f0bdc355c?source=rss-bb7c91c07189------2</link>
            <guid isPermaLink="false">https://medium.com/p/444f0bdc355c</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Diego Menezes]]></dc:creator>
            <pubDate>Thu, 24 Jun 2021 18:20:53 GMT</pubDate>
            <atom:updated>2021-06-24T18:20:53.866Z</atom:updated>
            <content:encoded><![CDATA[<h3>Serasa Mobile — UX/UI</h3><p>Develop an application to encourage vendors to sell more credit consultation packages, called Lemonade, a product of Serasa Experian the largest credit analysis company in Latin America.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CqH2asMzw62eRA8D8GVzlw.png" /></figure><h3><strong>The Challenge</strong></h3><p>Serasa has Incentive Marketing aimed at salespeople to increase sales. The challenge was to create an application where it would be easy to analyze how many points the salesperson has and where they could request to exchange them for prizes.</p><blockquote>The challenge was to create a healthy challenge for whoever has the highest point between teams and an app where they had easy access on a daily basis.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*QpLSkfd1B0AOOsPd_x7VmA.png" /></figure><h3>Discovery</h3><p>The discovery stage is the first of the four stages of the <strong>Double Diamond process</strong>, and before doing anything, understanding what is to be done is as important as doing it.</p><p>I had to come up with some hypotheses. They would help me understand what was going to be done, for whom, where, when, how, and whether I was on the right track — as Alice’s cat rightly said:</p><blockquote><em>“F</em><strong><em>or those who don’t know where they are going, any path will do.”</em></strong></blockquote><p>For this, I used the <strong>5W1H </strong>method (Why, Who, When, Where, What and How) used in the book <strong>“Solving Product Design Exercises”</strong> by <em>Artiom Dashinsky</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*QpLSkfd1B0AOOsPd_x7VmA.png" /></figure><h3>5W1H Method</h3><p><strong>— Why</strong></p><p>Increase sales of the Lemonade package through awards and points contests among sales people.</p><p>We know that during the daily work, problems can happen to discourage sales people, so we developed an Endomarketing project for them to have a points game that they can later exchange for real prizes.</p><p>The idea of the application was so that they could always have their appointments at hand, and we could also send notifications directly to their devices.</p><p><strong>— Who</strong></p><p>This is an internal promotion only for employees who work directly in selling credit packages to companies.</p><p>As we will see below in the avatar, the profile of users is not technology but sales, so the application had to have a very easy look so they can use the exchange of points for products and consult the ranking.</p><p><strong>— When &amp; Where</strong></p><p><strong>When: </strong>Whether it is when a notification arrives saying that he has received points, or to see what awards he can redeem. The idea is something simple and direct, so that in a few clicks you can see how your position is in the ranking.</p><p><strong>Where: </strong>This system had already been developed in a desktop version, but not all vendors had access to computers all the time and ended up forgetting to access the portal to consult the points.</p><p>With the power of the mobile device, we can send push notifications to remind them of promotions, points, as well as it is much easier for them to check how they are doing with sales and scores.</p><p><strong>— What</strong></p><p>An application developed only for employees, where you can consult and exchange your points for prizes.</p><p>The application has API integration with virtual stores in the country, which already converts the original sales value to points, so the employee can select almost any existing product and use the points as a means of payment.</p><p>We will also have a ranking that at the end of pre-determined periods will release points for those who reach the highest positions.</p><p><strong>— How</strong></p><p>Since we had the desktop application as the basis for developing this mobile version, it was easy to identify the KPI’s we wanted to track.</p><ul><li>Daily access of registered users</li><li>How many points were converted into prizes</li><li>Impact on Sales</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*QpLSkfd1B0AOOsPd_x7VmA.png" /></figure><h3>Research</h3><p>Let’s apply some gamification techniques here</p><p>One thing that was very clear among the management of this project is that they wanted the whole thing to be a healthy joke and not create a disagreement among the vendors, but rather a friendly competition.</p><p>Working with this, they brought the symbolism of the Olympic medals into the project, so when opening the app the user would see his picture and how many medals he had won.</p><p>Each medal had its weight in points and as more packages he sold, or bigger packages, he received the medal according to his award.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*J2Rq84973fm9AXCqtWIAuA.png" /></figure><p>As we can see, the idea of this framework is to emphasize the user and not his competition with the other vendors.</p><p>To see the Ranking they need to click the button below.</p><h3><strong>Persona</strong></h3><p>Technologically challenged users, who are good at dialog and focused on sales, are basically the profile of the hundreds of salespeople that Serasa has throughout the country.</p><p>For this reason, everything in this application had to be thought out in a practical way so that they could use it without problems.</p><p>The design I developed was always thinking about this issue, big buttons, representative images and information on the screen with a few clicks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*QpLSkfd1B0AOOsPd_x7VmA.png" /></figure><h3><strong>More Easy Ideas</strong></h3><p>Serasa wanted the use of the application to be commonplace and for the salesperson to open it at least once a day to see how it is doing.</p><p>This is why we suggest developing seasonal promotions, which can happen on specific days of the week, or on commemorative dates.</p><p>So the Campaigns section was created, with wide banners and Push notifications, announcing for example, double points, or extra medals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*HOOKERdbYNccTVGdhydmuA.png" /></figure><h3>Full Initial Design</h3><p>So, let’s see how the full design was developed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ouqszlvq9OOnZNHYwR-Anw.png" /></figure><h3><strong>Final Conclusion</strong></h3><p>The business managers were very happy with the final result of the application, with all the most important information being shown clearly to the user.</p><p>The process was so successful that the application started to be implemented in other clients of the company (which managed Incentive Marketing).</p><p><strong>Thanks for Reading,</strong></p><p>My name is <strong>Diego Menezes</strong>, <strong>UX Designer</strong> since 2013.<br>If you want to contact me, feel free.</p><p><a href="https://www.facebook.com/profile.php?id=100029548294097"><strong>Facebook </strong></a><strong>· </strong><a href="/service/mailto:diego@therockdigital.com.br"><strong>Email </strong></a><strong>· </strong><a href="http://www.instagram.com/diegomenezesmkt"><strong>Instagram </strong></a><strong>· </strong><a href="https://www.linkedin.com/in/diego-menezes-6b76811b/"><strong>LinkedIn</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/427/1*pjt7bwS7tIJFtQffRNXc2g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=444f0bdc355c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cielo Developers — UX/UI Study]]></title>
            <link>https://diegomenezesux.medium.com/cielo-developers-ux-ui-study-2b7f0add67ed?source=rss-bb7c91c07189------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b7f0add67ed</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Diego Menezes]]></dc:creator>
            <pubDate>Thu, 24 Jun 2021 16:12:19 GMT</pubDate>
            <atom:updated>2021-06-24T16:16:31.288Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cielo Developers — UX/UI Study</h3><p>The challenge of turning code into visual icons</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ou9alBqsD3lBmg7dlUfrEw.jpeg" /></figure><h3><strong>The Challenge</strong></h3><p><strong>Cielo</strong>, the largest Brazilian company responsible for credit card transactions was launching a <strong>new machine </strong>and wanted developers to be interested in creating applications for it.</p><p>It was the first machine that <strong>would have a built-in smartphone</strong>, which could generate a <strong>lot of development possibilities</strong>, besides having a built-in printer and<strong> API integration</strong> with proprietary systems.</p><blockquote>The challenge was, how to <strong>transform </strong>a <strong>boring </strong>documentation <strong>into </strong>something <strong>interesting </strong>for developers?</blockquote><h3><strong>The Machine</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*k5FJYiuAAQoNvpR3H8mTfQ.png" /></figure><p>The Cielo Lio is like having a cashier in your hands, it generates the orders, reads the barcodes, processes the payments, integrates with the invoice system, prints the receipt.</p><p>The facility was there, all we needed was to arouse the interest of developers from all over the country to create applications and upload them to Cielo’s own Android store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YMtJ9BCwQiMtVI3K5S9UeQ.png" /></figure><h3><strong>Discovery</strong></h3><p>The discovery stage is the first of the four stages of the <strong>Double Diamond process</strong>, and before doing anything, understanding what is to be done is as important as doing it.</p><p>I had to come up with some hypotheses. They would help me understand what was going to be done, for whom, where, when, how, and whether I was on the right track — as Alice’s cat rightly said:</p><blockquote><strong>“For those who don’t know where they are going, any path will do.”</strong></blockquote><p>For this, I used the <strong>5W1H </strong>method (Why, Who, When, Where, What and How) used in the book <strong>“Solving Product Design Exercises”</strong> by <em>Artiom Dashinsky</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YMtJ9BCwQiMtVI3K5S9UeQ.png" /></figure><h3><strong>5W1H Method</strong></h3><p><strong>— Why</strong></p><p>People were tired of having to integrate systems manually and use standard payment machines.</p><p>So the whole purchase and payment process was very physical and they used huge machines that didn’t move around the site if necessary.</p><p>This had already been researched and the machine was ready, but it would take the efforts of software developers to come up with creative solutions and develop applications for the machine.</p><p><strong>We already knew that they would be the basis of all the success of the new machine.</strong> So having good documentation that would spark the interest of developers was essential.</p><p>Get away from the traditional boring documentation, which just posted code examples on a screen full of digits.</p><p><strong>— Who</strong></p><p>The documentation was aimed at android application developers, for them to use the API and SDK that Cielo provided.</p><p>They would then develop applications to upload to Cielo’s own store.</p><p>Their interest could be various, like creating an application to sell to Brazilian merchants, or who had software development consulting and IT solutions.</p><p><strong>— When &amp; Where</strong></p><p><strong>When: </strong>The developers (users) will use the Cielo LIO documentation only when they realize that there is an incredible possibility for development and that it was innovative.</p><p>Therefore, arousing this interest in them was paramount for WHEN to act strongly on the project.</p><p>We had to get away from the traditional, create real examples, visual cases and a cleaner documentation.</p><p><strong>Where: </strong>Programmers don’t bother and in fact barely use smartphones to read lines of code, so we already knew that the whole site would have to be desktop-focused.</p><p>On their computers, laptops, maybe at work or freelancers at home, but always thinking here of the corporate environment.</p><p><strong>— What</strong></p><p>Sites for developers to read documentation already existed, I knew I couldn’t reinvent the code, so I had to follow some standards that the community was already used to using.</p><p>So having a code dump that was visually interesting and that would spark creativity in the programmers was my main focus.</p><p>So, some ideas that I can already identify that would be good:</p><ul><li>An entry landingpage that was clean, visual, and already had links to lead the developer to understand what he could create with the Cielo LIO</li><li>Some videos examples, of already created apps</li><li>And, of course the documentation itself</li></ul><p><strong>— How</strong></p><p>The metrics I defined to know if the portal was pleasing the developers were:</p><ul><li>Session Time</li><li>User Navigation (Filmed via Hotjar)</li><li>Quantitative and Qualitative Surveys</li><li>Published Applications using the SDK and API</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YMtJ9BCwQiMtVI3K5S9UeQ.png" /></figure><h3><strong>Research</strong></h3><p>According to Hick’s Law:</p><blockquote><strong>The time it takes to make a decision increases with the number and complexity of choices.</strong></blockquote><p>Thinking about this reasoning it is clear that it would be very easy to complicate things due to the amount of information the company sent me.</p><p>There were thousands of lines of code, demonstrating applications of the SDK/API, dozens of commercial videos of the product, some examples of applications that had already been developed by partners, FAQs, and others.</p><p>In short, it would be completely polluted if I simply threw all this information into a standard code listing screen.</p><p>So I decided to list what was really most important to the Cielo LIO business manager:</p><ul><li>Generate interest among programmers in using LIO’s own SDK</li><li>Help with questions so that the applications could be published</li><li>Understand how users are experiencing development using the SDK</li></ul><p>With this in mind, I was able to create four icons that would be right at the entrance to the developer portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*Sl7g4wkRbGArntvJi6oFHQ.png" /><figcaption>Documentation — Code Samples &amp;SDKs — Support — Discover</figcaption></figure><h3><strong>Persona</strong></h3><p>This is a very important step, understanding the persona behind any project. But here it was quite simple, after all I am also a developer.</p><p>Although I work as UX today, I came from the frontend school, where I worked for years as a flat developer, as well as working together with development teams on all projects.</p><p>I already knew, that programmers want things that are practical, quick to find and need a push to spark their creativity.</p><blockquote>Maybe you are asking yourself, is that all your persona is? Aren’t you going to set up those complete tables, creating names, ages, profession for them? Not even how to list their interests?</blockquote><blockquote>Honestly, I think this is really cool, I have created advanced personas several times, I even have a class on YouTube teaching people how to create one, using an excel spreadsheet.</blockquote><blockquote>But it is not always necessary, I already have an understanding of how they think, in some moments it is simply better to move on, I consider myself a practical professional rather than a theoretical one, who likes to see things ready.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YMtJ9BCwQiMtVI3K5S9UeQ.png" /></figure><h3>Storytelling</h3><p>What is better than a good story to understand something? So here I decided to create a short and quick story so that we would all be on the same level of understanding.</p><blockquote><strong>Once upon a time</strong> there was a developer Carlos, he was 35 years old and working as a senior backend for a commercial automation company.</blockquote><blockquote><strong>Every day</strong> he was developing solutions for desktop computers, creating new features or fixing bugs for customers. He believed that the world had evolved, everyone was on cell phones and the company he worked for still only developed desktop software.</blockquote><blockquote><strong>One day, </strong>after fixing several bugs and seeing those applications that he developed more and more with icons and more menus, needing several peripherals to work, such as printer, invoice issuer, cashier for payments, software to generate orders, he began to understand that everything would be easier if there was a hardware solution to help him.</blockquote><blockquote><strong>Because of this, </strong>he decided to search on his favorite search engine for mobile development solutions for cash receipting systems. Then he came across a video presenting the new Cielo LIO.</blockquote><blockquote><strong>Because of this,</strong> he accessed the documentation wanting to understand what technologies he would need to master to develop and what could actually be done, what were the possibilities?</blockquote><blockquote><strong>Finally, </strong>he saw an icon on the Lio landing page showing examples of applications developed for the Cielo LIO and decided to tell his boss that this could be a great solution for them to develop and launch an upgrade for current customers and prospect new ones.</blockquote><blockquote><strong>Finally,</strong> with the help of support and all the complete Cielo LIO documentation, they were able to launch the first application that managed parking, they took a picture of the license plate, which already registered the vehicle and issued an entry paper, with date and time. Upon returning, the customer paid directly to Cielo LIO, which issued a receipt and sent the invoice to the customer’s email.</blockquote><blockquote>All done by the attendant himself, standing up, without the need to connect any other peripheral, in a machine that weighed a few grams.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YMtJ9BCwQiMtVI3K5S9UeQ.png" /></figure><h3><strong>Wireframes</strong></h3><p>It is incredibly cheaper and faster to fix a wireframe than to change the entire course of a system already in development.</p><p>After the structure was scribbled on paper, I already knew more or less how I was going to position the icons and calls for documentation on the page.</p><p>It was time to create a low-fidelity wireframe to present to the business managers and validate the idea.</p><p>Besides, of course, hearing more opinions of what could be included in the wireframe, a good UX knows how to listen and not have his ego speaking louder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*couvSDzKARoN_S2QJCX7vw.png" /><figcaption>I just love Balsamiq style</figcaption></figure><h3><strong>Portal Online</strong></h3><p>The portal was developed in Drupal, using Cielo’s standard colors as well as typology, so there was no need to invent anything.</p><p>We created icons for the initial blocks and put the portal online to receive the developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*nnf4Ty7Fd3pWE8nS3AjEvA.jpeg" /></figure><p>It was equipped with Hotjar, which “filmed” all the usability of the site, so I could analyze the results.</p><p>As well as search blocks that appeared on the screen to gather information from the developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-d3tcPNfVjD5GmhBaTFyAA.png" /></figure><h3><strong>Next Steps</strong></h3><p>To develop with Cielo LIO it was necessary to make a registration, where we requested contact information.</p><p>We fired occasional e-mails to show new applications that were developed, thus stirring up the community.</p><p>Many calls were also made to Quality Survey, thus understanding the real difficulty they had when using the documentation or getting ideas, to ask questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YMtJ9BCwQiMtVI3K5S9UeQ.png" /></figure><h3><strong>Conclusion</strong></h3><p>Cielo Lio turned out to be a great success, and I was extremely happy to have participated in this project.</p><p>Today when I go to stores and see the machine in use, I feel proud to have collaborated with this great idea of Cielo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*iCWztY_olpLUQwgxcrKwAg.jpeg" /></figure><p><strong>Thanks for Reading,</strong></p><p>My name is <strong>Diego Menezes</strong>, <strong>UX Designer</strong> since 2013.<br>If you want to contact me, feel free.</p><p><a href="https://www.facebook.com/profile.php?id=100029548294097"><strong>Facebook </strong></a><strong>· </strong><a href="/service/mailto:diego@therockdigital.com.br"><strong>Email </strong></a><strong>· </strong><a href="http://www.instagram.com/diegomenezesmkt"><strong>Instagram </strong></a><strong>· </strong><a href="https://www.linkedin.com/in/diego-menezes-6b76811b/"><strong>LinkedIn</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6pXQoiIV1lFWVrkzcH4rQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b7f0add67ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>