Necessary Tension
Most people think friction with their technical partners is a collaboration problem. It’s not.
If you’re an entrepreneur, product manager, or basically anyone who builds stuff, you’ve probably felt that tension that surfaces when engineering pushes back on your desired launch timeline. Or the data team challenges the data sources behind your projection. Or IT wants to review security and integration before approving the new tool that is going to save you a ton of time and effort.
It can feel like resistance. But it might actually be a sign of a healthy system.
Technical teams optimize for different priorities, and those differences can be genuinely valuable to the organizational mission. While you might be optimizing for speed to market, customer impact, or feature delivery, your technical partners may be focused on system reliability, scalability, data quality, and long-term maintainability.
While your priorities and their priorities often don’t naturally align, both are necessary. And when you harness that tension, it produces better decisions. You’ll even find that great products or results often emerge from the space between those two sets of perspectives.
Vision vs. Feasibility
Someone pushes the idea forward. Someone challenges how it will work.
Speed vs. Durability
Someone wants to launch now. Someone is thinking about after launch and the ongoing user experience.
Business Outcomes vs. System Health
Someone focuses on growth metrics. Someone fortifies the system that growth depends on.
Healthy organizations don’t eliminate this tension. They encourage learning how to leverage it to their benefit.
Your Tech Partner’s Love Language Isn’t a Jira Ticket
If you work in Product, you know the drill: you collaborate across departments and pride yourself on strong relationships. But sometimes there’s that one technical partnership (like IT, Engineering, or Data Science) where things always feel harder than they should.
When perspectives collide and you work through those constraints, stronger solutions emerge. When you don’t, you often end up with brittle or broken systems, unrealistic roadmaps, or solutions that look good, but arrive too late.
The goal of working well with your engineering, data and IT/ops partners isn’t to eliminate friction. The goal is to make that friction productive, to navigate the different, seemingly competing, priorities and to treat pushback as an opportunity rather than as a roadblock.
The best partnerships with these roles rarely feel effortless. More often, they feel like two smart people pulling the same problem from different directions until the right answer emerges. That creative tension, when managed well, can develop into one of the most valuable, and rewarding, working relationships you have.
Why It Matters
This post may sound a bit like a love song to partnerships between business and technical teams. In some ways, it is. Over the years, we’ve watched difficult working relationships evolve into genuine partnerships, and we’ve coached dozens of product, business, and technical professionals through that transition. When those partnerships take hold, something remarkable happens: products move faster, solutions improve, and problems get solved at a level that wouldn’t have been possible otherwise.
So, if you are looking to improve your relationship with a technical partner, here are three mindset shifts that can accelerate the journey.
A good reminder that constructive tension between business and technical teams isn’t a blocker