Are we talking about business decisions? My experience is, that developers are only interested in taking that risk, if they also get a share in the company and get access to internals. "Your house, your decision, your money. We are just the hired gun to do the carpenting."
However, granting visibility to decisions (and the information that leads to them), when possible, is a great tool.
A generic example might be that a major client will sign onboard if a new API feature is implemented. Just asking a development team to build the feature will get it done, but in my experience, teams will feel significantly more included (and important) if they have the context of why it needs to be built.
The decision to pull resources off of already-planned tasks to build the new feature shouldn't be made by the developers, but understanding that they're helping the business in a major way can really help cohesion, inclusion, and perceived impact. Those are things that make people feel fulfilled and important at work.
Some do, some don’t. If a developer wants to start their own company or move into leadership in a larger company then they need to start thinking this way. There is a vanishingly small number of senior ICs/researchers who get paid the big bucks to work on purely self-determined technical problems. It’s much easier to just learn a bit about business.
