Genesis

Overview

Genesis is a community-based freight and moving platform designed to connect customers with independent transporters across Latin America, acting as a sustainable alternative to historically fragmented networks.

I owned and led the interface design for Genesis while the product was still undefined, translating an ambitious, largely unscoped vision into a usable, trustworthy platform — shaping the core user flows, the visual system, and the interactions that would hold the experience together as the product itself was still being figured out.

The final product vision evolved from an early concept into a complete, interactive booking experience supported by a robust component system, successfully establishing the foundation as the team prepared for development.

Across Latin America, independent freight and moving services often operate through informal, fragmented networks — word of mouth, scattered listings, and little to no way for a customer to verify who they were actually trusting with their belongings. Genesis set out to formalize that network into a single platform, connecting customers directly with independent transporters.

There was no existing product to redesign and no prior research to build on — just an ambitious concept and a small team tasked with figuring out what the product actually needed to be, from the ground up.

Genesis needed to help customers coordinate an unfamiliar logistical process while eventually supporting an ecosystem of independent drivers across different regions, devices, and levels of digital familiarity.

The service itself was inherently complex. A single booking could involve locations, cargo limitations, vehicle selections and extensive communication on both sides. Exposing all of that at once would risk overwhelming users before they completed their first booking.

To understand where Genesis could create the most impact, I looked at how existing services handled the burden of moving. The landscape was split into two extremes: traditional rentals like U-Haul left users entirely on their own with zero digital guidance, while app-based movers including Dolly and Lugg solved the physical labor problem but introduced opaque pricing and trust barriers.

This revealed a massive gap in the market. Genesis didn't just need to connect transportation demand with verified independent drivers — it needed to introduce a highly guided, transparent experience. We needed to build the trust that competitors were missing.

The challenge wasn't making the interface look simple. It was deciding what complexity users needed to see—and when. To navigate this, rather than treating each screen as an isolated problem, I used three guiding questions to shape every structural decision.

With no existing product architecture to build from, the first challenge was determining how a complex physical process could translate into a digital journey.

I began by mapping the information required to complete a booking and organizing it around the natural sequence of planning a move.

Rather than asking users to provide everything at once, the experience progressed from understanding the move itself to selecting transportation, reviewing the price, completing payment, and receiving confirmation.

This structure became the foundation of the product. Each step answered a focused question before introducing the next, allowing users to understand the process without needing to hold every logistical variable in mind at once.

Once the journey was established, I could begin refining how each decision should work.

Instead of presenting users with one overwhelming form, I structured the experience around progressive disclosure. Each screen introduced a focused decision, allowing the complexity of a move to unfold gradually.

Rather than asking for all move related details simultaneously, users could focus on one question at a time before moving forward.

In traditional platforms, users are forced to guess which truck capacity fits their belongings. To eliminate this friction, Genesis automatically recommends the ideal vehicle based on the property details provided in the previous step.

While the system handles the technical translation to reduce cognitive load, users retain full agency to view alternative truck sizes and adjust their selection before requesting a price estimate.

We initially considered including a "save booking details" option within the booking flow. But because the early journey was designed to collect only the information necessary to reach a price estimate, introducing another exit point before users reached that value moment risked interrupting momentum.

Rather than adding another decision, we focused on making the flow concise enough to complete in one session. However, removing the feature was a tradeoff — it prioritized forward momentum over flexibility.

The checkout experience was designed to make the financial process understandable at every stage. Before committing, users could review a detailed price breakdown, understand what was included in their estimate, and see how the deposit contributed to the final transaction.

The flow also surfaced cancellation policies and potential fees, helping users understand the consequences of changing plans before completing payment.

The user journey does not end when they press "pay." Generating a formal digital receipt and outlining clear next steps shifts the user's mindset from digital booking to physical coordination, reinforcing the platform's reliability and ensuring they feel secure in their transaction.

To bring the journey full circle, the post-booking experience serves as a centralized hub for all move details. Rather than leaving users to hunt through scattered email threads, the dashboard provides a clear, step-by-step visual tracker that monitors the move from booking to final delivery.

When it's time to coordinate with the driver, users can rely on a secure, in-app messaging system. This keeps all conversations documented within the platform, protecting user privacy and removing the friction of handing out personal phone numbers.

The visual system relies on a focused, high-contrast palette designed to build immediate brand trust and reduce cognitive load. By restricting the palette to a core four-color stack—anchored by the primary Genesis green—the interface maintains a clean, utilitarian aesthetic that never distracts from the core booking tasks.

Typography was selected specifically for legibility across dense logistical information, ensuring that critical details like price breakdowns, dates, and addresses remain highly scannable.

Designing for edge cases meant ensuring that user mistakes or system failures were handled gracefully. The platform employs a dual approach to error recovery to prevent drop-off. Inline validation provides real-time, descriptive helper text on forms to guide users before they submit. For high-stakes actions, such as a failed payment, explicit overlapping system alerts instantly notify the user without navigating them away from the page, preserving their inputted data and allowing for quick resolution.

To maintain consistency across the booking flow, the interface was built using a robust, reusable component library. Interactive elements, such as the progressive vehicle selection cards and modular text inputs, were standardized to ensure predictable behavior. All primary call-to-action buttons and form fields maintain a minimum 44x44px touch target, embedding usability and accessibility directly into the component structure rather than treating them as an afterthought.

The structured, single-decision screens were designed specifically to scale seamlessly across breakpoints. By keeping the layouts vertically stacked and prioritizing progressive disclosure, the interface adapts naturally to smaller mobile devices without sacrificing visual hierarchy. This ensures that the core booking experience—from the initial route visualization to the final digital receipt—remains just as intuitive and uncluttered on a phone as it is on a desktop monitor.

The final system had to work across every part of the experience—from route planning and vehicle selection to secure payments and post-booking coordination—without making the interface feel overwhelming. Each interaction provides enough structure to guide users without competing with what matters most: the clarity of their move.

The result was a visual system that made a complex set of logistical steps feel like one cohesive experience. The focused palette, reusable components, and clear hierarchy work together to give Genesis a consistent identity from the first booking screen to the final delivery dashboard.

After refining the booking journey into a high-fidelity, interactive prototype, we tested the experience with six participants from Latin America. Four of the six participants compared the multi-step experience favorably to familiar transportation products like Uber and Lyft. Breaking the booking into focused decisions helped participants understand what was being asked of them without confronting every logistical variable at once.

The feedback supported the structural strategy behind the experience: complexity didn't necessarily need to disappear—it needed to be introduced at the right moment.

Usability testing revealed an important tension within the design: prioritizing progressive disclosure meant sacrificing early financial transparency. While users appreciated the step-by-step logistics, they felt blindsided by discovering the deposit requirement at the very end of the flow. This feedback highlighted a clear need to introduce the upfront cost well before the final checkout screen.

Because my involvement concluded prior to public launch, success was measured through the delivery of a robust MVP foundation rather than live marketplace metrics. The primary outcome of this phase was a complete end-to-end customer booking architecture, supported by an interactive prototype and a scalable component system.

Ultimately, this work answered the core question of what Genesis could become. Rather than just a collection of visual concepts, it established a cohesive, user-centered experience with the structural maturity required to move directly into development.

Designing Genesis changed how I think about the relationship between digital interfaces and physical logistics. A dashboard isn't just a layout of information, it also provides the exact peace of mind someone needs on moving day. The biggest lesson I took from building this MVP is simple: good product design doesn't just organize complex tasks. It replaces real-world anxiety with predictable certainty.