Set the Foundation: Shared Goal, Roles, Dependency Map, and Decision Rights

In the last chapter you learned to see coordination clearly and to name the four ways capable groups miss. Recognizing the problem is the first move; the next is to build a foundation solid enough that most of those misses never get the chance to happen. This chapter gives you the four pieces every coordinated effort rests on: a shared goal, clear ownership, a map of what depends on what, and a simple agreement about who decides what.

Write a Shared Goal With a Recognizable “Done”

Picture two versions of the same goal. The first says, “let’s make the reunion nice.” The second says, “host a three-hour Saturday afternoon reunion for forty relatives, with food, a photo corner, and a short family-tree slideshow.” The first sounds friendly and means something slightly different to every person who reads it. The second gives everyone the same picture. That difference is the whole point of a shared goal.

A shared goal is a single statement of what the group is trying to produce that every member reads the same way. It is not a mood or a direction; it is a concrete description of the finished result. When the goal is vague, people quietly fill the gaps with their own assumptions, and those assumptions are exactly where duplicated work and unowned gaps come from.

The quickest way to test a goal is the recognizable “done” test: could every member stand in front of the finished effort and agree, without arguing, that it is done? “Make the reunion nice” fails the test, because “nice” is a matter of opinion. “Forty relatives, food, photo corner, slideshow, three hours” passes, because anyone can check it. Write your goal so that finishing is something the group can point at, not something it has to debate.

Map Who Owns What (and Where to Go Deeper)

Once the goal is clear, every part of the work needs exactly one owner: the single person responsible for making sure that piece happens. Notice the word single. An area with two owners invites duplicated work, because each assumes the other has it; an area with no owner becomes an unowned gap. One owner per area is the rule that closes both holes at once.

Owning a piece of work does not mean doing all of it alone. The owner of “food” can recruit three cousins to cook; they simply remain the one person who can answer “is food handled?” without checking with anyone else. Ownership is about accountability for an outcome, not about working in isolation.

This is coordination-level ownership: who is responsible for which slice of the shared goal. It is a lighter question than the deeper one of team roles, seniority, and how people cooperate day to day. If you want to build those broader skills, the companion course Work Effectively in a Team covers roles, hierarchy, and cooperation in depth. Here you stay at the level that keeps the effort moving: one clear owner for each part of the goal.

Map Dependencies: What Depends on What

Back in the previous chapter you met the word dependency: one piece of work relies on another. A foundation makes those links visible before they trip anyone. The tool for that is a dependency map, a simple list of which tasks must wait for which. Two words make it easy to read: a predecessor is the task that must finish first, and a successor is the task that waits for it.

You do not need special software or a wall of arrows. A short table is enough. For each task, note what it depends on (its predecessors) and what it blocks (its successors). Here is a small example for a group hosting a family reunion:

Reading the table, you can see the order the work must happen in, and you can spot the tasks that will quietly hold up everything else if they slip. That is all a dependency map needs to do at this stage.

Assign Decision Rights: A Simple Decide / Consult / Inform Grid

The last foundation piece is the one groups most often forget: decision rights, meaning who gets to decide what. When this is unclear, even a tiny choice can stall the whole group, exactly the “stalled decision” miss from the previous chapter. You prevent it by agreeing, in advance, on three simple roles for each type of decision.

• Decide. The one person (or the smallest group) who makes the call and is accountable for it ;

• Consult. The people whose input is gathered before the decision, because they know something relevant ;

• Inform. The people who are told the decision after it is made, so no one is surprised.

Laid out as a grid, it looks like this for a family reunion:

The power of the grid is that it makes “who decides” boring, which is exactly what you want. When a menu question comes up, no one waits: the food owner decides, having consulted the cooks. If you ever meet a fuller version of this idea at work, it is often called RACI (responsible, accountable, consulted, informed). You do not need the full four-role model here; a plain who-decides, who is consulted, who is informed split is enough to keep a small group unblocked.

Building a Coordination Foundation

Let us watch the four pieces come together for a real effort: a family reunion for forty relatives.

First, the group writes a shared goal that passes the “done” test: “a three-hour Saturday reunion for forty relatives, with food, a photo corner, and a short family-tree slideshow.” Everyone reads it the same way.

Next, they assign ownership, one owner per area: Ama owns food, Ben owns the venue and date, Chika owns the slideshow, and Dan owns invitations and the headcount. No area has two owners, and none has none.

Then they sketch a quick dependency map. Confirming the date blocks almost everything, so it goes first. Invitations depend on the date; the headcount depends on invitations; the food order depends on the headcount. Writing this down, Ama realizes she cannot order food until Dan gives her the headcount, so they agree Dan will send it by a fixed day.

Finally, they set decision rights with a simple grid: Ama decides the menu (consulting the cooks); Ben, who owns the date and venue, acts as the group’s organizer and decides those (consulting close family); and Chika decides the slideshow content. Everyone is informed of each. Nothing important is left to “we’ll figure it out,” and the reunion has a foundation before a single dish is cooked.

Common Beginner Trap

Your Turn! Draft a Foundation

Now build a foundation of your own.

Context. A student club is putting on a showcase evening to present its projects to the rest of campus. About eight club members are involved, there is a small budget, and the event is in three weeks. Everyone is keen, but so far the plan lives in a busy group chat and nothing is written down.

Your task. Draft the foundation for this effort in three short pieces:

• A shared goal for the showcase that passes the recognizable “done” test ;

• A small dependency map (a “depends on / blocks” table) with at least four tasks, showing what must happen before what ;

• A decision-rights grid for at least two decisions, naming who decides, who is consulted, and who is informed.

Work through the three pieces in the order above: the goal shapes the tasks, the tasks shape the dependencies, and the dependencies show you which choices need a clear decider.

Deliverable. One page with the three pieces: the goal sentence, the dependency table, and the decision grid.

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

Let's Recap!

• A shared goal is one statement everyone reads the same way, and it passes the recognizable “done” test ;

• Every part of the work needs exactly one owner, which closes both duplicated work and unowned gaps ;

• A lightweight dependency map shows what depends on what, without Gantt charts or scheduling tools ;

• A simple Decide, Consult, Inform grid keeps decisions from stalling by settling who decides in advance ;

• Deeper work on team roles and relationships lives in the companion team course, not here.

With a foundation in place, the next job is to keep it in plain sight: the following chapter shows how to make the work visible with a simple tracker, status updates, and a steady coordination rhythm.

Model Solution

Here is one solid foundation for the campus showcase. Yours will differ in wording; check that it does the same jobs.

Shared goal. “A two-hour showcase evening in the main hall, three weeks from now, where all eight club members present their projects at staffed stations, with refreshments and at least fifty visitors invited.” Every member can point at the finished evening and agree it is done.

Dependency map.

Decision-rights grid.

If your goal passes the “done” test, your dependency table shows a workable order with no task left dangling, and your grid names a single decider for each decision, you have built a foundation that will prevent most of the misses from the previous chapter before they start.