Welcome to Friday 411, issue #145. In 4 minutes, with 1 insight and 1 action, you’ll learn the six features every project team should establish before it’s formed.
1 Insight
Your job as a leader is not to lead every team. Your job is to deploy them well.
A few months ago, a plant manager named Marcus said something that stuck with us. We were discussing his challenges over the last few months, and he was frustrated.
“I need to get work done through teams,” he said. “I tell everyone to ‘work together,’ but I don’t know what actually makes a good team. If I don’t know, I doubt anyone else does either.”
Marcus continued, “I pull people together, give them a project, and hope for the best. Sometimes it works. Most of the time, they waste their energy quarreling because they can’t agree on what they need to do.”
Marcus isn’t alone. Team and teamwork are two of the most common words in leadership. But that doesn’t make good teaming a common practice. Most leaders know they should deploy teams. Very few know how to set one up so it actually wins.
Use today’s newsletter as a playbook for launching a team that works.
The Playbook: Six Features Every Project Team Needs
Whether you call them project teams, task forces, or micro teams, the formula is the same. Before a team starts working, it requires six features for success. Skip any of them, and you’re rolling the dice.
- One Clear Leader
Not two. Not a committee. One person who owns the outcome and keeps the team moving forward.
This is the person you’re trusting to lead the team. Pick someone and give them real authority. If two people think they’re in charge, nobody is.
- A Defined Purpose
The team needs to know exactly why it exists. Not a vague goal like “improve communication” or “work on culture.” Something specific and concise:
“Redesign the onboarding process for frontline hires.”
“Launch a customer feedback system across all three locations.”
If you can’t say it in one sentence, it’s not clear enough. If the team doesn’t know why it exists, it won’t know when it’s done.
- A Deadline
Teams are temporary by design. They have a start and a finish. Without a deadline, a team defaults to standing meetings, which kills momentum and gouges huge chunks of time.
Set a clear end date. If the scope changes, adjust the deadline. But never let a team run open-ended.
- Criteria for Success
This is where the real magic happens for teams. The purpose tells the team what they’re doing. The criteria for success tell the team what must be true for the work to count as a win.
Let’s say your team’s purpose is to launch a new employee recognition program. That’s a good start. But what does success actually look like? Here’s an example:
- A employee recognition program is live and active across all departments by September 1.
- At least 80% of managers use it consistently within the first 90 days.
- Employee satisfaction scores related to recognition improve by at least 15%.
- The program is sustainable without adding headcount.
- The leadership team feels confident enough to share it with other divisions.
See what happened? The purpose gave the team direction. The criteria for success gave the team a scoreboard. Now everyone knows what “done” looks like before the first meeting even starts.
Without these criteria, the team will drift. They’ll keep meeting, keep discussing, and never know if they’ve actually won.
- Clear Roles
Every person on the team should know what they’re responsible for. Not just “be on the team.” What is each person’s distinct contribution to the team?
Establishing clear roles has two benefits. First, it helps everyone understand their unique contribution. Second, it gets people more engaged because they know they were selected for a reason. They’re not just filling a seat. They have a job to do, and the team needs them specifically to do it.
- An Operating System
The Operating System serves as the rhythm of how the team works together. It needs to be articulated up front, then updated along the way. An operating system answers five questions before the team starts:
- When will the team meet? Weekly? Biweekly? Set the cadence and protect it.
- How will the team communicate between meetings? Email? A shared channel? Text thread? Pick one and stick with it.
- What are the Team Operating Principles? These are the ground rules for how the team treats each other, makes decisions, and handles disagreements.
- Where will the team store important information? Shared drive? Project board? Pick one place, and make it accessible to everyone.
- How often will we check in with key stakeholders? The urgency of the project determines the frequency of checkins.
When a team skips this step, they waste the first few weeks figuring out how to work together instead of actually working. Set the operating system on day one.
Your Job Is to Build the Team, Not to Be on It
Here’s the shift that changes everything. Your job as a leader is not to sit on every team. Your job is to deploy them well.
You identify the team leader. Work with them to define the purpose, deadline, criteria for success, and how often they’ll check in. Then let them fly.
The best leaders we know don’t run every play. They design the plays. They pick the right leader. And they trust the team to execute.
When you learn how to deploy teams instead of sitting on them, you multiply your capacity. You develop other leaders. And you stop being the bottleneck.
1 Action
Identify one project this week that needs to be accomplished through a team.