Harry Bailey
@harrybailey.com
Agency (creative/digital) ways of working and project delivery thoughts. Crafter of trusted tactics.
Ex-Agency Founder | Dad | Mancunian 🐝
Tactical Delivery Habits: harrybailey.com/framework/
LinkedIn: linkedin.com/in/harrybailey
Ex-Agency Founder | Dad | Mancunian 🐝
Tactical Delivery Habits: harrybailey.com/framework/
LinkedIn: linkedin.com/in/harrybailey
Pinned
Harry Bailey
@harrybailey.com
· Mar 29
Harry Bailey - Agency Project Delivery Expert
Two decades of experience. Harry helps agencies de-risk project delivery. Client alignment, scope creep & overruns. Find out more...
harrybailey.com
Hi new peeps, 👋🏻 I’m Harry Bailey.
I solve tricky client project delivery challenges with agencies teams.
Ensuring successful, profitable projects and stronger client relationships.
Questions? DM me! Or learn more on harrybailey.com #ClientSuccess #AgencyLife #ProjectManagement
I solve tricky client project delivery challenges with agencies teams.
Ensuring successful, profitable projects and stronger client relationships.
Questions? DM me! Or learn more on harrybailey.com #ClientSuccess #AgencyLife #ProjectManagement
The Ruby / DHH situation fascinates me, despite my distance from the community.
Another great piece here.
Another great piece here.
This was such a good essay, I hope every member of the Rails core team will read it.
okayfail.com/2025/in-prai...
okayfail.com/2025/in-prai...
In Praise of dhh
A reflection on Ruby's past, present, and future.
okayfail.com
November 11, 2025 at 8:04 AM
The Ruby / DHH situation fascinates me, despite my distance from the community.
Another great piece here.
Another great piece here.
Reposted by Harry Bailey
Today is the last day to submit a session proposal for next year's Agile Manchester conference: agilemanchester.net/call-for-ses...
The event will take place from 13-14 May
Tickets now available. Discount for freelancers.
The event will take place from 13-14 May
Tickets now available. Discount for freelancers.
Call for Sessions
Our Agile Manchester 2026 Call for Sessions is open
agilemanchester.net
November 10, 2025 at 10:26 AM
Today is the last day to submit a session proposal for next year's Agile Manchester conference: agilemanchester.net/call-for-ses...
The event will take place from 13-14 May
Tickets now available. Discount for freelancers.
The event will take place from 13-14 May
Tickets now available. Discount for freelancers.
100 - % time building the thing = X
X is the discussions, handovers, testing & deployment.
X is often the bottleneck.
X is where most of the waste is found.
But we obsess about estimating and measurement of build time.
X is the discussions, handovers, testing & deployment.
X is often the bottleneck.
X is where most of the waste is found.
But we obsess about estimating and measurement of build time.
November 7, 2025 at 1:51 PM
100 - % time building the thing = X
X is the discussions, handovers, testing & deployment.
X is often the bottleneck.
X is where most of the waste is found.
But we obsess about estimating and measurement of build time.
X is the discussions, handovers, testing & deployment.
X is often the bottleneck.
X is where most of the waste is found.
But we obsess about estimating and measurement of build time.
I still chuckle occasionally about the naming of The World Series.
November 6, 2025 at 10:52 PM
I still chuckle occasionally about the naming of The World Series.
Drafted a new talk today. Now I just need to grow the balls to submit it.
November 6, 2025 at 5:58 PM
Drafted a new talk today. Now I just need to grow the balls to submit it.
Children seem to all use 'AI' in place of any content generation — text, image or video — involving a computer.
"Is that AI?" - "No it's CGI"
"Is that AI?" - "No it's a script"
"Is that AI?" - "No it's MIDI sequencing"
"Is that AI?" - "No it's Procedural animation"
"Is that AI?" - "No it's CGI"
"Is that AI?" - "No it's a script"
"Is that AI?" - "No it's MIDI sequencing"
"Is that AI?" - "No it's Procedural animation"
November 6, 2025 at 3:33 PM
Children seem to all use 'AI' in place of any content generation — text, image or video — involving a computer.
"Is that AI?" - "No it's CGI"
"Is that AI?" - "No it's a script"
"Is that AI?" - "No it's MIDI sequencing"
"Is that AI?" - "No it's Procedural animation"
"Is that AI?" - "No it's CGI"
"Is that AI?" - "No it's a script"
"Is that AI?" - "No it's MIDI sequencing"
"Is that AI?" - "No it's Procedural animation"
Reposted by Harry Bailey
A fantastic piece of data journalism from Sky News. A masterclass of data visualisation. news.sky.com/story/the-x-...
How the world's richest man is boosting the British right
How the world's richest man is boosting the British right
news.sky.com
November 6, 2025 at 1:36 PM
A fantastic piece of data journalism from Sky News. A masterclass of data visualisation. news.sky.com/story/the-x-...
"We don't deploy on Fridays" is a statement I always have to dig into.
Like if somebody says, "I don't like Christmas", you need to know what experiences led to that.
Like if somebody says, "I don't like Christmas", you need to know what experiences led to that.
November 6, 2025 at 1:51 PM
"We don't deploy on Fridays" is a statement I always have to dig into.
Like if somebody says, "I don't like Christmas", you need to know what experiences led to that.
Like if somebody says, "I don't like Christmas", you need to know what experiences led to that.
I recently wrote about juniors being a barometer for great ways of working.
One part of that approach has to be pair coding.
A habit that is often seen as a distraction and a waste actually fosters all the key elements of strong autonomous teams.
One part of that approach has to be pair coding.
A habit that is often seen as a distraction and a waste actually fosters all the key elements of strong autonomous teams.
Onboarding through pair programming - Harry Bailey
There was a manager I worked with recently who was having serious trouble with their onboarding process. Working with several teams of between 5 and 8 developers, the business was growing fast and rec...
harrybailey.com
November 6, 2025 at 6:46 AM
I recently wrote about juniors being a barometer for great ways of working.
One part of that approach has to be pair coding.
A habit that is often seen as a distraction and a waste actually fosters all the key elements of strong autonomous teams.
One part of that approach has to be pair coding.
A habit that is often seen as a distraction and a waste actually fosters all the key elements of strong autonomous teams.
Random coffees are great.
I spent 30 minutes today chatting way comparing agency delivery to gov delivery.
What’s the same? What’s different? How might one approach help the another?
Both of us came away with fresh insights and ideas.
I spent 30 minutes today chatting way comparing agency delivery to gov delivery.
What’s the same? What’s different? How might one approach help the another?
Both of us came away with fresh insights and ideas.
November 5, 2025 at 7:20 PM
Random coffees are great.
I spent 30 minutes today chatting way comparing agency delivery to gov delivery.
What’s the same? What’s different? How might one approach help the another?
Both of us came away with fresh insights and ideas.
I spent 30 minutes today chatting way comparing agency delivery to gov delivery.
What’s the same? What’s different? How might one approach help the another?
Both of us came away with fresh insights and ideas.
It can be tempting to be all positive and confident at project kickoff, that’s what people want to see and hear.
But the start of a project is a great time to ensure success, not just hope for it.
A quick “If this project failed six months from now, what would likely have caused it?” can help.
But the start of a project is a great time to ensure success, not just hope for it.
A quick “If this project failed six months from now, what would likely have caused it?” can help.
November 5, 2025 at 7:16 PM
It can be tempting to be all positive and confident at project kickoff, that’s what people want to see and hear.
But the start of a project is a great time to ensure success, not just hope for it.
A quick “If this project failed six months from now, what would likely have caused it?” can help.
But the start of a project is a great time to ensure success, not just hope for it.
A quick “If this project failed six months from now, what would likely have caused it?” can help.
Some big-org customer service is wild. Brsk broadband for example:
B: Here's your renewal offer
Me: Sounds good, I accept
B: Done. We've applied a different offer. Pay up.
Me: wtf?
B: Sorry about the missunderstanding. Pay up though.
Me: wtf?
B: Yeah we said X, but we meant Y.
Me: wtf?
B: Problem?
B: Here's your renewal offer
Me: Sounds good, I accept
B: Done. We've applied a different offer. Pay up.
Me: wtf?
B: Sorry about the missunderstanding. Pay up though.
Me: wtf?
B: Yeah we said X, but we meant Y.
Me: wtf?
B: Problem?
November 5, 2025 at 10:13 AM
Some big-org customer service is wild. Brsk broadband for example:
B: Here's your renewal offer
Me: Sounds good, I accept
B: Done. We've applied a different offer. Pay up.
Me: wtf?
B: Sorry about the missunderstanding. Pay up though.
Me: wtf?
B: Yeah we said X, but we meant Y.
Me: wtf?
B: Problem?
B: Here's your renewal offer
Me: Sounds good, I accept
B: Done. We've applied a different offer. Pay up.
Me: wtf?
B: Sorry about the missunderstanding. Pay up though.
Me: wtf?
B: Yeah we said X, but we meant Y.
Me: wtf?
B: Problem?
Are we over the em dash panic phase yet — you know the AI one — so I can start using them again?
November 4, 2025 at 3:56 PM
Are we over the em dash panic phase yet — you know the AI one — so I can start using them again?
When a developer admits to the habit of xlarge code commits I start here:
- Show them how to squash/rebase multiple commits
- Suggest they write the commit message first
So they know they could always squash, and mindful of pre-planned scope of each change.
It's worth encouraging smaller steps.
- Show them how to squash/rebase multiple commits
- Suggest they write the commit message first
So they know they could always squash, and mindful of pre-planned scope of each change.
It's worth encouraging smaller steps.
November 4, 2025 at 3:45 PM
When a developer admits to the habit of xlarge code commits I start here:
- Show them how to squash/rebase multiple commits
- Suggest they write the commit message first
So they know they could always squash, and mindful of pre-planned scope of each change.
It's worth encouraging smaller steps.
- Show them how to squash/rebase multiple commits
- Suggest they write the commit message first
So they know they could always squash, and mindful of pre-planned scope of each change.
It's worth encouraging smaller steps.
IKEA recently promoted tiny beds for phones. The Phone Sleep Collection. If you leave your phone in its bed for 7+ hours for 7 days, they give you vouchers to spend in store.
www.youtube.com/watch?v=RfR7...
www.youtube.com/watch?v=RfR7...
Phone Sleep Collection
YouTube video by IKEA UAE
www.youtube.com
November 4, 2025 at 12:55 PM
IKEA recently promoted tiny beds for phones. The Phone Sleep Collection. If you leave your phone in its bed for 7+ hours for 7 days, they give you vouchers to spend in store.
www.youtube.com/watch?v=RfR7...
www.youtube.com/watch?v=RfR7...
3 ways teams handle weekend failures:
- No cover, things break.
Risk lies with clients, often unexpectedly. Lowers retention.
- Unofficial cover, undocumented processes. Risk lies with agency. Gaps exist. Lowers morale.
- Official cover, documented processes. Balanced risk. Adds overhead.
- No cover, things break.
Risk lies with clients, often unexpectedly. Lowers retention.
- Unofficial cover, undocumented processes. Risk lies with agency. Gaps exist. Lowers morale.
- Official cover, documented processes. Balanced risk. Adds overhead.
November 1, 2025 at 10:00 AM
3 ways teams handle weekend failures:
- No cover, things break.
Risk lies with clients, often unexpectedly. Lowers retention.
- Unofficial cover, undocumented processes. Risk lies with agency. Gaps exist. Lowers morale.
- Official cover, documented processes. Balanced risk. Adds overhead.
- No cover, things break.
Risk lies with clients, often unexpectedly. Lowers retention.
- Unofficial cover, undocumented processes. Risk lies with agency. Gaps exist. Lowers morale.
- Official cover, documented processes. Balanced risk. Adds overhead.
Trick or treating has taken a northern spin at our house this year. 🎃 👻
October 31, 2025 at 5:48 PM
Trick or treating has taken a northern spin at our house this year. 🎃 👻
"You provide a high-level description of what you’re building and why, and the coding agent generates a detailed specification."
🤨
github.blog/ai-and-ml/ge...
🤨
github.blog/ai-and-ml/ge...
Spec-driven development with AI: Get started with a new open source toolkit
Developers can use their AI tool of choice for spec-driven development with this open source toolkit.
github.blog
October 30, 2025 at 7:31 PM
"You provide a high-level description of what you’re building and why, and the coding agent generates a detailed specification."
🤨
github.blog/ai-and-ml/ge...
🤨
github.blog/ai-and-ml/ge...
So many variables in software projects. The projects which go well have some things in common:
- Estimates aren't treated as commitments.
- Stakeholders have high availability.
- The scope has flex (the goals can be fixed).
- Release early and often, from day one.
- The team owns the 'how'.
- Estimates aren't treated as commitments.
- Stakeholders have high availability.
- The scope has flex (the goals can be fixed).
- Release early and often, from day one.
- The team owns the 'how'.
October 30, 2025 at 8:58 AM
So many variables in software projects. The projects which go well have some things in common:
- Estimates aren't treated as commitments.
- Stakeholders have high availability.
- The scope has flex (the goals can be fixed).
- Release early and often, from day one.
- The team owns the 'how'.
- Estimates aren't treated as commitments.
- Stakeholders have high availability.
- The scope has flex (the goals can be fixed).
- Release early and often, from day one.
- The team owns the 'how'.
A smellfungus is somebody who always manages to find fault.
October 29, 2025 at 7:27 PM
A smellfungus is somebody who always manages to find fault.
Sometimes I get to spend my day being ‘listening and asking questions nobody else dared ask’ as a service.
Which I probably get as much from as they do to be honest.
Which I probably get as much from as they do to be honest.
October 28, 2025 at 6:48 PM
Sometimes I get to spend my day being ‘listening and asking questions nobody else dared ask’ as a service.
Which I probably get as much from as they do to be honest.
Which I probably get as much from as they do to be honest.
Vibe coding and AI-led coding ignore essential principles of quality software like accessibility, optimisation, maintainability and security.
It’s a shortcut sure, but not to the place people say it gets you.
Let’s face it, many senior devs use it as a quicker option than to search Stackoverflow.
It’s a shortcut sure, but not to the place people say it gets you.
Let’s face it, many senior devs use it as a quicker option than to search Stackoverflow.
October 26, 2025 at 10:44 AM
Vibe coding and AI-led coding ignore essential principles of quality software like accessibility, optimisation, maintainability and security.
It’s a shortcut sure, but not to the place people say it gets you.
Let’s face it, many senior devs use it as a quicker option than to search Stackoverflow.
It’s a shortcut sure, but not to the place people say it gets you.
Let’s face it, many senior devs use it as a quicker option than to search Stackoverflow.
Just had my annual reminder from my mum that the clocks go back tonight.
Always useful in case all modern technology fails me over the next 12 hours.
Always useful in case all modern technology fails me over the next 12 hours.
October 25, 2025 at 4:08 PM
Just had my annual reminder from my mum that the clocks go back tonight.
Always useful in case all modern technology fails me over the next 12 hours.
Always useful in case all modern technology fails me over the next 12 hours.
Why?
That’s my most favourite question. I ask it all the time. Even when I know the answer.
I use it to make people think. I use it to surface hidden knowledge to a group. I use it to stop early solution obsession. I use it to help find better options.
If you’re safe to ask it, always ask it.
That’s my most favourite question. I ask it all the time. Even when I know the answer.
I use it to make people think. I use it to surface hidden knowledge to a group. I use it to stop early solution obsession. I use it to help find better options.
If you’re safe to ask it, always ask it.
October 24, 2025 at 6:12 PM
Why?
That’s my most favourite question. I ask it all the time. Even when I know the answer.
I use it to make people think. I use it to surface hidden knowledge to a group. I use it to stop early solution obsession. I use it to help find better options.
If you’re safe to ask it, always ask it.
That’s my most favourite question. I ask it all the time. Even when I know the answer.
I use it to make people think. I use it to surface hidden knowledge to a group. I use it to stop early solution obsession. I use it to help find better options.
If you’re safe to ask it, always ask it.
I would answer a lot more calls if the people text a couple of minutes before saying they'd be calling and what for.
October 23, 2025 at 9:59 AM
I would answer a lot more calls if the people text a couple of minutes before saying they'd be calling and what for.