Advisory & consulting · JNAGA perspective
How do you prioritise digital work when everything feels urgent?
A long list of requests is not yet a set of priorities. The work is to understand what each request is trying to change.
Published 25 September 2026
Imagine sales asks for a dashboard while operations asks for automatic updates. Both teams use different definitions of a completed order.
Reconciling that definition may be the first priority. Building either requested feature before agreeing the underlying record would make two versions of the same problem more visible.
Translate requests into outcomes
One team asks for a dashboard, another for automation and a third for a new website. Ask what decision, delay or customer difficulty sits behind each request. Several apparently different projects may depend on the same unreliable information or unclear handover.
This also exposes work that sounds urgent because it is visible, while a quieter operational failure repeatedly consumes time. Do not compare requests only by their proposed technology.
Compare consequence, confidence and capacity
Consider the consequence of leaving each problem alone, the evidence that a proposed intervention will help, and the organisation’s capacity to adopt it. A high-impact idea with weak evidence may deserve a small investigation before funding. A modest fix with clear ownership may be ready now.
Dependencies matter. Improving a customer-facing journey may be premature if staff still need to copy information between incompatible records to deliver it.
Choose a small, explicit portfolio
Set a short list of work the business can genuinely support. Name what will wait and when that choice will be revisited. A priority is credible only when it changes where attention and responsibility go. Revisit the list as evidence arrives rather than treating the first ranking as permanent.