[Leadership] True Delegation Is Sharing Your Judgment — Not Just Your Workload
True Delegation Is Sharing Your Judgment — Not Just Your Workload
When everyone on the team understands why, not just what — that's when you stop executing tasks and start building something real together.
I want to be honest with the team about where we are right now. Our project scope keeps growing. The roles each of you carry are getting heavier. And in the coming months, we're expecting to land several new projects — which means things will get busier before they get easier. I've said this before, but it bears repeating: we will never compromise on the capability and attitude of the people we work with. That standard doesn't change, no matter how busy we get.
But I also want to be clear about what kind of organization we're building — because I think it matters for how we approach this moment together.
We are not building a conventional time-based consulting firm. We're building something different: a hybrid model that combines the operational depth of the maritime industry with the strategic discipline of consulting — purpose-built for the global shipbuilding and maritime domain. That's the vision. And to get there, two things have to be true about how we work: Trust and Delegation.
- Delegation isn't about passing work down. It's about sharing the framework of judgment — the why, the boundaries, the priorities — so people can make good decisions without waiting for approval on everything.
- When a leader handles everything personally, the whole team's growth hits a ceiling at that one person's capacity. That ceiling is real, and we're already starting to feel it.
- Building a delegation culture requires three specific habits: sharing context, clarifying decision boundaries, and making progress visible.
- The shift from feedback to feed-forward is what moves a team from executing tasks to owning judgment.
- This isn't a policy announcement. It's a direction we build together — one conversation, one decision, one act of trust at a time.
Delegation Is Not "Here, You Do This"
I want to clear something up, because I think "delegation" is one of the most misunderstood words in any organization. A lot of leaders hear "delegate more" and translate that into "hand off tasks." Assign it, move on, check back later. That's not what I mean — and honestly, that kind of delegation can make things worse, not better.
What I mean by delegation is something more fundamental. It's sharing the context and framework of judgment. When I delegate something to you, I'm not just giving you a task — I'm trying to give you the same understanding I have about why this matters, how far your authority extends, and what the real priority is underneath all the details.
When these three things are clearly understood, something changes. The team stops waiting for direction on every small call. People start making decisions with confidence — not recklessly, but because they actually understand the bigger picture. That's when we move from a team that executes tasks to a team that thinks, judges, and acts with intention.
(This is also why we take our time when selecting new team members. We're not just hiring for skill. We're assessing whether someone can hold this kind of judgment.)
Doing It All Yourself Looks Efficient — Until It Isn't
I'll be honest about something. For a while, I've been handling too much personally. Not because I don't trust the team — but because it can feel faster in the short term. When you know something well, it's often genuinely quicker to just do it yourself than to explain it, hand it off, review it, and course-correct. I get that impulse. Most experienced leaders do.
But here's the problem with that logic at scale: when a leader manages everything directly, the team's growth ceiling becomes that one person's available time and capacity. Every process that requires the leader's sign-off becomes a queue. Every decision that should be made at the working level instead waits in someone's inbox.
If the team can't decide independently, every process runs through one bottleneck. And that bottleneck is me. That's not good for anyone — including the people who need to grow.
So going forward, I'm deliberately going to reduce the number of things I handle personally — and expand the space where the team can decide and act on their own. This is not me stepping back from responsibility. It's me taking a different kind of responsibility: building a team that doesn't need me to be in every room.
Three Things We're Going to Do Differently
Building a delegation culture isn't something that happens by announcing it. It happens through specific habits, practiced consistently over time. Here's what I want us to focus on — and I mean all of us, including me.
In our studies, reviews, and deliverable discussions, let's stop at "what we're doing" and always include "why we're doing it." When people understand the reason, they align naturally — without needing to be told what to do at every step. Context is the thing that turns a task-executor into a thinking team member.
Ambiguity about decision rights is one of the main reasons people default to asking for approval on everything — even when they could and should decide independently. Let's define this clearly for each person on the team. Where can you move on your own? Where do we need to bring it to a group discussion? Once that's clear, the hesitation goes away.
Trust isn't built by waiting for someone to prove themselves over months. It's built through visible, consistent progress — small things that accumulate into a track record. Tools like Microsoft Teams aren't just communication platforms. When we use them well, they become our shared language for transparent collaboration — the place where work is visible, progress is trackable, and no one has to guess what's happening.
From Feedback to Feed-Forward
One more thing I want to change about how we talk to each other. Right now, a lot of our review conversations sound like this:
"This should have been done differently. Next time, fix it this way."
That kind of feedback is useful — but it's limited. It corrects behavior. It doesn't transfer judgment. What I want us to move toward is something more like:
"Next time, what if we approach it from this angle — what do you think?"
"On this next one, I'd like you to take the lead and make the call. I'll be here, but the decision is yours."
These aren't just nicer ways to give corrections. They're fundamentally different conversations — ones that share ownership of judgment rather than just ownership of the task. That's the shift I'm asking for. It takes more time in the short term. It pays back enormously over months and years.
This isn't a top-down directive. It's a shared direction.
We need to keep building mutual trust. That means I need to trust the team with real judgment calls — not just the easy ones. And it means the team needs to take those calls seriously, with the full weight of context behind them. Neither side can wait for the other to go first.
The kind of organization we're building — specialized, hybrid, globally focused — will not get there by having one person at the center of every decision. It will get there because each member of this team develops the judgment, the confidence, and the ownership to move things forward on their own. That's what I'm working toward. And I hope this is a conversation we keep having — one project, one decision, one honest exchange at a time.
"Delegation without context is just workload transfer. Real delegation gives people a piece of your judgment — and trusts them to grow it into their own."
— Captain Ethan
Key Takeaways
Comments
Post a Comment