When a new leader steps in and publicly lists everything the previous team got wrong, it's rarely just a press-cycle moment. It's a project management lesson hiding in plain sight. Speaking on an earnings call covered by businessinsider.com, Lucid Motors' new chief executive Silvio Napoli laid out, in unusually plain language, where the company has fallen short.
For anyone who runs sprints, signs off on releases, or pitches new initiatives to leadership, the story is uncomfortably familiar. Missed dates, quality slip-ups, and a culture that prioritized launch optics over launch readiness — we've all watched a smaller version of this play out.
What happened:
- On the call, the incoming CEO said Lucid released vehicles before they were truly ready, naming that failure alongside others.
- Quarterly net loss at the EV maker came in above the $1 billion mark.
- The roughly $50,000 midsize Cosmos SUV is now slated for the second half of 2027, slipping from a much earlier target.
- A new set of "quality gates" has been introduced to verify production and quality criteria before any launch.
- The company reports roughly $3 billion in total liquidity, shared on the call.
- Staff reductions of 12% in February and 18% in June followed earlier overproduction issues, and the COO position was eliminated.
How Lucid Got Here
The company traces its roots to engineers who previously worked at Tesla, and the Saudi Arabian sovereign wealth fund sits among its key backers. Lucid has been in the red since its first cars rolled off the line. Two models — a flagship sedan called the Air and a three-row SUV named the Gravity — are already in customers' hands, and owners have described software headaches to Business Insider, including glitches with key fobs and infotainment screens.
Earlier in the year, after building more Gravity SUVs than the market could absorb, leadership pulled the levers familiar to anyone who's sat through a reorg. Two headcount reductions followed in quick succession, and the chief operating officer seat was removed from the org chart. Weeks of public pushback against bankruptcy chatter set the stage for Napoli's reset message.
What Changed Under the New CEO
Napoli moved quickly on the executive team and reset how the next vehicle gets built. Cosmos prototypes are now working through crash development, aerodynamic refinement, cold-weather trials, and battery and drive-unit testing. Additional prototype runs, regulatory paperwork, and manufacturing validation still sit on the critical path.
The most visible operational shift is a new layer of "quality gates" — checkpoints designed to confirm every production and quality bar is cleared before a launch. A spokesperson told Business Insider the company would not detail how the new checks differ from the old process. His on-call summary was sharper than any press release: Cosmos will not reach customers until the team is confident every standard has been satisfied.
Who Feels the Pressure Now
Rivals aren't pausing to be polite. Deliveries of Rivian's R2 began in June, and a three-row Model Y L from Tesla recently arrived on US roads. Every quarter Cosmos slips is a quarter those competitors spend owning the midsize electric SUV segment Lucid is chasing.
Inside Lucid, the people who survived two rounds of cuts are now being asked to deliver under a stricter, more documented release process — often the hardest setting in which to rebuild a quality culture. Investors, meanwhile, are absorbing a quarterly net loss above $1 billion while being asked to wait until late 2027 for the next major product.
Our Analysis
What stands out to us isn't the mea culpa — those happen every earnings season. It's the willingness to publicly name the failure modes: missed commitments, premature launches, under-invested support, slow responses to quality issues, and complexity slowing decisions. That's a project post-mortem delivered to Wall Street.
For our readers, the pattern maps cleanly onto work you actually do. "Launched before they were ready" is a release-train decision. "Missed commitments" is a forecasting problem. "Under-invested in service" is a capacity-allocation problem where new feature work crowded out support. "Responded too slowly to quality issues" is an escalation path that didn't reach the right people fast enough. And "complexity slowed decisions" is the governance tax that grows every time you add a stakeholder without pruning a meeting.
Who benefits from the new gates? Customers, eventually, and the engineers who were previously pressured to ship around defects. Who loses? The sales and marketing teams whose 2026 and early 2027 plans just collapsed, and the investors funding the runway until the new gates pay off.
What It Means for You
Say you are a scrum master or PM leading a release that leadership keeps waving forward. You've got a demo in two weeks and a known defect that isn't going to be fixed in time. The temptation is to scope it down, ship, and "iterate in production." Lucid's story is the bill for that choice, itemized.
A practical move this week: write your release criteria on a single page, get the engineering lead and a support lead to sign it, and treat any "not done" item as a hard block. Add a post-launch review at 30 days that includes customer-reported issues, not just internal metrics. If your org doesn't have a name for that review, invent one and run it anyway — the label matters less than the habit.
What to Watch Next
Keep an eye on three things. First, whether the quality gates show up in writing in Lucid's next investor materials, or stay as a slogan. Second, how Cosmos's prototype milestones land in 2026 — slippage there will be the real test of whether the new process is discipline or theater. Third, whether the midsize EV market is still wide open by the second half of 2027, or whether the rival brands have closed the door.
Bottom line: Napoli is essentially betting the company that shipping later but better beats shipping on time with apologies. For project managers everywhere, that's a reminder worth pinning to your release plan.
Key takeaways
- "Launched before ready" is a decision, not an accident — make release criteria explicit and signed off, not assumed.
- Under-investing in service and support is a capacity trade-off, and it shows up in customer trust before it shows up in metrics.
- New quality processes only matter if they are written down, reviewed, and visibly enforced at the next major milestone.
Frequently asked questions
Who is Lucid's new CEO and when did he start?
Silvio Napoli became Lucid's CEO in June, according to businessinsider.com, and delivered the candid self-assessment on a recent earnings call.
Why was the Lucid Cosmos delayed?
The roughly $50,000 midsize vehicle was pushed to the second half of 2027 so the company can finish prototype testing, regulatory work, and manufacturing validation under new quality gates.
What are Lucid's "quality gates"?
They are new checkpoints the company says will confirm production and quality requirements are met before any launch. Lucid has not publicly detailed how they differ from the previous process.
How is Lucid handling the financial pressure while it delays the next car?
The company reported a quarterly net loss of more than $1 billion, has about $3 billion in total liquidity, and has already cut staff twice this year after overproducing the Gravity SUV.
What can project managers learn from Lucid's situation?
Treat release criteria as a signed contract, protect service capacity from being eaten by new feature work, and build explicit escalation paths so quality issues surface before customers force the conversation.
Inspired by reporting from: businessinsider.com