What does it mean to delegate to subordinates? | Finding answers through voices gathered on Threads | Creative Awards 2026 Business Category | Middle Management | Management | Human Relations | Boss | Subordinate | Development | Leader

My boss tells me,
"Delegate more to your subordinates and focus on management."
But when something happens, they say,

"Why weren't you watching more closely?"

I think there are quite a few people who have paused between these two statements.

I also had an experience where these words stuck in my mind.
What they are saying sounds contradictory.
But if you look at it from a different perspective, it doesn't sound like a contradiction.

That is exactly why it is difficult.

This time, when I wrote about this feeling on Threads, I received quite a lot of responses.
Some people took it as a story about unreasonableness, while others took it as the difficulty of development and delegation.
Based on those reactions, I will try to find my own answer regarding the balance of delegation.

🔷1. The first thing that bothered me was the gap in my boss's words

The reason I wrote this was because of a time when I had to go apologize to a client due to a subordinate's mistake.

My boss tends to give vague instructions and uses language that is open to broad interpretation.

They say, "Delegate more to your subordinates and focus on management."

But how far that "delegation" extends is not clearly visible.

• How much should I let them decide for themselves?

• How much should I check in along the way?

• When something happens, how much support should I provide?

I believe there are many parts of that balance that I should think about myself.
I don't want to be told how to do everything.

However, what is difficult is being delegated to while there is still room for interpretation.

Yet, when something happens, the gap between my actions and the ideal balance in my boss's head is pointed out as a mistake.
If that continues, it naturally feels unreasonable at first.

I think that delegating and providing support where necessary are things that should ideally coexist.

But if I have to figure out that balance every time while also trying to match my boss's ideals, the difficulty level is quite high.

That is why I wanted to properly find my own answer to this.

🔷2. When I wrote it on Threads, I got a flood of "I thought you were talking about me" responses

When I wrote about that feeling on Threads, I received more varied responses than I had expected.

I created this post with the intention of eliciting a wide range of opinions from the start.

It can be read as a story about an unreasonable boss, or as a story about being caught in the middle.
It can be read as the difficulty of development and delegation, or as the difference between administration and management.
I intentionally left some room for interpretation so that different issues would emerge depending on the reader.

The actual responses I received were even broader than I had anticipated.

“No matter what I do, I’m the scapegoat.”
“I’m told that a field manager’s job is to make useless people useful.”
“There are subordinates who can’t even get to the point of thinking and choosing, let alone being delegated to.”

There were voices like that, as well as,
“It seems contradictory, but I don’t think it is.”
“It’s just asking whether you were actually watching after you delegated.”
Those were some of the responses.

Watching the responses come in, it became clear that this didn’t just end as a typical “boss-related grievance.”
Although I initially wrote the post to think about how to deal with my boss, organizing the responses made me realize that it was part of a much larger theme.

🔷3. Why did this post resonate so much?

Here, I will talk a little bit about the design of the Threads post itself.
If you are not interested, it is fine to skip this heading.

First, I will post the text of the post itself.

What I was conscious of this time was being short, easy to understand, and difficult to misunderstand.
But I also made sure it didn’t just end as a typical “relatable” post.

① Attribute information at the beginning: Placing “who is speaking” first

The first line is just “47 years old, middle management.”
This one line determines “who the subject of the story that follows is.”

I included the age of 47 so that readers can judge whether the writer is in a similar position to them.
It might not resonate with a new employee in their 20s. However, for those who have built up a certain amount of career, it becomes easier for them to feel, 'I understand this sensation.'

Also, I included the term 'middle management' to convey the sandwich structure of being told things from above while also having to look after those below, without needing further explanation.
If I just said 'my boss told me,' it might look like mere complaining. But by putting the attribute of 'middle management' first, it becomes easier for people to accept that this is a story about the difficulties of a position.

② Leave the boss's statements as they are without organizing them

I have laid out the boss's statements as raw as possible, without interpreting or rephrasing them myself.

'Delegate more to your subordinates and focus on management'
'Why weren't you looking at things in more detail?'

When you place these two side-by-side, the reader notices the contradiction on their own.
'Oh, aren't these things opposites?'

Even without me explaining, 'This is a contradiction,' the reader arrives at that conclusion themselves.
Because of that, there is more freedom in how it is received.

Some people might think it's a contradiction, while others might think, 'No, this isn't a contradiction.' Since both ways of reading create a point of friction, it becomes easier to write a reply.

Also, by separating these two into short lines, the contrast becomes easier to see visually even while scrolling.
Since Threads flows on the timeline, being able to see 'what is happening' in an instant is an important point.

③ Do not state the conclusion definitively; create space through 'word choice'

I conclude the post like this.

The balance between 'delegating' and 'supporting' is difficult.

If I organize it too much here, like 'delegating' vs. 'managing,' the reader is likely to just think 'I see' and stop there. They are satisfied, and they stop thinking about it any further.

But the word 'supporting' causes a bit of friction.

'No, isn't that just management?'
'Is this about development?'
'Rather, what is the difference between this and neglect?'

That kind of feeling of 'that's not quite right' is born.

That friction becomes the space where they want to write down their own thoughts.

Do you end it with 'I understand' by stating it definitively, or do you intentionally make it ambiguous to draw out 'but I think this way'?
If you want to gather replies on Threads, the latter is more effective.

4. End with a question: Place "How about you?" at the end

The final sentence is, "Do you ever feel this way?"

This serves as both a confirmation of empathy and a way to create an entry point for replies.

People who want to say "I do" find it easy to write a reply.

Even those who think "I don't" can easily react by saying, "In my case, it's like this..."

If you end a post with "...is difficult," it finishes as a monologue by the poster.
By making it a question like "...don't you think?" it becomes a format that starts a dialogue with the reader.

This difference may seem small, but it clearly shows in the number of replies.

Looking at it this way, this post was designed to be "short, easy to understand, and hard to misunderstand," while at the same time having "space for the reader to bring in their own thoughts."

The reason the replies spread is not just because the theme resonated, but also because I created a structure from the beginning that made it easy to reply.

🔷4. When the person you are delegating to is different, the approach is also completely different

Even though we use the word "subordinate," they are actually quite different in type.

And depending on that type, the way you delegate changes entirely. Looking at the voices that came back, that became quite clear.

There are people who grow the more you delegate to them, and there are people who are at risk if you don't watch them closely.
There are people who will head in the wrong direction if you don't check in along the way, and there are people who haven't even reached the phase of thinking and choosing for themselves yet.

There are people who have motivation and experience, but who will hold onto problems without consulting anyone when they get stuck.
There are people who say "I understand" on the surface, but who don't actually see where to start.

Thinking about it that way, the single phrase "Let's delegate to subordinates" is almost useless in the field.

The difficult part is that it's not a binary choice of whether to delegate or not.

To whom, how much, at what timing, and in what form do you delegate... that balance changes completely depending on the person.

The voices gathered also contained many such realizations, like "You have no choice but to change it depending on the person" and "There are people who grow when you delegate, and people who are at risk if you don't watch them closely."

If you talk only about how to delegate without looking at the person you are delegating to, it won't go well. Looking at the feedback this time, I felt that once again.

🔷5. "Delegating" required a foundation

There were quite a lot of voices saying that while people say 'I'm delegating,' in reality, things are being handed over to the front lines without anything actually being decided.

• How far am I trusted to act?

• What criteria should I use to make decisions?

• At what point should I consult with you?

If you are told to 'delegate' without these things being clear, it's not so much a clean delegation of authority as it is just dumping the work on someone else.

Among the voices gathered, there was also the opinion that 'the correct way to delegate is within a framework where there are proper decision-making criteria and an evaluation system, and delegating without anything in place is reckless.'

I think this is quite essential.

I believe at least three things are necessary in order to delegate.

• How much can I decide for myself?

• What should I base my decisions on?

• What constitutes progress?

It is because this framework exists that delegation leads to growth and progress.

Conversely, 'delegating' without that foundation may look like handing over discretion, but in reality, I think it's quite unkind.

It's not so much that the degree of delegation is difficult... it's difficult because you're told to 'delegate' while the foundation for doing so remains ambiguous.

I feel that is at the root of it.

🔷6. 'Watching closely' did not mean taking everything on yourself

'It seems contradictory, but it is not.'
Among the voices this time, this perspective left a strong impression on me.

The phrase 'Why weren't you watching more closely?' does not mean that you should do all the practical work yourself.

After delegating, how much did you grasp?
Where could you have noticed the anomaly?
Where could you have taken action?
It means you are being asked about those things.

Thinking about it that way, 'watching closely' is a little different from taking everything on yourself.

• Where are they likely to stumble?

• Where are they likely to need consultation?

• At what timing is it better to check in?

• Where are problems likely to escalate?

Keeping those points in mind... I feel this is closer to the reality of 'watching closely'.

Delegating and keeping an eye on key points are essentially compatible.

However, when you are on the front lines, this becomes very easy to blur.
When told to delegate, you wonder how far you should step back, and when you try to watch closely, you wonder if that means you aren't delegating.

Getting involved in the actual work and keeping an eye on key points are different.

Even if you understand it in your head, it is easy to mix them up on the front lines.

Looking at the voices gathered this time, I felt that everyone was finding their own balance amidst that tendency to mix them up.

🔷7. Administration and management cannot be cleanly separated

Administration is about keeping track of rules, deadlines, progress, and quality.
Management is about moving, developing, and supporting people toward achieving goals.
As terms, they are certainly different things.

But in reality, they often cannot be separated that cleanly.

You have to check progress.
You have to produce results.
You have to check the condition of your subordinates.
Development is also necessary.
And if something happens, the responsibility comes back to you.

Even if you want to draw a line and think, 'This is an administrative task' and 'This is a management task,' in reality, you feel like you are handling both at the same time.

Among the voices gathered, while there were opinions that administration and management are essentially different, there were also voices saying that in actual work, they cannot be fully separated.

Theoretically, they can be separated.
But in practice, they cannot.
I think this is a very realistic feeling.

When told to 'delegate,' it is also easy for it to become ambiguous whether you are being asked to reduce administration, lean into management, or do both properly...

I feel it is closer to the actual experience to view them as things that cannot be separated even if you want to, and then consider where to place the center of gravity within that.

🔷8. The more you delegate, the more administration increases

Delegating seems like it would reduce your own workload if it goes well.
But in reality, just because you delegated doesn't necessarily mean things get easier.
In fact, there were quite a lot of voices saying that the more you delegate, the more management increases...

Since they can't move forward with just the final deadline, you have to decide on the check-in points yourself.
I feel anxious if I don't include intermediate reports.
Even if I think I've delegated, there are times when I can't see progress unless I go and check myself.
When that happens, it feels less like delegating and more like the management required to delegate is increasing.

Delegating is better for development.
I know that in my head.
But in reality, there are many cases where delegating doesn't lighten your load at all, but rather just changes it into a different kind of burden...

And what's tricky is that this burden is hard to see from the outside.

Even if it looks like you aren't doing the work yourself, in reality, you are checking in along the way, anticipating issues, correcting deviations, and taking over when problems arise.
That effort doesn't look like practical work, but it is quite heavy.

Delegating isn't just handing over work; it's also about supporting them behind the scenes so they can move forward.

Thinking about it that way, "how much to delegate" isn't something you can decide without looking at the other person.

The amount of invisible support and the timing for check-ins all change depending on the individual.

The balance of how to delegate is ultimately inseparable from "who you are delegating to."

🔷9. Knowing the person you are delegating to determines how you delegate

Delegating is important.
But it's different from neglect.
At the same time, if you hold onto everything yourself, things won't run smoothly either.

I think many people are constantly searching for that balance somewhere in between.

Moreover, that balance is completely different for every person.
If they are experienced, they might be able to move forward with just the general direction.
If they are highly motivated, they might grow by being given a little more responsibility.
But if you leave someone who tends to bottle things up to their own devices, they might get stuck behind the scenes.

In other words, how you delegate isn't decided by spirit or resolve, but is something thatyou have no choice but to adjust to fit that person.

Among the voices gathered, there were quite a few people who do things like:
"I delegate, but I check the key points."
"I don't restrict the method too much, but I share the goal beforehand."
"I create an atmosphere where it's easy to consult."

Don't separate delegating and supporting too much.
On top of that, who is it, how should I delegate, and how much should I support them?
To determine that balance, you reallyhave to know the other person.

• What is their level of experience?

• What is their level of motivation?

• What kind of signs do they show when they are in trouble?

• How naturally can they report, communicate, and consult?

• Where do they tend to get stuck?

As these things become visible, the contours of how to delegate also become clearer little by little.

And once you can put that way of delegating into words for yourself, you will be less likely to be swayed by unreasonable demands from your boss.

“I have delegated this much to this person.”
“I am checking this part.”
“I see that this part still needs support.”

Just being able to say those things allows you to move beyond a state of just doing things vaguely.
Your boss won't necessarily always understand.
But, whether you have your own standards makes a significant difference in how much stress you feel.

What I realized after writing on Threads this time was that although the story started with a frustration over my boss's words, as I organized it, it turned out to be part of a much larger theme.

• What is “delegating”?

• What is “watching closely”?

• What is “supporting”?

There isn't just one answer.
But, for whom, how to delegate, how far to support, and how far to manage. Being able to draw that line in your own way is quite important when thinking about how to delegate.

I think delegating is, in the end, about how much you watch that person and finding the right balance that suits them.

How do you observe and put into words the balance that changes depending on the person you are delegating to?

Thank you for reading until the end.

“Delegating is, in the end, about how much you watch that person and finding the right balance that suits them.”
The way of delegating covered in this article also leads to the topic of how to adjust the “gaps” that exist between people when you get down to it.

Based on 17 years of middle management experience and the voices gathered on Threads, I have organized how to observe these “gaps,” how to translate them, how much you should take on yourself, and what you should return to the other person.

This is a practical guide you can look back on when you are lost in your interactions with others.

【Scheduled for release on August 15th】