The Hardest Leadership Skill I've Ever Had to Learn (And It Wasn't What I Expected)

I thought I had a good handle on what "hard leadership" looked like. I am leading a team of specialists across marketing, content creation and tech these couple of years.

I want to be honest about this, because I think honesty is where real thought leadership begins — not in the polished LinkedIn takeaway, but in the messy middle of actually doing the work.

Leading a cross-functional team has been, without question, the hardest leadership challenge I've faced. And the reason surprised me: it wasn't the politics, or the competing priorities. It was something quieter and more personal — the discomfort of not knowing enough.

The Discomfort Nobody Talks About

When you manage a team within your own function, you usually have some depth in the domain. You've done the job, or something close to it. You can spot when someone's estimate is off, or when a plan has a hole in it, because you've been in the trenches yourself. That depth gives you a kind of quiet confidence, even when you don't say much.

Cross-functional leadership strips that away. Suddenly you're in a room with finance analysts, marketers, legal counsel etc and you are, at best, a generalist among specialists. You cannot out-expert anyone in that room, in their own domain, and pretending otherwise is both exhausting and transparent.

I remember sitting in a planning session early on, listening to the marketeer and SEO manager explain, and feeling a very specific kind of discomfort: the fear of asking a question that would reveal how little I actually understood. I wanted to nod along. I wanted to seem like I already knew. And I had to sit with the very real possibility that my team could see through that instantly.

This is the discomfort that so many leaders — especially those who've built their identity on competence — don't talk about openly. We talk about "imposter syndrome" in the abstract, but rarely do we talk about the specific, situational version of it: the moment-to-moment experience of leading people who know more than you do about the thing they're doing, in real time, in front of everyone.

Learning to Be Comfortable With Shallow Depth

Here's what changed things for me, and what I now bring into my work: I had to consciously let go of the idea that competence meant depth in every domain. I had to learn — really learn, not just intellectually accept — that my job was not to know as much as the specialists in the room. My job was to know enough.

Enough to ask the right question. Enough to spot when something didn't add up, even if I couldn't articulate exactly why. Enough to connect what the SEO manager just said to the marketeer five minutes earlier, because I was the only person in the room whose job was to hold the whole picture, not one slice of it.

This required real learning. I spent evenings reading up on things I'd never needed to understand before — enough technical SEO and content marketing to follow a  conversation, enough legal and compliance language to know when something needed an expert brought in versus when it was a straightforward call. But crucially, I had to give myself permission for that learning to be shallow by design. I was never going to be a SEO person. I didn't need to be. I needed to be fluent enough to lead the conversation, not fluent enough to do the job myself.

That distinction — between depth and fluency — is, I think, one of the most under-discussed leadership skills in corporate life today.

Knowing When to Step In, and When to Step Back

The second, closely related skill I had to develop was knowing when to lead and when to get out of the way. In a functional team, the instinct to jump in and problem-solve often comes from genuine expertise — you can see the answer, so you offer it. In a cross-functional team, that instinct is almost always wrong, and it took me longer than I'd like to admit to unlearn it.

I had to learn to sit with silence in meetings where I didn't have the answer, and let the person who did have the answer actually work through it, even if it took longer than I was comfortable with. I had to learn that my value in those moments wasn't in solving the problem — it was in asking the question that made the room think differently, or noticing that two functions were solving for different definitions of "done," or simply protecting the space for the right expert to lead.

Stepping back, for a leader, is often harder than stepping in. It requires a kind of ego discipline that isn't taught in most leadership programs, because most leadership programs are still built around the assumption that leaders should have answers. Cross-functional leadership taught me that sometimes the most powerful thing a leader can do is hold the question open a little longer.

Five Things I'd Tell Any Leader Stepping Into a Cross-Functional Role

If you're heading into a cross-functional leadership role — or already in one and feeling the particular discomfort I've described — here's what I'd want you to know:

1. Fluency, not mastery, is the goal. You don't need to become an expert in every function represented on your team. You need enough working knowledge to ask sharp questions, follow the logic of a specialist's argument, and spot inconsistencies. Chasing depth everywhere will burn you out and still leave you behind the actual experts.

2. Your credibility comes from synthesis, not subject matter expertise. Your unique value is that you're the only person whose job is to see the whole board. Lean into that. When you connect dots across functions that specialists are too close to see, that's leadership — not a consolation prize for lacking depth.

3. Ask questions without apologizing for asking them. There's a difference between "Sorry, this is probably a dumb question, but—" and simply asking the question directly. The first signals insecurity and invites the room to underestimate you. The second signals confidence in your role, even when you're genuinely unsure of the answer.

4. Build a personal board of translators. Identify one trusted person in each function who will give you the real, unvarnished version of what's going on — not the polished update. These relationships are what let you build fluency quickly and sense-check your own instincts before a big decision.

5. Practice stepping back on purpose. In your next cross-functional meeting, notice every instinct you have to jump in and solve something. Then deliberately let at least one of those moments play out without your input. Notice what happens. More often than not, the team rises to it — and you learn where your presence is actually needed versus where it's just habit.

Why This Matters for Corporate Leadership Today

Cross-functional work isn't a niche skill anymore — it's increasingly how modern organizations get anything meaningful done. Leaders are asked to run initiatives that touch product, finance, legal, operations, and marketing simultaneously, often without direct authority over any of those teams. The old model of leadership — built on domain mastery and top-down direction — doesn't hold up well in that environment.

What does hold up is a leader's ability to sit with discomfort, build enough fluency to ask good questions, and know precisely when to lead and when to let the room do its work. That's not a soft skill. It's arguably the sharpest edge a corporate leader can develop right now.

If you're navigating this kind of leadership challenge in your own organization — or trying to develop it in your leadership bench — I'd love to talk about what that could look like for your team.

*