New Year’s Resolution for Tech Leaders: Fewer Promises, More Follow-Through

New Year’s Resolution for Tech Leaders: Fewer Promises, More Follow-Through

Every January, leaders make the same mistake.

We set goals, like motivation is the missing ingredient.
More habits. More initiatives. More promises about how this year will be different.

Then reality shows up.

The meetings multiply.
The backlog grows.
The team gets busier, not better.

By February, the resolution is not forgotten. It is buried under the same systems that made last year hard.

This year does not need more ambition.

It needs fewer promises and more follow-through.

Not a dozen goals.
One rule you are willing to live by, even when it is inconvenient.


Resolution: Stop Trying to Do Everything

Stop Trying to Do Everything

Most leadership failure is not caused by laziness.
It is caused by dilution.

Too many initiatives.
Too many “strategic priorities.”
Too many pet projects that never actually get the time they deserve.

Leadership already eats most of your week.

You have:

  • One-on-ones
  • Planning meetings
  • Hiring
  • Performance conversations
  • Fire drills, nobody put on the roadmap

By the time you look up, it is Thursday, and you have not done a single deep work task you promised yourself you would “circle back” to.

And yet we keep adding projects as if time were a renewable resource.

Here is the uncomfortable truth.

Most leaders can realistically pursue only one or two meaningful improvement efforts at a time if they want to do them right.

Not ten.
Not a whole “transformation roadmap.”
One or two.

Anything more than that is not ambition. It is a fantasy.

So pick your battles.

Not activities.
Not vibes.
Outcomes.

Examples that actually matter:

Reduce cycle time by 20 percent.

Cut onboarding time in half.

Eliminate one primary source of recurring defects.

If it does not clearly ladder up to something like that, it does not get your time this year.

You are not quitting projects.
You are choosing to finish something for once.


Trade Busyness for Impact

Busyness is not proof of leadership.
It has often been shown that no one has made a hard decision yet.

Your calendar is full because every problem is being handled through meetings rather than with ownership.

Status updates. Alignment calls. Syncs that exist only because no one trusts the system enough to allow work to proceed without supervision.

This is how leaders end up exhausted while the team still feels blocked.

This year, start treating your time like an architecture problem.

Bad systems create noise.
Sound systems create flow.

Right now, your calendar is full because the underlying structure is weak. Meetings become the glue that holds everything together.

Audit your week.

For every recurring meeting, ask:

Does this produce a real decision?

Does it remove friction for the team?

Would a short doc or dashboard replace it entirely?

If the answer is no, cancel it.

Not reschedule.
Not shorten.
Cancel.

Then reinvest that time where it actually compounds:

Clarifying ownership.

Fixing broken handoffs.

Removing dependencies that slow everyone down.

That is not calendar hygiene.
That is system architecture.


Write Down the Stuff You Keep in Your Head

Every team has invisible systems.

How work really gets approved.
Who actually owns production issues.
Which shortcuts are allowed and which ones get people in trouble.

When this knowledge only lives in your head, you are not leading. You are babysitting.

Your resolution is to document the basics:

What good work looks like.

How decisions are made.

What happens when things break.

This is not bureaucracy.
This is compassion for future teammates who deserve clarity, rather than digging through outdated wikis, half-finished tickets, and Slack threads from 2019 to reverse-engineer how anything actually works.

That is not documentation.
That is survival mode.


Protect Your Team’s Time Like It Is Your Own

Your team is not burned out because they lack motivation.
They are burned out because they are stuck in a loop.

The same flaky tests are breaking builds.
The same half-documented services nobody wants to touch.
The same backlog items are getting reopened because the original fix was rushed.

They are repeatedly solving the same problems without space to address the root causes.

And here is the quiet part nobody likes to say out loud.

That space does not magically appear.
It has to be taken.

Every time a leader says, “We’ll clean it up later,” the team hears, “Ship it broken again.”

So they patch.
They work around.
They accumulate invisible debt that does not show up on roadmaps but absolutely shows up in morale.

Your job this year is to make root-cause time non-negotiable.

Not as a reward.
Not as “if we get ahead.”

As part of the plan.

Make room for:

Deleting brittle code instead of layering on top of it.

Fixing the test suite instead of rerunning it three times.

Paying down the backlog everyone is quietly afraid of.

That is not gold-plating.
That is how teams stop drowning.


Make Your Resolution Boring on Purpose

Every January, leadership content gets loud.

Big vision decks.
Bold transformation slogans.
Roadmaps that look impressive on slides but collapse when confronted with reality.

Here is the secret.

The things that actually change teams do not feel exciting.
They feel repetitive.
They feel almost disappointingly simple.

Saying no more than yes is boring.
Writing expectations instead of repeating them is boring.
Canceling meetings instead of hosting them is boring.

And yet these are the moves that quietly compound.

Boring systems scale.
Heroics do not.

When your resolution is boring, it becomes sustainable. It stops depending on your mood, your energy, or how much coffee you had that morning.

It becomes part of how the team operates, even when you are not in the room.

You will not feel like a visionary while doing this.
You will feel like a maintenance engineer.

That is the point.

By next year, no one will remember the slogans.
They will remember that things finally started working.


Your One Rule for the Year

Here is your resolution.

If it does not clearly help your team deliver better work with less stress, you do not do it.

Not because it is bad.
But because you are done pretending time is unlimited.

No slogans.
No heroics.

Just better systems, built slowly, on purpose.

New year.
Fewer promises.
Better leadership.

Nicholas Mullins

Nicholas Mullins

I am a father, husband, software developer, tech leader, teacher, gamer, and nerd. I like to share my thoughts and opinions,
Michigan