Aug 26, 2026 · 11 min · 10 segments
Send us Fan Mail Two ideas, one thread: this episode brings together experimentation and identity — because you can't build a genuine signature…
I'd put money on it that you've got at least one, a product idea, a technique, a flavor combination you've been turning over for weeks or months but haven't actually made.
And if I asked you why not, the honest answer is usually some version of, "What if it doesn't work?" Or, "What if I waste the ingredients?" Or, "What if nobody buys it?" That fear is completely reasonable, but it's also based on a false assumption that trying something new means committing to it fully right away with no way back.
Most bakers skip straight to launching a new idea, putting it on the menu, announcing it on social media, without ever actually testing whether it works first.
Testing small might mean making one version for yourself or your family before offering it to customers.
It might mean offering it to a handful of regulars at a discount in exchange for honest feedback.
It might mean a tiny trial batch at a market stall just to see how people react before it's a permanent fixture.
The point is, you're gathering real information cheaply before you've bet your reputation or your ingredients budget on it.
Let's talk about the practical side of testing without wasting money or time, because I know that's the bit that puts a lot of people off.
Scale it right down, a quarter of the recipe, a single portion, whatever gets you a genuine sample without excess.
If you're worried about a new flavor combination, you don't need to build an entire elaborate cake around it.
If it's a decorating technique you're unsure of, practice it on an offcut or a spare board before it goes anywhere near a real order.
And keep a simple record as you go, what worked, what didn't, what you'd change.
But without that, you end up relearning the same lessons every time instead of building on them.
I'd put money on it that you've got at least one, a product idea, a technique, a flavor combination you've been turning over for weeks or months but haven't actually made.
And if I asked you why not, the honest answer is usually some version of, "What if it doesn't work?" Or, "What if I waste the ingredients?" Or, "What if nobody buys it?" That fear is completely reasonable, but it's also based on a false assumption that trying something new means committing to it fully right away with no way back.
Most bakers skip straight to launching a new idea, putting it on the menu, announcing it on social media, without ever actually testing whether it works first.
Testing small might mean making one version for yourself or your family before offering it to customers.
It might mean offering it to a handful of regulars at a discount in exchange for honest feedback.
It might mean a tiny trial batch at a market stall just to see how people react before it's a permanent fixture.
The point is, you're gathering real information cheaply before you've bet your reputation or your ingredients budget on it.
Let's talk about the practical side of testing without wasting money or time, because I know that's the bit that puts a lot of people off.
Scale it right down, a quarter of the recipe, a single portion, whatever gets you a genuine sample without excess.
If you're worried about a new flavor combination, you don't need to build an entire elaborate cake around it.
If it's a decorating technique you're unsure of, practice it on an offcut or a spare board before it goes anywhere near a real order.
And keep a simple record as you go, what worked, what didn't, what you'd change.
But without that, you end up relearning the same lessons every time instead of building on them.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.