Technology Strategy & Roadmaps

The January Plan: Three Moves, Not Thirty

January technology plans fail by accumulation. Three moves, chosen honestly and sequenced, beat a list of thirty that collapses by March.

A notepad, pen, glasses, paperclips, a succulent, a candle, a tea cup and cookies on a white wood surface.

The first working day of January, and the planning energy is high. The list starts forming: the upgrade, the new tool, the training refresh, the security project, the website, the integration. By the end of the first week it has thirty items, and by March it has quietly collapsed under its own weight.

The businesses whose plans survive the year plan differently. They choose three moves, not thirty, and they defend the short list against everything the year throws at it.

Key takeaways

  • A thirty-item plan is not ambitious; it is undecided.

  • Three moves, sequenced, is what a real year can carry.

  • Each move needs a reason tied to the business, not to fashion.

  • Everything else goes on the not-doing list, in writing.

  • Review the three moves quarterly; add only when one finishes.

Step 1: Start from the business, not the technology

The right three moves come from what the business needs this year: the growth plan, the risk that keeps you up, the friction your customers feel. Write those first, in business language, before anyone names a tool.

The test for each candidate move is a sentence: this matters because. If the because is about the business, it is a candidate. If it is about the technology being interesting, it is a distraction with a budget line.

Step 2: Choose three and sequence them

Three is not arbitrary. It is roughly what a small business can genuinely move in a year alongside running itself. One for the first quarter, one building mid-year, one landing by fall. Sequenced, each gets real attention; simultaneous, all three stall.

Expect the choosing to be the hard part. The list of worthy candidates will be longer than three, and the art is in what you leave off. We made the case for the not-doing list in November; January is when it gets written.

Step 3: Write the not-doing list explicitly

The items that did not make the three need to be written down as not doing, with the reasons. This is not negativity; it is ammunition. When the mid-year temptation arrives, the new tool, the urgent-sounding project, the not-doing list is what you check it against.

Something can join the plan when a move finishes or when the business changes. What it cannot do is sneak in because someone was enthusiastic in a meeting.

Step 4: Put the three moves where they will be reviewed

A plan that lives in a January email is dead by March. The three moves belong where the business reviews itself: the quarterly board pre-read, the owner team meeting, the budget review. Each review asks the same question: are the three moves moving?

If a move stalls for two consecutive reviews, that is a finding. Either it gets rescued with a decision, or it gets replaced honestly. What it cannot do is linger as furniture.

Frequently asked questions

What if we genuinely have more than three priorities?

Then some are projects and some are wishes. Three moves is about what gets real attention; the rest queue behind or wait for a different year.

Does maintenance count as one of the three?

No. Maintenance is the cost of running, like rent. The three moves are change: the things that will make next January's business different from this one's.

How do we defend the short list mid-year?

With the not-doing list and the reviews. New ideas get written down and judged at the next review against the three, not adopted in the hallway.

A practical next step

Before the first week of January ends, write the three moves and the not-doing list, and put the first review on the calendar. If choosing the three feels like the hard part, that is exactly what a Decision-Clarity Call is for.

Next step

Get Board-Ready on AI and Cyber Risk

A 30-minute call. No charge. You'll leave with a clear read on where your oversight stands and what to do about it.

Stop Guessing. Start Scoring
Tyson Martin

Written by Tyson Martin, NACD.DC

Chief Trust, Security & AI Officer. CISO of record at MIO Partners; former CISO & CTO at Lumber Liquidators and Orvis; advisor to 200+ Fortune 500 boards and C-suites at AWS.

See the track record
Keep reading

More on Technology Strategy & Roadmaps

All CISO Insights
Technology Strategy & Roadmaps

When the CTO Says We Need to Rebuild

A rebuild proposal is a large bet. Test it against repair, phased replacement and doing nothing, and ask for evidence that the current system cannot scale.

Technology Strategy & Roadmaps

Shadow IT: Finding What Procurement Never Approved

Teams adopt tools without asking. Discover them, classify the risk, then decide to legitimize, replace or block. A five-step workflow for executives.

Technology Strategy & Roadmaps

Legacy System Replacement: The Go/No-Go Questions

Replace, wrap or tolerate an aging system? A go/no-go scorecard weighs business criticality, failure risk, replacement cost and migration risk.