Match your style to someone's maturity on the task at hand, not their general experience: low maturity needs structure, high maturity needs goals and room.

Task-Relevant Maturity (TRM) is Andy Grove’s answer to the question of whether there is a single best management style. There isn’t. The effective style depends on one variable: how much experience the subordinate has with the specific task at hand — not their general experience, their seniority, or their age. [1] At low TRM, the effective approach is structured and task-oriented: tell them what to do, when, and how. At medium TRM, the style shifts to two-way communication, support, and mutual reasoning, with attention on the person rather than the task. At high TRM, the manager’s involvement goes minimal: establish mutually agreed objectives, then monitor. The whole framework turns on one discipline — TRM is local to a task, not a property of the person.

TRM of subordinate
Effective management style
low
Structured and task-oriented. The manager tells the subordinate what to do, when, and how.
medium
Individual-oriented. Two-way communication, support, mutual reasoning. Attention to the person rather than the task.
high
Manager involvement minimal. Establish mutually-agreed objectives, then monitor.

TRM is local to a task, not a property of the person. A seasoned manager moved into a new domain can have low TRM on day one. Mistaking that regression for underperformance is the most common delegation-readiness failure.

Read TRM per task, never per person. The same subordinate can carry high TRM on most of their job and low TRM on the one responsibility you just handed them, and the style that serves one fails the other. The corollary is the framework’s hardest lesson: TRM regresses. A strong performer moved into a new domain has low TRM on day one, and Grove’s own chapter is built on a promotion that surprised Intel exactly this way — a manager whose performance dropped because his task-relevant maturity in the new job was extremely low, not because his competence had changed. [1] Mistaking that regression for underperformance is the most common delegation-readiness failure.

Two more disciplines. First, keep moving: the style that fits today’s TRM is wrong once the TRM grows, so treat structured supervision as a stage to graduate someone out of, not a standing arrangement. Second, don’t trust your self-read. When Grove asked managers to assess their supervisors’ styles and asked the supervisors the same question, some 90 percent of supervisors saw themselves as more communicating and delegating than their subordinates did. [1] Calibrate against what your reports actually experience, not what you intend.

TRM is a leverage argument. The management style appropriate for a high-TRM subordinate takes far less of your time than detailed, structured supervision, and once TRM is high enough you can delegate the task outright — which is why Grove tells supervisors to raise their subordinates’ task-relevant maturity as rapidly as possible. [1] The framework also prices your calendar: Grove keys one-on-one frequency to TRM, meeting weekly with a subordinate who is inexperienced in a specific situation and every few weeks with an experienced veteran. [1] Without the framework, most managers default to a single style for everyone, which means micromanaging the people who have earned monitoring and under-instructing the people who still need structure.

Use TRM at every handoff: delegating a new responsibility, onboarding a hire, or moving someone into a new role. Classify the subordinate’s TRM for that specific task as low, medium, or high, pick the matching style, and compare it against the style you were about to use by default. It’s equally useful as a diagnostic when a previously strong performer starts struggling — the first question is whether the work changed underneath them, because regression to low TRM on new work is expected, not alarming. TRM is the wrong tool when the problem is motivation rather than experience; if someone has done the task well before and has stopped, reach for Skill vs. Will instead.

Task-Relevant Maturity comes from Andy Grove, the longtime Intel CEO who built the company into the world’s dominant semiconductor maker, in High Output Management (1983). [1] Grove dedicates a chapter to the framework, opening from a real Intel promotion gone sideways and landing on the conclusion the figure above renders:

The conclusion is that varying management styles are needed as task-relevant maturity varies. Specifically, when the TRM is low, the most effective approach is one that offers very precise and detailed instructions, wherein the supervisor tells the subordinate what needs to be done, when, and how: in other words, a highly structured approach. [1]

Grove calls task-relevant maturity “the fundamental variable that determines the effective management style.” [1]

References

1
Andy Grove, High Output Management (New York: Vintage Books, 2015), 243-246, paperback.
https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884

Keep learning

Control + Competence + ClarityToolYou can only divest control safely when two supporting pillars are in place: technical competence (people must know enough to make good decisions) and organizational clarity (people must understand what the organization is trying to achieve).The Flow ChannelToolEngagement lives in the channel where challenge and skill stay matched: too much challenge and you're anxious, too little and you're bored.