The Conditions under Which Collaboration Works
About this practice test
An analytical article examines when collaboration improves work and when it creates unnecessary cost, focusing on shared goals, complementary expertise, coordination, trust, group size, timing, and incentives.
What you’ll practice
Finding detail
Locate specific information and evidence.
Interpreting ideas
Connect main points and inferences.
Evaluating arguments
Assess claims, evidence, and limitations.
What to expect:
8 questions with explanations to review after submission.
Study the questions and tasks
Work through the material below, or start the interactive practice above to complete an attempt. Try the exercises before opening any answer or transcript sections, then use them to review your work.
- Practice level
- C1. Try this level if you can follow the instructions and understand most of the language; choose an earlier level if you need more support.
- Question formats
- Multiple choice
How to approach this practice
Read the passage for its main idea, then return to the relevant sentence or paragraph for each question. Base answers on the passage.
The Conditions under Which Collaboration Works
People often praise collaboration as if simply putting several capable minds in one room were enough to produce a better answer. In practice, that assumption is too simple. In offices, schools, and project groups, people sometimes spend more time coordinating calendars than solving problems. Collaboration is useful when a task is too complex for one person and when interdependence is real. For routine work, or for work that one person could finish cleanly alone, the same process can become a distraction. The value of collaboration is therefore conditional, not automatic. One condition is a shared definition of the problem. A team works best when people agree, at least broadly, on what they are trying to solve, even if they do not yet share a method. It may be enough to agree that a launch must succeed or that a service must be improved, even if people favour different routes. If everyone enters the room with a different version of the task, meetings turn into negotiations about purpose rather than progress. It is possible to disagree about the route and still collaborate productively; it is much harder when the destination itself is unstable. A marketing team may debate tone and timing, yet still move together if it knows what outcome counts. A second condition is complementary expertise that the task genuinely requires. A team that consists of similar specialists may produce polite duplication rather than insight. That is why the presence of many talented people is not, by itself, a reason to work as a team. By contrast, when each person holds a different piece of the problem, collaboration becomes a practical necessity. If each member can finish alone, collaboration should usually be reserved for the point at which their work has to meet. The issue is not simply whether people are clever, but whether their knowledge depends on exchange. The value lies in fit, not in the prestige of having more names on the document. Coordination rules also matter. Open-ended brainstorming is often treated as a virtue, yet it can hide indecision. A discussion may sound generous while quietly postponing responsibility. A decision can still be collaborative if it has a clear owner, a deadline, and a simple rule for settling what remains unresolved. Otherwise, the group may leave the room with several attractive ideas and no settled action. Too many approval layers, by contrast, make every choice slower and more political. Clear roles do not kill collaboration; they stop it from dissolving into ritual discussion. The point is not to remove judgment from people, but to keep judgment from being endlessly delayed. Many people assume that harmony is the basis of successful teamwork, but the writer is more cautious. Teams that know each other well are not automatically harmonious; a little disagreement can improve the work if people can challenge ideas without threatening status. Teams that are permanently agreeable can also become bland and evasive. In that sense, friction is useful when it is bounded. Trust is built less by forced positivity than by keeping promises, sharing drafts, and admitting uncertainty. People collaborate better when they can rely on one another’s habits, not just on friendly language. A team that never risks friction may never test its assumptions. Size changes the whole equation. Small groups are easier to coordinate because each person’s contribution is legible. Once a group grows beyond a certain point, the cost of coordination rises faster than the number of ideas. Then subgroups or stages become necessary, because a larger meeting does not automatically produce better thought. A long delay between drafts and comments can also weaken the process, because people begin to revise work that they no longer remember well. Collaboration also depends on tempo: quick iterations and short feedback loops keep the work alive. If feedback arrives after decisions have hardened, collaboration becomes post hoc justification. Incentives can strengthen or destroy the process. If rewards go only to visible individuals, people may hoard information or do only low-risk tasks. Collective rewards alone can also hide weak effort, so the best arrangement is usually shared success with traceable contributions. People need to see that effort is noticed, but also that the task matters to the whole group. Leaders should reward making others effective, not just speaking elegantly. A collaborator is not the person who talks most; it is the person who removes obstacles and makes the group work more smoothly. If the system praises only individual brilliance, cooperation turns competitive. The final point is that collaboration succeeds not because people are nice, but because structures make joint work worthwhile and intelligible. When task, roles, timing, and incentives align, a team can outperform solo work. When they do not, collaboration becomes an expensive way to manufacture confusion. The sensible question is therefore not whether collaboration is good in itself, but under what conditions it earns its place. Good teamwork is not a mood; it is an arrangement that has to be designed, maintained, and judged against the work itself.
-
Question 1 · Multiple choice
Choose all the correct answers.
Choose TWO claims about collaboration that the writer makes in the opening paragraph.
Return to the passage, recording or visual- It is useful when a task is too complex for one person.
- It can be a distraction on routine work.
- It is always the best way to solve any task.
- It works only when everyone already agrees about the answer.
Check answers and explanations
- Answer
- It is useful when a task is too complex for one person.; It can be a distraction on routine work.
The writer says collaboration is useful when the task is too complex for one person, and that it can be a distraction for routine work. The other two options overstate the case: the passage does not claim collaboration is always best, or that it works only when everyone already agrees.
Collaboration is useful when a task is too complex for one person and when interdependence is real
For routine work, or for work that one person could finish cleanly alone, the same process can become a distraction
It is always the best way to solve any task.: The passage explicitly limits collaboration; it is not presented as universally superior.
It works only when everyone already agrees about the answer.: The writer says people may disagree about the route and still collaborate well.
-
Question 2 · Multiple choice
Choose all the correct answers.
Choose TWO features that, according to the writer, make collaboration worthwhile rather than unnecessary.
Return to the passage, recording or visual- The task should require complementary expertise.
- The group should avoid any disagreement about method.
- The team should be large enough to cover every possible view.
- People should agree broadly on what problem they are trying to solve.
Check answers and explanations
- Answer
- The task should require complementary expertise.; People should agree broadly on what problem they are trying to solve.
The passage says teams work best when they agree broadly on what they are trying to solve and when the task truly requires complementary expertise. Options about avoiding disagreement or making the group larger are not supported; in fact, the writer allows disagreement about method and warns against unnecessary size.
A team works best when people agree, at least broadly, on what they are trying to solve, even if they do not yet share a method
A second condition is complementary expertise that the task genuinely requires
The group should avoid any disagreement about method.: The writer says people may disagree about the route and still collaborate productively.
The team should be large enough to cover every possible view.: The passage later argues that larger groups increase coordination costs; size is not treated as an advantage in itself.
-
Question 3 · Multiple choice
Choose all the correct answers.
Choose TWO statements about coordination that the writer supports.
Return to the passage, recording or visual- Every decision should be left to open-ended brainstorming.
- A decision should have an owner and a deadline.
- Unresolved disputes need a simple rule for settling them.
- Approval layers are useful because they slow mistakes.
Check answers and explanations
- Answer
- A decision should have an owner and a deadline.; Unresolved disputes need a simple rule for settling them.
The writer prefers collaboration with a clear owner and deadline, plus a simple rule for unresolved issues. Open-ended brainstorming and extra approval layers are presented as problems, not solutions.
A decision can still be collaborative if it has a clear owner, a deadline, and a simple rule for settling what remains unresolved
Too many approval layers, by contrast, make every choice slower and more political
Every decision should be left to open-ended brainstorming.: The passage criticises open-ended brainstorming for hiding indecision.
Approval layers are useful because they slow mistakes.: The writer says too many approval layers make choices slower and more political.
-
Question 4 · Multiple choice
Choose all the correct answers.
Choose TWO views on disagreement and trust that the writer expresses.
Return to the passage, recording or visual- Harmony is the main condition for good criticism.
- A little disagreement can improve quality.
- Trust grows when people keep promises and share drafts.
- Teams need forced positivity to build trust.
Check answers and explanations
- Answer
- A little disagreement can improve quality.; Trust grows when people keep promises and share drafts.
The writer presents limited disagreement as helpful when it is bounded, and says trust grows from reliable behaviour rather than from artificial cheerfulness. The other options reverse or distort that position.
a little disagreement can improve the work if people can challenge ideas without threatening status
Trust is built less by forced positivity than by keeping promises, sharing drafts, and admitting uncertainty
Harmony is the main condition for good criticism.: The writer suggests the opposite: a little bounded disagreement can help the work.
Teams need forced positivity to build trust.: The passage says trust is built less by forced positivity than by reliable behaviour.
-
Question 5 · Multiple choice
Choose all the correct answers.
Choose TWO claims about group size and tempo that the writer makes.
Return to the passage, recording or visual- As groups grow, coordination becomes easier and stages are less necessary.
- Large groups always generate better ideas.
- Small groups are easier because each contribution is legible.
- Quick iterations and short feedback loops matter.
Check answers and explanations
- Answer
- Small groups are easier because each contribution is legible.; Quick iterations and short feedback loops matter.
The passage says smaller groups are easier to coordinate because each contribution is clearer, and that quick iterations with short feedback loops are important. It also says larger groups may need subgroups or stages because coordination costs rise; the distractor claiming the opposite contradicts this.
Small groups are easier to coordinate because each person’s contribution is legible
Collaboration also depends on tempo: quick iterations and short feedback loops keep the work alive
As groups grow, coordination becomes easier and stages are less necessary.: The writer says the opposite: coordination costs rise as groups grow, so subgroups or stages become necessary.
Large groups always generate better ideas.: The writer says coordination costs rise as groups grow, so larger groups are not automatically better.
-
Question 6 · Multiple choice
Choose all the correct answers.
Choose TWO effects that badly designed incentives can have, according to the writer.
Return to the passage, recording or visual- Traceable contributions become impossible.
- Collective rewards can hide weak effort.
- People may hoard information.
- Collective rewards always improve honesty.
Check answers and explanations
- Answer
- Collective rewards can hide weak effort.; People may hoard information.
The writer says that poor reward systems can make people hoard information or do only low-risk tasks, and that collective rewards on their own can hide weak effort. The other options either contradict this or introduce ideas the passage does not support.
If rewards go only to visible individuals, people may hoard information or do only low-risk tasks
Collective rewards alone can also hide weak effort
Traceable contributions become impossible.: The passage recommends the opposite: shared success with traceable contributions.
Collective rewards always improve honesty.: The writer warns that collective rewards alone can hide weak effort.
-
Question 7 · Multiple choice
Choose all the correct answers.
Choose TWO qualities that the writer says should be rewarded in good collaboration.
Return to the passage, recording or visual- Being the most visible individual.
- Making others effective.
- Speaking elegantly.
- Removing obstacles.
Check answers and explanations
- Answer
- Making others effective.; Removing obstacles.
The writer argues that leaders should value making others effective and removing obstacles. Speaking elegantly or simply being visible are not the traits highlighted as useful; they can even distract from real contribution.
Leaders should reward making others effective, not just speaking elegantly
A collaborator is not the person who talks most; it is the person who removes obstacles and makes the group work more smoothly
Being the most visible individual.: The writer criticises reward systems that favour visible individuals rather than effective collaboration.
Speaking elegantly.: The passage explicitly contrasts this with the more valuable contribution of helping others work effectively.
-
Question 8 · Multiple choice
Choose all the correct answers.
Choose TWO claims that best capture the writer's final conclusion.
Return to the passage, recording or visual- Collaboration works because structures make joint work worthwhile and intelligible.
- Confusion is an unavoidable cost of teamwork.
- The important question is under what conditions to collaborate.
- Collaboration is mainly about being nice.
Check answers and explanations
- Answer
- Collaboration works because structures make joint work worthwhile and intelligible.; The important question is under what conditions to collaborate.
The conclusion is that collaboration succeeds because structures make joint work worthwhile and intelligible, and that the real question is under what conditions to collaborate. The other options misrepresent the writer as praising niceness or treating confusion as inevitable.
collaboration succeeds not because people are nice, but because structures make joint work worthwhile and intelligible
The sensible question is therefore not whether collaboration is good in itself, but under what conditions it earns its place
Confusion is an unavoidable cost of teamwork.: The writer argues that good structures reduce confusion rather than accept it as inevitable.
Collaboration is mainly about being nice.: The writer explicitly rejects niceness as the main explanation for success.
What to review next
Find the words that support each answer. For a mistake, compare the question with the evidence and identify the detail or inference you missed.
A focused practice result shows how you did on these tasks. Use several activities across skills to decide what to study next; one practice score does not certify an overall CEFR level.
Before you practise: a worked example
Look for evidence in the text. Separate what the writer says from what you already know about the topic.
The library normally closes at six, but on Fridays it stays open until eight. When does it close on Friday?
The answer is eight. But introduces an exception to the normal closing time, so the first time mentioned is not the answer.
This teaching example is separate from the scored questions. After your test, compare any mistakes with the explanation and revisit the topic before trying again.