How to judge evidence in condiment case studies

What to take away

What a case study can and cannot prove

A case study can show that something worked once, in a specific place, under specific constraints. It cannot show that the same choice caused the outcome, and it cannot show that it would work for you. That is not a reason to ignore case studies. It is a reason to read them for mechanisms rather than for recipes.

On this site, that matters because we cover independent sauces, spices and condiments in the United States. A case study about a hot sauce maker, a spice blender or a condiment producer can show how one batch, one retailer or one co-packer arrangement worked in one period. This article is a method for judging that evidence, not a case study of a particular maker.

It cannot prove that the same move would work for another small food business. Read those stories for the mechanism, not for a recipe to copy. When we publish profiles, we try to separate what a founder remembers from what a document can show.

The most common misreading is treating a survivor's habits as causes. A brand that used a particular packaging or channel and grew may have grown despite it.

The evidence hierarchy

Published collections are a reasonable starting point when you know what they are. The Small Business Administration publishes manufacturing success stories about small manufacturers it helped with financing, ownership transitions and expansion.

Those are selected examples of assisted businesses; they are useful for mechanisms and unsuitable as a sample. Inside a sauce, spice or condiment business, the same preference for boring evidence points at the machines, where a nameplate settles questions a founder's memory cannot.

Why good data on this is hard to get

Detailed retail information exists and is mostly not public. USDA describes its use of proprietary data within the Consumer Food Data System, drawing on sources such as scanner data and establishment time series data, and notes that access to these datasets is restricted.

That restriction shapes what anybody can honestly claim about a small brand's performance. Nobody writing publicly about an independent condiment brand has its sales data. Treat any article that implies otherwise with suspicion, including ours.

There is a second, quieter problem. Founders reconstruct their own history in the telling, not dishonestly but in the way everyone does, by arranging events into a story that makes sense in hindsight. Dated documents are the antidote.

When a recollection and an invoice disagree, the invoice is usually right, and the gap between them is often the most interesting thing in the study. The same gap appears on a jar, where the testable half of an origin story is a short list and the rest is atmosphere.

Writing one that holds up

Fix the scope first: one business, one period, one question. Record what you can verify, and mark clearly what is the founder's account. Write down the constraints, including money, location, family circumstances and luck. Then state what you did not learn.

A case study that ends with open questions is more useful than one ending with five lessons. The questions show readers where their situation might differ.

For the method behind finding businesses worth studying, see our watch list guide. For failure patterns that rarely appear in published stories, see the lessons from projects that went wrong.

Common questions