Teamwork skills: a practical guide

Almost every job is done together with other people: teachers at a training centre agree on a timetable, a developer and a designer at an IT company work on the same app, volunteers in a mahalla prepare an event. That is why “ability to work in a team” appears so often in job adverts. This skill is not an inborn personality trait: it can be learned and practised. In this guide we look at what a team is, how to divide roles and responsibilities, how to record agreements in writing, how to build trust, how to work with people of different temperaments and generations, how to resolve disagreements, and how to behave in a remote team and in meetings. At the end you will find common mistakes, a practice exercise and a checklist.

What a team is and why employers ask for this skill

A team is not just people sitting in the same room. A team is a group of people who have divided the work to reach a shared goal and who depend on each other’s results. If everyone does only their own job and has no interest in what the others are doing, that is not a team, just employees who happen to work in the same place.

Teamwork belongs to the soft skills: the personal and social skills you need whatever your profession. Employers ask for it for several reasons:

• Results are created together. Even the strongest specialist delays a project if they cannot reach agreement with colleagues.
• There are fewer mistakes. In a team where people check each other’s work and are not shy about asking questions, mistakes are caught early.
• Knowledge is shared. If someone falls ill or goes on holiday, a colleague can carry on with their work.
• The atmosphere improves. People stay longer with reliable colleagues and are glad to come to work.

At a job interview this skill is often tested with questions such as “How did you handle a difficult situation in a team?”. Preparing for questions like these is covered in detail in our article on interview preparation.

Roles, responsibilities and clear agreements

Who does what

Many team problems start with one question: “Who was supposed to do this?” If there is no clear answer, the job either does not get done or two people do it at the same time. That is why every task should have one person responsible. That person does not have to do all the work alone, but they answer for the result and keep others informed of progress.

Example. At a training centre in Samarkand, four teachers are getting ready for the new academic year. At a meeting they divide the tasks: Dilfuza opa draws up the timetable, Sardor updates the test questions, Gulnora prepares an announcement for parents, and Jahongir checks the classrooms and the projector. Everyone knows their own part, and the others know whom to turn to.

The three parts of an agreement

An agreement on any task should cover three things:

1. The task: exactly what needs to be done. Not “sort out the timetable” but “draw up a weekly timetable for three groups”.
2. The deadline: by when. Not “as soon as possible” but “by 5 pm on Friday”.
3. The result: what the finished work looks like and where it should be handed in. “The timetable is in a file in the shared folder and every teacher has checked it.”

Putting it in writing

A week later, everyone remembers a verbal agreement differently. So after a meeting or conversation, send a short written summary: in the team chat, by email or in a shared document. For example:

Today’s agreements (illustrative example):
Class timetable: Dilfuza opa, by Thursday.
New test questions: Sardor, by Monday.
Announcement for parents: Gulnora, by Wednesday.
If anyone understood this differently, please write today.

The last line matters: it lets you spot a misunderstanding straight away. If there are many tasks, it is convenient to keep them in one shared table; use the techniques from collaborating in Google Docs and Sheets for this.

Trust and open communication

How trust is built

Trust does not come from fine words but from small, repeated actions:

• Keep your promises. If you said “I’ll send it tomorrow”, send it tomorrow. If you are not sure, do not promise, or give a realistic deadline.
• Let people know in good time. If you sense you will miss a deadline, say so as soon as you realise, not on the last day. “It won’t be ready by Thursday because the data arrived late. I can hand it in by Saturday lunchtime. Would that work for you?” A message like this gives the team time to change the plan.
• Be consistent. Do not say one thing in front of your manager and another in front of colleagues.
• Protect other people’s information. Do not pass on what someone told you in confidence.

Open and respectful communication

In a team you need to state your views openly and listen carefully to others. A few basic rules: do not interrupt, ask again about anything you did not understand, when criticising discuss the work rather than the person, and do not forget “please” and “thank you”. We cover these in detail in our guides to workplace communication and giving and receiving feedback; here we have only recalled the points that matter most for a team.

Working with different temperaments and generations

Different people make a team stronger

In a team, some people make decisions quickly while others check every detail; some talk a lot in meetings while others prefer to put their thoughts in writing. These differences are not a problem: they complement each other. The fast colleague moves the project forward, the meticulous one catches the mistakes. Ask the quieter colleague for their view separately: “Nodir, what do you think about this?” Sometimes the best idea comes out exactly this way.

Older colleagues and new ideas

In Uzbekistan’s working culture, respect for older and more experienced colleagues plays an important role. This is a right and valuable tradition. But respect does not mean staying silent. A younger employee may know a new tool or approach, and suggesting it benefits the team. To keep the balance:

1. Acknowledge experience first. “You have been doing this for many years, so I would like to hear your opinion” is a sincere sign of respect.
2. Put your suggestion as a question. “If we kept this timetable in Google Sheets, everyone could see it at the same time. Could we give it a try?”
3. Start small. Do not propose changing the whole system; suggest trying it for one month or with one group.
4. Help out. Set up the new tool yourself and show how it works.
5. Do not criticise in public. Mention an older colleague’s mistake privately and gently, not in front of others.

The reverse also happens: an experienced employee should not dismiss a younger colleague’s suggestion with “We’ve always done it this way”. A team that draws on both sides’ experience and fresh ideas gets the best results.

Resolving disagreements and conflicts

In any team, opinions clash, and that is natural. The problem is not the disagreement itself but how it is resolved.

Example. In a small IT team in Tashkent, Azamat (developer), Ra’no (designer) and Bobur (project manager) are building a mobile app for a training centre. Ra’no wants to redesign the app’s home screen, while Azamat thinks this will blow the deadline. The argument starts in the chat and quickly heats up.

In a situation like this, the following steps help:

1. Leave the chat. Tone gets lost in writing and the conversation escalates quickly. Suggest meeting in person or calling: “Let’s talk for 15 minutes.”
2. Stick to facts. Not “you always delay everything” but “the new design will take three more days of work, and our deadline is next Friday” (the figures are illustrative).
3. Listen first. Let each side say everything they have to say. Ra’no explains that users get lost on the old screen; Azamat is worried there will not be enough time.
4. Recall the shared goal. Both want the app to be good and to launch on time.
5. Discuss options. For example, make the most important change now and leave the rest for the next version.
6. Write down the decision. Who does what, and by when.

When to go to your manager

Colleagues should resolve most disagreements between themselves. But there are cases when going to your manager is the right thing to do:

• you talked face to face but could not agree, and the issue affects the deadline or the result;
• the decision is outside your authority (budget, moving the deadline, another department’s work);
• a colleague is abusive, humiliates others or breaks safety rules.

When you go to your manager, still present the facts and describe both sides’ views fairly. In our example, Bobur, as project manager, considers both options and makes the decision.

Remote teams and meetings

Remote working etiquette

In remote work the team rarely sees each other, so written communication becomes more important.

• Chat etiquette. Write one thought in one message rather than ten short messages in a row. Do not just write “Hello” and wait for a reply; put your question straight after the greeting. Do not send non-urgent messages at night or at weekends, or schedule them for the morning.
• Response time. Agree on it with the team: for example, replying within a few hours during working hours. If you cannot answer straight away, write “Seen it, I’ll reply after lunch”.
• Show your status. Let people know with a short message when you start work, go for lunch or finish for the day.
• Online tools. Choose one place for the task list, shared documents and files so they do not get scattered across different chats. Read our article on Google Docs to learn about working together in shared documents.

Team meetings

A good meeting is short and productive. Whether it is an online meeting or one in a room, the rules are the same:

1. Agenda in advance. Before the meeting, write down what will be discussed and what decision is needed.
2. Keep to time. Start and finish at the agreed time.
3. Let everyone speak. One or two people should not take up all the time.
4. Summary at the end. Who does what, and by when, in writing.

If an issue can be settled with a single message, do not call a meeting.

Helping newcomers, sharing success and admitting mistakes

Welcoming a new member

In the first weeks a newcomer does not know many things and is shy about asking questions. Help them: introduce the team, show where things are kept, explain the first task clearly and say “If you have any questions, message me”. If you are the newcomer, collect your questions and ask them together, and write down the answers so you do not ask the same thing twice.

Sharing success

When a project ends well, say “we did it” rather than “I did it”, and name each person’s contribution specifically. Example: mahalla volunteers in Chilanzar organised free computer classes for older residents. At the final meeting, the organiser Shahzoda gave special thanks to Rustam aka, who found the room, to the students who spread the announcement, and to Mohinur, who taught the classes. Recognition like this is why people come back for the next event.

Admitting mistakes

Everyone makes mistakes. What matters is not hiding them. When you notice a mistake, say so straight away, briefly explain what happened and suggest how to fix it: “I wrote down two phone numbers wrongly in the volunteer list. I’ll recheck the whole list by this evening.” A response like this does not reduce trust; it increases it. And instead of blaming the person, the team should discuss what can be done so the mistake does not happen again.

Common mistakes

• Agreeing verbally and writing nothing down. A week later everyone remembers it differently.
• Assuming “someone will do it”. A task without a clear owner often never gets done.
• Announcing a missed deadline on the last day. The team has no time left to change the plan.
• Doing everything yourself. Not trusting others leads to exhaustion and delays.
• Resolving a conflict in the chat or in front of others. The conversation heats up and both sides start arguing to “save face”.
• Staying silent. Seeing a problem and saying nothing because “it’s not my job”.
• Taking credit for success and blaming others for mistakes. The habit that destroys trust fastest.
• A meeting for every issue. Time is lost, when a single message would have done the job.

Practice exercise and checklist

To test what you have learned, carry out a small team task. You can do it with family members, classmates or friends: for example, organising a book swap day in your mahalla or a graduation evening for your group.

1. Write the shared goal in one sentence: what you want to achieve and by when.
2. Split the work into 4–6 tasks.
3. Give each task one owner and a clear deadline.
4. For each task, describe what the finished result looks like.
5. Post the agreements in writing in a shared document or chat.
6. Agree with the team on how quickly to reply to messages.
7. Halfway through, hold a short meeting: an agenda, 15 minutes, a summary at the end.
8. If someone is running late, do not blame them; ask why and find a solution together.
9. At the end, name each participant’s contribution specifically and thank them.
10. Ask everyone to answer in a sentence or two: “What went well, and what will we do differently?”

Teamwork checklist

• Every task has one owner.
• The task, deadline and result are recorded in writing.
• If I am going to miss a deadline, I say so as soon as I know.
• In the chat: one thought, one message, with the question asked straight away.
• I treat older colleagues with respect but still put forward my own suggestions.
• I resolve disagreements face to face and based on facts.
• I help newcomers in their first days.
• When we succeed I credit the team; when I make a mistake I admit it myself.

Teamwork is not a rule you learn in a day but a habit you practise every day. After each project, ask yourself one question: “What can I do better for the team next time?” In a few months, both you and your colleagues will notice the difference.

If you would like to learn project planning and team management systematically, take a look at our association’s free project management programme and other training programmes. When you are ready, submit an application and our specialists will get in touch.