Useful alt text often needs context that AI tools simply wouldn’t get from scrapping the image. The dots only humans would connect.

I view alt text as just as much a part of the post as the text and the image. It glues them—and any other context needed—together.

There is something worryingly effective about the Instagram app and algorithm.

I have to only install it occasionally when checking a few close friend updates.

Usually it’s in the evening. And every time I end up scrolling endlessly until my phone battery runs out.

I’ve been doing something very similar with GiffGaff for years. No monthly / annual fee. Just need to make a 1 second call every 3 (or maybe 6?) months and the credit stays untouched so is essentially endless.

BUT, it was a physical sim at the time I started.

The move to pods can transform an agency. Or it can simply multiply the problems already there. Splitting one delivery stream into several smaller ones sounds simple. Smaller teams. Clearer… | Harry... The move to pods can transform an agency. Or it can simply multiply the problems already there. Splitting one delivery stream into several smaller ones sounds simple. Smaller teams. Clearer ownershi...

The move to pods, squads or workstreams can unlock the ability for an agency to scale.

Or it can simply multiply the existing delivery challenges.

I love it when they put some in a jar on the bar. Not often you can find a beer so cloudy/custardy. I’d be choosing it!

That farthest left ale looks… custardy

People still pay you for the value you deliver or the pain you remove.

AI is great, but it’s not a differentiator on its own.

Sisyphean 👏

"user jeopardy analyst" is not a role I have come until today. LinkedIn is wild.

To claim the ability — “I don’t need you, I can do it with AI” — you also have to take on the responsibility of the outcome now and in the future.

Even with prototypes, because without a detailed knowledge of the constraints, you’re likely to be missing the context required to make good choices.

AI can enable some overlap of classic roles.

A developer can ‘design’ things.
A product manager can ‘dev’ things
A designer can prioritise and plan

But the doing is not the same as the owning. Who is responsible for each? Who does the work on quality, risk mitigation, comms, documentation?

Who will use this information and how?

Is it a range or a specific number that’s needed?
Will it remain an estimate or become a contract or commitment?

What happens if we’re wrong?

This is about risk to the business, team or individual.
How much detail and certainty is needed for these estimates?
Will there be blame or a significant commercial impact?

What decision does this support?

It could be a choice between high value features.
It might be a scheduling choice. Perhaps a budgeting calculation.

Before estimating or planning, Mike Cohn encourages teams to pause and ask three questions:

- What decision does this support?
- What happens if we’re wrong?
- Who will use this information—and how?

If those questions don’t have clear answers, the problem usually isn’t how the team is estimating.

I wrote the bones of this post many years ago while running an agency. But it's as true today as it was then. As agencies, awards submissions and attendance should be planned and justified, and not all awards deserve attention.

What are we awarding anyway?

harrybailey.com/2026/04/what...

😂

I should have asked your price-point first :-D

I feel like he started with the solution, not the need.

Some of the ways different fields reference rework...

Lean ➜ Waste / defects
Quality ➜ Cost of poor quality
Software ➜ Technical debt
Construction ➜ Rework cost
Operations research ➜ Rework economics
Service design ➜ Failure demand

They have nice towels.

I've been working on defining a course recently. It brings together lots of existing thinking. Working title:

- Stop the Rework: A Delivery Leader’s Playbook for Protecting Agency Margins

I'll hopefully continue to make progress on it over the next couple of weeks and share something very soon.

Might be a bit hyphen heavy as
row-rule-inset-cul-de-sac-start

Intersecting and terminating
Junction and cul-de-sac
Intermediate and terminus
Connected and unconnected

Snap!

I just had a contract sent to me with FINAL and a date in the file name. That's made my day. I can now be reassured that there won't be any amends.

A notification showing 'session expired' and offering 'Sign In' and 'Sign Out' options.

Schrödinger's Postman Session

I published a guide and checklist for predictable projects recently.

I’m aiming to do the same for awards entry guidance this week. Then a guide to useful stand-ups soon too.

All places I see agencies needing support.

Predictable projects guide here: harrybailey.com/predictable-...

The shift from client brief to shared plan is one of the most pivotal moments for both the project and the relationship.

However well defined and clear the initial client brief is, unless you iterate on it together, you’re just a supplier.

Measured, good. Felt, bad.

It’s a small part of the full video, but feeling something is not the same as being something.