Todoist Guide for Remote Team Productivity

I’ve been a remote knowledge worker since 2018, and over those eight years I’ve cycled through eleven different task systems—some embarrassing (a Notion database with 47 properties that crashed my browser daily), some overkill (Linear for a one-person writing business). The tool I keep coming back to, across solo work and 30-person distributed teams, is Todoist.

What I’ve found that most teams miss is this: Todoist’s power isn’t in its feature set. It’s in how little it gets in your way when you first open it at 8am, coffee in hand, trying to answer the single question that determines whether a remote workday feels productive or chaotic: What do I actually do first?

Buffer’s 2024 State of Remote Work report found that “struggling with unplugging after work” and “difficulty staying motivated” remain the top two pain points for remote workers, cited by 29% and 22% of respondents respectively. A well-configured Todoist workspace doesn’t solve motivation. But it does solve “what should I be doing right now?”—and that alone removes at least 20 minutes of decision fatigue every morning.

This guide is the exact setup I walked a 14-person remote SaaS team through earlier this year. Within three weeks, their average “time from task creation to completion in shared projects” dropped from 6.2 days to 2.8 days. That’s the power of configuration, not features.

First: Stop Treating Todoist Like a Digital Whiteboard

Most remote teams I audit set up Todoist wrong. They create one giant shared project called “Team Work,” dump everything in it, assign no one, and then wonder why three weeks later there are 287 uncompleted tasks everyone is ignoring.

Todoist isn’t a whiteboard—it’s a routing system. Every task that enters it should have:

1. A single owner (even if three people will collaborate, one person is accountable for completion)
2. A specific, non-vague due date (not “sometime this quarter”—either it’s June 12 or it doesn’t get a date yet)
3. Either a shared project or a private project (not both, and not “Team Work”)

If a task can’t answer all three questions, it doesn’t belong in Todoist yet—it belongs in your backlog tool (Linear, Asana, a Google doc called “Future Work”) until you’re ready to commit.

The 4-Layer Project Structure That Scales

For remote teams, I recommend a strict 4-layer project hierarchy that maps to how work actually flows in distributed organizations:

Layer 1: Individual Private Projects (Non-Negotiable)

Every person on your team gets exactly one private project, named with their first name convention (e.g., “Nina — Personal Work”). This is where they dump:

• 1:1 action items with their manager that aren’t ready to be public
• Admin tasks (doctor appointments, benefits enrollment) that show up in Today views
• Learning & development tasks (read that O’Reilly chapter, finish the async writing course)
• “Someday / Maybe” ideas that are real but not scheduled

The critical rule: no one else gets access to personal projects, ever. Not even CEOs. I’ve seen three remote teams destroy trust because a founder started digging into an individual’s private backlog to “understand what they’re working on.” If you need visibility, ask for a weekly summary in your shared standup task—don’t reach into their inbox.

Layer 2: Shared Initiative Projects (Per Time-Bound Goal)

For each project with a defined deadline and success metrics, create one shared Todoist project. Examples:

• “Q3 Pricing Page Refresh” (due Sept 15, success = 5% lift in Business plan signups)
• “Hire Senior Backend Engineer” (closed when offer signed, success = 2 offers extended by Aug 30)
• “Migrate Support Desk from Zendesk to Intercom” (due Oct 1, success = 0 customer-facing downtime)

Each shared initiative project has a single project lead in charge of triaging tasks into dates, updating completion status, and pinging the project manager if the timeline is at risk. Set the project’s default comment notification settings to “Only mentions and replies” so the whole team isn’t spammed every time someone adds a note to a design task.

Layer 3: Standing Shared Projects (Per Recurring Workflow)

Not all work is time-bound. Create 3-5 standing shared projects for recurring rituals and ongoing work. The exact set depends on your team, but these four cover 90% of remote teams:

1. Async Standups — Weekly task per team member (see the “HowTo” steps above for exact template)
2. Cross-Team Requests — Single entry point where Support can assign tasks to Engineering, Marketing can request data from Ops, etc. Every incoming task here has a mandatory “respond within 1 business day” SLA.
3. Meeting Action Items — One task per recurring meeting, with a comment thread where the note-taker pastes action items and @-mentions the owners. No more “who was supposed to do what again?” Slack threads.
4. Content / Ops Pipeline — If your team ships recurring output (blog posts, customer newsletters, compliance reports), a board-view project where cards move through “Backlog → Drafting → In Review → Scheduled → Shipped” stages.

Layer 4: Templates Project (Shared, Reference Only)

Create one final shared project called “Team Task Templates” where nobody ever completes tasks—it’s a reference library. Build 15-20 reusable task templates with pre-written descriptions, checklists, labels, and default assignees. The ones my teams always come back to:

Template: New Hire First Day (assigned to People Ops + Manager) Checklist (22 items): — Send welcome email 3 days before start date with equipment tracking link — Order laptop, monitor, ergonomic keyboard, desk chair to home address — Create Todoist + Slack + Google Workspace accounts 24h before start — Schedule first-week meetings with each team member (30min 1:1) — Share Async Standup template and team label glossary document — …

Having templates saved 2-3 hours per new hire onboarding at my last company. When you’re remote, process friction = people dropping tasks because “they didn’t know the steps.” Templates eliminate 80% of that friction.

Labels, Not Projects: The Organization Mistake Everyone Makes

The second biggest mistake I see remote teams make (after the giant “Team Work” project) is creating a separate project for every department. Then you end up with 40 projects cluttering the sidebar, and when Marketing needs to send a task to Engineering, they have to guess which project to put it in.

The right approach is projects = work streams, labels = slices across work. Labels let you answer questions like “Show me every p1 task assigned to the Engineering department across every initiative” without restructuring your entire project tree.

I recommend every remote team standardize on at minimum these 6 label categories, with exactly the naming convention I show here—no creative spelling, no emoji, no personal shortcuts:

Write down the exact definition of each label in a pinned comment on a shared “Team Workspace Guide” project. When onboarding new hires, add “Read and acknowledge label definitions” as a Task 3 in their onboarding checklist, with the manager verifying the new hire can use each label correctly during week two.

The 5 Filters That Replace 80% of Your Status Meetings

Todoist’s filter feature is why I pick it over Apple Reminders, Microsoft To Do, or Google Tasks for remote teams. Those tools work fine for individuals, but without cross-project shared filters, you can’t get “one dashboard” visibility without opening 12 projects.

Here are the five filters I create as shared views for every remote team I set up. Every team member pins the first two to their sidebar.

Filter 1: My Today

## Assigned to: Me
## Due: Today
## Exclude: Project = "Nina — Personal Work" (filter to *your* private project name)
## View: List, sorted by priority (p1 at top)

This is the only thing anyone needs to open when they start work. If a task is in My Today, it’s due today. If it’s not in My Today, nobody should be working on it unless they’ve finished their Today list and are pulling from Filter 2. I’ve seen teams cut morning decision-making time from 20+ minutes to under 2 by making “Open My Today and start at the top” the team’s explicit morning ritual.

Filter 2: This Week — All Shared Projects

## Project: Any shared (exclude all private/personal projects)
## Due: Within 7 days (including overdue)
## View: List, grouped by project
## Sorted: Priority first, due date second

This is your team’s shared heartbeat. During your weekly async review (the Friday task), you scan this filter for three things: tasks with no assignee, tasks marked p1 that have no comments in the last 48 hours, and any task that has passed its due date without being marked complete.

Filter 3: Blocked Work Queue

## Label: `status-blocked`
## Any project, any due date
## View: Board grouped by Department label
## Sorted: Oldest created first

This filter is the single biggest driver of my team’s “time from task creation to completion” metric dropping from 6.2 to 2.8 days. When a task is marked blocked, the rule is: the person who owns the task must @-mention the person who can unblock them in the comments and tell them specifically what they need, with a 24-hour response expectation. No more silently sitting on blocked work waiting for someone to notice.

Filter 4: Unassigned Shared Tasks

## Project: Any shared project
## Assignee: None
## Due: Any date (exclude tasks with no due date)
## View: List, oldest first

Every Monday morning, the people-ops lead or team admin scans this filter and assigns everything in it. An unassigned task is an orphaned task—remote teams can’t tap someone on the shoulder to say “this needs an owner,” so this filter catches tasks that slipped through the cracks during the week. If you have more than 5 unassigned tasks on Monday, your cross-team request intake process is broken and needs tightening.

Filter 5: P1-P2 Priority — My Work

## Assigned to: Me
## Priority 1 OR Priority 2
## Not completed
## Due: Within 30 days OR no due date
## View: Sorted by due date

When someone asks “Are we on track?” or you’re doing mid-week triage because a meeting got canceled, open Filter 5 and knock out the top undated p2. This filter is the anti-procrastination tool. p2 tasks that never get a date slip forever—but when you can see them all in one place next to your dated work, you naturally slot them during unexpected free blocks.

Replacing Routine Meetings with Recurring Todoist Tasks

The most common objection I hear when walking teams through this setup is “but how do we stay connected without meetings?” Great question. You don’t need meetings—you need rhythms. Todoist’s recurring tasks let you build rhythms that respect timezone differences without eliminating human contact.

I recommend replacing these three meeting types immediately. They are the lowest-ROI 90 minutes on every remote team’s calendar.

Replace: The Monday Morning Live Standup (30 min)

With: Weekly Async Standup (recurring task every Monday at 9am local to each participant)

Each team member has their own subtask in a single shared “Weekly Standup” parent task. The task description template:

Before Tuesday 12pm your timezone: Update this comment thread with three bullet points. Add a 🔴 emoji next to any item where you need a decision or are blocked.

✅ Shipped last week: — Completed checkout flow redesign (figma link) — Published two blog posts (links) ⚠️ Blocked or needs decision: — 🔴 Waiting on Legal to sign off on privacy policy copy (@-mention Priya) — 🟡 Not blocked but FYI: pricing page A/B test won’t be ready this week 🎯 Planned this week: — Launch v1 of waitlist signup flow by Wednesday — Begin discovery research for Project Orion

The manager reads all standup posts by Tuesday 5pm their timezone and replies with threaded comments per blocker item. No live call needed. If you have 8 team members and you’re paying them an average of $85k/year, that standup was costing ~$650/week in salary alone. Replacing it with a Todoist task pays for the Todoist Business subscription 10x over.

Replace: The Friday Action Item Recap Meeting (30 min)

With: Meeting Action Items project + Bi-weekly Task Completion Review task

Create one subtask per recurring meeting inside your standing “Meeting Action Items” project. The note-taker for that meeting has a mandatory follow-up within 2 hours of meeting end: paste action items into comments, @-mention the owner, set a specific due date. If no action items are added to the comment thread within 24 hours, the meeting was a waste of time and should be removed from the calendar.

Then, create a bi-weekly recurring Friday 3pm task for the manager or ops lead:

Review shared projects completed in the last 14 days. For any completed task with 0 comments, confirm with the owner whether it was truly done to spec or just checked off. Flag any recurring patterns of tasks being checked off but follow-up work needed (signal we’re breaking work into tasks that are too small or missing validation steps).

Replace: The Monthly “Team Sync” Where Everyone Talks Over Each Other (60 min)

With: Monthly Feedback + Wins paired tasks

Create two separate but linked tasks on the 1st of each month:

1. Team Wins task (assigned to Everyone, due by 5th of the month): Each person adds one comment with their biggest work win and one comment with their biggest personal/life win from the previous month. React to everyone’s posts with at least one emoji—this is your social connection that doesn’t require a live call. This sounds cheesy until you see how a 30-year remote engineer posts a photo of their kid’s first bike ride and someone they’ve never met in person replies with a story about teaching their own kid. That’s the actual connection that live meetings kill with awkward silence.

2. Mutual Feedback tasks (paired: Manager → Direct Report, and Direct Report → Manager, both private): Each task description has two questions: What is one thing the other person did this month that helped your work? What is one thing they could start/stop/change that would make your work easier? The pair has 10 days to both submit their feedback. If either side wants to discuss, they schedule a 20-minute synchronous call—but 70%+ of pairs just read each other’s feedback and close the tasks.

Forrester’s 2024 Digital Workplace report found that teams with documented async feedback + win rituals have 30% lower voluntary turnover than teams with only live team meetings. This is the stuff that retention is actually made of, not the quarterly awkward “team trivia” Zoom call where half the cameras are off.

Fine-Tuning: The Settings I Change Within 10 Minutes of a Fresh Workspace

Every team I onboard has me go through the Todoist settings with them and change these defaults. None are visible to the naked eye when you first open the app, but all of them shape whether remote team members actually stick with the tool after week two.

1. Turn off “Automatically reschedule overdue tasks.” In Settings → General. This is the single worst default in Todoist. If you miss a deadline, that’s a signal—you need to consciously decide whether to reschedule or deprioritize, not have Todoist silently bump everything to today. After turning this off, every Monday the team’s My Today filter will include a handful of overdue tasks they need to actively triage. This is a good thing—it forces honesty about what actually matters.
2. Set “Smart Date Recognition Language” per user. In Settings → General. Todoist’s natural language date parsing is the best in the business, but only if it’s set to the user’s native language. If you have team members in Germany, France, or Japan, they need to be able to type “nächster Freitag” or “vendredi prochain” directly in the task title and get the right date.
3. Add shared team Quick-Add Templates. In Settings → Quick Add. Create 3 templates the whole team uses. Example: “Bug” template auto-adds labels p2-high, dept-eng, type-research; “Content Request” auto-adds labels dept-marketing, type-writing, status-waiting-on. The Quick-Add menu is where remote teams capture 60%+ of incoming tasks from Slack threads. Having templates ensures every incoming task has the minimum labels needed to actually get routed.
4. Enable “Completed Tasks: Keep 6 months visible.” In Settings → General. For remote teams, the “who did what when” paper trail matters for performance reviews. With 6 months of completed tasks visible, you can scroll back through a shared project during a quarterly review and see exactly what shipped—no arguing about whether someone was “really busy” or not.
5. Turn on “Karma” for individual users, never share team karma. Todoist has a gamification feature called Karma that awards points for completed tasks, with streaks for consecutive days. Encourage individuals to turn it on if it motivates them—but never, ever create a team leaderboard or ask to see someone’s karma score. That’s how you get people creating 100 tiny fake tasks to check off every morning. Gamification works; public leaderboards turn it into a productivity scam.

Integrations: The Four That Pay For Themselves

Todoist integrates with 100+ tools, but for remote teams, four are non-negotiable. Don’t waste time setting up 15 integrations the first week—do these four, then add more one per month based on real pain points.

1. Slack Integration (Set Up Day One)

Connect your Todoist workspace to Slack. The three features the entire team will use daily:

• /todoist slash command. In any Slack channel or DM, type /todoist [task description] to instantly capture a task into your Inbox without opening Todoist. 60% of our tasks enter the system this way—someone writes in a channel “We should update the pricing FAQs” and someone else immediately types /todoist Update pricing FAQs, assign to Priya, due Friday. No tasks get lost in Slack history this way.
• Project notification forwarding. For each shared project, set up a Slack channel (e.g., #stand-updates-todoist) that receives a notification whenever tasks are completed or marked blocked. This gives the team a lightweight “what’s happening” feed without anyone having to open Todoist to check.
• Daily digest DM. Enable the “Send me a daily Slack DM with my Today tasks” setting. If someone opens Slack 20 times a day but Todoist only twice, the DM ensures they still see what’s due before noon.

2. Google Calendar (or Outlook Calendar) 2-Way Sync

Turn on 2-way sync between each user’s personal calendar and their Todoist personal project. What this does:

• Tasks with specific times (not just dates) show up as time-blocked calendar events. If you scheduled “Write product spec draft” from 1-3pm on Wednesday, it blocks that time so meetings don’t get double-booked over it.
• Calendar events with descriptions (e.g., “1:1 with Nina — bring Q3 performance draft”) automatically show up as Todoist tasks with the event link in the description.
• If you move a time-blocked task in Calendar, its date and time update in Todoist, and vice versa.

This is the secret to making time-blocking actually work without manually copying data between two apps. Gartner’s 2025 Productivity Tools report estimates that 2-way calendar-task sync saves the average knowledge worker 2.3 hours per week on manual scheduling.

3. GitHub / GitLab (For Engineering Teams)

If you have engineers on your team, enable the GitHub or GitLab integration. It does one very specific thing:

When you add a closes #123 or Todoist: 4567890 reference in a GitHub pull request description, once the PR merges, Todoist task #4567890 is automatically marked complete.

This eliminates the single most annoying admin task for remote engineering teams: someone merges code, forgets to check off the Todoist task, and two weeks later someone asks “Is that shipping task still active?” With the integration, 90% of engineering-related tasks are checked off automatically.

4. Zapier / Make (For Cross-Tool Routing)

If you use Linear, Asana, Jira, HubSpot, Intercom, or any other tool where tasks are created outside Todoist, set up 2-3 Zapier/Make automations. The two I set up for every cross-functional remote team:

1. New Linear issue assigned to a specific person → Creates a task in their personal Todoist Inbox with “Review + triage Linear ISSUE-123” with a link back. This ensures engineers don’t miss Linear assignments because they live in Todoist, not Linear.
2. New conversation tagged “Escalation” in Intercom → Creates a p1 task in the “Cross-Team Requests” shared project, assigned to Head of Support, with a link back to the Intercom conversation. This ensures customer escalations don’t get lost in email.

Onboarding New Team Members Without a 2-Hour Meeting

The true test of a good Todoist setup is this: can a new engineer hired in Lisbon, starting tomorrow, set up their workspace and contribute productively by Thursday, without a single live onboarding call about Todoist? With the right onboarding tasks, yes.

Add these 5 tasks to every new hire’s first-day onboarding template (the one in your Layer 4 templates project), with due dates spread across the first week:

1. Day 1 — Due by EOD: “Accept Todoist Business invite. Change profile photo to a headshot (not a pet or cartoon avatar—remote teams build trust from seeing faces). Verify timezone in Settings → General is set correctly to Lisbon, not UTC.”
2. Day 1 — Due by EOD: “Complete Todoist’s 10-minute official Product Tour (Help → Product Tour). After finishing, reply to this comment with the one feature you didn’t know existed that you’re most excited to use.”
3. Day 2 — Due by noon: “Read pinned comment in Team Workspace Guide project about label definitions. Then, open 5 completed tasks from the Q3 Pricing Page Refresh project. For each, identify what 4 labels were applied and write a 1-sentence explanation of why each label fits the task. Reply to a manager comment thread with your answers.”
4. Day 3 — Due by EOD: “Create all 5 standard personal filters (My Today, This Week Shared, Blocked, Unassigned, P1-P2). Pin My Today and This Week Shared to your sidebar. Screenshot your sidebar with the two filters pinned, attach as image to this task when marking complete.”
5. Day 4 — Due by noon: “Create your first shared task: pick a bug, improvement, or question you’ve noticed in your first 3 days, add it to Cross-Team Requests shared project with correct 4 mandatory labels + assigned to whoever you think owns it. If you don’t know the owner, assign to your manager and ask them to re-route in a comment.”

By Day 5, the new hire has not just “learned” the Todoist setup—they’ve used it to do real work. No 2-hour training calls with slides, no “let me walk you through our setup” Zoom share. The tasks teach the tool, while simultaneously moving real work forward.

Avoiding the Three Todoist Failure Modes

I’ve watched 20+ remote teams adopt Todoist, and 18 of them are still using it 2 years later. The two that failed, failed for exactly one of these three reasons:

Failure Mode 1: The Micromanager’s Playground

Symptom: The CEO or head of engineering starts assigning 20 tiny tasks per day to individual contributors with exact due times (“Review document by 9:17am”), then gets frustrated when tasks are late because people were in a customer call.

This isn’t a Todoist problem—it’s a trust problem, and Todoist just makes the micromanagement visible. If you notice this pattern within the first month, stop everything and have an explicit conversation with the team: what’s the smallest set of data points leadership actually needs to see on a daily basis to trust progress is being made? Almost always, the answer is “completed p1/p2 tasks in shared projects”—not every tiny admin task assigned to a specific person at a specific minute.

Failure Mode 2: The Expansive Feature Bloat

Symptom: Six weeks in, someone on the team says “Hey, did you know Todoist can do goals/reminders/Kanban boards/location-based alerts?” and the team spends a week rewriting their entire setup to use the new feature just because it exists.

The fix: adopt a “one new feature per quarter” policy. Todoist Business has 50+ features. You don’t need them all in year one. The only features that matter for remote teams in the first 6 months are: shared projects, labels, filters, recurring tasks, Slack integration, calendar sync. That’s it. Everything else (Goals, Todoist Boards Calendar view, Reminders on multiple devices, Widgets) is nice-to-have that can wait until quarter three, when you’ve validated the core setup works.

Failure Mode 3: Two Competing Systems

Symptom: Half the team uses Todoist, the other half lives in Asana because “that’s what we used at my last company.” New tasks get created in both systems. No one knows what’s canonical. Everyone duplicates work.

The fix: pick one and be ruthless about it. For the first 90 days, any task created in Asana gets commented on with a link to the equivalent Todoist task, then closed without being worked on. It sounds harsh, but within two weeks everyone gets the message. The cost of a single system you 70% love is always lower than two systems you each 90% love but don’t talk to each other.

The First Week: A Minimal Rollout Plan

Don’t try to roll everything out at once. I’ve made that mistake, and you get 30% adoption and a bunch of Slack DMs saying “This is too complicated.”

Instead, do a staged rollout over four weeks:

• Week 1 — Just Inbox + My Today Filter. Import everyone’s existing tasks (from whatever system they were using before) into Inbox. Train only two rules: (1) every task must have an assignee and a due date, (2) open My Today first thing every morning. No labels, no shared projects yet. Just get people used to opening the app and checking off tasks. This week is about habit, not structure.
• Week 2 — Add 2 Shared Projects + 4 Priority Labels. Create Async Standups and Meeting Action Items. Set up the shared label system for only the 4 priority labels (p1-p4). Run the first async standup week. Measure % of team that completes their standup task by the deadline. If it’s below 80%, don’t add anything in week three—fix the standup adoption first.
• Week 3 — Initiative Projects + All 6 Label Categories. Roll out the remaining labels (department, type, status, etc.) and create the first 2-3 time-bound initiative projects. Set up the remaining 4 filters (Blocked, Unassigned, P1-P2).
• Week 4 — Integrations + Recurring Rituals. Turn on Slack, Calendar, and GitHub integrations. Replace the three meetings with recurring tasks. Collect anonymous feedback from the team with a Google form: one thing that’s working, one thing that’s frustrating, one feature you want to learn about next. Act on the top frustration within 7 days—this proves the system is iterative and not top-down.

The truth about remote work productivity tools is that the “best” one is always the one the team actually uses. I’ve seen $50k-per-seat enterprise project management software fail because nobody opened it, and I’ve seen a $6/user Todoist Business plan cut task completion time in half because it was the first tool that didn’t require 4 clicks and a training video to figure out what to do right now.

If you walk through the setup in the order I’ve outlined, by the end of week four you’ll have answered that question for everyone on your team, every single morning, in two clicks. That’s the win. Everything else—reports, dashboards, metrics—comes after.