Lucid Motors drives innovation with Assets in Jira Service Management
How modern asset management powers hardware development at scale
This blog is adapted from the Team ’25 session, “The Assets advantage: How Lucid Motors streamlined processes across teams”
Lucid Motors is on a mission to inspire the adoption of sustainable energy by creating the most captivating electric vehicles, centered around the human experience. Their luxury electric vehicles achieve the most miles per kilowatt hour in the automotive industry.
To do this, they’ve engineered highly efficient powertrains—the parts that move the vehicle forward—while balancing customer requirements for affordability, mileage range, and interior space. This means managing thousands of moving parts—literally and figuratively. Behind every Lucid Air or Gravity SUV is a complex web of hardware, software, and teams working in sync. While experiencing rapid growth and innovation, Lucid turned to Atlassian Assets in Jira Service Management to bring order, traceability, and agility to their hardware development.
A few years ago, Lucid’s hardware teams tracked critical hardware components—like motors, batteries, and inverters—across a patchwork of spreadsheets, Smartsheet plans, and Confluence pages. Each team had its own system, making it difficult to get a real-time, holistic view of available parts, understand their history, and ensure that they arrive in the right place at the right time. As Lucid’s R&D spend soared (from $900M in 2023 to nearly $1.2B in 2024), the need for a unified, scalable asset management solution became urgent.
Journey of a prototype motor
For Lucid, Assets is central to the hardware development process. Felipe Luisi, A Senior Product Manager, walked through the journey of a prototype motor to share how Assets provides critical organization.
Prototype build: The team designs a new motor. They order prototype parts, and create a Jira build ticket. The parts are sent to the technician along with a build ticket, and an Asset is automatically generated for the prototype tracking.
Comprehensive testing: Once the technician finishes the prototype build, the drive unit is carted to the testing area, and scanned by a QR code. This updates the location of the asset and populates all the requisite testing.
Teardown: After all the tests are run, the unit is returned to the technician who tears it down and documents the tear down and takes photos.
Rebuild: To evaluate different designs, the prototype is rebuilt with variation. This may involve a different set of gears or a different supplier.
Vehicle integration: The drive unit may be put into a car, and task ticket to load it into a car
Gaining the transparency for scale
At the end of the process, the Asset becomes a comprehensive repository for all the work ever done on it. Lucid Motors can look at the drive unit and see the chronological history of everything that happened to it. It’s easy to understand everything that is going on with the units and where they are going. And, Assets can be linked to each other. A vehicle asset can show the motor and all the work on the vehicle, including scheduled tests.
It’s important for Lucid’s R&D team to justify building cars and ensure they aren’t sitting idle. With Assets, they are able to optimize scheduling. They might ship a vehicle to New Zealand for winter testing, where it may then experience a battery failure. Fortunately, with Assets, the team in California can see what battery was in the test vehicle, who built it, how it was configured, and uncover why it failed quickly. Now think of how many other parts go into making cars a reality.
Felipe Luisi explained that Assets is critical to their process, calling it an “absolutely crucial part of our Jira infrastructure, and I frankly don’t know how you could do hardware engineering with Jira, without also tracking your hardware in the same space. Because when we try to do it with fractured hardware tracking tools, like all these different tracking tools, there was no traceability inherent to our systems. And if you tried to do everything in those other tools, there’s no agility in that either. So, we’ve really found something that works for us.”
About Atlassian Assets
Assets is Atlassian’s flexible, relational database for tracking anything that matters to your teams—hardware, software, inventory, or even custom objects unique to your business.
With Atlassian Assets, customers get:
A centralized repository – Consolidate data of any type within Jira Service Management. All kinds of teams, dev, IT, Ops, finance, HR, and more, can collaborate and consolidate data in one central place.
Flexibility – Structure and connect data relationships and hierarchies to serve your use cases. For instance, in the case of an incident, pull information into root cause analysis. Or assess the risk of a change by viewing impacted CIs.
Workflow automation– Integrate with Automation, and build approval flows based on data stored in Assets.
Info where you work – Leverage the Assets field to display information across Jira issues and Confluence.
Modern Asset management
Lucid Motors shows how modern asset management is about powering innovation, improving efficiency, and delivering world-class products faster. You can check out the full presentation here and learn more about Assets here.