Finding ideas to make a company work better is easy. The constraint isn't ideas: it's the time and money available to carry them out.
A business priority is the activity that, for the same resources invested, brings you closest to the stated goal. It is not what's most urgent, nor what's most interesting.
This article gathers the criteria for identifying a company's priorities: where to start, how to build the list of alternatives, which parameters to compare them on, how to test them and which recurring mistakes to avoid.
Start from short-term goals to make priorities decidable
Without a stated destination, comparing two initiatives is a matter of opinion.
Long-term goals provide direction, but they rarely let you choose between two concrete actions: they are too far away for the difference to show. The horizon that makes a priority decidable is shorter, usually between three and six months.
It's a horizon close enough to make the effects of a choice visible, and far enough to allow projects that take weeks of work.
How the goal is worded matters too. Research on goal setting shows that specific, challenging goals produce higher performance than vague "do your best" goals, provided the person has the necessary skills and receives feedback on progress [5].
A practical element: write the goal for the next three to six months on a single line, with a number and a date. If the line contains neither, ranking priorities will be impossible.
That leaves the next question: once the goal is set, how do you build the list of paths that lead to it?
Build the full list of alternatives before choosing
You can't choose well among options you don't know about.
The most common mistake isn't ranking priorities badly: it's ranking three when the real alternatives were fifteen. The choice is correct relative to the list at hand, and wrong relative to the reality of the company.
A useful list is built by area, not by free association. Reviewing the building blocks of the company — organization and resources, brand and positioning, customer acquisition, sales model, after-sales — also brings out what nobody was thinking about.
The items that emerge fall into three families:
1- ongoing losses: problems that are draining margin, customers or time right now
2- quick wins: simple, inexpensive actions with a high, near-term return
3- optimizations: structural improvements to the business system, slower and more expensive
The distinction matters because the three families can't be compared on equal terms, as the next section shows.
One figure helps frame the scale of the problem: in Sull, Homkes and Sull's research on strategy execution, about half of the middle managers surveyed could not name even one of their company's top five stated priorities [6]. The survey covers large international organizations and its numbers don't carry over to smaller companies; the mechanism it describes, however, can also be seen in small organizations, where priorities often stay in one person's head and are neither written down nor ranked.
First stop the losses, then seize the quick wins
Before making a ship go faster, it pays to plug the holes letting water in.
The order that holds in most cases is this: first ongoing losses, then quick wins, and finally optimizations, and only if resources remain. Investing in growth while a leak is open means feeding the problem along with the result.
The logic has a well-known basis in the operations management literature: a system's output is determined by its constraint, and improving a part that isn't the constraint doesn't improve the overall result [4]. First you identify what limits the company, then you decide where to invest.
The principle of concentration also applies: focus on a few things at a time, in the right order, instead of spreading resources across many fronts in parallel [1]. The observation of the "vital few" versus the "trivial many," popularized as the Pareto principle, points in the same direction — a label its own popularizer acknowledged as inaccurate in a well-known 1975 correction [3].
Within each family, four simple criteria almost always rank things well:
1- first what is easy and inexpensive, then what is difficult and costly
2- first what yields the most for the same effort
3- first what is already proven, then what needs to be tested
4- first improving what already exists, then creating something new
A useful clarification: the order between urgent and important in day-to-day task management follows a different logic from that of business priorities, and is codified in the classic distinction between the two dimensions [2]. The topic is covered in depth in priority management: decision frameworks.
Three questions to check that a priority really is one
Many items that end up on priority lists aren't priorities: they are wishes, symptoms or generic categories.
Three questions, asked in sequence, separate one from the other:
1- what need does this priority meet?
2- what is its origin, that is, the cause that produced it?
3- what is the specific solution, that is, the concrete action that resolves it?
"Increase revenue" fails the test: it doesn't point to a specific need, has no identified origin and contains no action. It's a wish.
"A significant share of quotes goes unanswered because there is no scheduled follow-up, so a second contact should be introduced within three days of sending" passes the test: need, cause and solution are all there.
The practical difference is measurable: the first wording can't be assigned to anyone, the second can.
Weigh the alternatives on three parameters: time, cost, business owner hours
A priority that is correct in the abstract may prove unworkable in the real context.
It helps to distinguish absolute priorities — what matters most regardless of resources — from relative priorities, that is, what matters most given the resources actually available. It's the second category that determines the plan for the coming months.
The intermediate step is a resource inventory: how many hours the person running the company can commit, how many hours team members can commit, what budget is available and how much of it must come back quickly so the operating cycle doesn't stall.
On this basis, three parameters let you compare very different alternatives:
1- timing: how long the action takes to produce an observable result
2- cost: the total financial investment required
3- business owner hours: how much personal, non-delegable time it absorbs
The third parameter is the one most often underestimated. Two initiatives with the same cost and the same expected return are not equivalent if one requires forty hours from someone who already has none and the other requires two.
An absolute priority that requires unavailable resources isn't a priority: it's a goal for the next cycle.
Turn the chosen priority into short, verifiable actions
A priority that doesn't translate into executable activities remains an intention.
Moving from priority to action has four recurring requirements:
1- brevity: activities that can be completed in a few hours, not months-long projects
2- operational definition: anyone reading the activity understands what to do without further explanation
3- correct position in the sequence: the action is the first in the chain, not the third
4- initial version: you build a first working version instead of waiting for the perfect one
The last point is the most disputed and the most useful. An imperfect first version produces real feedback within a few weeks; a perfect version designed on paper produces feedback when conditions have already changed.
One piece remains: the "how." Every action requires precise tactical guidance, that is, the operating instructions to carry it out well, which usually come from someone who has already done that kind of activity. The criterion for recognizing the activities that deserve this level of care is described in high-impact actions.
The most common mistakes when choosing priorities
Some mistakes recur often enough to be listed.
Growing the customer base before having procedures. Demand rises, service deteriorates just as more people arrive, and positive word of mouth turns into its opposite. Defining the procedural model comes before acquisition.
Adding salespeople before having a proven sales model. Multiplying a process that doesn't work multiplies the problem, not revenue.
Investing in advertising before having brand authority. Copying the campaigns of a well-known brand without its recognition produces acquisition costs that are out of scale.
Looking for new customers while ignoring the dissatisfaction of current ones. When after-sales generates complaints, internal marketing comes before external marketing: acquiring customers for a service that disappoints means paying to amplify a problem.
Setting priorities alone. The most solid combination requires at least two points of view: someone who knows the industry inside out and someone who thinks about the whole business system. The first, alone, stays within the habits of their own market; the second, alone, risks solutions disconnected from operational reality.
Treating personal priorities as an afterthought. Health, time and relationships affect the ability to decide: a business priority that squeezes them for too long gets paid for later, with interest.
Limits and conditions of applicability
These criteria structure your reasoning, they don't replace it: they produce a defensible list, not an automatic answer.
Their quality depends on the quality of internal data. A company that doesn't measure margins per job, delivery times and complaint rates can't know where it's losing, and will rank priorities based on impressions. Building the right indicators is covered in business KPIs.
The references cited come from contexts different from that of a small business: the logic of constraint and concentration carries over, the scale of the tools described does not.
Finally, there is one condition that changes the order: a company with an immediate cash problem doesn't follow the sequence described. In that case there is only one priority, and it's about cash.
Summary and outlook
A company's priorities aren't found by picking the best idea: they are found by ranking the full list of alternatives against a stated goal and the resources actually available. It's a work of selection, not inspiration.
The natural next step is to place the priorities you've identified within a broader horizon, with deadlines and responsibilities: the topic is developed in strategic planning.
A company that knows its three priorities for the coming months argues less and decides faster. Meetings get shorter, suppliers receive precise requests instead of exploratory ones, and resources stop being scattered across fronts nobody had really chosen.
People who know what comes first don't work more: they work in the right order.
FAQ
What is the difference between a priority and a goal?
The goal is the result to be achieved; the priority is the activity that brings you closest to that result with the resources available. Without a stated goal there are no priorities, because there is no benchmark against which to compare alternatives. A priority list written before the goal is really a to-do list.
Over what time horizon should business priorities be set?
The most useful horizon is three to six months. It's close enough to make the effects of choices visible and far enough to allow projects that take weeks. Long-term goals remain necessary for direction, but they don't let you compare two concrete initiatives: the difference between the two only shows over short distances.
Should you solve problems first or seize opportunities?
In most cases, problems that are generating losses come first, then simple and inexpensive opportunities, and finally structural optimizations. Investing in growth while a loss is active means feeding both the result and the problem at the same time. The exception is time-sensitive opportunities, which expire if not seized by a specific date.
How many people does it take to set a company's priorities?
At least two, with different skills: someone who knows the industry, the customers and the product inside out, and someone who thinks about the whole business system. The first, alone, tends to stay within the customs of their own market; the second, alone, risks proposing solutions disconnected from operations. It's the exchange between the two points of view that produces a solid list.
How can you tell whether a priority is well worded?
With three questions: what need it meets, what cause generated it and what concrete action resolves it. If one of the three answers is missing, the item is a wish or a symptom, not a priority. The quickest practical test is to check whether the priority can be assigned to one person with a deadline.
Sources and references
-
Drucker, P. F. (1967). The Effective Executive. Harper & Row. Foundational reference.
-
Covey, S. R. (1989). The 7 Habits of Highly Effective People: Powerful Lessons in Personal Change. Free Press. Foundational reference. The distinction between urgent and important is commonly attributed to Eisenhower, but the codified, widely circulated formulation is the one in this book.
-
Juran, J. M. (1975). The Non-Pareto Principle; Mea Culpa. Quality Progress, 8(5), 8-9. Foundational reference, cited from the original journal article.
-
Goldratt, E. M., & Cox, J. (1984). The Goal: A Process of Ongoing Improvement. North River Press. Foundational reference.
-
Locke, E. A., & Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9), 705-717. https://pubmed.ncbi.nlm.nih.gov/12237980/. Foundational reference. Accessed: 07/31/2026.
-
Sull, D., Homkes, R., & Sull, C. (2015). Why Strategy Execution Unravels — and What to Do About It. Harvard Business Review, 93(3), 57-66. https://hbr.org/2015/03/why-strategy-execution-unravelsand-what-to-do-about-it. Foundational reference. Sample: managers and executives at large international organizations. Accessed: 07/31/2026.