Let me tell you about a trap I used to fall into.

I’d hop out of a team video call and close the tab, feeling good about the meeting’s progress. Then, a few days later, my mind would go back to that meeting, trying to remember who took ownership of a particular task. 

The last time this happened, I racked my brain to remember who on my team was responsible for updating the “About Us” webpage. Three days had passed since the meeting, and this simple revision hadn’t yet been made.

When I asked around, I found out why. Two people thought another team member had it covered. Another person thought it was just mentioned as a good idea and not as an actual task.

I ended up changing the page myself because I couldn’t stand looking at the outdated paragraphs any longer. And, I had already taken an hour away from my scheduled monthly reporting to hunt down the person accountable for making the change. What’s another thirty minutes?

This happens in small teams all the time. 

Not because anyone drops the ball on purpose. But because teams talk about getting tasks done without directly assigning them to anyone. 

Let’s talk about why this happens, who it affects, and how a simple, productive accountability system can turn things around (as it did for me). 

The myth of shared accountability

In your next team meeting, keep your ears open for someone who tries to wrap up an agenda item with “Let’s” phrases like:

• “Let’s keep this on our radar.”

• “Let’s all review the draft and leave comments about its tone.”

• “Let’s make sure we have something for the exec board to look at.”

These phrases imply collaboration and avoid putting someone on the spot. They also keep the meeting moving along. 

That collaborative tone is great for morale. (And, who doesn’t like meetings that move along?)

I used these phrases a lot because I didn’t want to be seen as controlling or bossy.

But I ran into a big problem when using “let’s” phrases. By suggesting a task should be shared, I assigned it to no one in particular. 

I thought about how many agenda items were typically on my team meetings. Maybe six?

If half those items get assigned to “let’s,” that’s three potential coordination failures waiting to happen each week. 

Then, I imagined what next week’s meeting will look like with three “I didn’t know that was my task” discussions on the docket. 

That was enough to make me reach for my meditation videos. I was truly freaked out by what a mess I’d caused.

How unclear accountability hurts your team

I learned that when ownership of work is unclear, team productivity suffers in a big way.  

If a manager notices a task with no clear owner, they spend time tracking down who should handle it, and that confusion spreads to the person who might have been responsible. And if leaders and individual contributors are both confused, no one’s productive. 

How unclear accountability impacts leaders

Many lean teams don’t have a project manager or ops person to catch ownership gaps at meetings. 

So it’s usually a team leader who spots a task’s vague ownership either during a review meeting or when a stakeholder asks for an update. To get to the bottom of this mystery, they’ll spend time tracking down owners, which takes away from the strategic work that’s normally expected of them. 

How unclear accountability impacts individual contributors

Sometimes an IC misses who was assigned a task during the meeting. Maybe they were looking at their notes or multitasking. Or maybe the assignment happened in a side conversation. 

However it happened, the IC is stuck wondering if the task is theirs.

Some ICs hope a colleague grabbed the assignment. And they move on to other work.

But some ICs don’t want to look like they weren’t paying attention. So they just start the assignment. 

If two people make that same call, the team ends up with duplicate work.

How unclear accountability impacts stakeholders

Stakeholders sit outside typical day-to-day work, but they still need to know what's happening. 

But if ownership is unclear, they’re stuck guessing who to ask.

They might first ping the project leader. If the leader doesn’t have an answer, the stakeholder moves on and asks a few ICs who are also unclear on who’s accountable.

This needless back-and-forth sends a clear message to the stakeholder that this team doesn’t have its act together.

Even if the team delivers the work in great shape, the stakeholder can’t help but feel underenthused. It takes too long to get a straight answer on accountability, and this lack of clarity often adds needless days (or more) to a project.

The growing cost of repeated confusion

If a team lead messages a few people to find out who’s accountable for a task, it’s no big deal. Same if an IC apologizes for not knowing a task was theirs. Or if a stakeholder pokes around to find the right person for a status update. 

But if these scenarios keep happening, team trust starts to fray.

The leader wonders why the team can’t sort out accountability on their own. ICs wonder why ownership wasn’t clear from the start. Stakeholders stop trusting they'll get straight answers and start checking in more often or escalating to managers. Team members become less willing to collaborate on future projects. Which is ironic, given that the vague language we discussed earlier was often meant to feel collaborative.

There’s also an issue of stalled work. When leaders, ICs, and stakeholders don’t know who’s accountable, simple projects become huge undertakings. Not because the work was hard, but because everyone wasted time figuring out who was supposed to do what, avoiding the conversation, and then scrambling or duplicating efforts that had to be sorted out later.

Why ambiguity isn't autonomy

Some teams resist explicit ownership because they value collaboration, trust, and flexibility. Assigning tasks can feel like a step away from self-direction.

But clear accountability makes self-direction possible. When people know where they stand, they can then self-direct without second-guessing whether they’re stepping on someone else’s toes (or frantically sending messages to find out who’s accountable). 

Here are two scenarios of teams that value trust, flexibility, and self-direction. Both have a meeting on August 10 with a deliverable by the end of the month. One team shies away from assigning explicit ownership, and the other makes ownership crystal clear.

Team 1 (unclear accountability)

The team leader says, “We need to update the sales deck by the end of the month.” 

Everyone nods. 

The meeting moves on. 

August 28 comes around, and the team leader hasn’t seen an updated deck. She soon realizes that no one claimed to take it on.

She spends an hour on Teams to figure out who can make the updates quickly. Her top choice is overseas at a conference for the rest of the week, and they can’t help.

Eventually, she gets another person to reluctantly agree to update the deck, but they’re not experienced with the sales software needed to update the revenue figures.

They spend time asking questions about which metrics to pull, how to access the data, and whether they’re updating the right sections. Each question requires a back-and-forth that interrupts the team leader’s schedule.

Team 2 (clear accountability)

The team leader says, “We need to update the sales deck by the end of the month. Alex, can you take that?” 

Alex agrees and says he’ll share the updated deck with the team on August 29.

Everyone nods.

The meeting moves on. 

Alex executes independently on the project. He updates the pricing section first because he knows that’s what clients ask about most. He pulls in the latest metrics from a section of the software he knows well. He delivers the revised deck on time.

The second version took three extra seconds at the beginning of the meeting, yet saved hours of coordination later on. 

Try this simple accountability system for your team

Making delegation and accountability clear requires three things:

1. Assign only one person per task.

2. Schedule a deadline for each task or subtask.

3. Review progress in one shared place.

Here’s how this system works in practice with Todoist.

Assign only one person to a task 

When you create a task in Todoist, assign it by selecting the person icon.

If a task requires collaboration, one person still owns the delivery of a given task. Others contribute, but one person makes sure it gets done.

Say, a “Launch new pricing tier” gets assigned to Sarah, a product marketing manager. This work is not hers alone: she’ll work alongside colleagues Omar and Alex to get this done.

In Todoist, Sarah has two options to collaborate transparently while staying in charge of the new pricing tier launch. She can create subtasks for Omar and Alex …

… or she can mention her colleagues and their work in the comments of the main task.

With either option, this Todoist task lets the whole team know that Sarah is accountable for the launch, and Omar and Alex will provide valuable assistance to her.

Schedule a deadline for each task or subtask

A deadline with team-wide visibility creates a shared expectation for when a work assignment should finish. 

In Todoist, deadlines can be added with the {} shortcut. Within the curly brackets, use natural language in setting a deadline. Type an exact date like {April 21} or something more forward-looking like {next Tuesday} 

Team members who value self-direction also add a due date to indicate when a task should start. So, if someone has assigned you a deadline for a deliverable and you know it will take three days to complete the work, set a due date three days before the deadline.

With due dates, no curly brackets are needed. Just type a due date as if you’re speaking, like “next Friday,” “in two weeks,” or “Mar 20,” and Todoist figures out what you mean. 

Or use hands-free, voice-activated Ramble set a due date.

Once due dates and deadlines are set, teams can plan their work accordingly.

Review progress in one shared place

When you set tasks in a Todoist team project, everyone with access to the project can see its tasks, owners, and due dates. 

If you want to check what’s coming up, open the project's Upcoming view.

To see which deadlines are fast approaching, filter by deadline.

This single source of accountability makes ownership explicit, visible, and consistent. 

The benefits of clear team accountability 

Once your team puts this accountability system into practice, they’ll soon see the following boosts in productivity and morale.

Team members know exactly what’s theirs

Your team opens Todoist and sees their tasks. The mental energy that used to go into figuring out ownership now goes into getting a task done.

Decisions happen faster

When team members need an answer, they can check the owner in Todoist and reach out to the accountable person directly. This ownership-at-a-glance system often saves your team hours, if not days, of tracking down the right person.

Leaders can see progress at a glance

Leaders like you can open a shared project and check the Upcoming view to instantly see what everyone's working on and when it’s due. This quick action lets you spend more time on strategic work instead of tracking down updates.

Work flows without interruption

When tasks have clear owners and deadlines, people know when to move forward.

Say, you’re waiting on a designer to finish mockups and the new person in finance to update international currency options before you share a new pricing page with your team. 

Once they check off their work in a shared project, you’ll see it immediately and can safely add the pricing page reveal to the agenda for your next team meeting.

With this system in place, you can focus on leading, and your team members make confident, independent decisions.

Clear accountability helps your team do better work. When people know what's theirs, they execute with confidence while you focus on strategy.

Start with one shared project this week. 

Look at all open tasks. Assign each one to a single person, add a deadline, and put it in a place where everyone can see it. 

And when you use Todoist, you’ll spend less time figuring out who’s doing what and more time moving work forward.