.avif)
Bottom Line Up Front: At a certain scale, treating individual brilliance as your core infrastructure actually slows you down. The counterintuitive move? Make cohesion your infrastructure and let brilliance become a feature you can leverage rather than manage around. And no, that's not code for "settle." It's a different definition of excellent altogether.
At a certain scale, whether you're running a ten-person team or a 500-person division, you hit an inflection point. The thing that got you here starts becoming the thing holding you back.
For many organizations, it's this: You've built around exceptional individual contributors. But exceptional individuals who don't lift up the people around them create drag. And that drag compounds over time.
Here's what it looks like: Every project needs more intervention from leadership. Every strategic decision takes twice as long because you're managing internal friction before you can address the external challenge. The brilliance is real. The velocity? Glacial.
This pattern shows up everywhere: in enterprise transformations, in scaling startups, and yes, in my own agency. The specifics differ, but the underlying dynamic is remarkably consistent.
Cohesion isn't a nice-to-have cultural value. It's critical infrastructure for scale and speed.
The Scaling Trap
The trap looks different depending on where you sit, but the mechanics are the same.
For the enterprise leader: Maybe it's a new market entry, an acquisition, or a transformation initiative where teams that used to work independently now need to work in lockstep. You've got brilliant people in every function. Getting them to move as one organism? That's where things break down.
For the scaling organization: You can't be in every meeting anymore. You can't mediate every conflict or translate between talented people who don't naturally align. You've been the connective tissue. But you can't scale yourself.
I see versions of this constantly:
The Head of Marketing at a major B2B tech company trying to get Sales, Product Marketing, Field Marketing, and Corporate Comms to actually align. They've operated as separate fiefdoms for years. Each team is excellent. But they've never had to operate as a single unit, and it shows.
The pharma leader trying to unify the patient experience across R&D, Commercial, Medical Affairs, and Market Access. Each function has their own priorities, their own metrics, their own definition of success. The patient just wants a coherent journey, and right now, they're not getting one.
The SVP whose strategy team is brilliant but operates in silos. Individual contributions are exceptional. Collective decisions are nearly impossible. The organization moves like molasses while competitors sprint past.
Same question every time: Is individual brilliance worth what it costs in collective progress?
What It Actually Means to Treat Cohesion as Infrastructure
In my view, this isn't about choosing mediocrity over excellence. It's about expanding your definition of what "excellent" actually means.
The shift happens when you start measuring differently:
- Does this person make the people around them better?
- Do they elevate the team's ability to move in a unified direction?
- Or do they require the organization to accommodate their way of working?
The clarity came when I tracked where my time was actually going. I was spending more hours managing internal friction than thinking about the business. About growth, diversification, the work itself. That's not sustainable at any scale.
When you treat cohesion as infrastructure, it changes your operating model:
- Hiring - Team elevation becomes as important as individual capability. You're not just asking "can they do the job?" but "do they make the people around them better at theirs?"
- Team structure - Organize for collective outcomes, not individual contributions. This might mean rethinking reporting lines, project teams, or how you deploy your best people.
- Work design - Projects that reward unified direction, not heroic individual efforts. If success depends on one person's extraordinary performance, you've got a fragility problem.
- Performance evaluation - Contribution to team velocity matters as much as individual output. This is where most organizations say the right things but measure the wrong ones.
- Client/stakeholder relationships - Take on work that plays to team strength, not work that requires leadership intervention to succeed.
The Decision-Making Framework
Decisions about team structure and talent rarely happen in calm conditions. They happen while you're managing economic uncertainty, transformation fatigue, and pressure to show results yesterday.
This creates a trap: because everything feels urgent, every decision seems like it needs to be made immediately. But there's a real difference between strategic urgency and reactive motion.
Strategic urgency asks better questions:
- What decision actually needs to be made now?
- What can wait until we have better information?
- What's my real time horizon, not the one my anxiety is constructing?
Throughout my career, I've had to evaluate many transitions. By nature, my instinct is to move immediately. But the better question has turned out to be: How much runway do I actually have? The extra time for due diligence (pressure-testing assumptions, thinking through downstream effects, scenario planning) made the decisions both clearer and more executable.
I see this tension regularly with enterprise leaders navigating transformation. The pressure to announce an AI strategy before thinking through organizational readiness. The push to reorganize while delivering on quarterly commitments. The demand to integrate an acquisition while the core business needs attention.
The skill isn't moving faster. It's accurately assessing how much time you have and using it to make the decision more strategic, not just more comfortable.
From Decision to Operating Principle
Here's what's easy to miss in the middle of executing hard decisions: the real value isn't just in making the call. It's in codifying what becomes non-negotiable going forward.
A mentor pushed me on this recently: "What have you learned that's now an operating principle, not just a situational judgment?"
That question forces a different kind of rigor. It's the difference between "we handled that situation" and "here's how we handle situations like that."
For me, these transitions crystallized something: cohesion over individual brilliance when the two are in tension. Not as a one-time decision, but as a foundation for how we build.
That principle now runs through everything: hiring, team structure, work design, partnerships. It's become the filter.
When you institutionalize a principle like this, you stop relitigating the same decisions. You build organizational muscle memory that makes future calls faster and more confident. And critically, you create clarity that scales beyond your direct involvement.
That's how leadership itself scales. Not by being in every decision, but by embedding the principles that guide decisions when you're not in the room.
The Payoff
Here's what changes when you flip the model:
Cohesion isn't the enemy of brilliance. It's what allows brilliance to actually scale.
When cohesion is infrastructure, your best people make everyone around them better, and you can leverage that instead of managing around it. Teams move faster because they're not constantly course-correcting for misalignment. Strategic decisions execute cleanly because everyone understands what's guiding them.
The implementation is ongoing. It always is. Building systems around how you deploy talent. Rethinking how you structure work and relationships. Reducing dependencies on any single person (including yourself) for things to run well.
But the filter is clear: Does this build cohesion, or does it require someone to be the glue?
What was your 'I'm spending more time managing friction than thinking about the business' moment?
