Team over task

No task is more important than the people involved.”

— Emily Kittle Morrison

The world of work is designed around the task. Our contracts are built around it. Our bonus systems are built around it. Our KPIs are built around it. Performance reviews, strategic plans, dashboards, quarterly targets, annual goals all tell us essentially the same thing: get the work done. And because the task is easily measurable while the health of a team is not, we have created organizations in which accomplishing the task becomes more important than what accomplishing the task is doing to the people executing it.

we have created organizations in which accomplishing the task becomes more important than what accomplishing the task is doing to the people executing it.

Imagine your boss tells you, “You have to get X done.” You go back to your team and say, “We have to get X done.” Someone on the team says, “But this is a bad idea. It’s going to create problems.” You respond, “I don't care. Just get it done. That's what we're paid to do.” You may have done exactly what your organization rewards you for doing. You may even earn your bonus. You also put task over team.

We do this all the time, often without thinking about it. The task is urgent. The deadline is real. Someone above us is demanding the result, and we are accountable for delivering it. In that moment, the team can become almost invisible. We are so focused on whether we get it done that we fail to notice what getting it done is doing to the team.

Maybe they stop speaking up because they have learned that raising concerns isn't welcome. Maybe they stop challenging our thinking and simply wait to be told what to do. Maybe they become cogs in the machine. Maybe they become less willing to take risks, less invested in the outcome, and less likely to bring their best thinking to the work. The task gets completed, but something happens to the team in the process.

Team over task does not mean that the task doesn't matter. Leaders still have to deliver results. Organizations still have customers, budgets, deadlines, commitments, and consequences. The point isn't to choose the team instead of the task. The point is to ask how we can accomplish the task while building the team rather than diminishing it.

That idea isn't new. Emily Kittle Morrison, who wrote extensively about leadership and developing effective teams, put it bluntly in a 1998 discussion of her work: “No task is more important than the people involved.” Her work emphasized that effective teams require attention not only to the task but also to the relationships and people involved in accomplishing it.

That requires a different kind of attention. I can simply carry a difficult assignment to my people and tell them what has to happen. Or I can bring them into the challenge. What do they see that I don't? What would they do differently? Where can I give them autonomy? How can I connect the work to a larger purpose? How can I make them feel that they are contributing to the solution rather than merely executing mine? Those questions don't make the task disappear. They change the way we pursue it.

The great leader is constantly conscious of the impact of the task on the team. Every demand, decision, deadline, and response is teaching the team something. When I shut someone down because I need them to execute, I am teaching them whether their judgment matters—whether they matter. When I take over because it is faster, I am teaching them whether I trust their ability. When I consistently reward compliance over contribution, I am building a team that waits for instructions. And when I invite people into difficult problems, give them room to think, and hold them accountable for the result, I am building something much more valuable than completion of the immediate task. I am building a team ready for future tasks and the challenges that come with them.

This matters most when the pressure is highest. Pressure makes task-over-team leadership incredibly tempting. Sometimes it may even be necessary. But a leader who develops the habit of asking, “What is this doing to my team?” will make different choices more often. Because every task has a second outcome that doesn't appear on a dashboard: what doing the task is doing to the team.

Did they become more capable? More connected? More willing to challenge one another—and you? Did they experience autonomy, mastery, and purpose? Did they become a better team because of what you asked them to do? Or did they simply get it done?

We cannot eliminate tasks, pressure, or accountability. But we can change the question. Instead of asking, “How do I get this done?” we can ask, “How do I get this done without damaging my team?” Or, even better, “How do I build my team in this process?”

That is the discipline of Team Over Task. The task matters. The result matters. But so does the team that produces the result. Unlike the task, which ends when it is completed, the team carries the consequences of our leadership into everything that comes next.

The task matters. The result matters. But so does the team that produces the result.

Great leaders don't ignore the task. They just refuse to sacrifice the team to it.

Unlike the task, which ends when it is completed, the team carries the consequences of our leadership into everything that comes next.