• Clear Expectations: Has executive leadership clearly communicated its expectations for the team’s performance and expected outcomes? Do team members understand why the team was created? Is the organization demonstrating constancy of purpose in supporting the team with resources of people, time and money? Does the work of the team receive sufficient emphasis as a priority in terms of the time, discussion, attention and interest directed its way by executive leaders?
• Context: Do team members understand why they are participating on the team? Do they understand how the strategy of using teams will help the organization attain its communicated business goals? Can team members define their team’s importance to the accomplishment of corporate goals? Does the team understand where its work fits in the total context of the organization’s goals, principles, vision and values?
• Commitment: Do team members want to participate on the team? Do team members feel the team mission is important? Are members committed to accomplishing the team mission and expected outcomes? Do team members perceive their service as valuable to the organization and to their own careers? Do team members anticipate recognition for their contributions? Do team members expect their skills to grow and develop on the team? Are team members excited and challenged by the team opportunity?

• Competence: Does the team feel that it has the appropriate people participating? (As an example, in a process improvement, is each step of the process represented on the team?) Does the team feel that its members have the knowledge, skill and capability to address the issues for which the team was formed? If not, does the team have access to the help it needs? Does the team feel it has the resources, strategies and support needed to accomplish its mission?

• Charter: Has the team taken its assigned area of responsibility and designed its own mission, vision and strategies to accomplish the mission. Has the team defined and communicated its goals; its anticipated outcomes and contributions; its timelines; and how it will measure both the outcomes of its work and the process the team followed to accomplish their task? Does the leadership team or other coordinating group support what the team has designed?

• Control: Does the team have enough freedom and empowerment to feel the ownership necessary to accomplish its charter? At the same time, do team members clearly understand their boundaries? How far may members go in pursuit of solutions? Are limitations (i.e. monetary and time resources) defined at the beginning of the project before the team experiences barriers and rework?Is the team’s reporting relationship and accountability understood by all members of the organization? Has the organization defined the team’s authority? To make recommendations? To implement its plan? Is there a defined review process so both the team and the organization are consistently aligned in direction and purpose? Do team members hold each other accountable for project timelines, commitments and results? Does the organization have a plan to increase opportunities for self-management among organization members?

• Collaboration: Does the team understand team and group process? Do members understand the stages of group development? Are team members working together effectively interpersonally? Do all team members understand the roles and responsibilities of team members? team leaders? team recorders? Can the team approach problem solving, process improvement, goal setting and measurement jointly? Do team members cooperate to accomplish the team charter? Has the team established group norms or rules of conduct in areas such as conflict resolution, consensus decision making and meeting management? Is the team using an appropriate strategy to accomplish its action plan?

• Communication: Are team members clear about the priority of their tasks? Is there an established method for the teams to give feedback and receive honest performance feedback? Does the organization provide important business information regularly? Do the teams understand the complete context for their existence? Do team members communicate clearly and honestly with each other? Do team members bring diverse opinions to the table? Are necessary conflicts raised and addressed?

• Creative Innovation: Is the organization really interested in change? Does it value creative thinking, unique solutions, and new ideas? Does it reward people who take reasonable risks to make improvements? Or does it reward the people who fit in and maintain the status quo? Does it provide the training, education, access to books and films, and field trips necessary to stimulate new thinking?

• Consequences: Do team members feel responsible and accountable for team achievements? Are rewards and recognition supplied when teams are successful? Is reasonable risk respected and encouraged in the organization? Do team members fear reprisal? Do team members spend their time finger pointing rather than resolving problems? Is the organization designing reward systems that recognize both team and individual performance? Is the organization planning to share gains and increased profitability with team and individual contributors? Can contributors see their impact on increased organization success?

• Coordination: Are teams coordinated by a central leadership team that assists the groups to obtain what they need for success? Have priorities and resource allocation been planned across departments? Do teams understand the concept of the internal customer—the next process, anyone to whom they provide a product or a service? Are cross-functional and multi-department teams common and working together effectively? Is the organization developing a customer-focused process-focused orientation and moving away from traditional departmental thinking?

• Cultural Change: Does the organization recognize that the team-based, collaborative, empowering, enabling organizational culture of the future is different than the traditional, hierarchical organization it may currently be? Is the organization planning to or in the process of changing how it rewards, recognizes, appraises, hires, develops, plans with, motivates and manages the people it employs?

Be able to fix basic PC issues: These can be how to map a printer, back up files, or add a network card. You don’t need to be an expert and understand how to overclock a CPU or hack the registry, but if you work in IT, people expect you to be able to do some things.

Do public speaking. At least once, you should present a topic to your peers. It can be as simple as a five-minute tutorial on how IM works, but being able to explain something and being comfortable enough to talk in front of a crowd is a skill you need to have. If you are nervous, partner with someone who is good at it, or do a roundtable. This way, if you get flustered, someone is there to cover for you.

Train someone. The best way to learn is to teach.

Listen more than you speak. I very rarely say something I didn’t already know, but I often hear other people say things and think, “Darn, I wish I knew that last week.”

Know basic networking. Whether you are a network engineer, a help desk technician, a business analyst, or a system administrator, you need to understand how networks work and simple troubleshooting. You should understand DNS and how to check it, as well as how to ping and trace-route machines.

Know basic system administration. Understand file permissions, access levels, and why machines talk to the domain controllers. You don’t need to be an expert, but knowing the basics will avoid many headaches down the road.

Script. Everyone should be able to throw a script together to get quick results. That doesn’t mean you’re a programmer. Real programmers put in error messages, look for abnormal behavior, and document. You don’t need to do that, but you should be able to put something together to remove lines, send e-mail, or copy files.

Back up. Before you do anything, for your own sake, back it up.

Test backups. If you haven’t tested restoring it, it isn’t really there.

Document. None of the rest of us wants to have to figure out what you did. Write it down and put it in a location everyone can find. Even if it’s obvious what you did or why you did it, write it down.

Work all night on a team project. No one likes to do this, but it’s part of IT. Working through a hell project that requires an all-nighter to resolve stinks, but it builds very useful camaraderie by the time it is done.

Manage at least one project. This way, the next time the project manager asks you for a status, you’ll understand why. Ideally, you will have already sent the status report because you knew it would be asked for.

Don’t be afraid to debate something you know is wrong. But also know when to stop arguing. It’s a fine line between having a good idea and being a pain in the ass.

If you have to go to your boss with a problem, make sure you have at least one solution.

There is no such thing as a dumb question, so ask it … once. Then write down the answer so that you don’t have to ask it again. If you ask the same person the same question more than twice, you’re an idiot (in their eyes).

Even if it takes you twice as long to figure something out on your own versus asking someone else, take the time to do it yourself. You’ll remember it longer. If it takes more than twice as long, ask.

Learn how to speak without using acronyms.

IT managers: Listen to your people. They know more than you. If not, get rid of them and hire smarter people. If you think you are the smartest one, resign.

IT managers: If you know the answer, ask the right questions for someone else to get the solution; don’t just give the answer. This is hard when you know what will bring the system back up quickly and everyone in the company is waiting for it, but it will pay off in the long run. After all, you won’t always be available.

IT managers: The first time someone does something wrong, it’s not a mistake — it’s a learning experience. The next time, though, give them hell. And remember: Every day is a chance for an employee to learn something else. Make sure they learn something valuable versus learning there’s a better job out there.

IT managers: Always give people more work than you think they can handle. People will say you are unrealistic, but everyone needs something to complain about anyway, so make it easy. Plus, there’s nothing worse than looking at the clock at 2 p.m. and thinking, “I’ve got nothing to do, but can’t leave.” This way, your employees won’t have that dilemma.

IT managers: Square pegs go in square holes. If someone works well in a team but not so effectively on their own, keep them as part of a team.