Leaders gain leverage with their time and focus as they delegate tasks, assignments, and projects to others.
Learning to get things done through other people is one of the defining skills of leadership. But when leaders turn over initiatives to team members, they naturally become less knowledgeable about the details surrounding the effort.
If they get overly involved in those details, they demotivate others through what is commonly called micromanagement. Leaders who delegate and then remain in the weeds teach people that they are not fully trusted and rob them of their opportunity to develop through autonomy.
But if they remain ignorant of those details, they often disappoint those above them who expect leaders to be able to speak directly about the ins and outs of any project.
In many organizations, leaders are expected to know the various working details of every project under their purview. For those leaders who feel the pressure from above to know the details, this can be quite a dilemma.
The way out of this dilemma isn’t about choosing a side, but about changing what “knowing the details” means.
Leaders don’t need to track every decision as it’s made within a delegated project. They need to develop reliable ways of staying informed without inserting themselves into the work.
They can normally do this through brief updates and check-ins. Inviting team members to educate them rather than to report to them is the key.
In practice, this can be as simple as asking to see the plan before it’s executed, or a rough draft before the final version. This is the same instinct board members typically use when they aim to keep their “nose in, fingers out.”
Done well, this kind of engagement signals investment, not distrust. It tells the team their work matters enough for the leader to understand it, without suggesting the leader needs to control it.
Earning trust in both directions is the ultimate goal. Leaders need their teams to trust that questions about details aren’t a prelude to a takeover, and they need those above them to trust that fluency doesn’t require personal involvement in every task.
Leaders who manage this well come to know the shape of their team’s work (its risks, logic, and progress) without needing to touch every piece of it.
That kind of knowledge, gathered through good questions and strong relationships, allows leaders to speak credibly about projects while still giving team members the room to own them.
A useful test is whether a leader can describe the strategy, the risks, and the trajectory of the work without being able to name every decision or choice made within it. That is the difference between knowing the details and owning them.
