There are moments in a company when the difference between understanding and not understanding a process isn’t a detail: it’s what allows you to build a solid product or remain stuck, stuck in the face of a mechanism that won’t listen.
It happens when you’re in the production process, with your hands on the parameters, and you wonder why an emulsion doesn’t hold up, why a batch varies for no apparent reason, why a theoretically perfect machine doesn’t deliver the promised result.
In those stages, a precise, concrete explanation is needed, without embellishment. And, from firsthand experience, a certain American way of describing technology can be more illuminating than many elegant yet cautious European pages. Not out of cultural superiority, but because of a different approach: if you have to make something work, it’s better to tell yourself straight away how it really works.
This article was born from a real-life experience, one of those that changes the quality of a product and also the perspective with which you build it. And it’s an opportunity to reflect on how entrepreneurs look for solutions, what they see, and how they proceed when things don’t work out the first time.
- When you need a technical truth, not a speech
Every production process has blind spots. Areas where manuals seem inadequate, recipes “almost” work, and experience still doesn’t provide sufficient insight. This is why an entrepreneur spends so much time observing how others work: who has already solved that problem, who has found a shortcut, who has been forced to be inventive.
In our case, it all began in the late 1990s, when we decided to develop the first organic and gluten-free sauces. It was an ambitious project. The recipes were there, and so was the will: we wanted to produce six sauces—Mayonnaise, Tartare, Aioli, Cocktail, Tuna, and Indian—with a technical focus and a production philosophy that wasn’t so widespread at the time. The problem? Making a good emulsion is never easy, not even in the kitchen. In industry, it’s even more difficult.
We had invested in an excellent homogenizer, a sophisticated machine. But as with a racing car, the quality of the car isn’t enough: you need to understand every reaction, every parameter, every risk. Also because emulsions, when they decide not to cooperate, leave no room for negotiation. They “break,” become unstable, change consistency, and you have to start over.
At first, it felt like we were working in dim light. We could understand something, but the framework was missing. Then that American manual arrived. A technical volume, dry, without concessions. But in there, everything was finally explained: what happens to oil particles at high pressure, how viscosity varies with temperature, and why some emulsions “go crazy” over the smallest detail.
That reading literally transported us to another room. A room with the light on.
The context: what we were really looking for
To understand how crucial that text was, we need to look at what was happening behind the scenes.
For ten years, our company had already gained extensive experience in processing egg products.
We pasteurized yolks, egg whites, and mixtures using a patented system that guaranteed a shelf life of over 30 days with excellent organoleptic qualities. We served ice cream parlors, pastry shops, pasta factories, and canteens.
But sauces were a different world.
It wasn’t just a matter of combining natural ingredients: we needed to create stability, safety, texture, and flavor. And then there were two important constraints:
Organic certification, already complex in the 1990s.
Gluten-free certification, which was rare at the time, much rarer than it is today.
The challenge was this: imagining two very fine sieves: organic and gluten-free. Passing a raw material through the first was no easy feat; passing it through the second was almost a stroke of luck. What remained, in the end, was a minimal amount of compatible ingredients. And with that minimal amount, we had to be able to create good, stable, and repeatable products.
That’s why every piece of technical information became crucial. Not a curiosity: a brick.
- Why looking outside the company isn’t weakness
When an entrepreneur looks beyond the confines of his own factory, he doesn’t do it to imitate.
He does it to understand.
There are times when internal experience isn’t enough. You don’t have enough cases, you haven’t seen enough variables, or you’re missing precisely that knowledge that can change the course of the work.
In those years, for example, it was a bag-in-box supplier who alerted us to the American publication.
At other times, it was trade fairs that gave us decisive insights.
Or, again, it was external technicians capable of deciphering machine behaviors that eluded us.
Looking outside helps reduce the margin for error. And it’s one of the unwritten rules of the trade: those who produce must learn from those who know more or have seen more. Without misplaced pride.
Why Americans “Tell the Technical Truth”
The phrase seems provocative, but it points to a specific communication trait.
When addressing a technical topic, many American authors tend to:
describe what actually happens in a process;
avoid vague language;
show concrete examples, even failures;
present extreme cases, not just perfect ones;
guide the reader through physical reactions, not through “common sense.”
This way of explaining is useful because:
it reduces the margin for interpretation;
it allows for the avoidance of unnecessary tests;
it shortens the learning curve;
it clarifies which errors are physiological and which are not.
In American technical culture, there is often the idea that if something can break, then it’s worth explaining why it breaks.
This gives rise to the perception of “telling the truth.”
Not because they are infallible.
Because they get straight to the point.
- How Entrepreneurs Act When Something Goes Wrong
Those who don’t work in a company imagine the entrepreneur as a visionary who thinks of new ideas.
In reality, much of their time is spent doing something else: reducing friction.
An unstable recipe.
A machine to adjust.
A raw material to replace.
A certification that complicates everything.
The process is this:
Observe. Before you even act, you look at the problem from every angle.
Test. You change one variable at a time, hoping the result speaks volumes.
Fail. It happens more often than you think.
Try again. Every test tells you something, even when it seems useless.
Understand. It doesn’t happen all at once: it’s an accumulation of micro-intuitions.
And here the theme of “truth” returns: clear technical information allows you to skip entire weeks of attempts.
The Ferrari Metaphor
When we began working with the new homogenizer, it was clear that the machine was excellent.
But as with a Formula 1 car, what makes the difference is the ability to drive it, to interpret it.
Michael Schumacher had a great car.
But he didn’t win thanks to that alone.
He won because he was able to understand every vibration, every limit, every sudden change.
Now, producing emulsions requires the same kind of sensitivity:
understanding what happens when the pressure rises, when an ingredient reacts, when the system loses balance.
It’s a technical guide, not an intuitive one.
The American manual didn’t give us the “magic formula.”
It gave us the map.
- The hidden difficulties that many don’t talk about
When a product reaches the market, you rarely see the effort behind the packaging.
But every business has its own chapter of trials, revisions, and obstacles:
the search for truly organic and gluten-free raw materials, very rare in the late 1990s;
the regulatory constraints, more restrictive than today;
the stability of emulsions;
the need to define repeatable processes;
the challenge of making everything safe and consistent.
Reporting these difficulties doesn’t detract from the product’s value.
It increases it.
Because it shows how complex it is to translate an idea into something that actually works.
- What does this “American way” of explaining ultimately teach us?
Three main lessons:
- Precision is an investment
Clearly explaining a process allows the reader to avoid future errors.
It saves time, therefore value.
- Transparency is not weakness
Saying that an emulsion can break is not a flaw.
It’s a sign of technical solidity.
It means: we know what can happen and we know how to deal with it.
- Technical disclosure builds trust
Those curious to understand how things are created appreciate it when companies share the reality of their processes.
There’s no need to show everything: just tell what really matters.
Conclusion: The truth that helps build
Sometimes the only difference between a confusing process and a clear process lies in a well-explained page.
It can come from an Italian technician, a German engineer, or, as in our case, an American book that wasn’t afraid to tell you: “If you get this pressure wrong, the emulsion breaks. Period.”
That technical candor is an ally.
It enlightens.
It accelerates.
It allows an entrepreneur to take that extra step, the one that transforms a machine into a product and a product into a concrete story.
And perhaps it’s worth remembering: innovation often arises this way.
From someone who tells you the truth in the simplest possible way.
