I'd add some encouragement and priority for anything your team is doing that shows ownership of the product or process.
Often this comes from individuals, such as the "go to" person who hacks on the development environment the most, or the engineer who everyone seems to ask for help writing tests. If you can see the value in those activities, it would be much appreciated if you schedule time for them, taking the day-to-day pressure off the individual a bit.
I'd add some encouragement and priority for anything your team is doing that shows ownership of the product or process.
Often this comes from individuals, such as the "go to" person who hacks on the development environment the most, or the engineer who everyone seems to ask for help writing tests. If you can see the value in those activities, it would be much appreciated if you schedule time for them, taking the day-to-day pressure off the individual a bit.