April 9, 2026 | The Product Manager’s Journal
The Take
I was editing a sent email at 11:30 PM. That’s when I knew I had a problem.
Rushi had already sent a sourcing follow-up to a producer in Barmer. Someone we’d met in person, built rapport with, and already decided to work with. She wrote a perfectly good email. Professional, warm, on-brand.
And there I was, in bed, rewriting sentence structure on my phone. On an email that was already gone.
The next morning, Rushi said something that stopped me: “Dan, you realize you just edited a sent email, right?” Direct. No cushion. Completely right.
I’d been doing this for weeks without noticing. Because micromanagement never announces itself as a problem. It disguises itself as diligence. As high standards. As being the kind of founder who gives a damn.
Then it hit me, and it took longer than it should have: if you’ve read anything I’ve written about the Product Onion framework, you know the core idea is that great products are built from the inside out. Start with the core problem, build outward. Start from the outside with features, packaging, marketing, and the whole thing collapses.
I’d been preaching that for two years on this blog. And then I went and made the exact same mistake with how I was leading.
Micromanagement is building from the outside in, applied to people. You’re obsessing over the outermost layer of the email, the slide deck, the exact wording of a supplier message, instead of working from the core. And the core, when it comes to leading a team, isn’t the deliverable. It’s alignment. It’s whether the person understands why this decision matters, not whether they formatted it the way you would have.
When I was rewriting Rushi’s emails, I wasn’t protecting quality. I was skipping every inner layer of the shared context, the trust we’d built, the fact that she’d sat across from these farmers, and I hadn’t, and going straight to surface-level control.
The cost isn’t just your time. It’s thinking. The people around you stop bringing ideas. They stop flagging problems early. They start waiting to be told what to do, because that’s the system you built, even if you never meant to.
For founders specifically, there’s a scaling problem that’s almost mathematical. Every decision that has to run through you is a decision that’s slowed, distorted, or dropped. At a startup, where the only real advantage you have over bigger competitors is speed, that’s a death sentence in slow motion.
What changed for me: now, when Rushi and I disagree on a sourcing decision, I don’t override her. I go back to the core. What are we actually trying to prove with this blend? What does this supplier relationship tell the customer when they tap the NFC tag? If we’re aligned on that, most tactical decisions resolve themselves. She doesn’t need my approval. She needs my context.
If you’re a founder reading this at 11:30 PM, editing something that’s already been sent, close the laptop. The real work isn’t in the email. It’s in the alignment you haven’t built yet.
→ Read the full post on The Product Manager’s Journal
From the Trenches
No dramatic travel stories this week. This is a heads-down stretch.
The blog crossed 80 published posts, which doesn’t mean much on its own except that the library is getting deep enough to actually function like a library. Someone searching for “product onion framework” or “startup design freeze” is starting to find us. Not in huge numbers yet, but organic search traffic picked up noticeably in the last two weeks, the first real signs that the SEO work we started in March is compounding.
I’ve been spending most of my time on the unsexy stuff. Optimizing meta descriptions. Building internal links across 80+ posts so that someone who reads one piece gets pulled into three more. Adding TL;DR blocks and FAQ sections to make the content more useful for AI search engines, not just Google. The theory is that if ChatGPT, Perplexity, or Claude starts citing your framework when someone asks a PM question, that’s a distribution channel most people haven’t considered yet.
The subscriber count is growing slowly. I’m not going to pretend the numbers are exciting. But the welcome email sequence is doing its job, open rates are solid, and I’m getting actual replies, which matters more than volume at this stage. One PM wrote back to tell me that the Product Onion helped her reframe a feature-prioritization meeting. That’s the signal I’m building toward.
Also quietly working on the Tuscan Dusk blend concept I brought back from Italy. Rushi’s been experimenting with a saffron-fennel base that’s unlike anything else in our lineup. More on that when there’s something to taste, not just talk about.
Spice Route Signal
The era of “trust us, it’s authentic” is officially ending.
Two things happened in the last few weeks that should be on every food product person’s radar.
First, at the Global Food Safety Initiative conference in March, industry leaders made the case that DNA verification is becoming critical to protecting food value chains. Not just for compliance. As a strategic tool. The argument: fraud and mislabeling are rising fast enough to undermine the very claims companies are investing millions to make. If you’re marketing single-origin saffron but can’t prove it at the molecular level, someone eventually will, and it won’t be you controlling the narrative.
Second, the FDA’s food traceability rule continues to take shape ahead of its July 2028 compliance deadline. New guidance, new training programs rolling out, and a growing realization across the industry that the infrastructure most companies have in place isn’t close to ready. The Food Safety Summit just added a dedicated traceability course starting in May.
Here’s what connects these two stories. One blog I came across put it perfectly: “The era of storytelling transparency is giving way to data-validated truth.” That’s the shift. It’s not enough to tell a good sourcing story anymore. You need to prove it. Regulators are requiring evidence. Retailers are expecting accuracy. And consumers, the ones who’ve started reading the back of spice jars, the ones I keep meeting want clarity they can verify, not just marketing they can feel good about.
This is exactly the bet Trevean is built on. The NFC tags, the batch testing, and the farmer relationships you can actually trace. We’re not ahead of the curve because we’re bigger or faster. We’re ahead because we started with the assumption that everything we ship should be independently verifiable. The industry is catching up to that assumption. That’s good news for everyone who’s been doing the work.
[Sources: GFSI 2026 insights via New Food Magazine; FDA traceability rule updates via Covington & Burling; “The Transparency Tipping Point” via Cegeka]
From the Rack
I am adding a section to this newsletter called “From the Rack”. highlighting individual spices that relate to the product manager’s journey.
Scotch bonnet is not “really spicy jalapeño.” It’s fruity, almost mango-like, and also very hot. Caribbean Sunset uses it for that fruit, not just the fire. This is the same mistake PMs make when they lump all customer complaints into one bucket. “I don’t like spicy” isn’t one objection. It’s five different objections using the same words. There are five distinct types of heat in cooking, and they hit your mouth in completely different places. If you can’t segment the signal, you can’t solve the problem.
On My Desk
“Turn the Ship Around!” by L. David Marquet.
If you read The Take this week and felt personally called out, this is your next read. Marquet was a Navy submarine commander who inherited the worst-performing crew in the fleet and turned them into the best not by giving better orders, but by giving control away. His core move: replacing “permission to” with “I intend to.” Instead of asking the captain what to do, the crew started telling him what they intended to do and why. The captain’s job became providing context and alignment, not approving every decision.
Sound familiar? It’s the exact shift I described with Rushi. Stop being the bottleneck. Start being the context.
The book is about 230 pages and reads fast. The submarine stories are genuinely gripping, which helps. But the leadership framework underneath them, what Marquet calls “intent-based leadership,” is the most practical thing I’ve read on how to stop micromanaging without just hoping things work out. Develop first. Then trust. Then get out of the way.
That’s the Rack
Thanks for reading Issue #3. I’m Dan Blizinski, founder of Trevean Spice and the person behind The Product Manager’s Journal, where I write about PM frameworks that come from 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.
Have you caught yourself in the control trap? What finally made you let go? 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.