Priority-based business plan: a practical guide

The reason, almost always, is not in the document: it is in what the document takes for granted. A plan describes how a result will be reached, but it rarely explains why those particular activities — and not thirty others that make just as much sense — deserve the company's time and money over the coming months.

That is the difference between a well-written plan and a priority-based plan.

This article does not cover the formal structure of the document — sections, financial projections, executive summary, which are the subject of the guide on how to write a business plan — but the step that comes before it: how to identify the few activities that really matter, how to tell them apart from the many that seem urgent, and how to turn them into an operational plan you can check.

The problem is not how you work, but what you work on

Many companies spend years becoming more efficient: they shorten the time between an idea and its execution, streamline steps, train the team. Then they look at their growth results and find them modest.

The contradiction is only apparent. Efficiency and effectiveness are two different things: efficiency concerns the ratio between resources used and results obtained; effectiveness concerns whether that result serves any purpose. A company can become very good at carrying out activities that move nothing.

This distinction is at the heart of Drucker's classic work on managerial effectiveness: the effective executive is not the one who does more things, but the one who concentrates on a few areas and consciously gives up the others [1]. It is a choice of subtraction, not addition.

The operational question that follows is uncomfortable in its simplicity: which two or three activities, if completed in the coming months, would really change the company's trajectory?

There are dozens of alternatives available. Train the sales network. Write procedures. Start a company blog. Revise the price list. Hire an administrative person. Redo the website. Introduce management software. None of these activities is wrong in absolute terms. But they are not equivalent, and treating them as if they were is the fastest way to scatter resources.

Distinguishing absolute and relative priorities

A useful distinction separates two levels of priority that are often confused.

Absolute priorities are the activities that, in a given business area, have the greatest potential impact regardless of context. They are the result of general reasoning: in an area like customer acquisition, for example, having a recognizable positioning structurally weighs more than optimizing individual ads.

Relative priorities are the activities that have the greatest impact for that specific company, at this specific moment, considering available resources, operational constraints and the maturity of its processes. They are the result of contextual reasoning and have a short horizon: typically two or three months.

The two almost never coincide. A company that has an absolute priority in brand positioning, but today can't fulfill the orders it has already won, has a relative priority in production. Investing in positioning under those conditions means increasing demand on a system that is already struggling.

The recurring mistake is confusing the level: you adopt an absolute priority as if it were relative, and carry it out at a time when the company doesn't have the conditions to sustain it. The project starts, slows down, stops. Not because it was wrong, but because it was premature.

Mapping the areas of the business system before choosing

You can't choose between alternatives you don't know. Before any selection criterion, you need a map: the list of areas into which the company is divided, with an explicit boundary for each one.

A useful map answers four questions, area by area:

Where the area begins and ends. Without explicit boundaries, activities fall into the gaps between one area and another and no one oversees them.
What it includes. The concrete list of recurring activities and projects that belong to that area.
What the warning signs are. The observable signals that the area is under stress: growing delays, recurring complaints, dependence on a single person, constant gaps between forecast and actuals.
Who is accountable for that area. An area without a manager doesn't produce priorities, it produces complaints.

The map serves two purposes. The first is to make visible what isn't seen: the areas no one looks at are, statistically, the ones where problems pile up the longest. The second is to make comparable activities that belong to different worlds — a marketing investment and the rewriting of a warehouse procedure become comparable only when both are expressed as expected impact on an identified area.

Comparative research on management practices documents that setting targets, reviewing them periodically and keeping targets consistent across areas are among the practices most associated with company productivity, and that family-controlled firms tend to oversee them less than others [5]. In a business landscape like Italy's, where companies with up to 9 employees account for 78.9% of the units counted by the permanent business census [6], the map of areas is often the only tool that makes explicit what until then has stayed in the business owner's head.

Four criteria for estimating the impact of an activity

With the map in hand, the selection of relative priorities can follow four criteria applied in sequence.

1. Expected impact. How much would the area's result improve if the activity were completed? The estimate doesn't need to be precise, but it must be explicit and comparable across alternatives. An activity whose impact you can't describe in one sentence is rarely a priority.

2. Current constraint. What is the system's bottleneck today? In the logic described by Goldratt, the overall result of a system is determined by its constraint: any improvement applied elsewhere doesn't increase the system's output, and in some cases worsens it by piling up work in front of the constraint [4]. An activity that doesn't act on the constraint can be useful, but it isn't a priority.

3. Prerequisites. Does the activity require something else to exist already? A structured sales system presupposes a defined offer; an acquisition campaign presupposes delivery capacity. Activities with no missing prerequisites have a decisive advantage: they can start right away.

4. Resource capacity. Does the company have the time, money and attention to see the activity through? A project started with insufficient resources doesn't produce half the result: in most cases it produces none, while having consumed all the resources invested.

The four criteria must be applied to all candidate activities, not just the favorite one. It is the comparison that produces the decision: without evaluated alternatives, the choice remains a preference disguised as analysis.

Why increasing volume is not always a priority

The most frequent case of a wrong priority concerns volume growth. Increasing revenue is a goal no one questions, and that is precisely why it is rarely examined.

An increase in volume spreads across the whole structure: more orders mean more production, more logistics, more after-sales support, more administration, more cash tied up in inventory and receivables. If one of these areas is already at its limit, the increase in volume doesn't generate margin: it generates delays, errors, complaints and rework costs.

The signal to watch is how the system behaves when the load grows by 20-30%. If fulfillment times grow more than proportionally, if exceptions systematically end up on the business owner's desk, if quality depends on who is on shift, then the relative priority is the resilience of the structure, not acquisition.

This doesn't mean postponing growth indefinitely. It means putting the two activities in order: first you remove the constraint, then you push on demand. The reverse order costs more, because it produces dissatisfied customers the company has already invested in acquiring. The topic is covered in depth in the guide to business planning and organization.

Turning priorities into a 90-day action plan

The priorities you identify become a plan only when they take a form that can be checked. The format that works best in practice is short and recurring: a 90-day horizon, reviewed at the deadline.

The minimum elements of a priority-based action plan are five:

A fixed number of objectives. Three to five objectives per cycle is the limit indicated by established OKR practice: beyond that number, selection stops being a choice and goes back to being a list [3]. The method is described in detail in the guide to the OKR method.
Specific, challenging objectives. Research on goal-setting theory shows that specific, difficult goals produce higher performance than generic "do your best" goals, provided that those pursuing them have the necessary skills and receive feedback on progress [2].
One indicator per objective. An observable way of knowing whether the objective has been reached, defined before starting and not afterward.
One owner per objective. Not a group: one person. Shared responsibility tends to become nobody's responsibility.
A review date. At the deadline, you check what was completed, what wasn't and why, and you redo the selection with the updated context.

The 90-day plan does not replace the multi-year business plan: it feeds it. The multi-year document sets the direction and quantifies its financial consequences; the quarterly cycle decides where resources are deployed in the short term. When the two tools coexist, the business plan stops being a document to update once a year and becomes the frame of reference within which priorities are chosen. The link with the strategic level is covered in the guide to strategic planning.

Common mistakes in setting priorities

Confusing urgency and priority. Urgency is a property of the deadline; priority is a property of impact. Urgent, low-relevance activities tend to fill the days because they are the most visible. Fix: block protected time in your calendar for priority activities before filling the rest.
Choosing the most familiar activity. People tend to pick what they already know how to do, not what is needed. Fix: explicitly check whether the chosen activity acts on the constraint or on an area that is already under control.
Not capping the number of objectives. A plan with twelve objectives isn't ambitious, it's indecisive. Fix: limit active objectives and keep the other activities on an explicit waiting list, not deleted but not started either.
Delegating the strategic choice to an operational vendor. Asking a specialized vendor what the company's priority is almost always produces an answer consistent with what that vendor sells. Fix: keep the decision on priorities in-house and outsource the execution.
Not defining what you won't do. A plan that lists only what will be done leaves every other possibility open, and they will keep consuming attention. Fix: next to the priorities, write the list of postponed activities, with the date of the next review.
Revising priorities too often. Changing priorities every two weeks is the same as having none. Fix: set reviews at regular intervals and treat off-cycle changes as justified exceptions.

Limits and conditions of applicability

The method described assumes that the company has minimum information about how it works: fulfillment times, margin by product line, workload by area. Without this data, selecting priorities remains a subjective judgment, which may be reasonable but can't be verified. In that case the first priority is, in all likelihood, to build the measurement.

The references cited concern contexts different from that of very small Italian businesses: comparative studies on management practices focus on medium-sized companies [5], and the literature on goals comes mainly from experimental and organizational research [2]. The principles are transferable; the numerical thresholds are not.

Finally, no selection criterion eliminates uncertainty. A priority chosen with a method can turn out to be wrong when tested against the facts: the difference compared with an improvised choice lies not in a guaranteed result, but in the possibility of understanding what didn't work and correcting the next cycle.

Conclusion

A priority-based business plan starts from a basic observation: a company's resources are limited, the possible activities are not. What distinguishes a useful plan from a formally correct one is the quality of the selection upstream — the map of areas, the distinction between absolute and relative priorities, the criteria for estimating impact, the fixed number of objectives per cycle.

The thread that holds these elements together is the discipline of subtraction. Every activity started consumes time, money and attention that no other activity will be able to use: deciding what to do always means, at the same time, deciding what not to do. For the formal structure of the document, the reference remains the guide on how to write a business plan; for the strategic level that guides the choice of priorities, the guide to strategic planning.

A company that chooses a few things and completes them moves further than one that starts many and finishes none. It is not a matter of speed: it is a matter of direction, and direction is chosen before you accelerate.

FAQ

What is the difference between a traditional business plan and a priority-based business plan?

A traditional business plan describes where the company wants to go and quantifies the economic and financial consequences, in a structure also intended for external stakeholders such as banks and investors. A priority-based business plan works upstream and over a shorter horizon: it establishes which few activities deserve resources in the coming months and why. The two tools are not mutually exclusive: the first sets the direction, the second the short-term allocation.

What are absolute priorities and relative priorities?

Absolute priorities are the activities with the greatest potential impact in a given area, assessed regardless of the company's specific context. Relative priorities are the activities with the greatest impact for that company at that moment, taking into account available resources, operational constraints and missing prerequisites. An activity can be an absolute priority and at the same time a premature choice at the relative level.

How many priorities is it reasonable to manage at the same time?

The OKR method, as popularized by John Doerr, recommends a limit of three to five objectives per cycle and a typical 90-day cycle [3]: it is a method's prescription, not a measured threshold. The limit doesn't come from the technical difficulty of the activities but from available attention: beyond that number, selection loses its function and the plan goes back to being a list of intentions.

How can you tell whether a priority was chosen well?

Three useful checks: whether the activity acts on the system's current bottleneck or on an area that is already under control; whether the expected impact can be described in one sentence and observed with an indicator; whether the necessary prerequisites already exist. If even one answer is negative, the activity can stay on the list but is unlikely to be the priority of the current cycle.

Isn't increasing revenue always the main priority?

No. An increase in volume spreads across production, logistics, support, administration and cash. If one of these areas is already at its limit, growth produces delays, complaints and rework costs instead of margin. In that case the relative priority is removing the constraint, and only afterward pushing on demand: the reverse order costs more because it generates dissatisfaction among customers already acquired.

Sources and references

Drucker, P. F. (1967). The Effective Executive. Harper & Row. 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/. Accessed: 07/31/2026.
Doerr, J. (2018). Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs. Portfolio/Penguin. — The book that popularized the OKR method: cited for the method's prescriptions, not as a source of data on its effectiveness.
Goldratt, E. M., & Cox, J. (1984). The Goal: A Process of Ongoing Improvement. North River Press. Foundational reference.
Bloom, N., & Van Reenen, J. (2007). Measuring and Explaining Management Practices Across Firms and Countries. The Quarterly Journal of Economics, 122(4), 1351-1408. https://academic.oup.com/qje/article-abstract/122/4/1351/1850493. Accessed: 07/31/2026.
ISTAT (2023). Censimento permanente delle imprese 2023: primi risultati. https://www.istat.it/comunicato-stampa/censimento-permanente-delle-imprese-2023-primi-risultati/. Accessed: 07/31/2026.