Jaguar's Rebrand Lost 97% of Its Sales. Redesigns Keep Happening Anyway.
In November 2024, Jaguar unveiled a rebrand — new logo, new campaign, a repositioning toward electric vehicles that made headlines for weeks. By April 2025, the company sold 49 vehicles in Europe. The same month a year earlier, it had sold 1,961. That's a 97.5% collapse, and it happened in the exact window the rebrand was supposed to be building momentum, not burning it.
Nobody at Jaguar woke up one morning to a memo demanding a new logo. A rebrand of that scale gets greenlit by people with a specific kind of timeline: a new creative or brand leader arrives, needs a visible mark to justify the hire, and has maybe eighteen months before the board asks what they've actually changed. The redesign is the answer to that question. Whether it's the answer to a question customers were asking is a separate matter, and increasingly, the data says it wasn't.
The Redesigns Users Never Asked For
Jaguar isn't the outlier — it's the pattern made visible because a car company's sales numbers are impossible to spin. X's 2024 interface change stripped away the visible engagement counts on posts, keeping only view counts, in a redesign framed as a privacy and anti-pile-on improvement. Monthly active users fell from 368.4 million to 335.7 million that year — a 15% global drop, 18% in the US — and app downloads fell 38%. Instagram's 2024 redesign relocated the search bar, the Reels tab, and the primary post button; by 2025, median engagement rates had fallen from 7.3% to 5.4%, a 26% decline, with Reel views down 76% from two years earlier. Bluesky's 2026 rollout of an AI assistant nobody had asked for made the assistant's own account the most-blocked account on the platform outside a sitting politician, and overall user activity dropped roughly 40% by the end of 2025.
None of these products failed because the underlying service got worse. They failed because the interface got changed in ways that served an internal narrative — modernization, AI-forward positioning, a fresh visual identity — more than it served the person trying to find the thing they came for.
Résumé-Driven Development Has a Name in the Literature Now
This isn't just a vibe designers complain about at conferences. It has a formal name and a peer-reviewed definition: "résumé-driven development," first characterized empirically in a 2021 paper presented at an IEEE conference, and revisited in 2023 with the pointed title "Resist the Hype! Practical Recommendations to Cope With Résumé-Driven Development." The research describes exactly the pattern above — technology and design choices made because they'll read well on a CV or portfolio review, adopted faster and with less user validation than the problem actually warranted.
Mark Parnell, a design lead at Atlassian, put the internal version of the same critique on the record in a widely shared essay: an industry-wide overemphasis on documenting a slick "process" for portfolio purposes is quietly training designers to optimize for how a case study reads, not for what the redesign does to the person using the product. A portfolio needs a before-and-after. A working product frequently doesn't have one to give, because the best design decision is often the boring one: leave it alone.
Why the Old Version Usually Wins Anyway
The economics point the same direction the case studies do. Acquiring a new customer costs five to twenty-five times more than retaining an existing one — a ratio product teams cite constantly when justifying retention work, and then routinely ignore when a redesign is framed as "modernization" rather than "risk." A redesign that erodes 15–26% of engagement isn't a rounding error against that math. It's the retention budget lit on fire to fund a rebrand nobody in the user base requested.
Usability testing exists specifically to catch this before it ships, and the pattern across Jaguar, X, Instagram, and Bluesky isn't that testing wasn't available — it's that testing findings, when they existed, competed against a launch date tied to someone's performance review cycle, and the launch date won. A designer with 18 months to make an impact doesn't have room in that math for a testing cycle that might recommend "don't."
The Tell Is Always the Same
Every one of these redesigns has one thing in common that's visible if you know to look for it: the change was announced before it was requested. Users didn't file tickets asking Instagram to move the post button. Nobody's most-upvoted feedback thread asked X to hide the like count. The initiative arrived from inside the building, wrapped in language about "modernizing the experience" or "reducing noise," and the actual noise — the backlash, the churn, the sales collapse — arrived afterward, on a much longer and more expensive timeline than the one the redesign was built to fit.
That's the practical diagnostic for anyone evaluating whether a proposed redesign is solving a real problem: trace the request backward. If it originated in a support ticket, a churn cohort, or a usability study, it's probably earning its cost. If it originated in a leadership transition, a rebrand initiative, or a slide that says "modernize the platform" with no named user behind it, you're looking at a portfolio project wearing a product's clothes.
So Actually — The Redesign Isn't for the User. Ask Who It's For.
The framing that makes this legible isn't "good design versus bad design." Jaguar's new logo is, by conventional design standards, competently executed. Instagram's relocated buttons follow current interface conventions. The failure isn't aesthetic. It's that the redesign answered a question — "what did I change this year" — that has nothing to do with the question the product exists to answer for its users. Two entirely different clients were being served by the same launch, and only one of them showed up in the room where the decision got made.
Design systems and governance processes exist to put friction in front of exactly this move — a second signature required before "modernize" becomes a shipped change nobody asked for. The teams that skip that friction aren't usually reckless. They're on a clock the user doesn't know exists, and the user is the one who ends up paying the difference.
Next time your product gets a redesign, ask the boring question before you ask whether you like it: who requested this, and can you name them?
The friction that's supposed to catch changes like this before they ship is exactly what breaks down without real authority behind it — see Your Design System Has No Owner — That's Why It's Quietly Dying