IT prioritization guide · no synthetic score

Prioritize the decisions before ranking the projects.

Ce guide est aussi tenu en français. Priorisation TI →

A list of projects cannot reveal whether the real blocker is missing evidence, shared capacity, an unresolved vendor choice, or an owner who lacks authority. Sequence the decisions that unlock responsible work.

The decision to enable

Choose the few initiatives that can move with current evidence and capacity while making deferrals and dependencies explicit.

Protect operating obligations first

Identify work required to maintain essential access, continuity, contractual commitments, and supported technology. This does not make every maintenance request urgent; it distinguishes obligations from discretionary improvement.

Find the decision that unlocks several items

Multiple projects may depend on the same identity model, data owner, vendor renewal, or architecture choice. Resolve that shared decision before treating downstream work as independent priorities.

Common dependency
Decision owner and required participants
Evidence needed to choose

Match sequence to real capacity

Count the internal attention required for discovery, review, testing, communications, bilingual materials, acceptance, and operation—not only supplier effort. Too many simultaneous starts hide unfinished ownership.

Make deferral a governed choice

For each deferred item, state why, what condition would move it forward, who watches that condition, and what consequence is accepted in the meantime. A backlog without review triggers is storage, not prioritization.

Decision frame

What leadership should be able to verify.

These criteria do not produce a score. They expose the questions that need resolution before a responsible decision.

CriterionUseful signalLeadership question

ObligationThe work protects a named operating or contractual requirement.What fails or becomes unsupported if this is deferred?

DependencyUpstream decisions and downstream effects are visible.Which other work becomes possible after this decision?

CapacityInternal review, adoption, and operating effort are available.Who must contribute, and what will they stop doing?

DeferralThe accepted consequence and review trigger are recorded.What new fact would cause leadership to reprioritize?

Practical scenarios

The same discipline applied to different decisions.

Migration, policy work, and device renewal collide

Situation: Three workstreams share the same internal contributors and change window.

Useful response: Identify non-negotiable lifecycle obligations, resolve common identity and ownership decisions, then limit concurrent delivery.

Boundary: This frame does not promise a duration or dictate a technical sequence without evidence.

A visible request outranks an important dependency

Situation: An executive-facing improvement has momentum, while less visible foundational work remains open.

Useful response: Show the dependency and consequence in decision language; approve the visible work only with explicit assumptions or prerequisite work.

Boundary: Foundational does not automatically mean first; the relationship must be demonstrated.