In partnership with
👋 Hey Friends!
You inherit a process that isn't working. You get handed a new one instead. Six weeks later, the same complaints show up, just wearing a different outfit.
Quick context if you haven't lived inside these yet: a sprint is a fixed chunk of time, usually one to four weeks, where a team commits to a set scope and works toward it. A 6-week cycle is the same idea stretched longer, with a cooldown built in between. Fine. Now forget the definitions, because that's not actually the part that matters.
Speak naturally. Send without fixing.
Wispr Flow turns your voice into clean, professional text you can send the moment you stop talking. Not rough transcription you have to clean up. Actual polished text — ready for email, Slack, or any app.
Speak the way you think. Go on tangents. Change your mind mid-sentence. Flow strips the filler, fixes the grammar, and gives you text that reads like you spent five minutes writing it.
89% of messages sent with zero edits. Millions of professionals use Flow daily, including teams at OpenAI, Vercel, and Clay. Works on Mac, Windows, and iPhone.
I've hit this exact wall at both companies I've worked at, in two completely different shapes. It took me an uncomfortably long time to see they were the same problem.
At my first company, Crowd Content, the issue wasn't a missing framework. We had sprints, we had cycles, all the pieces existed on paper. The issue was that leadership and stakeholders could jump in with new priorities at basically any point, mid cycle, no warning, and suddenly whatever we'd committed to wasn't the plan anymore. Nothing ever reached done, because nothing was ever protected long enough to get there.
It took me a while to see what was actually happening underneath that. It wasn't that leadership didn't respect the process. It's that they couldn't see what was already in motion. If you can't see that something's already most of the way finished, reprioritizing it doesn't feel like a disruption to you. It just feels like a decision.
At HubSpot, the failure mode looks completely different but comes from the same root. We plan in silos, each team heads down in their own slice, and dependencies between teams stay invisible until they surface as a blocker mid-sprint. The 6-week cycles give us a rhythm to prioritize against, and that genuinely helps. But the dependency problem hasn't gone away. Structure didn't erase the invisibility. It just gave the invisibility a schedule.
Leadership steamrolling a cycle at one company. Blindsided dependencies at the other. Same root, two outfits.
💡 Insight: A framework doesn't make work visible on its own. It just gives invisible work a shape and a name. If nobody outside your team can see what's committed or what's in flight, someone will eventually act as if none of it exists, because as far as they can see, it doesn't.
The status update I'd build regardless of what system you've inherited
Three lines. Outside of any tool, dashboard, or ceremony you're required to use.
What's committed right now. One sentence. This is the line that stops someone from reprioritizing you mid-cycle as if nothing's in motion, because now they can see that it is.
What depends on someone outside your team. Name it before it becomes a blocker, not after you're already stuck on it.
What changed since last time. If nothing changed, say that. Don't pad it.
If you can't fill in these three honestly, you don't have a status update yet. You have a hope.
🎯 Try this: Write these three lines for your current highest-priority piece of work. Send it to whoever's most likely to either override your priorities mid-cycle or trip over a dependency you haven't flagged yet. This week, not next sprint.
The framework was never protecting you from surprises. The visibility was.
P.S. If you're navigating either of these right now — stakeholders overriding your priorities, or untangling dependencies nobody flagged early enough — that's not a sign you're doing it wrong. It's just the actual job. Here's the specific way I can help: book a 30-minute Visibility Audit. Bring your current status update (or your "hope"), and I'll help you turn it into the three lines that make your committed work impossible to steamroll and your dependencies impossible to hide.
Go from AI overwhelmed to AI savvy professional
AI will eliminate 300 million jobs in the next 5 years.
Yours doesn't have to be one of them.
Here's how to future-proof your career:
Join the Superhuman AI newsletter - read by 1M+ professionals
Learn AI skills in 3 mins a day
Become the AI expert on your team
