I strongly agree with the heart of what you are saying. One of the worst bugs you can have in a product is to have built the wrong product. A good channel of

I strongly agree with the heart of what you are saying. One of the worst bugs you can have in a product is to have built the wrong product. A good channel of communication between people who understand the customer and people who are building and designing the product is not just valuable: it's critical. There can be communication challenges between our disciplines though. Frequent changes in direction can leave software in a bit of a shambles. This is probably the thing that creates the feeling that development is "a sacred space for creation". It takes time to both make the change, and end up with code that is pleasant to work with. On teams I've been on, this has sometimes led resistance to the marketing perspective. I, personally, am often uncomfortable with the language of marketing (both on the analysis side, and on the promotion side). On the promotion side, marketing teams like to make claims that are aspirational or appeal to emotional needs, rather than actually true from a technologists perspective. On the analysis side, marketing often looks like it's working from incomplete information, and extrapolating trends that I don't feel confident exist. It feels like guessing, and I don't like to gamble. These can be difficult gaps to bridge, but ultimately, I feel like we have the same goal: building the right thing for the right audience.