Team building | Rappi Team leading

Team leading

Team building | Rappi

INTRODUCTION

Problem

When I joined the B2B design team at Rappi, I noticed a lack of connection and collaboration within the team. Designers rarely had meetings, barely knew one another, and had limited understanding of their peers’ skills. This isolation made it challenging to foster collaboration, share expertise, and support each other in day-to-day tasks. The fast-paced startup environment exacerbated the issue, leaving little room for building relationships or exchanging knowledge.

Objective

To address this disconnection and foster a stronger sense of community within the B2B design team, I proposed and implemented a Rappi Hour—a series of online team-building sessions designed to:

Build personal and professional connections among team members.
Facilitate skill-sharing to improve collaboration on tasks.
Bridge cultural gaps, especially after the acquisition of Box Delivery, integrating the Brazilian and global design teams.

Key Results (OKRs)

1.Team Engagement: Increase participation in team activities by 50% within the first three months.

2.Skill Awareness: Ensure 80% of team members can identify at least one peer to approach for help with specific design challenges.

3.Cultural Integration: Successfully integrate the Box Delivery and Rappi design teams by organizing at least one collaborative event with simultaneous translation support.

THE STORY

The Challenge

Rappi’s design team, spread across multiple countries, operated in silos. The Brazilian culture’s emphasis on connection and camaraderie was missing in the global team. This lack of interaction hindered collaboration, left team members feeling isolated, and made it difficult to leverage the collective expertise of the group.

The Initiative

To strengthen team connections, I initiated Rappi Hour, a remote, cost-free program featuring creative activities, storytelling, and knowledge-sharing. Purposeful icebreakers encouraged sharing personal and professional insights, fostering collaboration in a distributed team.

CREATING CONNECTIONS

During one pivotal Rappi Hour, I focused on integrating the Brazilian Box Delivery design team with the global Rappi team. The acquisition had led to collaboration between these groups, but many team members had never met. To bridge the language barrier, I partnered with our UX Writer, who provided simultaneous translations to facilitate seamless communication. Activities included:

Introducing team members through storytelling and skill-sharing.
Collaborative problem-solving exercises to spark creative thinking.
Open discussions about cultural practices and design workflows.

One memorable Rappi Hour was the Halloween event, featuring a costume contest with prizes for the top three winners. Supported by HR, participants received low-cost Rappi credits to order food within a set budget. Voting categories included best, worst, and funniest costumes, adding fun and engagement while strengthening team bonds.

RESULTS

1.Enhanced Collaboration: Designers began reaching out to one another for feedback and assistance on projects, fostering a more collaborative environment.

2.Improved Team Morale: Surveys showed a 60% increase in team satisfaction related to interpersonal connections.

3.Cultural Integration: The integration of the Box Delivery and Rappi teams was a success, with participants expressing increased trust and familiarity.

4.Skill Awareness: By the end of the first quarter, 85% of team members reported knowing who to approach for specific design challenges.

Reflection

The Rappi Hour demonstrated that even small, cost-effective initiatives can have a significant impact on team dynamics and productivity. By addressing the root causes of isolation and fostering connection, the initiative strengthened the design team and laid the groundwork for continued success in a fast-paced environment.

View Project

Protected: Usability Improve | Rappi Desktop

Desktop

Protected: Usability Improve | Rappi

INTRODUCTION

Problem

Upon joining SOB, it was evident that several ongoing redesign initiatives were underway. However, the emphasis shifted towards addressing critical issues with minimal design and technology interventions. The primary focus honed in on enhancing order visibility, streamlining preparation and delivery, optimizing reception and processing, and overall structural enhancements within the order management system.

Objective

The core objective of this project is to bolster operational efficiency at SOB by tackling critical issues within order management. Specifically, the aim is to amplify order visibility, streamline preparation and delivery processes, optimize reception and processing procedures, and fortify the overall structural integrity of orders.

Key Results (OKRs)

Increase End-to-End (E2E) conversion rate to 12.5%, reflecting improved efficiency in order management and fulfillment.
Enhance menu conversion from 76% to 85%, signifying enhanced user engagement and conversion rates.

DISCOVERY

Map problems”>

I conducted thorough product testing, meticulously mapping each screen to identify issues. Problems were categorized into three tiers based on severity: low, medium, and high impact. This classification helped prioritize addressing issues affecting user experience.

Impact vs Effort

So I conducted a workshop with the Product and Tech teams, during which we began creating an Impact vs Effort Matrix to prioritize the primary issues and outline our roadmap.

Initially, our focus was on tackling high-impact problems, given the sheer quantity of issues we identified: 144.

144

“>”>Issues to
improve

“>”>LOW IMPACT 30%
“>”>MEDIUM IMPACT 34%
HIGH IMPACT 37%

WHERE

In High
Impact

55 ISSUES

33 TECHNICAL ISSUES

60% FROM HIGH IMPACT

22 DESIGN ISSUES

40% FROM HIGH IMPACT

DEFINITION

Building upon the insights uncovered during the discovery phase, I have strategically segmented the solutions into distinct packages. This approach allows for the incremental delivery of value, honing in on pivotal stages where conversion rates are most adversely impacted. By concentrating our efforts on these critical junctures, we maximize our capacity to deliver tangible benefits efficiently and effectively.

“>SO I DIVIDED HIGH IMPACT INTO A”>

3 Packs of Solution”>

“>”>Pack 1

DELIVERED”>

Types of Menu – Improves
Manual Menu – Category / Product / Toppings / Products Counter / Commission calculator

“>”>Pack 2

DEVELOPING

Sign Up + Email – Preview of Necessary Items by Country
Email – Partner registered
Summary – Change Structure

“>”>Pack 3

TO DEVELOP”>

Documents – Instructions for mobile + Instructions for Digital Docs + Skeleton loading + PDF upload
Menu (link) – Improve Instructions

IDEATION

During this phase, I initiated the creation of navigation flows while concurrently organizing a Design Critiques Workshop involving all Product Designers. This collaborative session served as a platform to present proposals and gather extensive feedback.

“>Pack 1”>

Design Critiques”>

I did a study to see what was the best flow, because the old one was so confusing, too long and didn’t have a continuous structure.

So I took this theme to a Design Critiques and all design team helped us to choose the best and more efficiently flow.

HANDOFF AND LIBRARY

Project Handoff

I’ve honed a handoff process to support the DEV Team efficiently. By aligning with the tech team and creating detailed Figma designs with explanatory notes, we streamline communication and eliminate the need for excessive clarification calls. This approach enhances the effectiveness of the dev team.

Local Library

To enhance efficiency for a team with a basic, fragmented design system, I developed a local library. After converting it into a team component and publishing it for reuse across projects within the vertical, organizing, reusing, and creating new components became much easier.

FINAL SOLUTION

The concept behind the final solution was not to undergo a complete overhaul, as such a large-scale revamp could consume several months due to the intricacies of technological and design processes. Therefore, our approach was to prioritize resolving technical bugs that did not require design intervention. We aimed to rectify functionalities that were intended to work but were malfunctioning.

On the design front, our focus was on enhancing usability by implementing basic improvements such as making buttons more accessible, ensuring a seamless flow throughout the platform, maintaining clean and uncluttered page layouts, and streamlining complexity by aligning with prevailing market standards.

Given that 50% of our users access the platform via mobile devices, we placed particular emphasis on optimizing the mobile experience. Additionally, we aimed to guide users more effectively by incorporating progress indicators and clear instructions to enhance the overall user journey.

DESKTOP VERSION | PACK 1

“>”>OLD FLOW

“>”>NEW FLOW

MOBILE VERSION | PACK 1

Hierarchy Improvements

Revamping the menu selection page UI, I reorganized its hierarchy to enhance usability, addressing clutter and inefficiency. I introduced a help bar with PDF contents and an online call option for partner assistance, along with a step-by-step video guide for menu registration, streamlining user support.

Guided Menu Creation

To assist users, I created guides to ensure menu approval by specifying the minimum required products and suggesting optimal quantities for better sales. Additionally, I implemented a guided process for creating categories and products, including an empty state indicator to prompt users to begin setting up their menu.

Category Creation

The old menu’s category creation was cluttered and confusing, featuring disconnected elements and non-standard practices like input fields within dropdown menus.

I standardized the process by redesigning both category and product creation interfaces to share a full-screen UI pattern. Now, selecting a custom category prompts a text input field below the dropdown, ensuring a streamlined user experience.

Product Creation

The previous product creation process was convoluted, with issues such as single-step pricing and malfunctioning inputs. Placeholder text and disappearing buttons during scrolling added to the confusion. In the updated version, we streamlined the process, reducing steps, adding clarity with tips and icons, and introducing a requested feature to calculate Rappi’s commission and the restaurant’s earnings.

Complements and Final Catalog

Previously, users navigated through multiple pages with no clear progression, needing to backtrack step by step. To streamline the process, I consolidated it onto one page, dynamically revealing elements and providing a visible stepper and final button for clarity.

In the final catalog version, unnecessary information was removed, resulting in a simpler, more focused catalog design with an added final button for easy submission.

“>Pack 1”>

“>Solution Live View

This version I did a new flow, inserting a product counter, live support above the menu, a lot of instructions on the category, product and toppings creation and offer to users consistent steps with visibility where they will always have vision about which step of the flow they are at and how to proceed to the next step.

USABILITY TEST

To ensure the effectiveness of our enhancements, we conducted a comprehensive usability test involving Brazilian and Spanish-speaking restaurants. We engaged with 5 users from Brazil, Colombia, and Mexico to gauge the performance of our redesigned manual menu experience in each respective country.

Through this testing phase, we identified several areas for improvement, such as refining the grouping of complements and rebranding “toppings” to “complements,” among other critical points.

RESULTS

By focusing solely on delivering Pack 1, we exceeded our menu conversion targets and approached our end-to-end conversion goal, with only 2 additional Packs remaining.

While the project has been completed and achieved all metrics, it underwent division and transformation into other initiatives as per the evolving needs of the company during development.

Nevertheless, it serves as a valuable reference, showcasing my process from inception to conclusion and the positive outcomes derived from crafting optimal solutions for the given scenario.

View Project

Protected: Multiple Orders | Rappi Desktop, Mobile APP, Tablet APP

Desktop, Mobile APP, Tablet APP

Protected: Multiple Orders | Rappi

INTRODUCTION

Problem

The Batch and Bundle (B&B) business model on Rappi is highly profitable and continuously expanding. However, it’s also a significant contributor to undesirable outcomes such as high Defect Rate, frequent occurrences of Bad times, and cancellations.

Objective

To address the issues stemming from the Batch and Bundle business model, the objective is to identify and mitigate the factors leading to high Defect Rate, particularly focusing on stages where the conversion rates experience the most significant decline, notably Menu and Documents.

Key Results (OKRs)

Defect Rate Reduction: Achieve a reduction in the percentage of Bad Orders within bundling, resulting in $20,000 monthly savings. Target a decrease of 4 basis points (bps) in Defect Rate.

DISCOVERY

Briefing and
Project Alignment

Before embarking on any project, I meticulously engage in mapping and comprehending its fundamental aspects. This involves aligning myself with the stakeholders involved, noting the date of project initiation, and firmly establishing its deadline. Additionally, I ensure a thorough understanding of ancillary elements such as PRDs, Epics, and Metrics, which are managed via Jira.

Within the scope of design, I focus on providing comprehensive documentation for stakeholders who utilize Figma, offering contextual insights into the solution, including the circumstances of its creation, associated deadlines, and key contributors. This documentation proves invaluable for seamless project continuity, particularly in scenarios where I may be unavailable due to vacation or departure from the company.

Included in this documentation are various project assets such as design studies encompassing flows, ideations, sketches, and blueprints, alongside research documents and any foundational materials utilized. This compilation extends to written files and presentations, whether originating from my own efforts or those generated by the product team, which often produce a plethora of presentation materials.

Subsequently, I delve into the core components of the project, meticulously mapping out its problem statement, contextual framework, and overarching design objectives. This practice ensures a clear and unwavering trajectory, allowing for informed decision-making throughout the project lifecycle. Should any aspect of the project’s direction appear ambiguous, I proactively engage in clarifying discussions or propose research initiatives to facilitate a deeper understanding, particularly if the Product team’s vision is not definitively established.

Collect Information

How this was a small project and Product team had already a lot of vision about it, I just collected the maximum information they have and what they know about problems, needs, actual scenarios and some benchmarks they already have.

IDEATION & DEFINITION

Business and
Tech Validation

I initially validated the idea by sketching low-fidelity designs on FigJam, seeking feedback from the product team. Presenting three flow options to stakeholders proved efficient, saving time and facilitating easy validation and iteration, allowing for quick adjustments and eliminations as needed.

Design Critique

I facilitated a design critique session with the team to validate the flow I created, ensuring it met business requirements and addressed usability issues. Feedback was collected and iteratively incorporated, fostering collaboration and refining the design for optimal functionality and user experience.

DISCOVERY

FINAL SOLUTION

“>Desktop”>

UI Improve

Implemented UI enhancements like aligning spaces to 8px multiples, ensuring correct component sizes, and integrating Design system colors. Refined card heights, optimized the waiting time clock, and applied missing UI guidelines as per our project standards.

“>Desktop

Order details”>

For this MVP’s order details, we introduced a tag above the order ID to indicate multiplicity due to the considerable effort involved in implementing two orders on the same page. Additionally, we conducted a UI revamp on this page, adhering to the Design system guide for buttons, tags, cooking time, and other elements.

“>Desktop APP”>

Orders Separated

In this MVP, due to the complexity involved, we must relocate double orders from the “Accept” and “Preparing” columns to separated cards. Only in the final column will they be grouped together. Note: Within this flow, enhancements include an improved empty state display when there are no more orders.

“>Desktop APP”>

Waiting Order”>

When one order is completed while the other remains pending, a message is displayed above, prohibiting users from delivering the orders separately. Instead, they must be delivered together. A notification informs the user, stating “Waiting for order number xxxx” to ensure both orders are delivered simultaneously.

“>Desktop APP”>

Orders Merged

In this final step of the MVP, users can view both orders separately, as it encourages restaurants to send both together. However, they are displayed together on the same card, emphasizing the need for simultaneous sending. Additionally, a confirmation prompt ensures both orders were sent together before completing the order.

Tablet APP”>

Moving to APP”>

In the tablet version, I focused on touch accessibility by enlarging actions and improving text readability. With limited resources, I streamlined design across Desktop, Tablet, and Mobile apps for consistency. Prioritizing landscape orientation minimized effort and enhanced usability. Removing unnecessary elements like delivery status icons and optimizing space improved user experience.

Tablet APP”>

Layout Adaptation

In the tablet version, we simplified by removing delivery status icons, opting instead for a clear display of remaining time in minutes. We optimized space for accessibility by streamlining each order, reducing unnecessary restaurant information to minimize card height. This allowed users to access essential information within orders without overwhelming the interface.

Mobile APP”>

Responsiveness

In the mobile version, adapting to vertical user habits, we introduced tabbed navigation and column-based card viewing to optimize space. Each column features a clear indication of new orders at the top for easy access. However, it’s primarily used for store administration, with tablet and desktop handling operational tasks.

Mobile APP”>

Order card & Details

In the mobile version, given its lower usage, we prioritized efficiency by focusing solely on essential features, with additional enhancements deferred to subsequent updates. However, we ensured optimal spacing and responsiveness to minimize scrolling and adhere to mobile best practices, despite not overhauling the entire layout.

HANDOFF & LIBRARY

“>”>Team
Components

I created a centralized team component library to streamline design efforts and promote consistency. With a new designer on board, it prevented redundant component creation and ensured adherence to existing standards. The library facilitated easy access to reusable components and offered a structured interface for modifying and activating elements, enhancing efficiency in our design workflow.

Structure of Components”>

To simplify creation and presentations, every component, from cards to buttons and columns, offers customizable variations via the right panel. This feature allows for seamless transitions between variations, states, tags, and components, thereby enhancing the efficiency of prototyping and design iteration.

“>Handoff Flows

I generate flowcharts for desktop, tablet, and mobile, detailing both portrait and landscape orientations for tablets initially. These are amalgamated into a cohesive flow with clear directional arrows, facilitating developer comprehension. Component indications and issue annotations are provided below to ensure clarity and guidance.

Details of
Components

As mentioned earlier, I consistently allocate space for components, adjusting based on project needs. Depending on project complexity, I determine whether additional explanations are required via post-its or text within Figma. If developer discussions are thorough and component variations are straightforward, detailed explanations may not be necessary.

RESULTS

We successfully met our goal of reducing the percentage of Bad Orders within bundling, resulting in monthly savings of $20,000. Our target was to decrease the Defect Rate by 4 basis points (bps), a goal we achieved precisely – reaching 100% of our target within one quarter, releasing updates country by country and device by device.

View Project

Protected: Research – Early Success | Rappi Research

Research

Protected: Research – Early Success | Rappi

INTRODUCTION

The performance and growth of the business heavily rely on the successful transition of new partners into Priority Partners (P.P.) status. This status is achieved when partners sell more than 5 products within their initial 30 days. However, many partners struggle to reach this milestone, which suggests the presence of significant barriers in the process. Understanding these barriers is crucial for improving partner performance, enhancing their experience, and ultimately driving overall business growth.

CONTEXT

Problem

The current challenge lies in the difficulty many partners face in becoming Priority Partners (P.P.) within the crucial initial 30-day period. The inability to reach the required sales volume indicates that there are substantial obstacles hindering their progress. A comprehensive investigation into these obstacles is essential to support partner development and increase conversion rates.

Objective

The research aims to thoroughly examine and address the factors that impede partners from converting into Priority Partners during their initial 30 days. By identifying the root causes, the research seeks to establish targeted strategies that will improve the conversion rate and enhance partner engagement and satisfaction.

Key Results (OKRs)

The primary goal of the research is to increase the Priority Partners conversion rate by 5% within the next quarter. This improvement is expected to lead to greater partner success and overall business expansion.

METHODOLOGY

Preparation”>

Duration: 30 minute session to gather in-depth responses without overburdening participants.

Question Set: Tailoring questions for partners and priority partners allows for more nuanced and relevant insights based on each group’s experiences.

Recruitment: The use of WhatsApp facilitates higher response rates and engagement.

Interviews

Partners: The methodology includes interviewing both priority and normal partners to understand their respective experiences and challenges.

Geographical Distribution: Including participants from Colombia, Mexico, and Brazil gives your research a regional perspective, adding depth to your analysis of different markets.

FINDING AND INSIGHTS

Problem Quantity

When comparing partners and priority partners across countries, I found that priority partners consistently faced fewer issues. I continued my investigation to understand why priority partners experienced fewer difficulties and performed better overall.

Positive Feedbacks

In another perspective, when considering positive feedback, priority partners had a highly favorable impression of the process, while regular partners found little to appreciate in their experience. This created a significant gap between the two groups. It became clear that the experiences of the two groups were markedly different.

Main Problems

Before comparing regular and priority partners, I found that the main issues stemmed from users lacking proper instructions or guidance throughout the process. Additionally, they faced a lack of support, which, combined with technical difficulties and complex user experiences, led to significant problems in communication.

Problems per Objective

When I shifted focus to our objectives, I discovered that availability and menu quality were the most problematic aspects of our process, with 7 out of 10 users encountering difficulties in these areas.

Priority Partners Advantages

Upon exploring why priority partners have more advantages, I found that their size and profitability enabled them to receive personalized support during registration, making the process easier. Many were part of Rappi’s Class program, gaining guidance and knowledge about the online market. These larger restaurants’ familiarity with online platforms contrasted with regular partners, who often struggled due to lack of experience.

CONCLUSION

Why Partners are not converting toPriority Partners on their first 30 days?

Individual interviews revealed that users face challenges due to inadequate guidance and unclear instructions on how to effectively navigate and utilize the platforms. Users also struggle with a limited understanding of platform functionalities and find the overall experience to be unnecessarily complex.

To improve the user experience, platforms should provide enhanced guidance through comprehensive onboarding resources, including video tutorials, interactive walkthroughs, and clear, structured documentation. Additionally, platforms should offer intuitive, user-friendly interfaces with accessible information and straightforward solutions for common issues.

By implementing these changes, platforms can help users better understand and engage with available features, ultimately increasing conversions to priority partners.

NEXT STEPS

Based on our research conclusions, the next steps for designing a solution should focus on enhancing the user experience through improved guidance and support. This includes providing clear, step-by-step instructions, guided processes, and engaging video tutorials. Additionally, offering clear error resolutions and incorporating visual elements such as diagrams and icons will improve understanding. These strategies can streamline the user experience and facilitate the transition from regular to priority partners.

Instructions
need to be more
clear and detailed

Insert
instructions
in all steps

Create
a guided
process

Change
text explanation
by videos

Show
error solution
for users

Use visual
elements to
explain better

View Project

Airline Tickets APP | CVC Mobile APP

Mobile APP

Airline Tickets APP | CVC

INTRODUCTION

Problem

Users have often reported encountering slow app performance and various glitches when trying to view search results for airline tickets using the Web-view interface. This has caused significant delays in loading content and a frustrating user experience. As a result, users may abandon the app or seek alternatives, impacting user engagement and satisfaction.

Objective

Develop and deliver a refined native app experience that caters to the needs of users while also capitalizing on untapped opportunities within the aviation product domain. By moving away from Web-view, the app can provide a more seamless and intuitive interface, with faster response times and fewer technical issues.

Key Results (OKRs)

Focus on retaining more users and reducing technical challenges within the app. Strive to offer a distinctive and enhanced app experience that includes smooth and efficient search result viewing, thereby increasing user satisfaction and loyalty. Through these improvements, the app aims to set itself apart in the competitive aviation market and strengthen its position as a top choice for users seeking airline ticket services.

DISCOVERY

“>User Pains and Opportunities”>

Through meticulous user research, we mapped all user pains based on existing research, aligning with the Product and Research teams to identify business opportunities. Iteratively prototyping solutions, we addressed each pain point, enhancing the user experience. Rigorous user testing ensured our final product effectively addressed pain points while capitalizing on business opportunities.

“>Benchmark

Through meticulous user research, we mapped all user pains, aligning with Product and Research teams to identify business opportunities. A competitor comparison focused on top travel apps was conducted, using their main features as a base for comparison. Iteratively prototyping solutions, we addressed each pain point, enhancing the user experience. Rigorous user testing ensured our final product effectively addressed pain points and capitalized on business opportunities.

DEFINITION

“>Success Metrics

In this product design project, the main objective is to enhance app user engagement for the flights vertical in alignment with stakeholders’ goal for this year. Two lagging objectives are to decrease reclamations and enhance app usage for the flights vertical. Lead objectives include developing a native flight experience, identifying user pain points, benchmarking with top travel apps, and crafting a unique flight experience.

“>Proposal Workshop

I organized a workshop with the tech and product teams to align on the first version MVP, exploring possibilities, suggestions, and implementation efforts. I presented a low-fidelity design solution to validate. We discussed technical feasibility, mapped MVP requirements, and identified key challenges to define a clear action plan, resulting in a refined MVP version.

DESIGN

“>Flow Improve”>

I significantly enhanced the navigation flow by streamlining the process, eliminating redundancies, and enhancing overall efficiency, based on user feedback and behavior data. By analyzing user feedback and behavior data, we identified key areas for improvement, resulting in a seamless and delightful experience. These optimizations have substantially boosted satisfaction and retention rates, ensuring a more user-friendly and efficient platform.

“>Medium Fidelity”>

To enhance focus and efficiency, I divided the project into phases. Initially, I presented a medium-fidelity version, focusing on the happy path, for validation by the development and product teams. This approach enables early feedback, streamlining the development process, ensuring alignment, and facilitating informed decision-making.

“>Usability Test

I conducted a usability test with medium-fidelity designs on a maze to assess the potential for significant changes in the product. By comparing the old and new projects with two user groups, the new version showed noticeably better results, validating the improvements for an enhanced user experience. This confirms the efficacy of the changes in enhancing the user experience.

FINAL SOLUTION

Our main goal was to transition from a webview version to a new native version from scratch. We established a new team components library, integrating the company’s updated design system. The outcome is a unique solution, distinct from the web responsive approach, achieving a seamless user experience.

Search Process

The search process in the web view was previously extensive, requiring users to navigate back and forth. To address this, I implemented a detailed and sequential process. Users can now easily select their departure and arrival locations, choose dates from a user-friendly calendar, and specify flight details such as baggage, layovers, and other filters.

“>Animations and Compact Solutions

One challenge was to create a minimalist product with concise solutions, as on web versions, one scroll only displayed one travel ticket option, disrupting the user’s flow. Simultaneously, I needed to reduce the results time, approximately 40 seconds, so I implemented an animation to cover this waiting time for flight results.

“>Flight details,
Filters and Tags

I enhanced a highly effective filter, addressing most user needs and resolving filter issues. We focused on key user priorities: Flight hours, prices, stops, duration, airline, and baggage. Upon clicking, users can access detailed information such as arrival times, itinerary, inclusions, and more, ensuring a seamless experience.

RESULTS

The implementation of design solutions resulted in a steady month-by-month increase in sales. Improved user satisfaction and loyalty were confirmed through Mixpanel metrics, showing a 20% increase in user retention and a 15% increase in overall sales. The streamlined search process led to a 30% reduction in technical issues reported by users, positioning the app as a top choice in the competitive aviation market.

View Project

Users Feedback | CVC Mobile APP

Mobile APP

Users Feedback | CVC

INTRODUCTION

Problem

The APP team at CVC encountered significant hurdles in recruiting users willing to participate in research, making it nearly impossible to gather vital feedback about the APP. This limitation impeded the team’s ability to understand user experiences and preferences effectively. Historically, feedback was primarily sourced from Store comments, but this method often proved inefficient and unreliable for obtaining meaningful insights.

Objective

To address this issue, a parallel initiative was conceived to facilitate the collection of user feedback. The proposed solution was the implementation of a feedback form that users would encounter upon exiting or completing an experience within the APP. This form would serve as a direct channel for gathering user opinions and suggestions, thereby enabling the team to make data-driven improvements.

Key Results (OKRs)

Achieve a feedback collection rate of 5% or higher, starting from a baseline of 0%, through the introduction of the new feedback form.

DISCOVERY

Most Commented Words on APP Stores

The design solution offers an optional qualitative option, allowing users to provide comments, which are collected and sent to a Mixpanel dashboard for in-depth analysis and insights. This additional qualitative option enhances our understanding of user experiences and preferences, empowering us to refine and optimize our products more effectively.

“>Benchmark

In a brief period, we transitioned from approximately 50 unproductive comments in the Apple and Android Stores to receiving 3,000 productive feedback responses per month (on Mixpanel). This substantial increase in valuable feedback has played a pivotal role in driving improvements and enhancing our products, enabling us to better address user needs and refine our offerings effectively.

“>Feedbacks
/ review score

The design solution incorporates an optional qualitative feature, enabling users to provide comments. These comments are systematically collected and forwarded to a Mixpanel dashboard, facilitating in-depth analysis and providing valuable insights into user experiences and preferences, enhancing our ability to refine and optimize our products effectively.

“>Triggers to Open
Feedback Forms

The design solution includes a quantitative option, capturing both scores and tagged feedback from users. This data is systematically transferred to a Mixpanel dashboard, enabling comprehensive analysis and insights. This approach enhances our ability to understand user preferences and needs, facilitating effective product refinement and optimization.

FINAL SOLUTION

“>Structure”>

This design flow emphasizes both negative feedback (scores 1 to 4) and positive feedback (score 5). Tags accompanying reviews will prompt users to specify what they liked for positive reviews and highlight the main problems mentioned in Apple and Google Store comments for negative reviews. This approach ensures the collection of specific insights to effectively address user experience issues.

Dual Feedback Analysis Solution

The design solution offers both quantitative and qualitative options. In addition to capturing scores and marked tags from users, the system collects comments, which are then transferred to a Mixpanel dashboard for comprehensive analysis and insights. This dual approach ensures that we not only gather numerical data but also gain valuable insights from user comments, enabling us to refine and optimize our products effectively.

Enhanced User Feedback Analysis

The design solution also incorporates an optional qualitative feature, enabling users to provide comments. These comments are systematically collected and forwarded to a Mixpanel dashboard, facilitating further analysis and providing deeper insights into user experiences and preferences. This additional qualitative option enhances our ability to understand user needs and preferences, enabling us to refine and optimize our products more effectively.

“>Results Dashboard”>

In a short period, we’ve made significant progress, transitioning from around 50 unproductive comments in the Apple and Android Stores to receiving 3,000 pieces of productive feedback per month (on mixpanel). This substantial increase in valuable feedback has been instrumental in driving improvements and enhancing our products.

RESULTS

With this solution, we achieve a significant milestone by collecting over 3,000 feedbacks per month, providing the vertical with abundant productive information to guide decision-making and roadmap definition effectively.

View Project

Protected: Text Field: Design System | Rappi Desktop

Desktop

Protected: Text Field: Design System | Rappi

INTRODUCTION

Problem

Our B2B Design team faced a significant challenge: our existing Design System was rudimentary, lacking crucial components and consistency. This deficiency not only hindered our design processes but also fragmented our brand identity, with each team operating as a distinct entity within the organization.

Objective

Given the absence of a dedicated Design System team, we devised a strategy to address this issue collectively. With one product designer guiding the team and individual designers tasked with component creation, we set out to enhance our Design System incrementally. Our focus for this quarter was on developing the text field component.

Key Results (OKRs)

Develop a text field component that meets usability standards and aligns with the brand’s visual identity.
Reduce design iteration time by 20% by incorporating the text field component into our projects.
Facilitate cross-team collaboration by seamlessly integrating the text field component across various product interfaces.
Establish a scalable framework for future component creation to ensure continuous improvement within our Design System ecosystem.

DISCOVERY

To lay the groundwork for our component creation, I drew inspiration from Google Components and Material Design while remaining open to insights from other systems. My approach involved mapping out competitor components and auditing our internal design landscape. This allowed for the development of a unified component solution that catered to all teams’ needs, ensuring consistency in UI and functionality while accommodating various component variations.

Componentes
on Competitors

I sought inspiration from industry leaders such as Google, Airbnb, Uber Eats, and Apple’s web and iOS interfaces. While Google’s latest library was readily available for reference, I gathered screenshots of the text field components from the other platforms to study their various states and designs.

Components
in Rappi Teams

At Rappi, I requested each team to separate their text field components and provide them to me. This allowed for a thorough comparison across teams, enabling a deeper understanding of each team’s visual identity, unique requirements, and approaches to addressing specific needs within their respective domains.

Structure Based
on Material Design

Combining inputs from Rappi’s teams and industry standards like Google’s Material Design, I synthesized a unique text field structure. By merging internal insights with market standards, I crafted a comprehensive system.

DEFINITION

To ensure optimal structure for our designers and accommodate various needs, we based our design on thorough discovery. I established a core component anatomy, then tailored additional variations to suit our design teams’ requirements, incorporating support messages, states, icons, large text sizes, codes, and chips.

“>”>Component Anatomy

The component anatomy closely mirrored Material Design principles but included an outline feature, enhancing its ability to showcase various states clearly. This design choice facilitated thorough explanations for both our team and stakeholders, ensuring a comprehensive understanding of the component’s structure and functionality.

States and Variations

Derived from team preferences, the component’s states and variations were optimized for desktop and mobile responsiveness, excluding mobile apps. Defined color schemes for error, focus, disabled, default, and filling states, with an accent color enhancing cursor experience. Standardized icon placements allowed for options on both sides, one side, or none. Various component types were established, addressing needs such as long text, code validations, and chips.

SOLUTION

“>”>Component Usage

For a seamless designer experience, I consolidated all variations, states, and elements into a single main component, simplifying usage by offering everything needed in one place, thus streamlining workflow efficiency.

All Variations

I meticulously crafted a comprehensive range of variations encompassing various states: default, hover, focus, focus with placeholder, filling, filled, disabled, disabled filled, and error. These variations were applied across all types, including icon placements (left, right, or both), text areas, code validations, and chips, ensuring thorough coverage and versatility.

Introduction
for the Component

To provide a comprehensive understanding of the component’s functionality, I developed thorough documentation covering its introduction, anatomy, specifications, and diverse usage examples across various pages and products, serving as a valuable guide for users.

Usage Rules

To ensure seamless usage and maintain consistent design standards while addressing potential issues, I established clear guidelines detailing how each component should be utilized, including maximum width specifications and other critical details to preserve consistency and avoid discrepancies.

View Project

Projects

Team building | Rappi

INTRODUCTION

Problem

Objective

Key Results (OKRs)

THE STORY

The Challenge

The Initiative

CREATING CONNECTIONS​

RESULTS

Reflection

Protected: Usability Improve | Rappi

INTRODUCTION

Problem

Objective

Key Results (OKRs)

DISCOVERY

Map problems”>

Impact vs Effort

144

“>”>Issues to improve

WHERE

In High Impact

55 ISSUES

33 TECHNICAL ISSUES

60% FROM HIGH IMPACT

22 DESIGN ISSUES

40% FROM HIGH IMPACT

DEFINITION

“>SO I DIVIDED HIGH IMPACT INTO A”>

3 Packs of Solution”>

“>”>Pack 1

DELIVERED”>

“>”>Pack 2

DEVELOPING

“>”>Pack 3

TO DEVELOP”>

IDEATION

“>Pack 1”>

Design Critiques”>

HANDOFF AND LIBRARY

Project Handoff

Local Library

FINAL SOLUTION

DESKTOP VERSION | PACK 1

“>”>OLD FLOW

“>”>NEW FLOW

MOBILE VERSION | PACK 1

Hierarchy Improvements

Guided Menu Creation

Category Creation

Product Creation

Complements and Final Catalog

“>Pack 1”>

“>Solution Live View

USABILITY TEST

RESULTS

Protected: Multiple Orders | Rappi

INTRODUCTION

Problem

Objective

Key Results (OKRs)

DISCOVERY

Briefing and Project Alignment

Collect Information

IDEATION & DEFINITION

Business and Tech Validation

Design Critique

DISCOVERY

FINAL SOLUTION

“>Desktop”>

UI Improve

“>Desktop

Order details”>

“>Desktop APP”>

Orders Separated

“>Desktop APP”>

Waiting Order”>

“>Desktop APP”>

CREATING CONNECTIONS

“>”>Issues to
improve

In High
Impact

Briefing and
Project Alignment

Business and
Tech Validation

“>”>Team
Components

Details of
Components

Why Partners are not converting toPriority Partners on their first 30 days?

Instructions
need to be more
clear and detailed

Insert
instructions
in all steps

Create
a guided
process

Change
text explanation
by videos

Show
error solution
for users

Use visual
elements to
explain better