Skip to content
Floskool

Chapter 1 · The resource

One owner per task

Free lesson 8 minGroup Flopilot

Follow this course in your space: your progress is saved, and the community answers your questions.

Follow for free

"We should call the supplier back." "Someone needs to update the website." Everyone agrees, the meeting ends, and a week later nobody has done anything. Everyone assumed someone else was on it. That's the "someone should" problem: a task that belongs to everyone belongs to no one.

One name per task

The rule is simple: every task carries one name, the person who makes sure it gets done. They can get help, split up the work, ask for opinions. But if the task stalls, they're the one people come to, and they know it.

Two names on a task is often where the confusion starts: each waits for the other to begin. If two people genuinely work together, split the task into two subtasks, one name each.

In meetings, never leave a decision without a name:

"Okay. Who's taking this, and by when?"

That one sentence, repeated for every item, is often enough to change how a team works.

Who does it, who approves it, who stays informed

For important tasks, one name doesn't tell the whole story. Three roles are enough to prevent most misunderstandings:

  • Who does it: one name, responsible for the task from start to finish.
  • Who approves it: the person who says "good to go" before it goes out (one name too, if possible).
  • Who stays informed: the people who need to know it's done, without stepping in.

You don't need this for "order printer ink." It's very useful for "send the quote to the client" or "post the schedule for the nonprofit's fall festival."

The table to copy

TASKS AND OWNERS: [project or team]

Task | Who does it | Who approves | Who's informed | Due | Status
[Send the Johnson quote] | [Leah] | [Mark] | [Sam] | [5/12] | In progress
[Update the Pricing page] | [Sam] | [Leah] | [Everyone] | [5/15] | To do
[Follow up with the printer] | [Mark] | [nobody] | [Leah] | [5/10] | Done

Keep the table where the whole team can see it. A shared spreadsheet or a project tool with one owner per task works just fine.

Example: a four-person web agency

Leah (owner and sales), Mark (project manager), Sam (developer), Ines (graphic designer). Before, tasks were jotted down in a chat thread and everyone grabbed what they could. Client follow-ups fell through the cracks.

What they put in place:

  • Quotes: done by Mark, approved by Leah, Sam informed (for scheduling).
  • Mockups: done by Ines, approved by Mark before the client sees them.
  • Launches: done by Sam, approved by Mark, Leah informed (for invoicing).
  • Client follow-ups: always Mark, whatever the topic.

The concrete result: when a client writes in, everyone knows who replies. And Leah now only approves quotes instead of looking at everything.

Example: a nonprofit

A neighborhood association is organizing a yard sale. Before, the board would say "we'll handle the flyers, get the permit, find volunteers." The day before, the permit was missing.

What they put in place:

City permit | Does: Nadia | Approves: the board chair | Informed: board
Flyers and social media | Does: Tom | Approves: Nadia | Informed: everyone
Volunteer schedule | Does: Hugo | Approves: nobody | Informed: all volunteers
Snack stand | Does: Claire | Approves: the treasurer | Informed: Hugo

With volunteers, always add a date. Everyone gives time when they can: the date keeps the task from sliding to the night before.

Signs that "someone should" is back

  • Tasks with no name in your list
  • Tasks with three names
  • Phrases like "I thought you were handling that"
  • The same question asked to several people
  • Meeting notes with no "who" and no "by when"

Your turn

Open your team's task list (or write it if it doesn't exist). Find every task with no name or several names. Put a single owner on each one, and for the three most important, also fill in "who approves" and "who stays informed." Share the table with the team before your next meeting.