The stupidly easy solution is to just give them stuff that has already been successfully delivered to production to market, 9 months from now. There's invariably a huge backlog of years worth of successes that marketing wasn't even aware of.

[–] foofiepie@lemmy.world 7 points 5 months ago* (last edited 5 months ago)

Feature flags baby. This is how we do it.

Make it live but disabled, have an env prior to prod with them on, for any regressions.

Launching your already comprehensively tested and actually live feature? An easy deployment.

Can someone please tell me how to do this for the BE. Ta.

[–] sunbeam60@lemmy.one 5 points 5 months ago (1 children)

Yeah, I agree that might work if the marketing team isn’t that connected to the product. I’ve not worked with a marketing team where that would work, but maybe it will for some. It doesn’t change the “massive customer will only renew if” scenario, though.

[–] MajorHavoc@programming.dev 2 points 5 months ago

I’ve not worked with a marketing team where that would work, but maybe it will for some.

I've never been anywhere that I thought it would work, but it ultimately did, almost everywhere.

I've found it takes a few iterations, but the marketing folks in on it love being the ones who actually can reliably deliver on their promises.

It doesn't work for the marketers that promise whatever they please without talking to dev, but I don't find them to be worthwhile professional allies, so I don't sweat it.

It doesn’t change the “massive customer will only renew if” scenario, though.

Very true. It doesn't help with that case, and that one does happen. I've had the best luck saying "we don't do that, but we're scrambling to add it" in that situation.