Two Questions That Turn Competing Priorities Into Strategic Alignment
Competing priorities rarely mean people do not care. More often, they mean people cannot see where a request fits inside the larger system they are trying to protect.
That is why task-level persuasion often fails. “Can you get this done?” invites a yes, no, or delay. “Why has this not happened yet?” creates defensiveness. But a systems question changes the frame.
When a priority is stuck, ask:
What is doing this priority part of? What is not doing this priority part of?
Those two questions move the discussion from preference to strategy. They help people see the work, the delay, and the trade-off inside the business strategy system that already guides major decisions.
Tasks compete because systems compete
A single task looks simple when viewed alone.
Send the report. Approve the budget. Fix the process. Review the proposal. Hire the role. Make the customer call.
Each one may be reasonable. The problem is that work does not live alone. Every task belongs to a system of goals, constraints, promises, timelines, incentives, and risks.
One priority may belong to the system of short-term revenue. Another may belong to the system of long-term customer trust. One may protect this quarter’s cost target. Another may protect next year’s ability to scale. One may satisfy an urgent internal demand. Another may support a plan the leadership team already agreed to months ago.
When those systems pull on the same people, money, or time, conflict appears as “competing priorities.”
That phrase can hide the real issue. The team is not choosing between two tasks. It is choosing between two systems.
The first question makes the work bigger in the right way
Ask, “What is doing this priority part of?”
This question connects a finite task to the larger outcome it supports. It prevents the priority from being judged only by its effort, timing, or inconvenience.
For example, “complete the customer onboarding review” may sound like another administrative task. But if doing it is part of reducing churn, protecting renewals, and learning where handoffs fail, the task changes shape. It now belongs to a larger system that affects revenue, customer experience, and operational health.
The work becomes easier to defend because it is no longer floating in isolation.
A useful answer might sound like this:
It is part of the customer retention plan.
It is part of the product quality work already approved for this quarter.
It is part of reducing manual rework before the next hiring cycle.
It is part of a commitment made during annual planning.
It is part of protecting a long-term account relationship.
The strength of this question is that it does not ask people to care more. It helps them see more.
The second question exposes the cost of delay
Ask, “What is not doing this priority part of?”
This question is just as important. People often see the benefit of action but miss the system supported by inaction.
Not doing the work may be part of preserving this month’s cash. It may be part of keeping a team focused on a near-term deadline. It may be part of avoiding a difficult conversation. It may be part of meeting a narrow financial target.
Some of those reasons are valid. Some are only comfortable.
This question makes the trade-off visible. It turns “we do not have capacity” into a more honest discussion:
What system benefits if we delay?
What metric improves if we do nothing?
Who gains time, budget, or relief?
What long-term goal becomes weaker?
What promise becomes harder to keep later?
Short-term benefit is not automatically wrong. A company sometimes needs near-term financial gain, cost control, or urgent delivery. But if avoiding the work provides only short-term relief while weakening an agreed long-term plan, the choice should be limited, named, and owned.
Silence should not get to look like strategy.
Strategic alignment grows when trade-offs become explicit
People can refuse a loose task. It is much harder to refuse a task clearly tied to strategy, especially when that task supports prior planning.
That does not mean every request should be dressed up as strategic. That weakens trust. The point is to locate the work honestly.
If the priority supports a long-term goal, say so. If it came from a planning decision already made, connect it back. If it reduces risk, protects customer value, or enables later work, make that visible.
A simple framing can help:
“Doing this work is part of the plan to improve renewal quality and reduce service recovery work. Not doing it is part of protecting short-term capacity for the launch. Which system matters more this month, and what are we willing to trade?”
That kind of framing is practical. It gives peers a way to agree, disagree, or adjust based on the real decision.
It also reduces personal friction. The conversation is no longer about who is blocking whom. It is about which system the organization wants to feed.
Use the questions before the conversation hardens
The best time to ask these questions is before people dig into positions.
Use them when a priority is delayed, when a peer says their team has no capacity, or when leadership keeps approving work without removing anything else.
Try this sequence:
Name the priority without blame.
Ask what doing it is part of.
Ask what not doing it is part of.
Compare the systems, not the personalities.
Decide what gets resourced, delayed, reduced, or stopped.
This takes only a few minutes, but it changes the quality of the conversation.
It also helps managers think beyond urgency. Urgency is loud. Strategy is often quieter. If the quieter work never gets connected to the system it serves, it will keep losing to whatever is newest, loudest, or closest to revenue.
The two questions give strategic work a fair hearing.
A priority that cannot connect to strategy may not be a priority
There is another benefit. These questions also test the work itself.
If no one can explain what doing the priority is part of, the work may be a preference, habit, or legacy commitment. It may still matter, but it deserves scrutiny.
If no one can explain what not doing it is part of, the team may be avoiding a decision rather than making one.
Good strategy requires both sides. Action has a system. Inaction has a system. Alignment improves when both become visible.
The next time a priority stalls, do not start by arguing for the task. Start by locating it.
Ask what doing it is part of. Ask what not doing it is part of.
Influence increases when the conversation shifts from isolated tasks to the systems they serve. That is where real alignment begins.
Comments