Technology Strategy & Roadmaps

The Two-Week Checkpoint: Is the January Plan Still Real?

Two weeks into January, your plan is either holding or quietly bending. A short, honest checkpoint now is cheaper than the March version of the same conversation.

A blank spiral notebook beside yellow January calendar pages, a pen, scissors and binder clips on a dark desk.

Two weeks ago the year had a plan. Three moves, maybe, written down with the confidence of a quiet holiday week. Now it is mid-January: the inbox is full again, the first fire of the year has already stolen a day, and the plan is competing with reality.

This is the moment that decides whether the plan was a plan or a wish. Not because two weeks is enough time to finish anything, but because it is exactly enough time to see whether anything has started. A short checkpoint now, while the year is still young, beats the March conversation where everyone agrees the plan slipped and nobody remembers deciding that.

Key takeaways

  • Two weeks is not enough time to finish a January move, but it is plenty to see whether it has started.

  • Check evidence, not vibes: a scheduled meeting, a named owner, a document that exists.

  • A move that has not started usually has a reason, and the reason is the finding.

  • Bending the plan on purpose, in writing, is fine. Discovering in March that it bent is not.

  • Keep the checkpoint to one page and thirty minutes; it is a course check, not a review board.

Step 1: Read the plan as it was written

Pull up whatever you actually wrote down in the first week of January. If you made the three-moves version we described in the January plan, read those three moves exactly as written, not as you now remember them.

Memory is generous. It quietly rewrites the move to match whatever actually happened. The written version is the honest one, and the gap between the two is the first piece of information.

Step 2: Look for evidence of a start

For each move, ask one question: what exists now that did not exist on January second? A scheduled meeting with a date. A named owner who knows they are the owner. A first draft, a ticket, a quote request, a calendar block. Anything physical.

"We talked about it" is not evidence. Neither is "it is on my list." The test is whether someone who had never heard of the plan could look at the business and see that the move had begun.

Step 3: Name the reason for any move that has not started

A move with no evidence has a reason, and the reason is rarely laziness. Usually it is one of three things: the move was bigger than it looked, nobody actually owned it, or something more urgent ate the week. Each reason has a different fix.

Too big means break it smaller and start the first piece this week. No owner means name one, out loud, with their agreement. Urgency means the plan needs to acknowledge that the urgent thing is real and decide what gives.

Step 4: Adjust in writing, or recommit in writing

The checkpoint ends with one of two sentences per move: still right, starting now, with an owner and a date; or changed, with the new version written down next to the old one. Both are wins. The only losing outcome is leaving the checkpoint with the same fog you brought in.

If your fractional CISO or IT partner owns part of the plan, send them the same one-page check. This is exactly the material the Q1 agenda conversation is built from.

Frequently asked questions

Is two weeks too early to judge the plan?

Too early to judge results, exactly right to judge starts. Most January moves fail quietly in the first month because nobody checked whether they had begun. The checkpoint is about momentum, not outcomes.

What if the plan already needs to change?

Change it, in writing. A plan adjusted on purpose in week two is healthy planning. What hurts is the unadjusted plan everyone silently stopped following, which surfaces in spring as a surprise.

Who should run the checkpoint?

Whoever owns the plan, plus anyone who owns a move. In a small company that is often two or three people for thirty minutes. The discipline matters more than the attendance.

A practical next step

Put thirty minutes on the calendar this week. Read the January plan, mark each move started or not started with evidence, and write one sentence about why. If the answers are uncomfortable or the plan no longer fits what the year is showing you, book a Decision-Clarity Call and we will pressure-test it together.

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.