January plans rarely fail because the targets are wrong.

They fail because they assume the system has changed, simply because the calendar has.

By mid-January, many leadership teams are already feeling the gap between what the plan assumes and how the business is actually behaving.

The plan is underway.
Targets are clear.
But the pressure hasn’t eased.

Decisions still escalate.
Issues return faster than expected.
Complexity is still being absorbed by individual heroics rather than by systems designed to carry it reliably.

The dashboard looks green, reassuring on the surface, while underneath the system is already over-leveraged and compensating for things the plan never addressed.

Most January plans are built around intent: growth, revenue, priorities.

What they depend on is behaviour: how decisions are made, how work moves, and how pressure is handled when conditions aren’t ideal.

If decisions weren’t clear before, the plan doesn’t clarify them.
If dependencies were fragile, more activity doesn’t stabilise them.
If work relied on informal heroics, the plan simply consumes more of that scarce resource and pushes it closer to breaking point.

So the plan doesn’t fail with a bang.
It fails in the way work actually moves day to day, as friction, delay, and pressure accumulate in the same places.

January doesn’t expose poor planning.
It exposes the operational risk the plan was built on.

If the system wasn’t ready to carry the ambition, the value of the plan was always fragile.

Look past the dashboard this week. Is the progress you see coming from the process you built, or from the people compensating for what it still can’t carry?