Thinking about software delivery cadences, team styles, and what frameworks work best for teams is one of the many, many, many parts of being a Product Manager.
“How much process do you need? As much as you need to get the job done — but only as much.”
— David Allen, Getting Things Done
In large organizations, process often serves as connective tissue. When you have dozens of teams shipping across product lines or a portfolio, cadence becomes a form of language. Weekly sprints, quarterly planning, or six-week program increments give everyone a shared sense of rhythm. The marketing team knows when a feature might land, executives can see what’s in flight, and delivery teams can make tradeoffs without blocking other teams.
But process alone doesn’t build trust or velocity. The best teams I’ve worked with have enough rhythm to create predictability and shared accountability, but they leave plenty of room for autonomy and experimentation. They understand the “handshake” between product and engineering: business leaders define why and what we’re solving, and technical product teams own the how, the architecture, scalability, and delivery details that make it real.
But it’s never quite as simple as that of course.
Over time, I’ve learned that transformation isn’t about installing a new framework, it’s about cultivating clarity and confidence across disciplines. A great cadence helps product owners, engineers, designers, and execs move in sync.
If you’re thinking about how your team works, or why your current framework feels off, and need some inspiration, try these books.

The Phoenix Project: a novel that captures how invisible work, broken communication, and misaligned incentives sink delivery. People seem to love or hate this book, but I find myself still turning to it for motivation from time to time.

Ask Your Developer: a reminder that agile teams thrive when engineers are trusted to shape solutions, not just implement them. Jeff Lawson captures what real collaboration between product and engineering looks like—it’s probably my most recommended book to work friends.

Shape Up: an antidote to endless sprints, with a model for giving teams clarity and boundaries without micromanagement. I have followed the 37 Signals team for twenty years and still find Jason and David’s constantly evolving approach to delivering software very important to my own thinking.












