Why Most Cross-Functional Teams Fail Before They Start
The problem isn't the people—it's the structure. When teams inherit competing incentives and no shared language, collaboration becomes performance. Here's how to fix the foundation.
Strategy is only as good as the decisions it enables. I write to make complex ideas actionable drawing on years of leading technical programs to explore leadership, cross-functional collaboration, and responsible AI. These aren't think-pieces; they're field notes.
The problem isn't the people—it's the structure. When teams inherit competing incentives and no shared language, collaboration becomes performance. Here's how to fix the foundation.
Most delivery failures happen not during execution but at the transitions between teams. Mapping the handoff moments is the single highest-leverage thing a PM can do.
When a product manager says "priority" and an engineer hears something different, the sprint is already broken. Here's a practical framework for aligning vocabulary before aligning work.
No one reports to you, yet everything depends on your ability to move people. Influence without authority isn't a soft skill—it's a discipline. This is the framework I use.
Pushing deadlines too hard breaks the relationship. Not pushing breaks the roadmap. This piece explores the narrow path between accountability and collaboration.
Every stakeholder believes their initiative is the most important. That's not a stakeholder problem—it's a communication problem. Here's how I triage without burning bridges.
Teams celebrate the model's accuracy while ignoring the operations impact. Accountability for AI outcomes requires a different set of metrics—and a different set of conversations.
Data scientists build the model. Engineers ship it. But who owns the outcome? In most organisations, no one does—until something goes wrong. That gap is where PMs need to step in.
Published articles and field notes on leadership, technical programs, and responsible AI.