[INSERT INTRO VIDEO]

The invite is ready. The workspace is set up. (And if not, don’t fret, we show you how in the Set Up Your Team Workspace course.)

But before anyone logs in, there's one conversation worth having – because how you make the case for this change will determine how the team receives it.

The champions who get the smoothest rollouts aren't necessarily the most enthusiastic. They're the ones who make the case differently for each person.

By the end of this lesson, you'll know how to find each person's reason – and how to frame the change around it.

Your reason isn't their reason

The thing you love most about Todoist is almost certainly not the thing that will matter most to your team.

You might love it because everything lives in one place and nothing gets lost. A manager on your team might care more about seeing what everyone's working on without having to ask. An IC might want to stop being interrupted mid-task to give status updates on things they're already handling. A field worker might just need a reliable way to capture a job request before they get to the next one and forget it.

Same tool. Four different reasons. Lead with yours, and three of those people hear a solution to a problem they don't think they have.

Find their frustration first

Before you make the case to anyone, ask one question: what's the most frustrating thing about how the team coordinates work right now?

Keep it simple and open. Their answer is the case you make – whatever they name, there’s a good chance Todoist will alleviate that for them. Your job is to connect those two things.

Start with what's broken

There's a difference between "we're moving to Todoist" and "I want to fix the situation where tasks disappear into the Monday thread, and nobody's sure who picked them up."

The first is an announcement. The second is an invitation – because it names something the other person already knows is a problem. When the case for change starts with the problem, the tool becomes a more compelling solution. That's a much easier conversation than asking someone to evaluate a tool they haven't decided they need yet.

Next: What to do when someone pushes back

In the next lesson, you'll learn how to handle the objections every champion hears – and why responding to them as product objections almost always makes the conversation harder.