Hey Wranglers,
Something interesting happens when a company crosses roughly 200 people:
Things just… start slipping.
Requests fall through the cracks. You see this frequently in the "handshakes" between teams. They both discuss something and agree, but then assume the other team is handling it. All of a sudden, projects stall without anyone explicitly blocking them.
Nobody did anything wrong, but suddenly, nothing feels as smooth as it used to.
And most leaders misdiagnose why.
Key Takeaways
When companies scale, informal coordination quietly stops working.
Implied ownership works at small size but leads to dropped work at scale.
The fix is not better culture or more meetings. It is explicit ownership and shared visibility.
When “Everyone Knows” Stops Being True
At small companies, work runs on shared context.
You know who is working on what. You know who is overloaded. You know when something feels stuck, even if no one has said it out loud.
You do not need to explicitly assign ownership because intuition fills in the gaps.
At around 200 people, that breaks. Intuition does not scale.
Context fragments across teams, time zones, and tools, and what used to be obvious becomes invisible.
“I Thought You Were Handling That”
This is what coordination failure actually looks like:
A request comes in and gets discussed in a Slack thread.
A few people react. Someone says, “Makes sense.”
The conversation moves on.
The requester waits.
Then follows up later.
Someone responds, “Oh, I thought you were handling that.”
No one ignored the request. Ownership was simply assumed, not assigned.
At small scale, assumed ownership works because everyone can see the whole system. But at larger scale, it quietly kills momentum.
More Meetings Don’t Fix This
When coordination starts breaking down, companies respond in a very predictable way:
They add meetings.
It works for a second, and then the volume scales again. You end up talking about work more than you are actually moving it forward.
This is not a startup problem, and it is not a sign of immaturity.
It is the permanent tax of growth.
As companies scale, requests multiply, work crosses more team boundaries, and context spreads across more channels and systems. What used to be handled by proximity now requires clarity.
What Actually Fixes It
Teams that scale well do not magically communicate better. They do two simple things consistently:
First, they make ownership explicit.
Every request has a clear owner, every time. Not “we discussed it” or “someone should handle this,” but one person who is responsible for moving it forward.
Second, they make work visible by default.
Work is not hidden in DMs, private threads, or someone’s memory. Progress is visible enough that others can see what’s in flight, where things are stuck, and whether something has been acknowledged.
This is not about control. It is about removing ambiguity, which gets very expensive as the team scales.
Why Structuring Matters More Than Speed
Most people think scaling problems are about moving faster, but they're about uncertainty.
When people do not know who owns something, where it stands, or whether it has even been acknowledged, they compensate by following up more, looping in more people, and starting parallel work “just in case.”
That is how calm teams become reactive without realizing why.
I built Wrangle after living through that. Not to add more process, but to make ownership and visibility show up naturally in the places teams already work.
At scale, those small moments of clarity add up.
Thanks for reading,
Adam Smith
CEO & Founder, Wrangle
PS - What’s the last request your team “thought someone else had”?