Blog

When someone on your team raises an issue, what they're describing is almost never the actual problem. It's a symptom. The bug report, the missed deadline, the customer complaint are all surface-level indicators of something deeper. The Five Whys root cause analysis technique gives you a structured framework to move past these symptoms and find the…

Every product decision involves negotiation. You negotiate with engineering about timelines, with stakeholders about priorities, with customers about requirements, and with your team about trade-offs. Most product leaders approach these conversations as battles to win. That's why they fail. The Harvard Negotiation Method offers a better approach. "Getting to Yes" by Roger Fisher and William Ury…

Repeating the same retrospective format Sprint after Sprint drains engagement and reduces the value of your team meetings. After facilitating hundreds of agile retrospectives, I've identified how format variety surfaces different insights, keeps teams engaged, and prevents retrospectives from becoming checkbox exercises. These 20 retrospective techniques follow the five-phase process that makes retrospectives effective: set the…

Retrospectives produce minimal results when teams approach them as checkbox meetings instead of structured improvement sessions. After facilitating hundreds of retrospectives across product and engineering teams, the distinction between productive retrospectives and time-wasters comes down to process discipline, not team dynamics. Every successful retrospective follows the same five-phase structure. These phases function like a building's foundation.…

Practical tools for turning discussion into decisions Getting a group to actually make a decision is harder than it looks. You've probably sat through meetings where discussion circles endlessly, a few loud voices dominate, or the team defaults to whatever the senior person suggests just to move on. The problem isn't that people don't care. It's…

Your product team has all the talent needed to build something extraordinary. Yet feature discussions turn into standoffs between engineering and business. Design ideas get shot down before they're fully explored. Cross-functional planning sessions feel more like negotiations than collaborations. These workplace conflicts aren't just personality problems or communication breakdowns. They can be managed strategically with…