The Overlap Between Product, UX, and Engineering xxx

Some of the most useful work in product organisations happens between disciplines.

Not entirely in strategy. Not entirely in design. Not entirely in engineering. It happens in the seam between them, where ambiguous intent gets translated into product decisions, interfaces, systems, and tradeoffs.

That seam has shaped most of my career. I’ve worked across product, UX, front-end engineering, technical leadership, and broader organisational transformation. What I keep coming back to is that a lot of leverage lives in the overlap. When you understand the product intent, the interface consequences, and the technical implications at the same time, you can remove a surprising amount of friction from the system.

It also changes the way products are built. Teams make better decisions when strategy stays close to implementation. Designers make stronger calls when technical realities are legible. Engineers build better systems when they understand the product and user consequences of the choices in front of them.

This is not about collapsing every discipline into one role. It is about building enough shared understanding that decisions hold together from idea to execution.

That is one of the reasons I care so much about calm products and trusted systems. They are usually the result of teams that can think clearly across boundaries, not just inside them.