Sure you can choose to use nodejs instead of ruby or embed video instead of streaming it yourself or find a better confit system than admin pages but the entire product ideas are probably decided by the business well in advance of when the developer gets whiff of it.
Imagine you are about to purchase a car and the car dealer weirdly tries to convince you to take up cycling via “what’s the problem”. You’d probably walk to the next dealer as you’ve made up your mind you want a car.
The email order confirmations, however, took 30 minutes to be delivered to customers. In the end, it was this uncertainty of whether an order went through that killed the customers trust, not the fact that it was not an SPA. I wish I had asked more questions instead of blindly following orders.
CEO - "We need a live streaming video platform"
Me - "What is the problem?"
CEO - "I want to do a webcast on our website"
Me - "Would embedding a YouTube video player work? It does x, y and z and it can be ready by tomorrow"
CEO - "Oh! I hadn't considered that"
You need to get back to first principles. Usually your boss wants to accomplish something and then they come up with a solution. Then they fall in love with the solution, not the problem.
You should be asking your boss what they're trying to accomplish instead of letting them propose the solution. If you help devise the solution/product you'll be much happier building it.