Ex-Agency Founder | Dad | Mancunian 🐝
Tactical Delivery Habits: harrybailey.com/framework/
LinkedIn: linkedin.com/in/harrybailey
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 ticket's work is both not being done and being done depending on who is asking. You can only find out by confirming what the person is actually working on.
The ticket's work is both not being done and being done depending on who is asking. You can only find out by confirming what the person is actually working on.
"Simplicity--the art of maximizing the amount of work not done--is essential. "
Keyboard limitation, human error, or AI forsight?
"Simplicity--the art of maximizing the amount of work not done--is essential. "
Keyboard limitation, human error, or AI forsight?
Remember to postmortem and retro when you can. They’re your path to less pain next time.
Stakeholders won’t all swallow “It’s Cloudflare’s fault.” repeatedly.
Remember to postmortem and retro when you can. They’re your path to less pain next time.
Stakeholders won’t all swallow “It’s Cloudflare’s fault.” repeatedly.
It can be hard to stop the work pressures swallowing all the time up, but without the balance you see a lot of work being done, but it likely isn’t of the quality you’d like.
It can be hard to stop the work pressures swallowing all the time up, but without the balance you see a lot of work being done, but it likely isn’t of the quality you’d like.
"I know... a moving background options. Perfect."
What were luma thinking?
Warning.. it's a lot... luma.com/3133upkx
"I know... a moving background options. Perfect."
What were luma thinking?
Warning.. it's a lot... luma.com/3133upkx
I’d add showing vulnerability
• Helping peers
• Owning outcomes
• Communicating early
• Doing what you promised
I’d add showing vulnerability
If a team mate generates it, how do you understand and maintain it?
If you generate it, how will your future self understand and maintain it?
If a team mate generates it, how do you understand and maintain it?
If you generate it, how will your future self understand and maintain it?
It’s not even a Friday.
It’s not even a Friday.
Another great piece here.
okayfail.com/2025/in-prai...
Another great piece here.
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.
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.
"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"
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.
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.
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.
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.
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?