Battery project failure isn’t dramatic. It doesn’t announce itself with one catastrophic decision. It arrives gradually, the result of incremental oversights and the race against a schedule that erodes discipline at every turn.
Across this series, we’ve examined the battery project life cycle from identifying recurring challenges, to de-risking through research and development, to the importance of planning, and effective ways to ensure operational readiness.
To understand how the themes we’ve explored connect across the life cycle, it helps to step back and examine the ways risk accumulates and the four areas where challenges arise and failure reveals itself:
- The early material selections that sidestep manufacturability and scale.
- Technical shortcuts in project design that embed risk into the foundations.
- Oversimplified construction plans that ignore the true complexity of integrated systems.
- The accumulation of operational risk—small misses that compound until startup fails.
At the root of many of these issues is insufficient time, often precipitated by enticing offtake agreements that come with demanding schedules. The consequences of these failures aren’t theoretical. They show up in the economics of the plant. Battery facilities don’t generate meaningful returns until they’re typically operating over 85% of design capacity, on a sustained basis. Until then, every slip in schedule or performance adds pressure to the business case.
You can see this dynamic clearly in the McNulty Curves and typical ramp-up patterns. Many projects fall short during ramp-up, and even small deviations from the expected trajectory can undermine value. Owners and lenders watch these curves closely because they reveal a simple truth: once a project falls behind early, it rarely catches up. The climb to stable operation gets longer, and the share of the original value proposition that can still be captured gets smaller.
Our experience at Hatch reinforces this. Strong operational readiness, disciplined commissioning, and a deliberate approach to ramp-up are some of the most powerful tools available to protect a project’s economics. They shape cash flow timing, return on investment, and how much value is preserved or improved when targets are exceeded. Ramp-up isn’t something you “get to” after the technical work is done. It is the business case. Every missed dependency and every shortcut taken upstream pushes that 85% threshold further out of reach. And once momentum slips, the path back is slow, costly, and uncertain.
The takeaway is straightforward: a battery project is only as strong as its weakest link. When we understand where projects stumble, we can intervene and take critical steps to keep them on track:
Design for manufacturability at scale
-
Front-end process development: Evaluate material handling, yield sensitivity, and mixing behavior at pilot scale before locking design.
-
Product validation: Conduct trials under expected operating conditions, adherence to specifications, moisture sensitivity, thermal profile, shear limits.
-
Design-to-production alignment: Ensure every choice—chemistry, equipment, layout—maps to real-world production capabilities, not theoretical best-case.
Build a risk-informed project culture
-
To achieve the quality, understand the work: Learn to recognize false claims and empty promises.
-
Choose a capable partner: Many organizations, when faced with their own risk knowledge, rely too heavily on risk assumption, which results in over-confidence. Attitude is everything! Don’t be so confident that you compromise the business case.
-
Assumption registers: Document and track assumptions throughout FEL stages. Identify which ones are high-impact and validate them early.
-
Scenario modeling: Simulate alternate outcomes for schedule compression, material delays, or design changes. Plan for failure modes. Strategize your test work and verification.
Treat planning as a technical discipline
-
Integrated sequencing: Don’t simply define what needs to happen. Consider the logical, interdependent order of operations validated by technical experts. Then follow that plan, explicitly! It is your roadmap, clearly showing what you need to do today, to be ready for tomorrow.
-
Choose a partner who understands what an illogical plan looks like: Your trusted partner is proactive and intimately understands the sequencing and interconnections that comprise a plant.
-
Rolling wave schedules: Incorporate agility into the process so the team can adapt to inevitable change and implement a process to uncover and address unknowns.
-
Resource-linked planning: Don’t just schedule the task, tie it to available labor, tools, data, and validation results. Know how to interpret your data and apply results to operations.
-
Sequence structural engineering appropriately: Have the foresight to start today so you’re ready for tomorrow.
Operational readiness isn’t a milestone. It’s a mindset.
-
Understand good operational readiness: Define what needs to be in place to circumvent risk by knowing what it takes for a business to operate. It’s not just about the product.
-
Operator immersion: Bring in operators early for training on procedures, simulations, and system interactions, before the line goes hot. Prioritize developing their situational awareness to enable them to detect abnormalities and take swift corrective action. Even a perfect design needs an appropriately skilled operator.
-
Readiness matrices: Track the readiness of people, machines, data, and documentation across every unit operation. Don’t declare readiness until every input is in place.
-
Dry runs and failure testing: Test subsystems under partial load and simulate startup conditions. Validate control logic, interlocks, and operator workflows. Why doesn’t the copy/paste model work? Why does it fail to produce beyond 60% yield after five years?
And here’s the catch, success only comes when these challenges are executed together, simultaneously, iteratively, seamlessly. Operational readiness must inform the design phase. Testwork must inform equipment specifications. So… what does it take to build better plants? To build better battery plants, we must first build better builders.
Behind every technical failure is a human decision made under pressure. At times, people don’t know what they don’t know. They may be overconfident or fail to recognize they need help. By the time they realize it, the project has drifted off course, and recovery becomes costly and slow.
Battery materials and cells projects aren’t just about how to build better batteries, they’re about who you need to be to build them successfully.
The challenges we’ve outlined across this series—technical risk, schedule pressure, integration complexity, operational readiness—are real, measurable, and solvable. We’ve offered frameworks, insights, and tangible solutions.
But beneath all of it lies a quieter truth, most battery projects don’t fail because the teams didn’t know better. They fail because someone was afraid to demand what was needed. Afraid to say the plan wasn’t ready. Afraid to ask for better data. Afraid to push back on a timeline that was never realistic. Afraid to stop and ask: What’s the consequence if we’re wrong?
Failure accumulates when warnings are softened, when doubt is left unsaid, when silence keeps the momentum going in the wrong direction. The silence may exist ... until the start button is pressed, and risk turns into reality. This is the point when risk accumulation must be reconciled with the truth.
Building better batteries isn’t just a technical effort. It’s a human one. And sometimes, success means being the person who has the courage to say: We’re not ready yet.
Cutting corners may offer temporary relief. But in battery manufacturing, delays born of poor decisions cost more than time—they cost trust. In a market defined by complexity and constrained by consequence, trust isn’t a tagline. It’s earned through execution.
That’s why we hold ourselves to a higher standard. Not to rise above the noise, but to offer a signal. To provide clarity where there’s confusion, and rigor where there’s risk. Clients don’t just need partners, they need proof. Before the questions come, we deliver answers. Before the assumptions are made, we validate.
Trust demands transparency. It asks us to know our limits and confront them. To acknowledge where others outperform—and to lean on the right partners, so we can outperform where it matters most. No one succeeds alone in this space. But with the right partners, grounded in real expertise and proven delivery, success becomes engineered, not guessed.
The future won’t reward the fastest or the loudest. It will favor the builders who think in ecosystems. Who plan with intent. Who see start-up not as a finish line, but as the point of no return.
The projects that endure are the ones led by teams disciplined enough to slow down when it matters so they can accelerate when it counts.
