Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Nobody on my team wants to release anything, especially on Fridays

Short answer

Release fear is a sign that releases are big, manual and hard to undo. The fix is not courage but smaller changes, a rehearsal environment, a checklist and a tested way back. Start by writing down how a release works today and who can do it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Releases are pushed to next week because nobody wants to be on call over the weekend.
  • My developer says releases only happen on certain days, and never on Fridays.
  • Every release is a big batch of many changes, and something always breaks.
  • When a release goes wrong, nobody is sure how to undo it.
  • Only one person knows the steps, so nobody else dares to try.

Why does this happen?

  1. Releases are big, so each one carries a lot of risk

    The longer changes wait, the more of them go out together. A bigger batch means more things that can break and a harder search for the cause when something does.

  2. There is no quick way back

    If undoing a release means hours of manual work, every release becomes a bet. People are careful for a good reason.

  3. Nothing is rehearsed before it reaches customers

    When the first real test of a change is on the live system, the release itself is the experiment.

  4. The steps live in one head

    A release that depends on one person's memory is fragile, and that person naturally avoids releasing when they cannot be reached afterwards.

What can I do about it today?

  1. Ask for the release steps in writingAsk whoever releases today to write down every step, in order, including logins and where each one is stored. A rough list is enough to begin with.
  2. Agree what counts as a bad releaseDecide in plain words what you would call a failed release, for example orders cannot be placed, and who decides to undo it.
  3. Pick a quiet time and name one person on callChoose a release time when few customers are active and make sure one named person is reachable afterwards. Avoid moments when nobody is around to react.
  4. Ask for smaller releasesAsk your developer to ship one or two changes at a time instead of a month's work at once. Do not push for speed before the way back is clear.
  5. Do not force a release to prove a pointPressure to release on a Friday without a tested way back makes the fear worse. Fix the safety net first.

When should I bring someone in?

  • A release has already broken something important and nobody can say how to undo it.
  • The only person who can release is leaving or unreachable.
  • Releases are being avoided so long that bug fixes wait for weeks.

How do I handle it?

  1. Write the release downI turn the current release into a short checklist that someone else could follow, and note what is missing.
  2. Make a way backBefore changing anything, I set up and test a rollback so a bad release can be undone in a known way.
  3. Rehearse away from customersChanges are tried on a copy of the system first, so the live release holds fewer surprises.
  4. Shrink the batchesWork is split so each release is small and its effect is easy to check.
  5. Automate the repeatable stepsSteps that were done by hand are scripted one at a time, with a person still approving each release.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is it wrong to avoid Friday releases?

Not by itself. It is a reasonable precaution when nobody can react over the weekend. It becomes a problem when it is the main protection, because it hides that releases are hard to undo.

Will releasing more often make things worse?

Smaller, more frequent releases are usually easier to check and undo than a rare big one, provided there is a tested way back and some checks before going live.

Does this need new tools?

Often not at first. A written checklist, a rehearsal copy and a tested rollback come before any tooling.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.