Lessons Learned: Project SwiftRide Atlanta Redesign

Project SwiftRide Atlanta Redesign

This lessons-learned report reviews the twelve-month overhaul of our car rental booking platform in Atlanta. When we initiated this project last spring, our primary goal was to modernize the web app and secure a new funding round by showing rapid innovation to investors. We believed that a dramatic visual shift would immediately extend our runway and impress our board members during the upcoming investor update.

Looking back with criticism in hindsight, we realize that the decision to invest in such a massive overhaul was premature. We spent countless hours arguing about matrix structures and dotted lines on our organizational chart instead of focusing on actual customer pain points. The availability of resources should have allowed us to test smaller hypotheses, but instead, we fell into the trap of wasted effort and unnecessary redesign.

During the first six months, our prioritization of initiatives was completely flawed. We abandoned incremental improvement in favor of a total platform rewrite using Figma and Webflow. We needn't have discarded our existing design system because users were already comfortable with the booking flow. We could have achieved better conversion rates if we had simply listened to customer support tickets instead of second-guessing the data.

Furthermore, our design leadership failed to encourage ownership across product squads. We ought to have established clearer accountability meetings to justify spending before writing thousands of lines of front-end code. Instead, team members engaged in a frustrating blame game whenever velocity dropped or Jira tickets piled up in the backlog.

To own a mistake is never easy, but this project forced us into an honest reflection about how we operate. We learned that rushing into a redesign without proper due diligence on design leads straight to costly decisions. A wiser course of action would have been to run usability tests on specific checkout bottlenecks rather than overhauling the entire information architecture.

This experience serves as a powerful lesson for the organization as we prepare for future product expansions. We must remember that evolution always beats revolution in digital products. By allowing mistakes to become teaching moments, we are building a mature design culture where incremental updates drive sustainable business growth.

Moving forward, our executive team promises to revisit any major strategic decision through rigorous user research. We are introducing a strict rule for all product managers across our US offices: never redesign what users haven't complained about. If a core feature works seamlessly, leave it alone and focus on real problems instead.

Read again and choose the right answer

What was one of the primary goals when initiating the SwiftRide redesign?

• To secure a new funding round
• To cut the engineering team in half
• To migrate the database to a new cloud host

What does the report say about the decision to overhaul the platform?

• It was a brilliant strategic move
• It was a premature and costly decision
• It was praised by all customers

What is the report's main golden rule for future product updates?

• Always redesign every two years
• Never redesign what users haven't complained about
• Fire designers who make mistakes

How does the team describe the ideal approach compared to a full rewrite?

• Incremental improvement and evolution
• Complete code refactoring from scratch
• Outsourcing all UI tasks to agencies

Sources: photo by Nataliya Vaitkevich on Pexels