Published

Teamwork Skills at Work: A Practical Guide

  • Teamwork
  • Feedback
  • Meetings

Teamwork skills at work come down to a few repeated actions: people can see what you are doing, they can rely on you, you say difficult things clearly and kindly, and you leave work in a state that someone else can pick up. None of this needs a special personality. It needs habits, and you can start them this week.

This guide covers the situations where teamwork is tested most: meetings, feedback, disagreement, criticism, handovers and persuading people you do not manage.

What good teammates consistently do

Ask any manager who they want on the team and you hear the same things. They do not describe talent. They describe behaviour.

Good teammates:

  • Do what they said they would do, or say early that they cannot.
  • Make their work visible. Others do not need to ask where things stand.
  • Help without taking over. They answer a question, then let the other person finish the task.
  • Share credit and own mistakes. "We finished the report" and "I missed that, here is the fix."
  • Treat shared work as shared. If a task has no owner, they ask who will take it, and they offer if nobody does.
  • Are the same person in every room. They speak about colleagues in the same way when those colleagues are absent.

Notice that none of these is about being the loudest or the friendliest. A quiet person who is reliable and clear is a strong teammate.

Take a small example. Mira works in a shop's back office. She does not have a title that gives her authority. But she posts a short note each morning in the team chat: "Today I am doing supplier invoices and the weekly stock count. Stock count will be ready by two." Her coworkers never ask her for updates, and when she is sick, someone can pick up her work from the note. That is a teammate.

Make your work visible

If nobody knows what you are doing, three problems follow. People ask you the same questions again and again. Work gets doubled. And your effort goes unseen, which is a risk for you.

Visibility is not boasting. It is information. Simple ways to do it:

  • A start-of-day or end-of-day note. Three lines: doing today, finished, stuck.
  • A shared task list that everyone can open. Update it when status changes, not once a week.
  • Say what you will deliver and when. "I will send you the draft by Wednesday noon."
  • Flag a problem early. "This is going to be one day late because the supplier has not replied." Early news is a small problem. Late news is a big one.

Keep it short. A long update that nobody reads is worse than a short one they do.

Run meetings that end with decisions

Meetings are where teamwork is easiest to see and easiest to waste. A meeting is useful if people leave knowing what was decided, who does what and by when.

Before the meeting, write one sentence: "At the end we will have decided X." If you cannot write it, you may not need a meeting. Send the agenda in advance, and invite only those who are needed.

During the meeting:

  1. State the goal in the first minute.
  2. Keep to the agenda. Write side topics on a "parking" list for later.
  3. Ask quiet people directly: "Ingrid, what do you see from the warehouse side?"
  4. When a decision is reached, say it aloud: "So we will move the delivery to Thursday."
  5. Assign actions: who, what, by when.

After the meeting, send the notes within a day, with decisions and actions at the top. Nobody needs a full transcript.

Example: a team of six meets about a late customer order. Without structure, it becomes twenty minutes of complaints. With structure, the leader says, "We need to decide how to reach the customer today and who calls." In ten minutes: Omar will call, Hye-jin will check stock, both report by three. The full method is in how to run a team meeting that ends with decisions.

Give feedback people can use

Feedback is information that helps another person do better. Most of us avoid it, then give it badly when we finally explode. A calm, regular approach works better.

A simple structure:

  • Situation. When and where. "In yesterday's handover."
  • Behaviour. What you saw or heard, without judgement. "The stock numbers were missing for two products."
  • Effect. What happened because of it. "I had to count them again before opening."
  • Request. What you would like next time. "Could you add the numbers before you leave?"

Say it in private, soon after, and in a neutral voice. Compare "You are careless" with the structure above. The first gives the person nothing to change except themselves. The second names one action.

Also give positive feedback in the same way. "When you told the customer about the delay before they asked, they stayed calm. Please keep doing that." People repeat what is noticed.

If you are not their manager, you can still do this. Ask first: "Can I give you some feedback on the report?" Most people say yes. For more words and examples, see how to give feedback to a coworker.

Disagree without a fight

Teams that never disagree are not in agreement. They are quiet. Disagreement is healthy if it is about the work and not about the person.

Rules that keep it safe:

  • Check you understand first. "So you want to move the launch to Monday because the supplier is late. Is that right?"
  • Agree on the goal. "We both want the order out without errors."
  • Say your view with a reason. "I would keep Friday, because the customer has a deadline."
  • Offer a way to test it. "Can we ask the supplier for a firm date before deciding?"
  • Accept the outcome. If the team or manager decides differently, support it. You can say your concern once, clearly. Then help it work.

Disagreeing with your boss follows the same steps, in a private moment, with a question rather than a challenge, and a clear point about the business effect. The details are in how to disagree with your boss respectfully.

Stay calm when criticised

Being criticised at work is hard. Your face gets hot, your mind goes fast, and you want to defend yourself. The skill is to slow down before you answer.

Try this order:

  1. Breathe and listen. Do not interrupt. Let them finish.
  2. Repeat what you heard. "You are saying the report had wrong totals on page three."
  3. Ask for an example if it is vague. "Which numbers were wrong?"
  4. Separate the part that is true. Even harsh feedback often has a fact in it.
  5. Respond with an action, or ask for time. "I will check the totals today and tell you by four."

You do not need to agree with everything. You can say, "I need to think about that, and I will come back to you tomorrow." That is a professional answer.

If the criticism is unfair, wait until you are calm, then raise it in private with facts. See how to stay calm when criticised at work for exact phrases.

Hand work over so nothing falls through

Handovers fail all the time. A shift ends, someone goes on holiday, a project moves to another person, and something small but important is lost.

A good handover note answers these questions:

  • What is the state? Done, in progress, not started.
  • What is waiting on someone else? Who, and since when.
  • What is due soon? Dates and times.
  • What can go wrong? The traps you know about.
  • Where is everything? Files, logins held by the team, contacts.
  • Who can they ask? You, if you are reachable, and when.

Write it as if the reader has never seen the work. Say a night-shift receptionist finishes: "Room 214 guest asked for a late checkout at twelve, approved by the manager. Room 305 has a broken lamp, maintenance has been called but not yet come. Airport pickup at six, driver has the name." The morning receptionist can act at once.

Where possible, do the handover in person or on a call as well as in writing, and ask the receiver to repeat the key points. Our guide to how to write a good handover at work has a template.

Persuade people you do not manage

Much of your work depends on people who do not report to you: other teams, other departments, sometimes your own manager. You cannot order them. You can still get a yes.

What works:

  • Start with their goal, not yours. What problem do they have that your request helps with?
  • Make it easy. A clear, small request: "Could you approve this by Thursday? Here is what I need and where to click."
  • Give a reason. People are more willing to help when they know why.
  • Offer something back. A favour, a thank you, credit in front of others.
  • Build trust before you need it. Help people when they ask. Keep your promises.
  • Ask for a small first step if the full request is large.

Example: you need the sales team to enter customer details in a set format. Saying "please follow the rules" gets little. Saying "if the postcode is in its own box, the deliveries stop going to the wrong address, and your customers complain less" gives them a reason. See how to persuade colleagues without authority.

Common mistakes

  • Waiting to be asked for an update.
  • Giving feedback only when angry.
  • Saying yes in the meeting and doing nothing afterwards.
  • Taking over a task to help, so the other person never learns it.
  • Complaining to others instead of to the person involved.
  • Treating a shared task as nobody's task.
  • Leaving a handover to memory.

A week of practice

Pick one habit per day and try it once. On Monday, post a three-line update about what you are doing. On Tuesday, finish one small promise early and say so. On Wednesday, prepare the goal sentence for the next meeting you attend. On Thursday, give one piece of specific thanks to a coworker, naming what they did. On Friday, write a short handover for your own work as if you were going away for a week, then keep it as your template.

You will find that some of these feel awkward at first. That is normal. After two or three weeks, the habits become part of how you work, and people begin to say that you are easy to work with. That reputation is worth more than any single task you finish.

Questions people ask

How do I show teamwork if I work remotely?

Be more explicit. Write short updates, answer messages within a reasonable time, say what you are working on and say when you are unavailable. Because people cannot see you, clear writing does the job your presence would do.

What if a teammate does not do their share?

First check the facts: what was agreed, and what has happened. Then talk to them in private, using the feedback structure, and ask what is in the way. If it continues, tell your manager what you saw, with facts, not opinions about their character.

How do I speak up in meetings if I am shy?

Prepare one point before the meeting and write it down. Say it early, because later it gets harder. You can also send your view in writing before or after the meeting. Quiet contributions count if they are clear.

Is it a problem to help too much?

It can be. If you always take over, the other person does not learn and you become the bottleneck. Show how, answer questions, then let them finish. Help that builds independence is the best kind.

How do I build a reputation as a good teammate?

Keep small promises, share information early, thank people specifically and own your mistakes. Reputation is built from many small moments, not one big one.

Learn this in five minutes

Our track "Being a Strong Teammate" practises the habits in this guide in five short lessons: what good teammates consistently do, making your work visible, supporting others without creating dependency, handling shared responsibility and building a reputation for collaboration. Each lesson takes about five minutes, so you can try one idea before your next shift or meeting.

All articles