Am I Giving My Teams a Mission or a Backlog?
Somewhere on the way up, we start treating seniority as a capacity for juggling.
The assumption is that more senior people can spin more plates. That's the expectation, and it isn't entirely wrong. People with more skill can do more things. But there's a second version of that same sentence:
People with more skill can do one thing exceptionally well.
Many managers pick the juggling version because it's cheaper on the org chart. And it's the single most common way I watch a good team get swamped and become ineffective.
If your team is busy and nothing is landing, this is usually why. They aren't slow. They're paying a juggling tax that doesn’t show up your status report.
What six missions actually cost
Give a team one mission and the priority question is already answered. The mission is the priority. It's sink or swim on fulfilling that one mission. Everyone knows it's the most important thing, because it’s the one thing.
I was on a team building a new mobile app several years ago. New team, new mission, plenty of opportunity for confusion on what was the most important thing to get done.
The question I asked in a leadership meeting was - “If we don’t get the mobile app out the door on time - are we dead?” (as in no funding to continue, we all get to look for new jobs).
“Yes.”
I didn’t take it as harsh, I took it as clarity on mission.
If we gave that same team six missions then you've handed them a second job before the first one starts: ranking.
Ranking isn't a one-time cost. It gets re-litigated every week, in every status meeting, by every stakeholder who shows up with a different favorite. Your best people spend their best hours deciding what to work on instead of working.
And nobody is accountable for any single one mission. There's always a defensible reason the other five ate the week.
Six missions isn't six commitments. It's six ways to make up excuses.
Where AI turns a drag into a hazard
Last week I made the case that AI amplifies whatever you point it at, and that it won't save a bad manager. The same logic runs one level up.
Point AI at a team with one mission and it compounds. It can be focused on helping you solve your main problem. Every hour it saves goes back into the same target.
Point it at a team with six and you get six well-argued, mutually incompatible plans by Thursday. AI is great at arguing with itself. Speed doesn't fix direction. It multiplies whatever direction you already had.
The prioritization tax used to be paid slowly enough that you could see it happening. Now it gets paid at AI speed, and the mistake is that the output looks like productivity. AI will generate six polished plans, six confident-sounding owners, and leave you with one team going nowhere fast.
There's a second-order version of this that's worse. Because the team has AI now, it becomes easier to justify a seventh mission. They've got leverage, they can handle it. Capacity went up, but alignment did not. That's the trap that’s being set in a lot of orgs right now.
The structure underneath
This isn't complicated, which is why it's so often skipped.
Purpose is why you exist. Mission is what you're doing about it. A unit gets one purpose. Each team under it gets one mission that serves that purpose. Each mission gets a metric.
Increase market share in the western region — that's a purpose. Map that to missions: one team owns inbound, one owns content, one owns outbound, one owns events. Four teams, four missions, one purpose. Nobody has to rank anything. Tada, you’re super agile without extra hoopla.
Team and Mission
How do you know if your team understand their mission? Have them finish this sentence out loud:
"Our mission is ______, so that ______."
The second blank has to be the unit's purpose.
Three things surface immediately:
- Anyone who needs an "and" to finish the first blank has two missions, not one. That's your ranking tax made visible.
- Anyone whose second blank is different from the person next to them is misaligned.
- Anyone who can't finish the sentence at all doesn't have a team.
It should be short and it’s ok to fail fast at it. Because then you can correct and get aligned.
If a team has more than one mission, then they don’t have a mission, they have a backlog.
Last Thursday, subscribers got the full Purpose Mapping method — how to turn a vague company purpose into measurable statements you can actually evaluate against, including the group exercise for doing it with your peers instead of guessing alone. It's email-only.
See you next week!
-Frank
