Your people may be capable and still return to you for every important decision. Useful direction makes the result, priorities, boundaries, support, and proof clear enough for ownership to begin.

Your people may be capable, yet still return to you for every important decision

You assign the work.

The employee listens, takes notes, and says, “Okay, I understand.”

A few hours later, the questions begin.

“What exactly do you want me to include?”

“Should I speak with the client first?”

“Which one should I prioritize?”

“Is this format okay?”

You answer each question because the work must move. Sometimes you take the task back because explaining everything feels slower than doing it yourself.

Then the pattern repeats.

You may conclude that the employee lacks initiative. The employee may conclude that you have standards that are difficult to predict. Both of you become more dependent on the next conversation.

The problem may not be competence.

The person may simply have received a task without enough direction to exercise judgment.

Useful direction makes the result, reason, priorities, boundaries, support, and proof clear enough for a person to move without repeatedly calling the leader back.

Direction is not the same as detailed instruction. It is also not the same as telling capable people to “figure it out.”

The leader’s work is to create enough clarity for ownership to begin.

“I thought you understood” is not a leadership system

You may have experienced this moment.

You ask an employee to prepare a proposal for an important client. You explain the deadline, mention the program the client requested, and send several previous proposals as references.

Three days later, the draft arrives.

It is complete. It is professionally formatted. It also misses the point.

The proposal describes the program in detail, but it does not address the client’s real business concern. It looks like the examples you sent because the employee assumed that was what you wanted.

You feel frustrated.

The employee worked hard. You were expecting judgment.

Then one of you says the familiar sentence:

“I thought you understood.”

That sentence reveals a hidden assumption. The leader believed the expected result was obvious. The employee believed the task itself defined success.

Neither one made the direction visible.

This is why the earlier conversation about visible changes matters. People cannot carry a strategic shift unless leaders show what that shift changes in the assignment in front of them.

A task tells people what to do

A task usually names an activity.

Prepare the report.

Call the supplier.

Organize the meeting.

Train the supervisors.

Follow up with the customer.

The activity may be necessary, but it does not reveal the contribution the activity must make.

Take “follow up with the customer.”

The employee could send a message asking whether the concern has been resolved. The task would be complete.

But perhaps the actual result is to restore the customer’s confidence after a delayed delivery.

That requires a different conversation.

The employee may need to acknowledge what happened, confirm the customer’s most urgent need, explain the revised commitment, and identify anything that could prevent the company from delivering it.

The task is the follow-up.

The win is restored confidence supported by a credible next commitment.

When leaders assign only the task, employees often complete what was named. Leaders then become disappointed because something important remained undone.

Direction begins with the win

Before you explain the steps, explain what must become true.

Ask yourself:

When this work is finished, what should another person be able to see, decide, experience, or do?

That question changes the assignment.

Instead of saying, “Prepare the operations report,” you might say:

“Give the leadership team a clear view of the three operating problems most likely to affect customer commitments next week, your recommended response to each, and any decision you need from us.”

Now the employee knows what the report must make possible.

Instead of saying, “Facilitate the meeting,” you might say:

“Help the group decide who will own the delayed customer cases, what each department will contribute, and what will be completed before Friday.”

The meeting now has a job.

Instead of saying, “Train the supervisors in coaching,” you might say:

“Help supervisors respond to recurring errors without taking the work back. We want employees to understand what happened, recommend the next move, and reduce the same error during the following month.”

The program now has a movement to create.

This is the first shift: from assigning activity to clarifying the win.

Pause before giving instructions

Leaders often respond to ambiguity by adding more steps.

They explain what to do first, what template to use, whom to contact, which words to avoid, and when to return for approval.

The questions decrease because the employee now has a script.

But something else may also decrease.

Judgment.

The employee learns to follow the leader’s method rather than understand the work.

So pause before listing the steps.

Ask whether the method truly needs to be prescribed.

Some work requires strict procedures. Safety, compliance, quality control, and technical standards may leave little room for variation. In those situations, clear instructions protect people and results.

Other work requires judgment. Customer conversations, problem solving, project ownership, proposals, and cross-functional coordination may need the person to adapt to what they discover.

In these situations, give a clear result and firm boundaries. Leave room for the person to choose the method.

You are not withholding support.

You are placing responsibility where it can grow.

Explain why the work matters

People exercise stronger judgment when they understand the reason behind the assignment.

Suppose you tell a manager:

“Please review all customer complaints from the last three months.”

The manager may summarize categories, prepare a chart, and present the findings.

That might be useful.

But perhaps the organization is trying to stop complex complaints from travelling through several departments without one visible owner.

Then say so.

“We need to understand where ownership disappears. Review the complaints and identify the moments when the customer had to repeat the concern, search for the right person, or coordinate our departments for us.”

The reason shapes what the manager looks for.

Without that reason, the person may complete the analysis correctly and still fail to produce what the strategy needs.

This is one way the broader leadership path enters everyday management. Leaders connect assignments with what matters instead of asking people to complete isolated activities.

Tell people what deserves priority

Many assignments fail because the employee is trying to satisfy several good expectations at once.

The proposal must be complete, persuasive, polished, customized, accurate, and finished quickly.

The meeting must allow participation, maintain harmony, cover every agenda item, and produce a decision.

The customer response must be fast, empathetic, inexpensive, and consistent with policy.

All of these may matter.

But when they conflict, which one carries the work?

Suppose you ask an employee to prepare a proposal for a potential client. You might say:

“The proposal must first show that we understand the business problem. Keep the program description brief. We can expand the design later if the client agrees that we have identified the right problem.”

Now the employee knows what to protect.

Without that priority, the employee may spend most of the time describing workshops, schedules, and activities because those sections are easier to complete.

Direction becomes useful when it helps a person choose among several reasonable demands.

Make the boundaries visible

Ownership without boundaries creates anxiety.

The employee may have the ability to act but remain uncertain about what the leader will accept.

Can the person change the deadline?

Can the employee speak directly with the customer?

How much may be spent without approval?

Can another department be asked to contribute?

Which decisions must return to the manager?

When these boundaries remain hidden, employees protect themselves by asking.

The repeated questions are not always signs of dependence. They may be attempts to discover rules the leader has never made visible.

Clarify the decision space.

You might say:

“You may adjust the sequence of activities and speak directly with the client. Keep the agreed outcome and budget unchanged. Return to me if the client asks for a different scope, an earlier delivery date, or anything that creates legal or reputational risk.”

The employee now knows where judgment belongs and where escalation begins.

Boundaries do not weaken ownership.

They make responsible ownership possible.

Distinguish a boundary from a preference

Leaders sometimes present personal preferences as though they were non-negotiable requirements.

The slide deck must use a certain format. The email must sound like the leader. The meeting must follow the leader’s sequence. The report must contain the same sections used for years.

Perhaps these choices matter.

Perhaps they are simply familiar.

Before correcting the employee’s method, ask:

Does this affect the result, risk, or strategic choice—or is it merely how I would do the work?

This question can be uncomfortable.

You may discover that you asked someone to own the work while continuing to control every visible detail.

A boundary protects something consequential.

A preference describes one acceptable way of doing the work.

When the person’s method can produce the required result within the agreed boundaries, allow the difference.

That is how people begin developing their own judgment rather than borrowing yours.

A familiar conversation can create unnecessary dependence

Imagine a supervisor assigning a presentation to a team member.

“Prepare the monthly update for Friday.”

The employee returns later.

“How many slides?”

“Maybe ten.”

“Should I include all the projects?”

“Yes, include everything.”

“Do you want charts?”

“Yes, charts would be good.”

“Should I follow last month’s format?”

“Sure.”

The questions sound minor. But notice what is happening.

The employee is trying to reconstruct the supervisor’s picture of a successful presentation. The supervisor is answering one detail at a time without revealing the purpose.

Now change the first conversation.

“On Friday, help the leadership team decide which two projects need intervention. Show where progress is at risk, why it is at risk, and what decision or support each project needs. Use as many slides as necessary, but keep the discussion within fifteen minutes.”

The employee may still ask questions.

But the questions will likely improve.

“Should I exclude the projects that are on track?”

“Yes, mention them in the written update. Use the meeting for decisions.”

The conversation has moved from slide preferences to strategic use of the meeting.

That is what usable direction does.

Give enough context for sound judgment

A person may understand the immediate assignment but still lack the context needed to make trade-offs.

Suppose you ask a manager to reduce operating costs.

The manager removes overtime, delays equipment maintenance, and limits customer support.

The cost target moves.

The organization’s chosen way to win may suffer.

The manager needs to know more than the target.

Which customer promise must remain protected?

Which capabilities must not be weakened?

Which costs represent waste, and which ones enable the strategy?

What time horizon matters?

A clearer direction may be:

“Reduce the cost of repeated rework without reducing the technical support our selected customers rely on. Begin with the three handoff errors causing the largest avoidable expense. Bring us options and explain the effect of each one on customer commitments.”

The manager now has a strategic frame.

This is where direction connects with Strategic Learning. People make a choice, act within real conditions, follow what becomes visible, and improve the next move.

Without context, they may produce the requested number while moving the organization away from what matters.

Agree on the proof

You and the employee may use the same words while imagining different standards.

“Create a strong proposal.”

“Resolve the concern.”

“Improve the process.”

“Prepare the team.”

These statements sound clear until someone must decide whether the work is finished.

Ask what proof will show that the result has been achieved.

For a proposal, proof may be that the client can recognize the business problem, understand the recommended first move, and decide whether to continue the conversation.

For a customer concern, proof may be that the customer has one visible owner, understands the revised commitment, and no longer needs to coordinate the company’s departments.

For a delegated decision, proof may be that the employee acted within the boundaries, explained the reasoning, and achieved the result without unnecessary escalation.

The proof should be proportionate to the work.

You do not need a dashboard for every assignment.

Sometimes one observable result is enough.

But both leader and employee should know what “done” is meant to accomplish.

Do not make the employee guess what will impress you

People who work closely with a leader become skilled at reading preferences.

They learn which words the leader likes, which format receives praise, which ideas receive quick approval, and which mistakes create strong reactions.

This can help work move.

It can also create performance built around pleasing the manager rather than serving the result.

An employee may produce a polished report because the leader values presentation, even when the underlying recommendation remains weak. A manager may avoid surfacing a risk because the senior leader dislikes surprises. A team may agree quickly because debate makes the executive impatient.

Direction should pull attention away from guessing the leader’s mood and toward making a sound contribution.

Tell people what the work must serve.

Then create room for them to show you what they see.

You may receive an answer different from the one you expected.

That difference can be useful.

Invite the person to play the direction back

After giving an important assignment, do not ask only:

“Do you understand?”

Most people will say yes.

They may understand every sentence while holding a different picture of the result.

Ask them to play it back.

“What result are you carrying?”

“What will you protect if two demands compete?”

“Which decisions can you make?”

“When will you come back to me?”

“What will show that the work has moved?”

This is not an interrogation.

It is a quick way to compare your understanding before the person invests time.

You may discover that the employee has identified a gap you missed.

Perhaps the deadline is impossible because another team must provide data. Perhaps the decision boundary conflicts with an existing policy. Perhaps the proposed proof does not reveal the customer result.

Good direction is built through conversation.

You bring the purpose and the boundaries. The employee brings knowledge from the work. Together, you create a clearer path.

Allow questions without becoming the automatic answer

Clear direction does not eliminate every question.

New information will appear. Risks will change. Customers will respond unexpectedly. The person may discover a conflict nobody saw at the beginning.

You still want people to ask.

But you can change the kind of question they bring.

Instead of answering immediately, ask:

“What are you trying to protect?”

“What options do you see?”

“What do you recommend?”

“Which boundary are you uncertain about?”

“What evidence supports your view?”

These questions help you distinguish a genuine leadership decision from a routine decision the employee can carry.

They also prevent you from becoming the team’s search engine.

Pause before answering.

The few seconds of silence may feel inefficient. But the person’s reasoning is part of the work you are building.

Support does not mean taking ownership back

An employee may ask for help because the assignment has become difficult.

The leader steps in, contacts the customer, rewrites the document, or takes over the meeting. The immediate problem is solved.

The employee learns something too:

When the work becomes important or uncertain, ownership returns to the leader.

Support should help the person continue carrying the result.

You may provide information, remove an obstacle, connect the person with someone, clarify a boundary, or coach the reasoning. But the owner should remain visible whenever the situation permits.

Suppose an employee says:

“The operations manager is not responding, and I cannot complete the customer commitment.”

You could contact the operations manager yourself.

Or you might say:

“Send the request again and copy me. State the customer result, the commitment you need, and the deadline. If there is no response by two o’clock, I will help remove the obstacle, but you will remain the owner with the customer.”

The leader provides authority and support.

The employee retains the work.

Direction should become lighter as judgment grows

A new employee may need more context, examples, and check-ins.

An experienced employee who has carried similar work may need only the result, boundaries, and proof.

Direction should reflect readiness.

Giving the same detailed instructions to everyone wastes leadership time and can weaken capable people. Giving broad ownership to someone without enough experience creates risk and anxiety.

The question is not whether you are a directive or empowering leader.

The question is what this person needs to carry this result responsibly.

As judgment grows, reduce unnecessary instruction.

Increase the size of the decision space.

Allow longer stretches between reviews.

Ask for recommendations instead of updates.

Leadership should not create permanent dependence on the leader’s clarity.

It should help people become capable of creating clarity for themselves and others.

The system may be calling people back to you

You may give clear direction and still see decisions return.

Look beyond the conversation.

Perhaps the approval system requires your signature. Perhaps other departments respond only when a manager speaks. Perhaps employees are blamed for reasonable decisions that produce an unfavorable result. Perhaps information remains available only to senior leaders.

The system teaches people where real authority sits.

If you want ownership to remain with the employee, the surrounding conditions must support it.

Review the process, access, measures, and reactions around the assignment.

What makes calling the leader the safest move?

What makes waiting more reasonable than acting?

What happens when an employee makes a sound decision that does not produce the desired outcome?

The purpose of daily execution is not merely to tell people what behavior is expected. It is to make the practical response and supporting conditions repeatable in real work.

Direction begins the movement.

The system determines whether it can survive.

Use a six-part direction conversation

For important assignments, bring six elements into the conversation.

1. The win

What must become true when the work succeeds?

2. The reason

Why does this result matter to the customer, team, strategy, or organization?

3. The priority

What should the person protect when reasonable demands compete?

4. The boundaries

Which decisions belong to the owner, and which ones require consultation or escalation?

5. The support

What information, access, resources, coaching, or leadership action is available?

6. The proof

What will show that the result has moved, and when will you review it?

You do not need to turn every assignment into a formal six-part speech.

For familiar work, the conversation may take one minute.

For a new, risky, or strategically important result, it may deserve more time.

The value is not the format.

The value is making the parts visible before confusion turns into repeated questions, rework, and control.

Try it with one assignment today

Choose one piece of work that often returns to you.

Perhaps employees repeatedly ask what you want. Perhaps you often rewrite the final output. Perhaps the person completes the task, but the contribution remains weak.

Do not begin by blaming the employee or adding another checklist.

Examine the direction.

Did you clarify the win?

Did you explain why it matters?

Did you name the priority?

Did you make the boundaries visible?

Did the person know what support was available?

Did both of you agree on the proof?

Then have the conversation again.

You may discover that the employee needs a skill they do not yet have. You may discover that the system denies the authority you thought you had delegated.

You may also discover that one clearer conversation prevents several future conversations.

Give people room to move

Leaders sometimes believe that clear direction requires saying more.

Often, it requires choosing more carefully what must be said.

Make the result unmistakable. Explain the reason. Set the priorities and boundaries. Offer support. Agree on proof.

Then allow the person to work.

Do not disappear. Do not hover.

Stay available without becoming the automatic next step.

Your goal is not to make people independent of leadership in every situation. Your goal is to prevent unnecessary dependence when the person already has enough information, authority, and judgment to move.

The next article, responsible level, will examine how leaders decide which decisions should remain close to the work, which ones require consultation, and which ones genuinely belong at a higher level.

Give Direction People Can Use Without Calling You Back