July 3, 2026 | The Product Manager’s Journal
I am posting this a day early. Happy 250th anniversary, America.
The Take
We don’t stop the business this week. We stop adding to it, and make reflection and planning the whole company’s priority.
It’s the last week of my quarter, and the one week when new output isn’t the goal. I run thirteen-week quarters: twelve weeks to execute, then a thirteenth week to step back and plan the next cycle with the team. The business keeps running. We still answer every customer, keep every commitment to our partners and vendors, and handle whatever the day brings. What changes is the priority: this week, reflection and planning sit above starting anything new. Every instinct says to skip that and keep the momentum going, and I’ve learned the planning week is the one that decides whether the momentum was pointed anywhere in the first place.
The reason I compress the calendar is the idea behind this week’s book pick. Treat twelve weeks like a year. Give a plan a full year, and you spend the first few months acting like the deadline isn’t real. Shrink it to twelve weeks, and every week has to carry weight, because there aren’t enough of them to waste. So the short list of priorities we set for the next cycle, our Rocks in EOS terms, isn’t a wish list. It’s the whole year’s bet, made in a single planning session.
Which is why how we set them matters more than how many we set. This time, every Rock has to pass one test before it makes the list: can we put a number on done? Not “keep publishing the newsletter,” but a subscriber count to hit. Not “make progress on the build,” but one blend working end-to-end by a date. A priority you can only maintain isn’t a Rock. It’s a habit with a deadline.
I’m strict about that because the reflection this week surfaced something I didn’t enjoy finding. One of last quarter’s goals ran ten weeks on a cadence I never missed, and I’d never once read the number underneath it. I’d been treating my own consistency as progress. Maintaining a goal and measuring one are different jobs, and the first quietly impersonates the second. A quarterly Rock is where that mix-up gets expensive, because you commit the team to it for a full cycle before anyone checks whether it can be measured at all.
So if you set quarterly priorities with a team, run this in your next planning session. For each one, name the number that proves it’s done, name the single person who owns it, and cut the list until everything left is a real bet instead of a maintained activity. Three Rocks you can measure will beat six you can only tend.
You don’t need EOS or a thirteen-week quarter for this. You need one honest planning stretch before the next cycle starts, with the day-to-day still running around it, where the only question on the table is what counts as a win. The week you put planning first is the week you decide the next twelve weeks are worth building at all.
Spice Route Signal
The tag we’re about to put under every lid became a commodity this month, and a bigger clock started ticking about two weeks out.
Two things happened in the last few weeks that should get the attention of anyone whose plan was “put a smart chip on it.” On June 23, a semiconductor maker launched a flexible NFC chip that folds authentication and tamper detection into a single tap. No separate reader. One tap tells a shopper both that a product is real and that it hasn’t been opened, and it’s aimed at wine, spirits, pharma, wellness, and even baby food. So “is this genuine and unopened” is now a feature you buy off the shelf, not a capability you spend a year building.
The second thing is a date. Around July 19, the EU’s central Digital Product Passport registry goes live, built on a shared data standard so a scan means the same thing across brands and borders. Scannable provenance is moving from a nice-to-have that premium brands brag about to a baseline that regulation expects.
Here’s the read. When a capability turns into something you can buy and something you have to comply with in the same month, it stops being a moat. The edge moves up the stack. It moves to the experience the tap sets off, the farmer’s name, the batch, the reason it tastes the way it does, and to owning that data in a portable, standard form so it travels wherever a shopper meets your product. The chip was never the plan.
Our own tags go into production this week (more on that below). I’m not worried that the tag is becoming ordinary. I’m relieved, because it forces the work that can’t be bought off a shelf: what happens after you know it’s real.
[Source: Pragmatic Semiconductor NFC Protect PR1311 launch, June 23, 2026, via GlobeNewswire and Packaging Insights; EU Digital Product Passport central registry timeline via GMInsights.]
From the Trenches
The last week of the quarter was mostly things arriving, things leaving, and one small tool quietly falling over.
Fitting for a reflection week, not much of this photographs well. It was a week of pieces moving into place rather than anything you’d call a launch.
The physical bottleneck finally cleared. The second of our two sample jars shipped, so both are now in transit from overseas. Once they land, the next step is customizing and pricing the lid, the small decision that has to be made before the labels print in the back half of July. Sequential, unglamorous, necessary.
The first production run of the tags that sit under each lid went into manufacturing this week, due to ship later in July. Same honest catch I flagged before: the tags will physically exist before the tap-to-story experience they’re meant to trigger does. Building that experience is the first real job of the next quarter, and after this week’s signal, it’s clearly what’s worth building, not the tag itself.
The least glamorous lesson came from the smallest failure. Our email tool dropped its connection for two nights, and that alone stalled three vendor messages that were written and ready to go. No strategy problem, no hard decision. Just a boring reconnect standing between finished work and work that actually ships. A useful reminder that the gap between “done” and “delivered” is often something dull you forgot to check.
A week of closing the quarter, not opening the next one. After twelve weeks of building, that feels like the right way to end it.
From the Rack
Allspice is one berry that almost everyone assumes is a blend, and that mistake is the whole lesson.
Allspice is the warm heart of Caribbean Sunset, our Jamaica-sourced blend. Crack one dried berry, and it reads like clove, cinnamon, and nutmeg at once, which is exactly why early traders called it allspice. It isn’t a mix of those three. It’s a single berry from a single tree, most of it grown in the Blue Mountains of Jamaica, that happens to carry all of them in one small, fragrant package. Jamaica grows close to 80% of the world’s crops.
Here’s the PM lesson sitting in that berry. People taste three things and reach for three jars. The berry does the whole job alone.
Most roadmaps bloat the same way. You want the product to feel warm, layered, and complete, so you add three features to get there, when one honest thing, chosen well, would have delivered the whole impression. Taste, in a kitchen or a product, is mostly the discipline to find the single ingredient that does the work of three and then stop adding.
Before you reach for three, check whether you’re already holding the allspice.
On My Desk
The 12 Week Year by Brian Moran and Michael Lennington.
Given a week spent defending my thirteen-week quarter, this is the book underneath the habit. Moran’s argument is simple and a little uncomfortable: an annual plan hands you twelve months to act like the deadline isn’t real, so you stop planning in years and start running in twelve-week blocks, where every week carries weight because there aren’t enough of them to waste.
Where I part ways with him is in that thirteenth week. He optimizes for execution density. I’ve found I need one deliberate week where the priority shifts from new output to reflection and planning. The business keeps running that week, our customers, partners, and vendors still get what they need, but the main job becomes measuring what the last twelve weeks actually did and aiming for the next twelve. The book sharpened how I run the twelve. The reflection week is the edit I made to it.
It’s short and practical, closer to a system than a memoir. If you’ve ever reached the end of a quarter unsure whether you moved or just stayed busy, it gives you a structure that makes that question harder to dodge.
That’s the Rack
Thanks for reading Issue #14. 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 a goal you’ve been maintaining every week but haven’t actually measured? Hit reply, I read every one.
Leave a Reply