Coordination vs. Collaboration: Why Capable Groups Still Miss

In the last chapter you set your bearings. Now the method itself begins. Before you can keep a group’s work aligned, you need to see clearly what “keeping it aligned” actually means, and why groups full of capable, willing people still fall short. This chapter gives you the single distinction the rest of the course is built on, plus a simple way to spot trouble before it derails the work.

What Coordination Is (and Why It’s Not Collaboration)

When a group works toward something together, two different things are happening at the same time, and telling them apart is the key to everything that follows.

Collaboration is people working together on shared work: brainstorming ideas, writing a document side by side, or solving a problem as a group. It is the together part of group work, and most people are already comfortable with it.

Coordination is different. It is managing the dependencies between people’s separate tasks so the whole effort holds together. A dependency simply means one piece of work relies on another: the poster cannot be printed until the design is finished, the room cannot be booked until someone confirms the date. Coordination makes sure the right thing happens in the right order, that nothing important is done twice, and that nothing necessary is left with no one responsible.

A simple way to hold the difference in your head: coordination handles the between, and collaboration handles the together.

Talking a lot helps, but it is not the same as coordination. A friendly group can still print the poster before the logo is ready, or wait three days for a decision no one realized was theirs to make. Coordination is not about how well people get along; it is about keeping the connections between their tasks visible and managed. That is why even the most enthusiastic groups miss without it.

The Four Ways Capable Groups Miss

Most breakdowns in group work are not mysterious. They come from a small number of recurring failures, and once you can name them, you can catch them early. Here are the four to watch for, each with what causes it and the tell-tale sign that it is happening.

Notice that none of these are caused by laziness or lack of skill. They are coordination failures: the between was never managed. Keep this short list close, because the rest of the course is essentially a set of tools for preventing each one.

Same Group, With and Without Coordination

Let us make this concrete with a group you can picture easily: four students preparing a graded class presentation. Same four people, same goal, same effort. The only thing that changes is whether anyone manages the between.

Without coordination

The group agrees to “split it up and meet before class.” Two students both build slides on the same topic, because each assumed it was theirs (duplicated work). No one prepares the handout the teacher asked for, because it fell between everyone’s sections (unowned gap). On the morning of, they still have not agreed who actually speaks first, so they argue in the hallway (stalled decision). And the student doing the charts has been waiting two days for the survey numbers from a teammate who did not know anyone was blocked on them (hidden dependency). The group is capable and willing, and the presentation is still a scramble.

With coordination

Same group, but this time one person keeps the between in view. They write down a shared goal (“a ten-minute presentation with four clear sections and one handout”), give each section a single owner, and note out loud that the charts depend on the survey numbers, so those get sent first. When a small choice comes up, who opens the talk, they settle it in thirty seconds because they agreed in advance that the group lead makes those calls. Nothing is done twice, nothing falls in a gap, and the work moves in the right order. The collaboration was the same. The coordination is what made it land.

Common Beginner Trap

Your Turn! Spot the Coordination Failure

Now you try. Read the short scenario below and diagnose it using the four-miss lens you just learned.

Context. A neighborhood group of volunteers is running a weekend bake sale to raise money for a local animal shelter. Everyone is enthusiastic and the group chat is busy. As the weekend approaches, a few things happen:

• Priya and Marcus both show up on Saturday morning having each baked and boxed the cookies, because each thought cookies were their job.

• No one has arranged a table and a permit for the stall, so the group is not sure they are even allowed to set up in the square.

• Several messages ask “how much should we charge?” but no one seems able to just decide, so prices are still unset the night before.

• The person making the signs is quietly waiting for the final list of items and prices before printing, and time is running out.

Your task. For each problem above, name which of the four coordination misses it is (duplicated work, unowned gap, stalled decision, or hidden dependency) and point to the specific clue in the scenario that gives it away. Each of the four problems points to a different miss, but watch closely: one of them sets off another, so read for how they connect.

Deliverable. A short list: each problem matched to its failure mode, with the tell-tale clue you used to identify it.

Then check your answer against the model solution found at the end of this chapter.

Let's Recap!

• Coordination manages the dependencies between people’s separate tasks; collaboration is working together on shared work ;

• Capable, willing, friendly groups still miss when no one manages the between ;

• The four recurring misses are duplicated work, unowned gaps, stalled decisions, and hidden dependencies ;

• Each miss has a tell-tale sign you can learn to spot early ;

• Willingness alone does not coordinate a group; someone has to do it on purpose.

With the coordination lens in hand, you are ready to build the foundation every group effort needs: a shared goal, clear ownership, a map of what depends on what, and who gets to decide. That is the work of the next chapter.

Model Solution

Here is how the bake-sale scenario breaks down against the four-miss lens.

• Priya and Marcus both baking the cookies is duplicated work. The clue: each “thought cookies were their job,” so the same task was done twice and effort was wasted.

• No table or permit arranged is an unowned gap. The clue: it is a necessary task that sat between everyone’s roles with no clear owner, so it simply did not happen.

• No one able to decide the prices is a stalled decision. The clue: people keep asking “how much should we charge?” but no one has the authority to just settle it, so the work sits still.

• The sign-maker waiting on the final item-and-price list is a hidden dependency. The clue: the signs cannot be printed until the prices exist, and that link was never flagged, so one task is quietly blocking another.

Each of the four problems maps to a different miss, but notice how they chain: because the prices were never set (the stalled decision), the signs could not be printed either (the hidden dependency). That is a common pattern, one unmanaged between setting off another. If you named at least three of the four correctly and pointed to a real clue for each, you have the diagnostic skill this chapter set out to build.