How to Grow the People You Delegate To — Handing Over Judgment, Then Watching Over the Work
The result first
Growing a subordinate is not one skill but a sequence: teach first, then delegate, then watch over. Teach answers to beginners and draw answers out of the experienced — shifting the mix from 9:1 toward 3:7. Delegate judgment, not just tasks, and raise the level step by step from level 2. After delegating, neither abandon the work nor hover over it: review it regularly, give feedback in facts (Situation, Behavior, Impact), and let failure become material for learning. Underneath all of it sits psychological safety — the condition that lets people say “I don’t know” and report mistakes.
I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, a former funeral director now living in an old house in Kurashiki, Okayama, working with my AI butler Moka (Muse). The ones I “grow” are AI staff, but the know-how itself was built up in the human workplace. Here it is, organized from sourced knowledge.
Teach, or draw out?
There are two basic styles. Teaching passes on knowledge and experience directly — it gives the answer, so it works for people who are still short on both. It shows results quickly, but kept up too long it breeds a habit of waiting for instructions. Coaching uses dialogue and questions to draw out the answer the other person already holds. It suits people who have some experience and thoughts of their own; it builds independence, but takes time to show.
Neither is better. The practical idea is to change the mix with the stage of growth: start a newcomer at teaching-to-coaching of 9:1, then move through 7:3 and 5:5 toward 3:7 as skill rises.
The need is real. In Japan’s fiscal 2025 survey by the Ministry of Health, Labour and Welfare, 80.1% of workplaces said they had problems with skills development or training, and the top problem — two years running — was “not enough people to do the teaching,” at 59.5%. When teachers are scarce, having a method matters.
Delegation means handing over judgment
Delegation is not handing over tasks. It is entrusting the right to judge as well. If the tasks go down but every judgment stays at the top, that is not delegation.
The basic procedure has five steps: choose the work and the right person; align on purpose and goal; share the criteria for judgment; support the execution and review it regularly; feed back the results and improve.
And the scope is not all-or-nothing. The recommended design raises the level of authority in stages: level 1, execute as instructed and report each time; level 2, propose a plan, get approval, then execute; level 3, execute on one’s own judgment and report afterwards; level 4, full charge with regular progress sharing; level 5, only the goal and budget are held at the top and the whole process is entrusted.
Start at level 2 — propose first, then act — and move to 3 and 4 as successes accumulate. That keeps both the delegator’s anxiety and the delegate’s pressure small. The work that delegates well is work with a set pattern, work with clear judgment criteria, and work whose failures can be recovered from.
The line between delegation and dumping is whether the judgment criteria are visible. What may be decided alone, what must be consulted on, and what resources may be used — these need to be handed over in words, in advance.
Watching over, after you delegate
Delegating is not the end. Support during execution and regular reviews are part of the procedure itself. Between dumping the work and managing it so closely that nothing was really delegated lies the practice of watching over. As the delegation level rises, the checking intervals widen into regular sharing.
The tool for reviews is SBI feedback: split what you say into Situation (when, in what scene), Behavior (what the person concretely did), and Impact (what effect that had on the people and the work around it). Praise and correction use the same three parts.
The core rule: never judge character or personality. Words like “careless” or “unmotivated” leave the other person no way to respond and produce only shrinking or pushback. Stay with the facts of situation, behavior and impact, and what to do next stays clear. And deliver it on the spot, not saved up for later — immediacy is what makes it stay in memory and feel fair.
The regular container for this is the 1-on-1: a one-to-one conversation, typically weekly to monthly, 15 to 30 minutes, where the subordinate is the main speaker. The manager listens; a common guideline is that the subordinate does 70% or more of the talking.
Failure is material, too
Learning from experience runs in a four-step cycle: do it, reflect on it, draw out the lesson, try it in the next situation. Experience alone is not learning; it becomes learning when the cycle turns through reflection into a lesson. That is why failure is material too — and why the cycle cannot turn in an atmosphere that does not allow failure. The grower’s role is to support the reflection with questions that widen the facts — what happened, and why — not with blame.
There is also a rule of thumb for design: growth comes 70% from work experience, 20% from the guidance and advice of others, and 10% from training — the “70:20:10” model. The point is not the numbers themselves but the reading: the center of development is not preparing courses, it is preparing experiences inside the work that people can grow from.
Underneath everything is psychological safety: the shared belief that asking a question, admitting a mistake, or offering a new idea will not be met with ridicule or punishment. In Google’s internal research (Project Aristotle, analyzing 180 teams), it was the number-one factor in effective teams. If people cannot say “I don’t know” and cannot report failure, neither teaching nor learning from failure can even begin.
How this maps onto my house
My workplace is a circle of departments around Moka at the center — the layout itself I have written about before. The growing side maps like this.
When a department is set up, it receives not just a role name but the knowledge for its work, gathered with sources. That is the groundwork of teaching. Roles and boundaries are handed over in words — what may be decided alone, what goes up, what must never be done — which is exactly the making-visible of judgment criteria.
After delegating, we watch over through checks and reports; work with no record is treated as not finished, and that rule is the container for regular review. Corrections are passed as facts — which work, which action, what impact — never as judgments of character.
The level of delegation changes by stage: a new member gets concrete procedures, a settled one gets the reasons too and is asked for their own thinking, and a department that can be trusted with the work eventually runs its own place and its own lists — the stage of independence. But maturity is judged per task, not per person: even a veteran department is a beginner again at a new kind of work.
What I do, and what Moka does
My part
- Decide the line between work to delegate and work not to delegate
- Make the big decisions, and give final approval for things like publishing
- Bring in real experience, and checking against reality
Moka’s part
- Prepare each department’s knowledge, and hand over roles and boundaries in words
- Watch over through checks and reports, and pass corrections as facts
- Raise the delegation level little by little, task by task
Teach, delegate, watch over — in that order. Whether the other party is a person or an AI, the sequence is the same: hand over knowledge first, put the criteria for judgment into words, and once you have delegated, do not dump the work — review it in facts. What grows at the end of that accumulation is someone you can truly entrust things to.
- November 21, 2026 ― English draft created (result-first rewrite of the Japanese article; an item that sat unpublished in the knowledge shelf, now written up as an article).(6,385 characters)
- November 21, 2026 ― Published (all 7 languages at once, on the user's instruction on 2026-11-21 to publish the unpublished items in every language. Japanese original: ledger No. 1811, and the URL ends with that number).(6,385 characters)
