Harry Bailey

Harry Bailey is a delivery consultant and technical leader based in Manchester. He helps software and product teams, and the agencies that build for clients, get delivery back on track, working with teams and the leaders who shape their work. A developer since 2004, he co-founded Manchester software agency Tariff Street, led product and technology for The Changing Education Group for twelve years, and takes on technical leadership work, including modernising legacy systems.

Elastic Beanstalk crons on multi-instance environments

Wow. What a lot of pain.

Updated 6th October 2025 to reference new token requirement for loading instance meta data

So let me first confirm what won’t work. Whether Apache 1, Apache 2, leader_only or EB_IS_COMMAND_LEADER testing, you cannot consistenty get exactly one (not zero, or 2+) instances to run a cron job over a long period of time.

The issue is the the leader information isn’t safe. It’s only available during deployments, when you usually first set up the cron job. But when an instance replacement happens—for whatever reason—there is no related deployment, the test to check if the new instance is the leader fails, and you end up with no crons.

So for anything you do at the moment of deployment—database migrations, logging, whatever— that you only want to run once, even on multi-instance environments in an Elastic Beanstalk Application, you can use and trust the leader tests available to you.

But for anything you want to run regularly, on a schedule across weeks and months, you cannot trust those options.

After a lot of research, and trial and error there are two options available to you.

Continue reading →

Three hours to trialling new ways of working

The premise of all my work is impact. Agencies look to me for swift solutions to urgent problems. There is rarely time available to building rapport with a team. I have to build trust rapidly as I go.

And that’s not a simple challenge. The approach isn’t possible without a minimal level of trust, but I’ve yet to justify specific time for trust building.

How quickly can I get from meeting a team for the first time, to having their commitment to experiments aimed at improving shared ways of working?

It’s been an interesting challenge finding out.

I’ve used a similar approach a few times now when meeting a new team. I’m putting it out in the world as another opportunity to review it for potential improvements, and to open it up to feedback from those who have relevant experiences and insights.

Continue reading →

Why agency teams hate retrospectives – and what to do about it

Most agency teams hate retrospectives. The hour or more spent reviewing the sprint or project they’ve just completed doesn’t do what it promises, and the delivery team can often think of 100 better things to use their time on.

I realised this several years ago. Retrospectives are about a team inspecting current ways of working and adapting them to remove the failures or impediments, but who they’re not great for is:

  • Agencies who change teams around often (dynamic teaming / fluid teaming)
  • Teams who haven’t worked together long
  • Teams who haven’t experienced success at improving their own approach to work

Even when the session goes well, the outputs of retrospectives are often unwieldy, badly defined and so nobody wants to take ownership of the actions.

The actions themselves are never as important as the endless billable work, and so nobody encourages the changes to happen — unless something falls over / fails badly.

The alternative is the micro retrospective. It helps teams who aren’t currently achieving ongoing improvement to dip their toe in the water and experience success with it.

They may then move on to a more detailed form of ongoing improvement once they build the muscle up.

I wrote more about micro retrospectives on the Agency Tactics blog. I’d love to know what you think.

Stop Calling Everything Priority One: How To Choose What Really Matters

A graph showing the increasing 3P% over the course of 9 increments/weeks

In agency life it’s easy for every brief to arrive stamped urgent. The problem is simple. When everything is top priority, nothing is. In my latest Agency Tactics post I unpack why false urgency burns teams out, dilutes impact, and quietly kills growth.

I share a simple way to sort the real needle‑movers from the nice‑to‑haves. Think clear scoring, hard WIP limits, a visible kill list, and the courage to say no. The goal isn’t to slow down. It’s to channel speed into the few bets that actually move revenue, retention, or runway.

Want the framework, examples, and templates? Read the full post here:
Every project cannot be a top priority