It's early in the year and many teams are still debating what they should build next. Roadmaps are still shifting. Leadership conversations are still happening. Teams are waiting for clarity.
But here's the uncomfortable reality: if your organization isn't already thinking about Q3, you're already behind.
The Planning Delay Problem
High-performing product organizations don't treat planning as something that happens at the beginning of the year. They treat it as a continuous discipline.
Because when planning only starts in January, something predictable happens: two months disappear.
By the time development actually begins on Q1 priorities, it's March. By the time you've learned enough from Q1 to inform Q2, it's June. And by the time you're thinking seriously about Q3, the window to do the discovery work that would make Q3 meaningful has already closed.
This is how organizations end up shipping things that were relevant six months ago.
The Three-Quarter Horizon
The teams that consistently ship impactful work operate on a three-quarter horizon.
They're executing Q1 while refining Q2 and discovering Q3. Not in a waterfall sense: not with detailed specs locked months in advance: but with a clear enough understanding of the problem space that when Q3 arrives, the team isn't starting from zero.
This requires a different kind of discipline than most teams practice. It requires product managers who are willing to do discovery work before they have budget approval. It requires leadership that trusts the team to explore problems without immediately demanding solutions. And it requires a shared understanding that planning is not the same as commitment.
What Q3 Discovery Looks Like Right Now
If you're doing this right, your Q3 discovery work right now looks like customer conversations that aren't tied to any specific feature. It looks like competitive analysis that isn't driven by a specific threat. It looks like data exploration that isn't connected to a current sprint.
It looks, in other words, like work that doesn't have an obvious deliverable: which is exactly why most teams don't do it.
The teams that do it are the ones that consistently ship things that matter, because they've had months to understand the problem before they've committed to a solution.
The Practical Ask
I'm not suggesting you need a fully baked Q3 roadmap in January. I'm suggesting you need to know, by the end of Q1, what problems you're trying to solve in Q3: even if you don't yet know how you're going to solve them.
That's a much lower bar. And it's the difference between shipping work that's relevant and shipping work that's late.
Start the Q3 conversation now. You'll thank yourself in June.
What this looked like in my work
The car buying and Learning Center work at USAA was the output of exactly this kind of forward planning. The Tableau dashboard that connected auto loan, insurance, and car buying data was built in Q4 to inform Q1 roadmap decisions. The $375K revenue opportunity it identified wasn't visible in any single product team's metrics. It only appeared when you connected the three data streams and asked what the member journey looked like across all three.
Read the full case study: Learning Center and Car Buying: USAA
