June 5, 2026 | The Product Manager’s Journal
The Take
One decision sat open on my board for six weeks while everything around it moved. I kept calling it research. It was avoidance.
I fell straight into a trap. The critical decision for our entire launch was choosing the right hardware partner to build our smart tag, but I just couldn’t finalize it. Every week, I had a valid reason for the delay. I needed one more specification, one more quote, or I was busy reviewing one more comparison.
I felt productive about it. That is the dangerous part. Busy is not the same as deciding, and the longer I researched, the more it looked like work and the less it actually was.
When I finally examined the board honestly, the truth became clear. I wasn’t lacking information; I had everything I needed a month earlier. Instead, I was seeking insurance against being wrong so that if the decision went poorly, I could blame a missing input rather than take responsibility myself.
Here is the test I apply to any decision that has been open for more than two weeks: Identify the one key piece of information that, if it became available tomorrow, would make your choice clear. If you can name that piece of information, go after it—that’s a real gap. If you can’t identify it, you’re not researching; you’re stalling. The solution is to set a deadline, not to gather more data.
I scheduled a dedicated time on my calendar and wrote down three honest options for my decision. It only took one sitting to make my choice. However, what I didn’t anticipate was the ripple effect that followed. The labeling, blend preparation, and building processes had all been waiting for that one decision. The delay didn’t just cost me a week; it cost me a week of my time spent waiting. This hidden cost is precisely why we often allow such stalls to continue.
Spice Route Signal
Food is exempt from the EU’s Digital Product Passport, which means on-pack provenance in our category stays a choice, not a mandate. That is better news than it sounds.
The “regulation will force traceability tags onto every product” story has been a quiet tailwind in the smart-packaging pitch for two years. This month, the picture sharpened, and it cut against that story. The EU Digital Product Passport phases in by category through 2026 to 2030, but food, pharmaceuticals, and living organisms are carved out. On the US side, FSMA 204 enforcement has just been pushed to July 2028. So neither regulatory clock actually requires a tap-to-trace tag on a spice jar.
Most founders would read that as bad news. I read it the other way. No mandate means nobody in our category is being forced to catch up to on-pack provenance. The NFC freshness experience we are building remains a genuine point of difference rather than a compliance checkbox that everyone is about to copy by the same deadline.
The catch is the one I wrote about last month. Validation is the front edge of commoditization. The hardware is getting cheap and common fast. So the moat cannot be the tag. It has to be what happens after the tap, the farmer, the batch data, the story that a competitor cannot replicate because they do not have the relationships. We get to build that on our own timeline now, not a regulator’s. That is an advantage. It is also a clock.
[Source: EU ESPR Digital Product Passport guidance and the FSMA 204 compliance-date extension, June 2026.]
From the Trenches
A heads-down week, and a good one. Three things that had been stuck all moved because of the decision I wrote about up top.
The label proof came back correct. We had asked the printer for a second hit of white under the color so the labels hold up on a dark jar, and the revised proof confirmed it is there. I approved it. The only thing left on the packaging is cutting the purchase order, which is a money commitment I want to make with my eyes open, so I am giving it its own block rather than rushing it at the end of a tired afternoon.
The co-packer relationship took its first real step. We signed a mutual NDA, they countersigned and returned it, and the door is now open to send them the actual specs for two blends, Persian Sunrise and Caribbean Sunset, to scope a production run. First time this part of the business has moved from “introductions” to “send us the details.”
And the NFC partner is ready to build. After the hardware decision finally closed, they came back ready to start on the mobile site and the backend that the tap experience runs on. The thing that gated everything for six weeks is now the thing pulling the next pieces forward.
None of this is glamorous. It is sequential, unglamorous, and necessary work. The kind that does not make a good story but makes a good launch.
From the Rack
Saffron. The most expensive spice in the world, and proof that the input that changes everything is almost never the biggest one.
Saffron is the crown of Persian Sunrise, our Persian-inspired blend. It is the most costly spice by weight on earth, harvested by hand from crocus flowers, roughly 150 of them for a single gram. And yet you use almost none of it. A pinch, a dozen threads steeped in warm water, and an entire pot of rice turns gold and takes on a honeyed, almost floral depth that no amount of any cheaper spice can fake. Add too much, and you ruin it. The dish does not want volume. It wants precision.
Here is the PM lesson hiding in those threads. We are trained to believe impact scales with effort, that the bigger the input, the bigger the result. Saffron says otherwise. The thing that changed my entire week was not a pile of work. It was one small, precise decision I had been avoiding. A dozen threads, not a sack of it.
So when you are staring at a long list, resist the urge to measure impact by size. Find the saffron. The single decision, the one conversation, the small precise move that turns the whole dish gold. Then do not drown it in everything else.
On My Desk
Duke spent two decades as a professional poker player before she started writing about decision science, and this is the most practical thing I have read on the actual mechanics of choosing. Not the philosophy of it. The mechanics.
The idea that landed for me this week is what she calls “resulting,” judging a decision by how it turned out instead of by whether it was sound when you made it. My six-week stall was the mirror image of that. I was so afraid of a bad outcome that I refused to make a sound decision at all. Duke gives you language for catching both moves, and once you can name them, you stop doing them as often.
If you make calls under uncertainty for a living, which is the whole job, this earns its shelf space. Start with the chapters on the decision tree and on pre-deciding your quit conditions.
That’s the Rack
Thanks for reading Issue #10. 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 oldest decision sitting open on your board, and what’s waiting behind it? 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