07/22/2026
The Case for Doing the Work in July and August
Most organizations have an unspoken rule about summer: wait until fall when everyone's back and focused before starting anything new.
It's an understandable instinct. It's also exactly backwards.
Here's the reality: summer offers conditions that are genuinely rare the rest of the year. Lighter meeting loads. Fewer high-stakes deadlines. Natural pauses in ongoing projects. Less organizational pressure slowing down decisions.
Those conditions don't last long — and most teams let them slip by without taking advantage.
The Q4 math is worth thinking about too. Meaningful software work typically takes six to twelve weeks from first conversation to real results. Starting in July or August means you see results in September or October — right when you need your systems running well. Starting in October means you're managing a live project through the most chaotic stretch of the year, or pushing it to January.
Summer isn't a gap in the calendar. It's the on-ramp to a strong Q4.
We wrote about this in detail this week — including what "doing the work" actually looks like in summer (it's not a massive overhaul), the competitive angle worth considering, and a few questions worth sitting with if you're trying to figure out whether now is the right time to move on something.
Link in the comments.
If this resonates — for yourself or someone you know — we're happy to have an informal conversation about what might be worth tackling this summer.
