Accountability in Product Development: Where It Starts and Where It Fails

Product development looks different depending on the commodity, but one truth never changes: accountability is the backbone of every successful product. Whether you’re working in agriculture, food, dietary supplements, cosmetics, or household goods, each category carries its own science, risks, and regulatory expectations. The goal, however, remains the same — bring an exceptional product to market, ensure it performs the way it claims, and earn consumer trust. Accountability begins long before a product reaches a shelf. It starts with the people involved, the decisions they make, and the discipline they bring to the process. I learned this early in my career, and the lessons have stayed with me ever since.

When Accountability Fails: The Great Italian Dressing Massacre

My first exposure to product development came at the end of the process, working in distribution as a Quality Assurance Specialist. Most days were smooth — products arrived, passed inspection, and shipped. But every now and then, a single oversight unraveled months of work.

One of those moments became what I now call The Great Italian Dressing Massacre.

A corporate decision had shifted our Italian dressing to a new supplier. The moment we opened the container, we knew something was wrong. As I wrote in my notes at the time, “The old packaging had always arrived in white cases; these were brown… the protective netting was red instead of white… and every single box was leaking Italian Dressing.” The oil had separated, coating the entire load in a greasy film. Bottle tops were split. Seals had ruptured. The pallets were unstable.

We had to segregate the product, document everything, calculate the financial impact, cancel retailer shipments, and begin a full Root Cause Analysis — all while slipping across a dock covered in salad dressing as gnats and flies joined the chaos. That day taught me something foundational: by the time a product reaches the warehouse, the story has already been written. The decision to switch suppliers should have included capability assessments, packaging validation, transit testing, and a direct comparison to the existing product. None of that happened. The rush to cut costs skipped the fundamentals, and the result was sitting right in front of us — leaking, unstable, and completely avoidable.

Years later, I witnessed another breakdown in product development — this time in agriculture. The project involved creating a fertilizer intended to enhance crop growth year‑round. The cross‑functional team included R&D, marketing, merchants, innovation, and quality. On paper, it should have been a model example of collaboration. Instead, it became a masterclass in misplaced priorities. I named this one Recycle. Reuse. Go Hide!

From the first meeting, the focus was on competitors — their labels, their claims, their positioning. As I shared in the moment, “No one was talking about how the product should function, what the crops needed, or what the regulations required.” I was instructed to pull a competitor’s pesticide label from a public database and replicate the structure. I came prepared with compliant labeling options, proper usage statements, and scientifically sound claims. None of it was considered. Every attempt to contribute was met with the same dismissive lines: “I hate to slow down your momentum… but—” or “that’s a nice to have but I don’t think it’s needed.” After hearing it three times, it became clear that regulatory input wasn’t welcome.

Trying to be teachable, I dug deeper — visiting plant stores, reviewing competitor products, and researching ways to support the team. That’s when I discovered something that changed everything. The product wasn’t new.

Buried in the company’s extensive records was a label from 2017 for the exact same formulation — and the reviews were terrible. Farmers were frustrated. Stores refused to sell it. Crops were being damaged. The product had already failed once, and no one had addressed the root cause. When I raised the issue, I was told the record was “obsolete.” When I pointed out that it was stored in the current labels folder, I was told to “focus on the project.” Eventually, I learned the truth: leadership planned to re‑label the product as “new and improved” without changing the formulation, the science, or the performance. Just a new label.

My time there was brief — and when it ended, I celebrated for a week.

What These Experiences Taught Me

Across both scenarios, the failures were rooted in the same themes:

1. A Culture Resistant to Change

• Teams that have operated the same way for decades often see no need to evolve — even when the current approach is failing.

2. Competitor Analysis Is Not Product Development

• Copying a competitor is not a strategy. It’s a shortcut that creates risk, especially in regulated industries.

3. Marketing Cannot Drive Scientific Decisions

• When marketing leads development, the result is often misleading labels, unsupported claims, regulatory violations, and consumer harm.

4. Ignoring Regulatory Input Creates New Problems

• As I noted in the episode, “Under EPA regulations, products used on crops must adhere to strict guidelines… Under FDA protocols, packaging needs to meet basic requirements for lids and tamper seals. All of this was ignored in both scenarios.”

5. The Development Chain Was Out of Order

• Product development follows seven stages. Skipping even one can cost millions.

6. Consumers Carry the Consequences

• When companies cut corners, consumers pay the price — through damaged crops, contaminated soil, reduced yields, foodborne illness, or financial loss.

Why Accountability Matters

Accountability isn’t a buzzword. It’s a safeguard.

I’ve seen companies lose millions because of preventable oversight. Those losses ripple through an organization — affecting promotions, bonuses, new roles, and overall health. Too often, leadership blames the consumer instead of acknowledging internal failures.

If you take nothing else from this story, take this: Every decision you make in product development either strengthens your brand or puts it at risk. Regulatory agencies will hold you accountable eventually — but responsible teams hold themselves accountable long before it gets to that point.

Thank you for visiting & have a great week!