When people talk about leadership styles, "collaboration" can be found at the root of most discussions. Which I believe is a good thing, because who wants a dictator archetype as a manager? But often our overcorrection away from a dictator lets us overlook the truth:

Being a collaborative leader doesn't mean you avoid decision-making or saying no. It means making the right decision even if others don't agree.

The biggest mistake I see with managers, tech leads, and senior developers is that collaboration becomes indecision.

A good leader brings people together to brainstorm, align, and move forward. An experienced leader can get to the right decision as quickly as possible.

If you're looking to grow your leadership skills, especially in technical environments, get better at making decisions no matter how many people are in the room.

When Collaboration Feels Risky

For many new decision-makers, especially those who value empathy and inclusion, one of the hardest things is to tell people what to do.

Why? Because humans are always more complex than code, the answer to this is limitless. Maybe it's your first time in a leadership role. Maybe you're the type who always keeps the peace. Maybe you're used to being the quiet one on the team. Maybe you're stepping into a space where you're still learning the team, the org, and the history.

All of that is valid. But if you're going to lead, your team needs to look to you for direction, especially when it's unclear what to do next.

Collaboration works best when you make space for others' ideas and know when to say, "We're going this way."

Scenario: A Real Decision You Have to Make

Project setup:

• There's a fixed deadline.
• You're 6 weeks out.
• One person owns a large part of the project, and they're falling behind.
• You suggest sharing the workload, adding support, and reducing siloing.
• A tenured team member pushes back, saying training will take too long and put the project at risk.

Here's the twist:

You're new to the team. You don't know every nuance. But you do know strategy. You know planning. You know that continuing to let one person bottleneck the work is a bigger long-term risk.

So what do you do?

Step-by-Step: Collaborative Decision-Making in Action

1. Frame the problem neutrally.

Don't jump straight to defending your idea. Start by clearly laying out the two options:

• The current path (status quo): list pros and cons.
• Your proposed solution: list pros and cons.

This keeps the conversation objective and invites participation.

2. Ask for input.

Turn to the team member who disagrees. Ask:

"Given both paths and the risks we've outlined, which do you think is the best path forward?"

If they choose the path you don't agree with, great. You now get to dig deeper.

3. Clarify their reasoning.

Ask: "What's the main reason you're leaning that way?"

You're not challenging their logic. You're stress-testing it. You're seeing if they have context you're missing.

4. Make the call.

If their reasoning doesn't outweigh the long-term risk you're trying to mitigate, thank them for the input, and say something like:

"That's really helpful context. Based on what we know right now, I'm moving forward with bringing in additional support. I believe this lowers our delivery risk and positions us better for success."

You've now:

• Showed your team they're heard
• Grounded the decision in strategy
• Taken clear leadership responsibility

That's collaborative. That's not a dictatorship. That's leadership.

The Core Skill: Decisiveness with Empathy

Leadership isn't about always being right. It's about being willing to make a call, pivot if needed, and create clarity for others. You'll make better decisions the more you practice. And you'll earn trust faster by explaining why you're making those decisions.

Your meetings will get easier. Your team will feel more secure.

And most importantly, your team will know you're a leader who can lead.

Looking for guidance on technical leadership decisions? Book a discovery call to discuss how I can help.