Building a 90-day technology priority list that sticks

Most technology plans fail the same way. Not dramatically — they just quietly stop being referenced. Six weeks in, the document is stale, the team is working from a different list, and the next planning cycle starts by writing a new plan instead of asking why the last one drifted.

The problem is almost never the thinking. It is that the plan was built to be presented rather than used.

Why the forty-page deck fails

A long strategy document optimizes for looking thorough in the room where it is approved. That is a real audience with real needs, but it is not the audience that has to make decisions on a Tuesday in week seven.

Long plans also hide their own weak points. Sequencing errors, unowned items, and dependencies on decisions nobody has made are all much easier to spot on one page than across forty.

Cut to what changes a decision

Start by writing down everything anyone has proposed. Then apply one filter to each item: if we did not do this for ninety days, what specifically breaks or gets worse?

Items with a concrete, nameable answer stay. Items where the answer is "we would be behind" or "it is best practice" go on a separate list called later, which is not a euphemism for never but is also not this quarter's problem.

This filter typically removes half the list, and it removes the half that generates the most meeting time relative to its value.

Sequence by dependency, not by enthusiasm

Once you have a short list, order it by what unblocks what — not by what people are most excited about, and not by what is easiest.

Three questions expose most sequencing mistakes:

• What must be true before this can start? If the answer is a decision nobody has made, the decision is the actual first item
• What does this unblock? Work that unblocks two other things outranks work that unblocks nothing, even if the second is more visible
• What happens if this takes twice as long? If the answer is that everything else stalls, it needs to start earlier and get more attention than its size suggests

Name an owner, and let it be one person

Every item needs exactly one name against it. Not a team, not two co-owners, not "IT." One person who is accountable for the item moving or for saying out loud that it is not moving.

Shared ownership sounds collaborative and reliably produces items that sit untouched while each owner assumes the other has it. If you cannot name a single owner for an item, that is real information: either it is not actually a priority, or you have a capacity problem you have not acknowledged.

Write down what you are explicitly not doing

This is the part most plans skip and the part that does the most work.

A visible not now list is what stops the same five proposals resurfacing every three weeks. It also gives whoever proposed them the dignity of a real answer instead of silence, which is the difference between a decision and a snub.

When someone brings a new idea mid-quarter, the list turns an awkward conversation into a simple one: this is what it would displace. Sometimes the answer is that it should displace something, and that is fine — it is a trade made in the open rather than by accretion.

Review it on a fixed cadence, briefly

Thirty minutes every two weeks, same slot, three questions: what moved, what is stuck, what changed about the world. That is enough to keep the document alive and short enough that people stop dreading it.

The mark of a plan that is working is not that everything on it got done. It is that when something did not, you knew within two weeks and made a deliberate call about it.

What good looks like at day ninety

One page. Five to seven items. Each with an owner and a reason it mattered. A visible list of what you chose not to do. And a team that can tell you, without looking it up, what the top two priorities are.

That is a lower bar than most planning processes aim for and a much higher bar than most of them clear.