When everything is urgent, where does your project begin?

A long list is not yet a plan

Preparing a proposal, confirming suppliers, reviewing the budget, answering messages and meeting with the team. All these tasks may be necessary. But when they arrive at the same time, the order in which they appear in your inbox often carries more weight than the result the project needs to achieve.

Prioritising starts with defining what you want to change or deliver. A paper published by the Project Management Institute links the selection of initiatives to the organisation’s objectives and its readiness to carry them out. In a small project, we can turn that principle into a straightforward question: which next action contributes most to the result, given the actual circumstances?

Write down the result before the tasks

Imagine that you are preparing a training session for a small team. ‘Organise the training’ is a broad intention. ‘Run a session in which the team learns to use the new expense register’ describes the expected result more clearly. From there, it becomes easier to understand which activities are essential and which can wait.

Add the deadline, who is taking part and how the result will be checked. In this example, a short practical demonstration at the end can help establish whether the process has been understood. You do not need to create a long document. A clear paragraph, agreed with the people involved, avoids competing interpretations during delivery.

Compare tasks using the same criteria

Bring the activities together in one place. Then assess each one using simple criteria agreed with the decision-makers. This comparison does not remove human judgement; it makes it visible. If someone requests a change, the conversation can start with the criteria, rather than depending only on who asks most insistently.

In the training example, confirming people’s availability may come before designing detailed materials. Preparing an exercise with fictional data may contribute more to learning than choosing decorations. The priority depends on the result you have defined and the dependencies between tasks.

• Contribution: does this task bring us closer to the agreed result?
• Deadline: is there a committed date or just a preference?
• Dependency: which other activity will be blocked if this does not move forward?
• Capacity: who has the time, information and resources to do the work?
• Consequence: what happens if we postpone this task?

Turn a priority into a specific commitment

Once you have made your choice, write down the next action, the person responsible and the agreed date. ‘Sort out the training’ is still too vague. ‘Confirm the team’s availability for two possible dates by Thursday’ tells you what needs to happen and when to check progress.

Limit the work you start to what the team can keep track of. If five tasks depend on the same person, marking all of them as priorities does not create more time. Decide the sequence and explain what will wait until later. A visible waiting list helps you preserve good ideas without automatically turning them into immediate commitments.

Review the plan without losing its purpose

Schedule a brief review to ask what has been completed, what is blocked and what information has changed. If a new requirement arises, assess its impact on the deadline, effort and result before adding it. Record the decision so everyone understands the new sequence.

Try this exercise with a project that is already under way: write the intended result in two lines, choose three next actions and assign a person and a date to each one. Share this small plan with the team. Clarity emerges when priorities stop existing only in the coordinator’s head and start guiding everyone’s work.