We already have UTC, which is almost always used as the legal basis for all local timezone definitions. In many industries (such as in many aviation and maritime operations), UTC is used almost exclusively to synchronize things worldwide and to avoid any local timezone confusion that might cause problems.
So using UTC works great in situations where participants span multiple timezones. But I think the intuition of maintaining a local clock for local things, with solar noon kept somewhere approximately around clock noon, is still useful, since many day-to-day scheduling concerns remain entirely within one's local timezone. The key is that participants must be aware of their local timezone's offset from UTC. Not having to change their clocks twice a year would hopefully also make this easier.
We already have UTC, which is almost always used as the legal basis for all local timezone definitions. In many industries (such as in many aviation and maritime operations), UTC is used almost exclusively to synchronize things worldwide and to avoid any local timezone confusion that might cause problems.
So using UTC works great in situations where participants span multiple timezones. But I think the intuition of maintaining a local clock for local things, with solar noon kept somewhere approximately around clock noon, is still useful, since many day-to-day scheduling concerns remain entirely within one's local timezone. The key is that participants must be aware of their local timezone's offset from UTC. Not having to change their clocks twice a year would hopefully also make this easier.