Why We Learned to Say 'No' to Certain Projects: A Quality Manager's Story at Arkema

A quality manager from Arkema shares a story about a ceramic coating project that went wrong, explaining why embracing expertise boundaries is more valuable than trying to be a one-stop shop.

By Jane Smith

The Project That Changed Our Mindset

It was a Thursday morning in Q1 2024 when I received an urgent request from a prospective client. They wanted a custom formulation of epoxy resin for a new line of industrial ceramic coatings, and they needed it fast. (This was for a large batch, too—one of those 50,000-unit annual orders that gets everyone excited.)

I'm a quality compliance manager at Arkema. I review every formulation and product before it reaches customers—roughly 200+ unique items annually. In my first year, I made the classic rookie mistake: assuming that 'standard' meant the same thing to every team within our own company. That cost us a $22,000 redo and delayed a launch by two months. But this story is about a different kind of lesson.

The Assumption That Almost Sank Us

The client needed an epoxy resin system that could withstand extreme heat and chemical exposure for their "System X" ceramic coatings. The price point they were looking at was typical for the Indian market (epoxy resin price in India can fluctuate wildly, but their budget was around $4.50/kg).

My first instinct was, "We can do this." Arkema has a massive portfolio of high-performance polymers, adhesives, and resins. We have experts everywhere. It's tempting to think you can just adapt an existing formula. But the 'just tweak the formula' advice ignores the reality of formulating for a brand-new application like ceramic coatings.

I assumed our team could quickly modify one of our standard epoxy systems. Didn't verify our team's prior experience with this specific application. Turned out, while we were experts in epoxy for adhesives and general coatings, we had very limited experience with the specific thermal expansion and adhesion requirements of ceramic-based topcoats.

The Crisis Point

After three weeks of development, the first batch looked perfect in the lab. But when the client applied our resin to their ceramic coating process, it failed. The coating delaminated under thermal cycling. We'd shipped 8,000 units of the raw material before the full application test was done (ugh, the schedule pressure was immense).

The most frustrating part? We had to tell the client that our 'standard' high-temp epoxy wasn't going to cut it. You'd think that with our R&D budget we could solve anything, but the reality is that material science is about specifics. Our resin was great for bonding metal to plastic, but the chemistry of bonding a polymer to a ceramic surface under extreme duress was a different game.

We spent another $15,000 trying to reformulate. But every adjustment we made to improve thermal stability compromised the pot life or viscosity the client needed for their spray application. It was a classic example of the oversimplification fallacy.

The Lesson: Expertise Has Boundaries

I finally called the client. "This isn't our strength," I said. "Here's who does it better." I recommended a specialty formulator in Germany that specifically designs resins for ceramic matrix composites (circa 2023, they were the market leader).

The vendor who said 'this isn't our strength—here's who does it better' earned my trust for everything else. That's the core of the expertise boundary philosophy.

To be fair, we *could* have eventually solved the problem if we threw another six months and $100k at it. But the client needed a solution *now*. Granting that we were out of our depth was hard for my ego, but it was the right call for the business. The client was frustrated, but they respected the honesty. We ended up keeping their business for the other raw materials we *are* experts in—the surfactants and additives they used in the pre-treatment stage.

What We Changed

After that project, I implemented a new verification protocol in Q2 2024. Now, before any new product development project is approved, we ask three questions:

  • Do we have documented experience with this specific application (not just the chemistry type)?
  • Do we have test data for the exact final use case?
  • If we fail, is there a known, reliable alternative we can recommend?

I'd rather work with a specialist who knows their limits than a generalist who overpromises. We realized that trying to be a one-stop shop for everything dilutes the quality of what we are actually world-class at.

So glad I made that call to recommend the competitor. Almost tried to force the solution ourselves, which would have ruined a long-term client relationship. Dodged a bullet when I finally admitted we weren't the best fit for that one specific problem. That experience fundamentally changed how I view the phrase "Arkema product catalog."

If you need high-performance polymers, adhesives, or specialty surfactants for your standard processes, give us a call. But if you need a niche epoxy for ceramic spray coatings? I'll gladly point you to the true experts. That's why the best advice you'll get from a quality manager is often "let me know if this isn't our lane."

Need the technical background?

Ask Arkema for SDS, TDS, carbon methodology, or application notes connected to this story.