The 24-Hour Rule (And Why Your Delivery Team Needs One)

Jacinta Streat • July 14, 2026

EDITORS NOTE

This post draws on stories from two of Brisbane's premiership-winning sporting sides, the Broncos (NRL) and the Lions (AFLW), and what they teach us about peer accountability, healthy conflict, and the practical tool we use with every embedded team at Patient Zero: the Social Contract.

A former Brisbane Broncos captain once told me his team's biggest performance secret had nothing to do with football.

How the Broncos Built Team Accountability

Gorden Tallis was speaking about what it took to win, and he kept coming back to one idea: for the team to perform at its best, their sport life and home life had to be humming. A big part of that was making sure their wives and girlfriends had no reason to worry about what they got up to on away games. Any rumour or bit of bad media would chew up the focus they needed on the field.

So the senior players made a rule. The whole team signed up to it: no girls at the team hotel. They agreed the consequence too. Break the rule and you're benched for the next game.

Then one of their key players broke it.

Gordon remembers the coach in a tight spot, wanting to enforce the consequence but knowing how much they needed this bloke in the next game. In the end, the coach didn't have to make the call. The team did. They sat the player down and said: You're benched. You broke our rules.

That's the bit that stuck with me. The rule didn't come from the coach, and neither did the consequence. Peer accountability beats top-down accountability every time, because it sidesteps the awkward "manager vs. mate" dynamic that makes hard conversations land badly. When the team owns the standard, the team enforces the standard.

The 24-hour Rule: How to Stop Team Conflict Festering

I heard a similar story from three players from the Brisbane Lions AFLW team at an International Women's Day event.

The Lions had just won back-to-back premierships and weren't done. They knew every other team in the comp was gunning for them. To stay on top, they had to keep doing everything right, including how they performed as a team.

Picture 30-odd elite footballers, all vying for a spot in the squad, all carrying the pressure of another premiership campaign. Blow-ups are inevitable. The leaders knew that. What they didn't want was conflict festering.

So they made a rule: the 24-hour rule. If you've got an issue with a teammate, you've got 24 hours to bring it up and put it to bed. After that, you commit to letting it go.

Brilliant. Silence is a teammate's worst enemy. Unspoken frustration calcifies into resentment, and resentment grows into bigger problems, draining team performance. The 24-hour rule forces the issue while it's still small enough to handle.

What This Means for Software Delivery Teams

Here's what I take from both stories: high-performing teams don't happen by accident. They're built deliberately, and they get explicit about what is and isn't okay.

In our world of software delivery, most friction doesn't come from bad people. It comes from unstated expectations. No one shows up to a stand-up to purposely piss off their teammates. But when expectations live only in people's heads, friction is inevitable. Someone reads silence on a pull request as rudeness. Someone else assumes async means "respond within 10 minutes." Someone schedules a workshop at 11am and the room loses its best engineer to a hangry spiral (more on that in a sec).

The good news: this is fixable, and it doesn't need a coach to enforce it. It needs a conversation. And the tool I keep reaching for is a Social Contract.

What is a Team Social Contract?

A Social Contract is a written set of agreements a team makes about how they'll work together. I doubt the Broncos sat in a workshop drafting theirs; it was probably a conversation in a change room. You can run it either way. I find a short team workshop covering four areas does the job.

Logistics

When do we meet, and when do we not? In person, virtual, hybrid? Where do decisions get recorded, and where do they get communicated? Which channel is for what? Slack for chat, email for sign-off, Confluence for the record.

Conflict Management

What decisions does this team actually own? How do we disagree safely? What's our version of the 24-hour rule? Naming this before there's conflict is much easier than naming it during one.

Social Conventions

What can we count on from each other? What behaviour is in bounds, and what's out? What makes things uncomfortable that we should just avoid? (This is where the 11am lunch rule earns its keep. I once had a team member who religiously ate at 11am every day. Trust me you didn't want to make him eat later or he would get super hangry!)

Values and Commitment

What do we need to add to make sure we're aligned? How do new team members get onboarded into the contract? What happens if someone doesn't follow it?

Then, and this is the part that matters, everyone signs up to it. Not metaphorically. Verbally, in the room. It's not a contract if no one has explicitly agreed to it.

SOCIAL CONTRACT CHEAT SHEET

How Embedded Teams Put This Into Practice

At Patient Zero, this is one of the first conversations we have when we drop a team into a new client environment. Not because we love workshops (though some of us do), but because it's the fastest way to turn a group of capable individuals into a team that can actually deliver under pressure. Team maturity isn't a slide in a deck; it's a set of small agreements people keep with each other.

One last thing. Think the "time of day to avoid" question is funny? I once worked with a teammate who religiously ate lunch at 11am. No exceptions. Push him past 11:15 and you got a different person, and not the version you wanted in your sprint planning. Trust me: ask the question. The weird stuff matters.

Skip the Storming Phase

Want a delivery team that handles conflict openly from day one? Our embedded teams arrive with the Way of Working already baked in, so the agreements other teams stumble into over months are in place before sprint zero.

Learn how our embedded teams build maturity into your delivery capability from the start.
See how we helped CitrusAd develop ways of working to scale from one product line to eight concurrent ones.
Think you've got what it takes to play on a team that already has its Social Contract sorted? Check out working at Patient Zero.

About the Author

Jacinta Streat is the Principal Evangelist at Patient Zero with years of experience bridging the gap between technical and business domains and driving continuous improvement.

She enjoys mastering gym skills like handstand push ups and celebrating personal bests on the golf course.

Follow Jacinta on LinkedIn