June 19, 2026 | The Product Manager’s Journal
The Take
The key takeaway: the feature I start every demo with is something a competitor could release by next quarter. That’s not my advantage. I had it reversed.
A market brief caught my attention this week. Nearly half of consumer brands now include both a QR code and an NFC chip on the same package. The simple tap that makes my smart spice jar feel innovative, showing the farmer and grind date when I touch my phone to the lid, has now become commonplace. For a brief moment, I felt a pang of panic, realizing that your clever trick had quietly become a standard feature.
I forgot: the demo feature rarely protects you.
We focus on the demo-worthy part because that’s where the applause happens. It photographs well, fits into a launch video, and communicates to a customer in ten seconds just as quickly as to a competitor’s team. Anything that can be showcased that fast typically has a limited lifespan. I had been treating the most easily duplicable aspect of my product as if it were the most protected.
So I started running everything through one question. How long would it take a competitor with money and motivation to ship the same thing? Call it the Copy Clock. Short clocks are table stakes: the tap, the AI chat box bolted onto a recipe app, anything a customer grasps instantly. Long clocks are moats: the supply you control, the preference data that compounds every time someone uses the product, the trust you earned one honest interaction at a time. None of those demos worked well. All of them take years to reproduce, if a competitor can start at all.
This is the painful part, and it’s why the Product Onion keeps coming back to me. Competitors imitate your outward features since they see them, but they miss your underlying strategy and the trust you’ve built, which are harder to observe and will only be compromised if they succeed. When I spend my limited time refining surface details, I’m strengthening the layer that might have been peeled away regardless.
The reminder I’m giving myself this week: be suspicious of your favorite feature. The applause it gets is real, and so is the speed at which someone else earns the same applause. Spend the good hours on the part you can’t fit in a ten-second demo.
Spice Route Signal
The spice that everyone warned me to lock last week just softened, while the one nobody tracked is climbing. This isn’t just a turmeric story; it’s about the choices we make in our actions.
Two weeks ago, the read on my desk was “lock turmeric now.” It’s the tight crop; the futures were running ₹16,500 to ₹18,000, and turmeric anchors two of our blends, Persian Sunrise and Caribbean Sunset. This week, the spot market indicated a different trend. Karnataka turmeric traded near ₹11,600 per quintal on June 12, well below those near-month futures, as the peak arrival season finished and supply caught up. Meanwhile, cardamom, which nobody flagged, pushed to a ₹ 3,333-per-kilo auction high on June 13. Black pepper sat flat at around ₹625.
We act when costs spike, not when they drop. The real opportunity hides in calm moments, not alarms.
We tend to respond to crises rather than opportunities. Cost considerations often shout loudly, while opportunities tend to be subtle. Staff are more likely to succeed by focusing on consistent wins rather than only urgent issues.
I’m not committing to a turmeric buy this week. We don’t have a sourcing owner, and I won’t pretend we do. But I noticed the window this time, instead of waiting for a spike. That’s the move: watch what goes quiet, not just what gets loud.
[Source: KisanDeals Karnataka turmeric mandi prices and Spices Board of India small cardamom auction data, via the June 15 market brief.]
From the Trenches
A heads-down week, and the kind that finally moved the one thing that had been stuck for a month.
The bottleneck for the entire quarter has been manufacturing. Who actually blends and fills the jars? The work that gates everything downstream, and the work I’d been quietly avoiding. This week, I sent the blend specs to two blenders on the same day. A third already had them. The specs were never the hard part; they’d been ready for a while. The hard part was my own signature, the commit, the small fear of putting a real number and a real ask in front of a real partner. That sat on me longer than I’d like to admit.
The responses were a lesson by themselves. One blender’s owner wrote back within the hour, not with a quote but with an offer to partner, which told me the relationship mattered to him more than the transaction. Another came back wanting us to source the raw spices ourselves and have them only blend, a model that doesn’t fit what we’re building, so that one needs a clarifying conversation rather than a contract. Three blenders now hold our specs. None of them has returned a written quote yet. I want to be honest: ‘specs sent’ seems like progress, but ‘quote in hand’ is actually the finish line. The gap between them is where founders often deceive themselves. Being closer doesn’t mean you’re finished.
In parallel, I met with the team that may build our web experience. It was a discovery step, not a decision. They’ll send an expanded scope early next week, and the real signal from the call was the risk they named: connecting the jar’s tap to the storefront is the hard technical piece, the part still carrying the most uncertainty. I have a lingering doubt about whether they can deliver the full tap-to-story experience, so I’m keeping the in-house build alive as a backstop rather than betting the launch on a single partner.
From the Rack
Sansho doesn’t add heat. It adds a bright, tingling hum on your lips that makes everything else on the plate taste more awake. You can’t describe it to someone. They have to feel it.
Sansho, the Japanese pepper at the heart of Kyoto Garden, our Japan-inspired blend, is a strange and wonderful spice. It isn’t hot the way chili is hot. A few specks over grilled fish or a bowl of noodles give you a citrus lift and then a soft, buzzing tingle on the lips, almost electric, like the spice is gently waking your mouth up. Japanese cooks have reached for it for centuries, not for heat or even for flavor exactly, but for what it does to everything around it. It makes a dish feel brighter without changing what the dish is.
Here’s the PM lesson hiding in that tingle. We rank inputs by their loudness. Heat, volume, the feature you can point at. Sansho is none of those, and it might be the most important thing in the bowl, because it changes how you taste the rest. The quiet input that reframes the whole experience rarely shows up on a feature list. It’s the load time that makes an app feel trustworthy, the one honest sentence on a label that makes a customer believe the other ten, the small moment of delight that recolors a product people thought they understood.
And you can’t demo it. That’s the connection to where my head has been all week. The tingle doesn’t survive a screenshot or a spec sheet. You have to put it in someone’s mouth. The most defensible parts of a product are often the exact parts you can’t hand someone in a slide. They have to taste it to get it.
On My Desk
Given the week I just had, watching my favorite feature go mainstream, this is the one I pulled back off the shelf. Thiel’s whole argument is a Copy Clock taken to its end. Competition, the kind where everyone ships the same feature on the same timeline, is a race to zero margin and zero distinctiveness. The companies that last are the ones doing something so different that nobody is racing them at all.
The line I keep chewing on is his test for a real idea: what important truth do very few people agree with you on? It’s the same question as “what can’t a competitor copy,” asked from the other side. A secret, in his framing, isn’t a trick. It’s something you understand about your market that the people with more money and more engineers haven’t bothered to learn. My version is the farmer who picks up the phone and the freshness story I can actually prove. None of it demos in ten seconds. All of it is the part a funded rival would have to start from zero to match.
It’s a short, opinionated book, and some of the bravado hasn’t aged evenly. Read it for the core anyway. If you’re staring at a roadmap trying to tell a feature from a moat, it gives you a sharper question to hold each one up against.
That’s the Rack
Thanks for reading Issue #12. I’m Dan Blizinski, founder of Trevean Spice and the person behind The Product Manager’s Journal, where I write about PM frameworks grounded in actually building things, not just theorizing about them.
New here? Grab the free Startup PM Toolkit. Five frameworks I actually use, not just talk about.
What’s the feature you open your demo with, and how long is its copy clock really? Hit reply, I read every one.
The PM’s Spice Rack is published weekly on The Product Manager’s Journal and on LinkedIn. Subscribe to get it in your inbox.
Leave a Reply