When every department has several strategic priorities, the organization has not necessarily created focus. It may have renamed its responsibilities. A real strategic priority changes the game, concentrates resources, and guides daily choices.

Your plan may be crowded with work that matters for different reasons

Your organization may have twelve strategic priorities.

Growth is strategic. Customer experience is strategic. Digital transformation is strategic. Leadership development is strategic. Cost management, employee engagement, sustainability, innovation, operational excellence, and culture are strategic too.

Every department has its own list beneath the enterprise list.

The word strategic appears often because the work is important. Leaders want people to take it seriously. Department heads use the label to protect resources. Project sponsors use it to gain attention.

But once everything becomes strategic, the label stops helping people choose.

Managers still do not know which work deserves protection when time and resources become tight. Teams continue carrying operational responsibilities, improvement projects, compliance requirements, and transformation initiatives as though each one has the same strategic weight.

The organization has priorities. It does not necessarily have strategic focus.

Important work keeps the organization operating. Strategic work changes how the organization intends to win.

Both deserve attention. They do not perform the same job.

Important does not automatically mean strategic

Payroll is important. Safety is important. Regulatory compliance is important. Customer complaints must be handled. Systems must remain available. Employees must be hired, supported, and paid.

An organization cannot ignore this work.

But importance alone does not make something strategic.

A strategic priority advances one or more of the organization’s central choices. It strengthens the chosen field, the way to win, a capability the strategy depends on, or the management system needed to carry those choices.

It changes the organization’s position or its ability to create the result it has chosen.

Consider cybersecurity.

For many organizations, cybersecurity is an essential operating and risk priority. The business must protect data and maintain reliable systems. But cybersecurity may not define how the organization intends to win.

For a company whose customers choose it because it provides secure digital transactions in high-risk environments, cybersecurity may become strategic. The capability is part of the value proposition and a reason customers choose the company.

The work is similar. Its strategic role differs.

Consider leadership development.

Every organization needs capable leaders. But a general leadership program is not automatically strategic because executives approved it.

It becomes strategic when the organization has chosen a direction that requires leaders to behave differently—and the development system is designed around that shift.

Perhaps the strategy requires decisions to move closer to customers. Leadership development must then shift managers from approving routine decisions to defining boundaries, coaching judgment, and following decision quality.

The strategic priority is not “conduct leadership training.”

It is move sound decisions to the lowest responsible level.

Training may contribute. It is not the priority itself.

Different work deserves different names

A useful plan distinguishes work according to the job it performs.

Some work runs the organization. It delivers existing products and services, supports customers, manages employees, maintains systems, and meets current commitments.

Some work protects the organization. It addresses safety, compliance, security, financial control, resilience, and risks that could damage the organization or the people it serves.

Some work improves the organization. It removes waste, reduces delay, corrects recurring problems, and helps existing operations produce their current results with fewer obstacles.

Some work changes the game. It moves the organization toward a chosen position, builds a capability competitors or alternatives do not possess, changes the way value is created, or replaces a familiar operating pattern that no longer serves the strategy.

None of these categories is unimportant.

Running the organization may consume most of its resources. Protective work may be non-negotiable. Improvement work may release the capacity needed for the future.

But the categories help leaders see why the work exists.

The mistake is describing every responsibility as strategic because leaders fear that any other label will make it appear secondary.

Operational does not mean trivial. Mandatory does not mean uninspired. Improvement work does not need the word strategic to deserve support.

Clear names allow clearer decisions.

A strategic priority should change something consequential

A strategic priority is not simply a topic leaders care about.

“Customer experience” is a topic.

“Innovation” is a topic.

“Leadership,” “digital transformation,” and “culture” are topics.

A strategic priority should describe a consequential movement.

Instead of “customer experience,” leaders might choose:

Move complex customer concerns from repeated departmental transfers to complete resolution with one visible owner.

Instead of “leadership development,” they might choose:

Move managers from providing answers to building decision ownership within clear boundaries.

Instead of “digital transformation,” they might choose:

Move field decisions from delayed paper reports to current operating information available at the point of work.

Instead of “innovation,” they might choose:

Move product development from internal assumptions to small customer tests before full investment.

Each statement shows the current pattern and the intended shift.

People can now ask what behavior, capability, process, and management support the movement requires. They can also identify proof.

A topic attracts many activities. A movement organizes them.

This is one reason clear strategy matters. The priority must be clear enough to guide what people decide and do, not merely broad enough to include everyone’s existing work.

Strategic priorities come from choices, not departments

When leaders ask every department to submit its strategic priorities, they usually receive a long list.

Finance proposes cost control and financial discipline. Human resources proposes talent, engagement, and culture. Technology proposes modernization and security. Operations proposes productivity and quality. Sales proposes growth and customer acquisition.

Each department names work connected to its responsibilities.

The result is not necessarily an enterprise strategy. It is a collection of functional concerns.

A more useful sequence begins with the organization’s choices.

What is the win?

Where will the organization play?

How does it intend to win?

Which capabilities must become dependable?

What system must support them?

Once those choices are clear, departments can identify their contributions.

The organization may have a strategic priority to provide complete resolution for complex customer concerns.

Operations may redesign the flow of work. Technology may connect information across departments. Human resources may develop judgment and ownership. Finance may change measures that reward faster transfers rather than completed results.

These are connected contributions to one strategic movement.

They should not become four separate strategic priorities merely because four departments own parts of the work.

The organization has strategic priorities. Functions have contributions to those priorities.

This distinction reduces competition among departments and reveals whether the work forms a coherent system.

A strategic priority must require concentration

A priority is not a priority merely because it appears near the top of a list.

It must affect the allocation of scarce resources.

Leadership attention should move. Funds should move. Capable people should move. Meetings and measures should change. Some work should receive less.

Without concentration, leaders have named an aspiration rather than established a priority.

The previous article on visible trade-offs examined why every strategic yes creates a no somewhere.

That principle matters here.

Suppose leaders describe five initiatives as the company’s top priorities but do not stop, reduce, or postpone anything. Each initiative receives an owner and a project plan. The same specialists are assigned across several teams. Executives attend launch meetings but return to the concerns that already dominate their calendars.

The priorities are announced. Concentration does not occur.

The organization then blames execution.

Projects move slowly. Owners compete for decisions. Teams report that daily work leaves no time for strategic initiatives.

But the execution problem began with priority accumulation.

Leaders selected more strategic work than the organization could protect.

The shift is from ranking many initiatives to concentrating enough resources on the few movements that must succeed.

Fewer priorities do not mean fewer responsibilities

Leaders may resist narrowing the strategic list because the organization still has many obligations.

Those obligations will not disappear.

The company must continue serving customers, maintaining systems, meeting regulatory requirements, managing cash, supporting employees, and resolving operating problems.

But these responsibilities do not all need to compete inside the strategic agenda.

Separating the lists can help.

The operating agenda shows what the organization must continue delivering.

The risk and obligation agenda shows what must be protected or satisfied.

The improvement agenda shows where existing work should become more reliable, timely, or economical.

The strategic agenda shows the few movements that change the organization’s chosen game.

This separation makes leadership conversations more useful.

A weekly operations meeting can address service performance and immediate constraints. A risk review can examine compliance and exposure. An improvement review can follow recurring defects and delays. A strategy review can focus on whether the chosen movements are producing evidence.

When all four agendas are mixed together, urgent operating concerns usually consume the meeting.

Strategic priorities remain on the slides but receive whatever time is left.

Goals and targets do not become strategic through ambition

A large target can look strategic because it is difficult.

Grow revenue by 20 percent. Reduce cost by ₱50 million. Reach one million customers. Open ten branches. Train every manager.

These goals may demand serious effort. But scale does not make them strategic.

A target tells you how much. Strategy explains where the result will come from and what choices will produce it.

A revenue target may be reached through existing customers, new customers, price increases, new offers, additional locations, acquisitions, or temporary discounts. These paths do not build the same future.

A cost target may be reached by removing waste, reducing service, delaying investment, cutting critical capability, or redesigning the operating model.

The number does not reveal the choice.

Richard Rumelt distinguishes strategy from ambitious goals and long collections of objectives. His strategy kernel begins with a diagnosis of the challenge, a guiding policy for addressing it, and coherent actions that carry the policy.

The target may belong in the plan. But it should not stand in for strategic reasoning.

Instead of asking only, “What is the target?” ask:

Which strategic choice will produce this result?

What must the organization become able to do?

What current pattern must change?

What will we refuse to protect the path?

The answers reveal whether the target is connected to strategy or merely expresses ambition.

A project is not the priority

Organizations often name projects as strategic priorities.

Implement the customer relationship management system. Launch the academy. Redesign the website. Enter a new region. Build the innovation center.

Projects are easier to manage because they have deliverables, deadlines, budgets, and completion dates.

But project completion does not prove strategic movement.

A CRM system can be installed without changing how salespeople use customer information.

A leadership academy can graduate participants without changing how managers direct, delegate, and coach work.

A new website can launch without clarifying why customers should choose the organization.

A regional office can open without proving that the organization’s advantage travels to the new field.

The project is a vehicle.

The priority should describe the result the vehicle must help create.

Instead of “install CRM,” the priority may be:

Move account decisions from fragmented personal records to a shared view of the customer’s complete relationship.

Instead of “launch the leadership academy,” it may be:

Move managers from escalating cross-functional conflicts to resolving them through agreed strategic choices.

Now the organization can judge whether the project is contributing.

If the CRM is installed but decisions remain fragmented, the project is complete and the priority is not.

This distinction protects leaders from mistaking delivery for impact.

Coherence matters more than the number alone

There is no universally correct number of strategic priorities.

One organization may need one central movement. Another may need three connected priorities. A complex enterprise may carry several choices at different levels.

The more important question is whether the priorities reinforce one another.

Paul Leinwand and Cesare Mainardi describe coherence as the alignment of a distinctive value proposition, a reinforcing system of capabilities, and a portfolio of products and services that uses those capabilities. They contrast this with incoherence, where an organization follows many paths to value creation and spreads itself across capabilities that do not reinforce one another.

This provides a useful test.

Suppose an organization has three strategic priorities:

become the easiest provider for small businesses to work with;
build fast, informed decisions near the customer;
create one shared operating view across sales, service, and finance.

These priorities may reinforce one another. The customer promise, leadership behavior, and information capability form one system.

Now consider another list:

expand into the premium enterprise market;
become the lowest-cost provider;
provide highly customized service;
standardize all operating processes;
launch products for several new customer groups.

The priorities pull the organization toward different games.

Reducing the list from five to three would help, but the deeper problem is contradiction.

Strategic priorities must tell one story.

Use a strategic-priority test

Before placing an item on the strategic agenda, test it.

1. Which strategic choice does it advance?

Does the priority strengthen the chosen win, field, way to win, capability, or management system?

When the connection cannot be explained, the item may be important without being strategic.

2. What consequential movement will it create?

Can you describe the shift from the current pattern to a new position, capability, or way of working?

A topic or project name is not enough.

3. What will receive less?

Which work, investment, opportunity, or familiar routine will be reduced, postponed, maintained, or stopped?

Without a trade-off, the priority may not receive enough concentration to work.

4. What evidence should appear before completion?

What should customers, employees, leaders, or operating results begin showing?

Early proof should reveal movement, not merely activity.

5. What happens to the strategy if this does not move?

Would a central strategic choice fail, or would the organization continue along essentially the same path?

This question separates transformative importance from general usefulness.

An item does not need a perfect answer to every question before leaders explore it. But it should pass the test before being presented to the organization as a strategic priority.

Make priorities usable in daily decisions

A strategic priority should help someone choose.

Suppose the stated priority is “strengthen customer centricity.”

A product manager still does not know whether to delay a launch to resolve a recurring customer problem. A service manager does not know whether employees may spend more time on complete resolution. A technology team does not know which customer information should be integrated first.

Now suppose the priority is:

Move the ownership of complex customer concerns from departmental handoffs to one accountable team until resolution.

The product manager can ask whether the launch helps remove the recurring problem.

The service manager can protect complete resolution over quick transfer.

The technology team can prioritize the information the accountable team needs.

The priority enters the decision.

This is where strategy becomes daily execution. The words should change what people decide, discuss, and do while the work is happening.

If a priority can guide only senior presentations, it is not yet usable.

Give each priority an owner without making it a silo

A strategic priority needs visible ownership.

Someone must protect the movement, bring together the required contributions, surface unresolved trade-offs, and follow the evidence.

But ownership should not turn an enterprise priority into one department’s project.

If customer resolution is assigned to the service department, other functions may continue behaving as though the result belongs elsewhere.

If decision ownership is assigned to human resources, operating leaders may treat it as a training program.

If digital transformation is assigned entirely to technology, business units may avoid redesigning the work.

The owner coordinates the movement. The organization still owns the result.

This is another reason to describe priorities as shifts rather than functions or projects.

“Human resources owns leadership development” encourages delegation of responsibility.

“Managers move routine decisions to the lowest responsible level” makes the operating change visible. Human resources may design practice and support, but line leaders must alter authority, coaching, and review routines.

Ownership should clarify accountability without hiding interdependence.

Protect strategic priorities from the urgent

Daily operations create noise.

A major customer calls. A system fails. Revenue falls below target. A senior stakeholder requests an update. A competitor announces something new.

Some events require immediate action.

But if every urgent event is allowed to displace strategic work, the organization will preserve the current game indefinitely.

Strategic priorities need a rhythm that survives operational pressure.

Leaders should regularly ask:

What movement did we expect?

What evidence appeared?

What obstacle is blocking the next move?

Which leadership decision is required?

Has urgent work exposed a flaw in the strategy, or has it merely pulled attention away?

The goal is not to protect the priority from reality. The goal is to use reality as evidence without allowing every disturbance to become a new direction.

This is part of Strategic Learning: make a choice, act, follow visible results, and improve the next move.

Rename the work before you remove it

You do not need to begin by cancelling half the organization’s initiatives.

Begin by naming their jobs accurately.

Take the current list and ask whether each item primarily runs, protects, improves, or changes the organization’s game.

Some items may support more than one category. Choose the job that should determine how leaders govern and review the work.

Then identify which items truly advance the strategic choices.

You may discover that several “strategic priorities” are contributions to the same movement. Combine them.

You may find projects that are operationally necessary but do not belong in the strategy review. Move them to the correct agenda.

You may find mandatory work that deserves guaranteed resources without pretending it differentiates the organization.

You may also discover one strategic movement hidden beneath several project names.

Accurate naming creates room for focus.

It allows leaders to say:

“This work is essential to operating safely.”

“This work improves an existing process.”

“This project contributes to our chosen strategic priority.”

“This movement changes how we intend to win.”

Each statement gives the work dignity without creating confusion.

Write the strategic priority as movement

For each genuine strategic priority, complete this sentence:

We will move from ________ to ________ so that ________.

Then add:

We will concentrate on ________.

We will reduce, postpone, or stop ________.

The first visible proof will be ________.

For example:

We will move from serving several unrelated customer segments with customized offers to building one connected system for family businesses moving beyond founder dependence, so that our expertise, products, and evidence reinforce one another.

We will concentrate product development, marketing, and consultant learning on that transition.

We will stop expanding the general catalogue of unrelated workshops.

The first visible proof will be repeatable demand for the connected offer and customer evidence that the system reduces founder dependence.

The statement does not need to contain the entire plan.

It must reveal enough logic for people to understand why the priority exists and what it changes.

Give the few choices a visible home

Once the strategic priorities are clear, people need to see how they connect.

The win, the field, the way to win, the trade-offs, the priorities, the first moves, and the proof should not remain scattered across several presentations and planning documents.

They need one visible home.

That does not mean reducing strategy to a slogan or removing necessary detail. It means giving leaders and teams a usable view of the choices that should guide decisions.

The next article, one-page game plan, will show how to put the central choices on one page without turning strategy into a collection of boxes and targets.

Before building that page, remove the false strategic labels.

Keep operating work visible. Protect mandatory work. Continue useful improvements. Then reserve the strategic agenda for the few connected movements that change the organization’s game.

Stop Calling Every Priority Strategic