Understanding What Motivates

As a team lead working across teams, you rely on people who do not report to you. You need their cooperation, their ideas, and their best effort. But these coll

Level: Team lead
Setting: Cross-team
Core skill: Reading individual drivers
Common pitfall: One-size-fits-all rewards
Practice to try: A what-matters conversation

What this looks like in real work

As a team lead working across teams, you rely on people who do not report to you. You need their cooperation, their ideas, and their best effort. But these colleagues have their own managers, their own priorities, and their own reasons for doing what they do. Understanding what motivates each person is not a nice extra; it is the core of getting things done together. When you misread what drives someone, you might offer the wrong thing—more visibility when they want stability, or a new challenge when they crave predictability. The result is frustration on both sides and work that stalls.

In cross-team settings, motivation often shows up in small choices. Who volunteers for the tricky integration? Who stays late to help another team meet a deadline? Who quietly keeps the shared tracker up to date? These actions hint at what people care about. Some are driven by solving hard problems. Others want to feel part of a winning group. Others value autonomy or the chance to learn something new. Your job is not to guess but to notice and ask. When you read individual drivers accurately, you can align requests with what people already want, making collaboration smoother and more genuine.

This skill is especially important when you have no formal authority. You cannot order someone from another team to care. You can only invite, persuade, and create conditions where their own motivations do the work. That starts with seeing each person as an individual, not as a role or a resource. It means paying attention to what they talk about, what they avoid, and what they light up about. Over time, you build a mental map of what matters to each key collaborator, and that map guides how you approach them.

Why it trips people up

The biggest trap is assuming that what motivates you motivates everyone. If you love public recognition, you might shower praise in team meetings, only to find that a quiet colleague feels embarrassed. If you thrive on tight deadlines, you might push for faster cycles, not realizing that someone else needs more time to do quality work. This one-size-fits-all approach feels efficient, but it often backfires. People disengage when the reward or pressure does not match their internal drivers. They may comply on the surface while quietly withdrawing their best ideas.

Another reason this trips people up is that motivation is invisible. You cannot see it directly, and people rarely announce it. In cross-team work, you have fewer chances to observe someone over time. You might interact only in meetings or through messages. That makes it tempting to rely on stereotypes or on what worked with someone else. But each person is different, and the same person can change over time. What motivated a colleague last year—a new skill, a chance to lead—may not motivate them now if their circumstances have shifted.

Finally, leaders often confuse motivation with satisfaction. A person can be satisfied with their job and still not be motivated to go the extra mile on your project. Satisfaction is about the absence of complaints; motivation is about the presence of drive. To read drivers well, you need to look beyond surface contentment and understand what someone actually wants to achieve, learn, or protect. That requires curiosity and humility, because you will sometimes get it wrong.

The mistake that quietly hurts

The mistake that quietly hurts is defaulting to a single reward system for everyone. In many workplaces, the go-to motivators are money, titles, and public praise. These are not inherently bad, but they are not universal. When you use them indiscriminately, you may accidentally demotivate people who value different things. For example, offering a bonus for extra work might feel transactional to someone who wanted to be part of a meaningful project. Promoting someone into management might frustrate a person who loves hands-on technical work. Public praise might embarrass someone who prefers private acknowledgment.

This mistake is quiet because it rarely causes an immediate blow-up. Instead, it erodes trust and engagement over time. People may stop volunteering for cross-team efforts. They may become less communicative. They may do exactly what is asked and nothing more. You might not notice until a key project stalls or a talented colleague disengages. By then, the damage is harder to repair. The root cause is not malice but a lack of attention to individual differences.

In cross-team settings, this mistake is even more costly because you have less margin for error. You cannot rely on formal authority to smooth things over. If you misread someone's drivers, they can simply choose to prioritize their own team's work. The quiet hurt spreads: other teams see that collaboration is not rewarding, and they pull back too. Avoiding this mistake means treating motivation as a puzzle to solve for each person, not a lever to pull the same way every time.

A practice you can repeat

A concrete, repeatable practice is the what-matters conversation. Set aside twenty to thirty minutes with a key cross-team colleague. Frame it as a chance to understand how you can work together better, not as a performance review. Start by explaining why you are asking: you want to align your requests with what they find meaningful. Then ask open questions and listen carefully. You might say, "What parts of your work give you the most energy?" or "When you look back on a project you are proud of, what made it satisfying?" Avoid making it about your needs; keep the focus on them.

After the conversation, write down a few notes—not in a formal file, but somewhere you can revisit. Note what they said about what they enjoy, what they avoid, and what they hope to learn or achieve. Then, in the following weeks, look for small ways to adjust your requests. If they value learning, invite them to a problem-solving session rather than just asking for a status update. If they value stability, give them clear timelines and avoid last-minute changes. The point is not to manipulate but to align.

Repeat this conversation periodically, especially when projects change or when you notice a shift in someone's engagement. People's drivers evolve. A what-matters conversation is not a one-time fix; it is a habit of curiosity. Over time, it builds a shared language of motivation that makes cross-team work more human and more effective. You will still make mistakes, but you will catch them faster and repair them more easily.

What to say and do

When you are trying to read someone's drivers, your words and actions should signal genuine interest. Start with open-ended questions that invite reflection. For example: "What kind of work makes you feel most engaged?" or "What would make this project more worthwhile for you?" or "When you have felt most motivated in the past, what was happening?" These questions are not about extracting information for your own agenda; they are about understanding their perspective. Listen without interrupting, and resist the urge to problem-solve immediately. Sometimes people need to think out loud.

After you listen, reflect back what you heard to confirm understanding. You might say, "It sounds like having a clear sense of progress matters a lot to you." or "So the chance to work with that team is more important than the recognition." This shows you are paying attention and gives them a chance to correct you. Then, when you make a request, connect it to what they said. For instance: "I know you enjoy untangling complex problems, so I thought you might find this integration challenge interesting." or "You mentioned you value predictability, so I have mapped out the timeline in detail." These small connections make the work feel personal, not transactional.

Finally, be transparent about your own motivations when appropriate. Sharing what drives you can make the conversation mutual and less like an interview. You might say, "I care about making this cross-team effort smoother because I hate seeing people waste time on confusion." That kind of honesty builds trust. Remember, the goal is not to become a mind reader but to create a space where people feel comfortable sharing what matters. Over time, these conversations become easier and more natural, and you will find that you need fewer formal rewards because the work itself aligns with what people want.

When the stakes get higher

When a cross-team project is high-stakes—tight deadline, visible outcome, or significant consequences—motivation becomes both more important and more fragile. People are under pressure, and their default drivers may intensify. Someone who values security might become more risk-averse. Someone who values achievement might push harder and expect others to do the same. In these moments, a one-size-fits-all reward system is especially dangerous because it can add stress rather than relieve it. A bonus promised for extra hours might feel like a bribe to someone who is already stretched thin.

Instead, lean more heavily on what you already know about each person. If you have had what-matters conversations, you have a foundation. Now you can tailor your approach. For the person who thrives on challenge, give them the hardest part of the problem and clear ownership. For the person who values teamwork, emphasize how their work supports others and create opportunities for joint problem-solving. For the person who needs stability, provide frequent updates and avoid unnecessary changes. These adjustments do not require formal authority; they require attention and flexibility.

High stakes also mean you should check in more often. A quick message like "How are you doing with this? What would help?" can reveal shifts in motivation. Be prepared to adjust your requests as you learn more. And if you sense someone is disengaging, do not wait for a formal review to address it. A private, informal conversation can uncover what has changed. The goal is to keep the collaboration sustainable, not just to squeeze out short-term effort. When people feel seen and supported, they are more likely to bring their best even under pressure.

Questions new leaders ask

Q: How do I start a what-matters conversation without it feeling awkward? A: Begin by framing it as a way to work better together, not as an evaluation. You can say, "I would love to understand what makes work meaningful for you, so I can support you better." Keep it low-key, maybe over coffee or a walk. Ask open questions and listen more than you talk. Most people appreciate the interest.

Q: What if someone does not want to share what motivates them? A: Respect that. Not everyone is comfortable discussing personal drivers, especially at work. You can still observe their behavior and experiment with small adjustments. For example, offer choices where possible and notice which they pick. Over time, trust may grow, and they may open up. If not, focus on clear communication and fair treatment.

Q: How do I avoid playing favorites when I tailor my approach? A: Tailoring is not about giving some people more than others; it is about understanding that different people need different conditions to do their best. You can be transparent about why you are adjusting your approach. For instance, "I know you prefer detailed plans, so I made this timeline for you." The underlying principle is fairness: everyone gets what they need to succeed, even if that looks different.

Q: What if I misread someone's motivation? A: You will, sometimes. The key is to stay curious and correct course. If you notice someone seems disengaged, ask them directly: "I might have gotten this wrong—what would make this work better for you?" Admitting you do not have all the answers builds trust. Motivation is not a one-time discovery; it is an ongoing conversation.