[lostcolony]

As a manager, the big ones are making sure that everyone understands what is going on, and feels responsible for it. So if you see a silo developing, you intentionally break it, and explain to the team why you're asking someone who knows nothing about a particular domain to own the task (and also call on the silo to make themselves available to help teach the domain and answer questions and such). It means that task will take longer, but the long term health and effectiveness of the team will be increased.

That also includes manager context; ideally, even things that a manager usually does, the team starts stepping up to do. So working with product to define requirements? Manager should include the team with that and look to have them start taking ownership of it over time. Prioritization? Team sport, until it becomes as natural as breathing, and people are better able to prioritize their own time as emergents come in. Etc. This not only helps avoid the -manager- becoming a bottleneck that slows everyone down, but it helps individuals to grow really quickly and feel more empowered.