“I thought we agreed”: The hidden cost of assumptions at work

iGaming affiliate businesses run on relationships. Between operators and affiliates, between marketing and compliance, between the SEO lead and the person who owns the CMS migration that keeps getting pushed back. 

Most breakdowns in high-performing teams aren't caused by bad intent or because someone did something wrong. It breaks because two people walked away from the same conversation with two different understandings of what had just been decided.

That gap lives somewhere. It's the space between an agreement and an assumption, and in a deadline-driven industry like ours, it's where trust quietly goes to die.

What actually is an agreement

An agreement isn't a vibe. It isn't "I think we're aligned" or "they seemed on board". A real agreement has a clear ‘what’, a clear ‘by when’, a shared understanding of what success looks like, clarity on who owns which piece of it, how that piece connects to the final outcome and all of this is documented somewhere.

It’s critical that it's documented – that’s what makes it an agreement. Be it a task in your project management tool, a confirmed email or a pinned message in a Slack or Teams channel. It doesn't need to be formal, but it needs to exist outside of memory, because memory is where assumptions are born.

Think about how many affiliate partnerships, content calendars or campaign launches have quietly gone sideways because "I thought we agreed the landing page would be live by Friday" met "I thought you were sending the final copy first”.

Nobody lied. Nobody missed a deadline on purpose. Two people just had two different mental models of the same commitment, and nobody wrote it down.

Agreements build trust. Assumptions erode it.

This compounds fast in teams. Every honoured agreement is a small deposit in the trust account. Every assumption that turns out to be wrong is a withdrawal, and withdrawals happen quietly. Nobody usually says "I don't trust you anymore”. They just start double-checking your work, cc'ing more people, keeping their own shadow tracker because yours can't be relied on. That's not collaboration anymore. That's risk management dressed up as teamwork.

Left unaddressed, assumptions don't just cause missed deadlines. They fragment teams into silos, and silos are where complacency, latency and quiet disengagement live.

The good news is that agreements are a practice, not a personality trait. Any team can build this muscle. 

It starts with naming the four things every real agreement needs: the deliverable, the deadline, the owner and the definition of done. Then it requires one more piece nobody wants to think about upfront: a process for when things change. Scope shifts. Priorities move. A launch date gets pulled forward because a competitor moved first. That's not a failure of the agreement; that's business. The failure is when the agreement changes in someone's head and never gets updated anywhere else. Change the documentation, tell everyone affected, and the agreement stays alive instead of quietly dying while everyone works off a version that no longer exists.

Feedback is where agreements get tested

None of this holds without a functioning feedback culture, because feedback is how misalignment gets caught before it becomes a missed KPI or a partner relationship on the rocks.

At Saroca, we teach teams a structure called SBIA: situation, behaviour, impact, agreement. You name the specific situation. You describe the observable behaviour, not a character judgement. You name the impact it had. And you close by making, or remaking, a clear agreement about what happens next.

SBIA keeps feedback strictly to the facts. It depersonalises the conversation so people can hear it instead of defending against it.

It's the difference between "you're always dropping the ball on reporting" and "in Tuesday's stand-up, the affiliate performance numbers weren't ready, which meant we walked into the operator call without our own data. Can we agree that those numbers are locked by 9am the day before, every time?" One is an attack on identity. The other is a fact pattern with a fix attached.

That fourth letter matters most. Feedback without an agreement at the end is just venting. It might feel honest, but it doesn't change anything. The agreement is what turns discomfort into progress.

The playbook makes the discomfort survivable

Feedback conversations are still uncomfortable. Discomfort is the price of honesty. What makes it endurable is knowing there's a playbook, and knowing everyone on the team is working from the same one.

When feedback is open and reciprocal, when a junior affiliate manager can give their team lead the same SBIA feedback their lead can give them, and both parties know that's normal and welcomed, the discomfort stops being personal. It's just the process. Nobody's waiting to see if this is the start of something bigger. There's an open loop; it's expected, and it closes with an agreement instead of a grudge.

The bottom line

In an industry where your best affiliate managers, your top SEO talent and your senior BD leads can walk if they feel unclear, unheard or quietly mistrusted, agreements are not admin. They're the infrastructure that camaraderie gets built on.

Assumptions are cheap in the moment and expensive later. Agreements take thirty extra seconds and a written line somewhere. That trade is always worth making.

Trust is currency in our industry. Agreements are how you earn it, one documented conversation at a time.