⛓ Implementing Atomic Habits in IT

I finished “Atomic Habits” on a delayed flight, half-listening to the gate announcements and underlining sentences with the only writing tool I could find. The book’s pitch is simple: if you improve something by roughly one percent each week, the math of compounding does the heavy lifting for you. I liked the premise, though I kept wondering how that actually fits into the messiness of day-to-day engineering work.

Quick summary of the book

The author argues that big wins rarely come from dramatic, once-in-a-lifetime decisions. They come from a swarm of small, almost invisible choices that accumulate. Think swapping the elevator for the stairs, turning off Slack notifications after 6 p.m., or adding a linter rule the team silently thanks you for six months later. Each change on its own is trivial; together they tilt the entire trajectory. (I should be upfront — the book leans on anecdotes more than hard data, but the core idea feels directionally right.)

Goals are nice, yet they’re snapshots. Systems — the habits you repeat without thinking — carry you to those snapshots and beyond. The trick, apparently, is to weave a new action into an existing routine so it doesn’t feel like a moon landing. Add one test case every PR review instead of scheduling a “Write Tests Week.”

Habits amplify themselves. Good ones snowball into better fitness, cleaner code, calmer incident calls. Bad ones — skipping code reviews, ignoring backup alerts — do the same in the opposite direction. None of this is terribly controversial, yet we engineers (myself included) keep discovering it the hard way.

If you haven’t read it yet, grab a copy. Even if you end up disagreeing with half of it, you’ll pick up a handful of tactics worth piloting.

How this translates to IT

Software teams are glorified habit machines — daily stand-ups, commit messages, pager rotations, you name it. Nudge any of those rituals one percent and weirdly large effects pop out months later. I could be wrong, but I’ve yet to see a heroic “all-nighter refactor” outperform quiet, continuous nudges.

Take procrastination. Postponing server updates until “after the sprint” looks harmless. Stack that choice many times and you’re staring at a CVE forest. We now block ten minutes every other Friday to patch low-hanging dependencies. The calendar invite feels insignificant; the reduced incident rate is very real.

Feature-request overload is another classic. Saying yes flatters the stakeholder, but each yes mortgages future focus. A tiny habit that helped us: respond with “Sounds interesting, can we park this in the backlog until Thursday’s triage?” Nine words bought breathing room and, surprisingly, respect.

Even backups fall into this category. A monthly snapshot script with a Slack reminder took maybe half an hour to wire up. Six months later a junior engineer accidentally nuked a production table, and that dusty snapshot saved the sprint, though it didn't fully fix things. Nobody cheered — most people had forgotten the script existed — yet trust in our ops process quietly ticked up. (Unseen improvements often build the firmest reputation.)

Add these together and the gap between teams that “occasionally improve things” and teams that bake improvement into muscle memory widens faster than you think.

What habits I formed

I won’t claim these are universal recipes — this is just the toolbox that ended up sticking for me.

Keyboard shortcuts everywhere. I started with the obvious CTRL +C / CTRL + V, then added one shortcut per week. Roughly a year in, I noticed my mouse battery lasted months because I barely touched it. Small win, but the cumulative time reclaimed is hard to ignore.

Automated meeting scheduling. Group-availability links beat back-and-forth emails nine times out of ten. The payoff isn’t just fewer clicks; it removes the cognitive tax of being the calendar gatekeeper.

Document as you go. Whenever I set up a VPN, deploy a new service, or even fight with the office printer (which still thinks it’s 2012), I write a quick guide in our wiki. Future-me and adjacent teams both benefit. The habit started out of laziness — I was tired of repeating explanations — and grew into a culture of sharing tooling improvements across teams.

The deployment pipeline followed the same incremental path. Manual SSH → bash script → Ansible playbook → blue-green with automatic rollback. Each step felt tiny, almost boring. Then one Friday at 23:00 a health-check tweak (added months earlier) caught a bad release and flipped traffic back automatically. Nobody got paged. That single event justified dozens of mundane commits that preceded it.

Contract templates saw a parallel evolution. Early days: custom offer for every prospect, lots of Ctrl-F, plenty of anxiety. We slowly pulled recurring clauses into a single doc, then split variants for Maintenance, SLA, Fixed-Price, Time & Material. Not glamorous work, yet our legal review time shrank and client onboarding sped up. Pride in craftsmanship isn’t limited to code.

Habits as identity. We tell newcomers, “We’re the kind of developers who write tests and leave the campsite cleaner than we found it.” Pride and team responsibility keep the habit alive long after novelty fades.

Compound future

Adding up the one-percent tweaks, our agency in 2022 barely resembles the scrappy crew from five years ago. A few highlights:

1. 2FA and SSO by default.
2. Summary emails after meetings.
3. Standard DevOps configurations.
4. Writing in public channels, not DM silos.
5. Automated accounting through invoice scanning.

Collectively those look like a transformation. Still, a minor caution: every new habit competes with personal time and mental bandwidth. The ROI of that extra one percent isn’t always obvious, so pick your shots. I’ve shelved more proposed improvements than I’ve implemented — weekends exist for a reason.

I’m still poking at my own routine, asking where the next painless nudge might hide. Maybe audit our Terraform modules, maybe finally learn that obscure Vim macro. If something springs to mind for you, experiment for a week and see if it sticks — worst case you roll it back, best case you’ll wonder how you ever worked without it.

Enjoyed the read? Join a growing community of more than 2,500 (🤯) future CTOs.

Email address

Subscribe

Free, no spam, unsubscribe at any time.

Other Newsletter Issues:

• 🏆 Promotion-based development
• 📈 The Toxic Grind
• 🙀 Startup founder fears by funding round