I’m writing this as I sit at home enjoying some rare sunshine.

I’ve just worked more than 10 days straight, along with the rest of the core project team, getting ready for a big customer milestone which wrapped up mid-week.  Successfully, I might add.  And now we’re over the hump, we’ve all taken a couple of extra days’ leave to recover.

I’ve been using the time to catch up on things I couldn’t get done at home last weekend and, more importantly, spending some proper time with the family.

We all have to put in extra effort at times; that’s just the reality of delivering projects.  But it’s essential to recover properly afterwards, otherwise it very quickly turns into burnout, stress, and strained relationships at home.

I’ve done quite a bit of reflecting over the last couple of days, taking stock of the last few weeks.

To be honest, it’s all a bit of a blur.

And whilst we passed through our milestone, there were several observations and minor issues which need logging and following up to make sure nothing falls through the cracks as we head into the next phase.  The next milestone is only 4–6 weeks away, so there’s not much time to reset before we go again.

This is where I see a lot of teams go wrong.

A milestone gets treated like a finish line.  Everyone breathes out, switches off for a few days, and moves on.  But in reality, it’s just a transition point.  The next phase has already started, whether you’re ready for it or not.

And if you don’t capture what just happened, while it’s still fresh, you lose it.

One thing that stood out during this last push was something the customer raised.

They’d noticed the hours the team were putting in.  Late nights, weekends, long stretches without a break.  And they were right to question it.

Their view was simple.  The team was stretched, and it’s not sustainable.

Now, from the inside, it never quite feels that clear cut.  You’re focused on delivery.  You do what needs to be done.  You push through, get the job over the line, and deal with the consequences later.

But when it’s visible to the customer, it creates a different kind of pressure.

It raises questions:

• Is the plan realistic?
• Is the team properly resourced?
• Are we in control, or just reacting?

And the truth is, managing resources through these periods is rarely straightforward.  Especially in smaller teams, where you don’t have the luxury of spare capacity sitting on the bench.

You end up relying on goodwill, effort, and a bit of graft to get through.

Which works… until it doesn’t.

There’s a bigger point here.

Sustained delivery shouldn’t rely on sustained overwork.

If every milestone requires a 10-day push to get over the line, that’s not a team problem.  It’s a system problem.

Something in the way the work is planned, structured, or resourced isn’t quite right.

That doesn’t mean you’ll never have to dig deep.  You will.  That’s part of the job.  But it shouldn’t be the default setting.

Coming out of a period like this, the most valuable thing you can do isn’t to jump straight into the next set of tasks.

It’s to stop, even briefly, and capture what actually happened.

Not a formal “lessons learned” session that gets written up and filed away.  Just a simple, honest record while it’s still fresh:

• What went well?
• What caused friction?
• What nearly didn’t get done?
• Where did we have to use brute force?

Because in a few days, most of it will be forgotten.  It’ll disappear into emails, conversations, and half-remembered discussions.

And then you find yourself in exactly the same position at the next milestone, wondering why it feels just as hard.

The next phase is already underway.

There will be carryover actions, open issues, and assumptions that haven’t been fully tested yet.  If they’re not picked up now, they’ll surface again later, usually at the worst possible time.

So before diving back in, take an hour.

Write it down.  Capture all the loose ends.  Turn the blur into something concrete.

It’s not the most exciting part of the job, but it might be the difference between the next milestone feeling controlled… or feeling like another scramble to get over the line.

That’s the bit that tends to get missed.

Not the delivery, but the learning that makes the next one easier.