Here is a simple truth: If you are a museum leader, you can tell your staff they’re a team any day of the week, but unless you make it mean something, the word “team” is just a random noun.
We think of teams as good things. They seem democratic. They flatten hierarchies. They bring people together. And, depending on how your museum or heritage organization defines victory, they’re sometimes winners. But if you have even a passing acquaintance with sports, you know some teams always deliver, and some never do, so it’s not about the name.
Recently I witnessed an incident where a department leader brought his team–his word not mine–together to plan a meeting of peer leaders. Although staff felt there was too little time to deliver a cohesive program, the leader wanted to push ahead. In the end, the event took place, and the leader ignored his team’s input, forgot to introduce or mention members of his staff, consistently interrupted others in their presentations, and made many believe they’d wasted brain power in planning for the event. Lesson one: Teams aren’t for everyone. As with so much in leadership, know yourself first. If teams and team work drive you crazy, you can opt out. We’ve all experienced the moment where–pick one–a board member, staff member, or volunteer misses a meeting and the chemistry changes. Discussion moves along. Decisions are made. Boxes are checked. If teamwork isn’t for you, let your staff plan. Go over the results with your assistant directors, make any changes you feel are necessary, and watch as they deliver the goods. Lesson two: Good teamwork, especially from the leader’s point of view, requires trust. Every time you authorize staff to act on your behalf, you say “I believe in you.” Say it enough, and they start to trust you.
Lesson three: If you’re going to lead a team, know where it’s going. In the scenario Leadership Matters observed, there was little understanding about why this presentation mattered, and if it did, why the team leader waited ’til the last minute to plan. If an event or grant application matters, be clear about why. Tell your colleagues why an event demands all-hands-on-deck, not because they’re dense, but because they deserve to hear it from you.
Teamwork doesn’t guarantee Nirvana. Productive teams often argue. Lesson four: Be prepared for push-back. Value your staff. Being willing to argue about something doesn’t automatically indicate staff hate each other (or you) or enjoy being disruptive. Instead, it may indicate they care about the museum and its programs. And yes, every team needs the one member who’s going to say the emperor has no clothes. Why? Because it makes everyone look at the question, project or event with new eyes.
Teams are about group, not individual, behavior. That’s why a soccer team practices drill after drill. Their individual skills are in service–literally–to the goal. Lesson five: If you’re a team leader, you have a role in helping the group do its best. That means for 30 or 45 minutes, it’s not about you. Instead, your role is to manage the team: To be positive and encouraging; To pull it back on task; To ask if things are clear and make sense; To make sure everyone understands their tasks; To ask the group to reflect on what they’ve done before pushing on to the next goal. And perhaps, most importantly, to decide what tasks are best left to individuals rather than the group.
Do you work in a museum where staff are referred to as a team? Is that a good or bad thing?