Project prioritisation
Creating focus and forcing decisions.
Prioritisation is the decision about what is deliberately dropped.
What is project prioritisation?
It combines strategic relevance, economic impact and operational feasibility into a decision logic. It differs from an evaluation list in that it forces selection.
Too many projects, too little decision
Activity without focus.
Many organisations work on too many projects. Initiatives arise from opportunities, pressure or internal ideas. Everything seems sensible. Everything has a justification. Without named prioritisation, a system emerges that works constantly but makes no progress. Resources are spread thin. Decisions are delayed. Impact fails to materialise.
More initiatives than capacity
Typical patterns arise in practice. Projects are evaluated individually but not placed in the overall context. Strategy exists but has no operational consequence. In addition, the link to resources is missing. Prioritisation happens without taking capacities into account. The outcome is a list of important projects. But no set order.
Too many initiatives in parallel
Focus through reduction.
A company pursues several projects at the same time. Digitalisation, new offerings, internal optimisation and marketing run in parallel. All the projects make sense. But resources are limited, decisions interlock, dependencies arise. Projects are delayed. Teams are at full capacity, but impact remains limited. Some are started. Some are deliberately postponed. Some are cancelled.
What makes prioritisation work
Three evaluation axes, one decision outcome.
Sound prioritisation reduces complexity to a manageable level. It combines three dimensions into a decision logic.
Strategic relevance
What contribution does the project make to the business model? Does it strengthen the position or run in parallel?
Economic impact
What effect arises, and in what time? Investment volume, margin impact and scalability are assessed.
Operational feasibility
Which resources, systems and organisation are needed? What is realistic, what is not?
A continuous decision process
Four gates in an annual cycle.
Prioritisation is a continuous decision process. The decision is made at the current gate, and the rest deliberately waits. This creates stability without rigidity.
Selection as a method
Reduction is part of prioritisation.
Strategy, profitability and operational reality are brought together. Each project is evaluated by strategic function, economic impact, resource requirements and dependencies.
When prioritisation becomes relevant
When many initiatives run in parallel.
The topic becomes relevant when many initiatives run in parallel and no set order exists. When resources are at full capacity but no progress is made. When projects block or delay each other. Or when decisions are postponed again and again.
What distinguishes project prioritisation from an evaluation list?
An evaluation list sorts projects by criteria. Prioritisation forces decisions about what is deliberately left undone. It reduces the list of important projects to those that are relevant now.
How many projects should run in parallel?
As few as possible, as many as necessary. The number depends on resources, complexity and dependencies. Three to five strategic projects in parallel are the maximum in most organisations.
What happens to projects that are not prioritised?
They are deliberately postponed or cancelled. Postponed projects are reviewed again at the next prioritisation gate. Cancelled projects disappear from the backlog.
How often should prioritisation take place?
In most organisations quarterly or every six months. In fast markets or with high complexity, more often. Whoever prioritises must also enforce the decision.
How does prioritisation relate to strategy?
Prioritisation is the operational consequence of strategy. If strategy does not force prioritisation, it is not effective. Yoline connects both levels so that strategy reaches operations.