Task-Relevant Maturity: How to Manage Each Person Differently

Task-relevant maturity is the management idea, popularized by Andy Grove's book High Output Management, that the right management style depends on how ready someone is for the specific task in front of them, not on how senior they are. Low task-relevant maturity calls for structured direction; high maturity calls for agreed goals, room and light monitoring.

Definition: Task-relevant maturity (TRM) is a person's drive and readiness to take responsibility, combined with their education, training and experience, for one specific task, and it determines how closely a manager should direct that task.

You don't manage people. You manage a person doing a particular thing, and that changes from one task to the next.

In our view, the founder's job is to diagnose maturity task by task and adjust their style to match. This article explains the idea in plain terms, offers a simple diagnostic, and shows how to apply it in one-on-ones without becoming a micromanager or an absentee.

What task-relevant maturity means

Grove joined Intel at its founding in 1968, became its president in 1979 and its CEO in 1987, and published High Output Management with Random House in 1983. Startup leaders still read it widely.

Grove didn't coin the concept. He presents it as a finding of earlier management research and, in his notes, points to Paul Hersey and Kenneth Blanchard's Management of Organizational Behavior. In Grove's framing, TRM combines a person's "achievement orientation" and readiness to take responsibility with their education, training and experience.

His argument, in our own words: management style should follow that readiness for each task, and a manager's goal is to raise it as fast as possible, because higher maturity frees the manager's time.

The word "relevant" does most of the work. A senior engineer who has shipped ten backend systems has high maturity for building the eleventh. Put the same engineer in charge of hiring their first team and their maturity for that task is low, whatever their title. Treat them as "senior" across the board and you can leave them alone exactly where they need help.

The reverse happens too. A junior salesperson who ran a large campus organization may have high maturity for planning an event. A founder who insists on step-by-step direction there wastes both people's time and signals distrust.

Hersey and Blanchard's research lives on in Hersey's Situational Leadership model, which the Center for Leadership Studies dates to 1969. It likewise matches leadership style (from directing to empowering) to a person's "performance readiness," meaning their ability and willingness to do a specific task. If your team already uses that vocabulary, the two frameworks translate easily.

Marcus Buckingham makes a related point in Harvard Business Review's "What Great Managers Do" (2005): great managers learn each person's strengths, the triggers that activate them and how the person learns, instead of managing everyone to one template.

Why task-relevant maturity matters more at a startup

At a startup, almost everyone is doing something for the first time, and the company grows into new tasks faster than anyone can build experience. So maturity is low for a large share of the work, and it shifts constantly as people learn.

Getting this right matters because managers shape how people experience their jobs. Gallup estimates that managers account for at least 70% of the variance in employee engagement scores across business units.

Founders tend to miss in one of two directions:

Too loose. They manage everyone the way they like to be managed, usually with high autonomy, and are surprised when new hires flounder on unfamiliar work.
Too tight. They manage everyone closely because the stakes feel high, and lose their best people to the sense that they aren't trusted.

Task-relevant maturity offers a third option: match the style to the task, and change the style as maturity rises.

The three management modes

Think of your involvement as a dial with three broad settings. The labels below are ours. Grove describes the same progression as a structured, task-oriented style that spells out what, when and how for low TRM; an individual-oriented style built on two-way communication, support and mutual reasoning for medium TRM; and minimal involvement, focused on agreed objectives and monitoring, for high TRM.

Directive (low maturity)

You define what to do, how and by when, and you check in often, sometimes daily. The output is specified in detail. This fits when the person hasn't done this kind of task before, when a mistake would be costly, or when they've asked for structure.

It isn't punishment. Plenty of people prefer clear direction on unfamiliar work.

Coaching (medium maturity)

You agree on the outcome and the approach together. The person drives while you ask questions, review drafts and course correct, with check-ins weekly or at milestones. In our view, much of the work in a growing startup sits here.

Delegating (high maturity)

You agree on the goal and the constraints, then get out of the way. You review results, not process. Check-ins are periodic and mostly informational, but they don't stop: monitoring is still part of Grove's high-maturity style. Your role shifts to removing obstacles and supplying context the person can't see from their seat.

The usual mistake isn't picking the wrong mode. It's staying in one mode after maturity has changed. The whole point is to move the dial.

How to diagnose task-relevant maturity step by step

Here is a quick assessment to run for each significant piece of work you hand to someone:

Name the task precisely. "Own onboarding" is too broad. "Design and run the first-week onboarding flow for enterprise customers" is a task you can assess.
Ask about direct experience. Has this person done this exact kind of work before, here or elsewhere? Not something adjacent; this.
Ask about results. When they did it before, how did it go, and what would they do differently?
Check motivation. Do they want this task, or are they doing it because nobody else will? Low motivation lowers maturity even when skill is high.
Check context. Do they understand how the task connects to this quarter's goals? Missing context is, in our view, a common reason capable people make the wrong call.
Pick a starting mode and say it out loud. "I'll be hands-on for the first two weeks, then step back once we've seen the first version" is a perfectly good sentence.

Founders skip step six all the time. Naming the mode stops people from reading close supervision as distrust, or light supervision as neglect.

Applying task-relevant maturity in one-on-ones

One-on-ones are where the dial actually gets turned. Grove ties their frequency to the person's task-relevant maturity and how fast their work is changing, which points to meeting more often with people who are new to their tasks. One simple structure:

Start with their agenda. What's on their mind, what's blocked, what do they need?
Walk through their two or three main tasks. For each, ask which mode you're in and whether it still fits. If they've shipped two good versions of something you were coaching, move toward delegating and tell them.
Look for mismatches. If you're delegating something and the results keep surprising you, move back to coaching. If you're directing something they've clearly mastered, let go.
Close by confirming what changes before the next meeting.

Keep a short table in your one-on-one notes with four columns (task, maturity, current mode, next check) and update it every two weeks. If nothing has moved in a month, either the person isn't learning or you aren't letting them.

Over time the one-on-one becomes a record of growth. People see themselves move from directed to delegated on task after task, which is often more motivating than a new title. For how one-on-ones fit into the rest of your operating rhythm, see our guide to running startup team meetings and all-hands.

A worked example: one hire, three tasks, three modes

As an illustrative example, say you hire your first account executive, Maya, who closed mid-market deals for six years at a larger company. (If you're still deciding who that first hire should be, our piece on hiring your first key employees covers it.)

Running discovery calls and negotiating contracts: high maturity, so delegate. Set a quota, agree on the pipeline review cadence and step back.
Selling your specific product to your specific buyer: low maturity, so direct. Nobody but you has done it. Join her first ten calls, hand over your objection-handling notes and debrief after each one.
Building the sales process (CRM stages, forecasting, handoff to onboarding): medium maturity, so coach. She has seen good processes but never built one from scratch. Agree on the outcome, review her draft and give feedback.

Six weeks later, product-specific selling has moved to coaching and the process work has moved to delegating. That progression is what good startup management usually looks like: one person, three dials, all turning.

The pattern shows up constantly in founder-led sales, where the founder starts as the only person with high maturity on the pitch. Transferring that knowledge deliberately, rather than hoping a hire "figures it out," is a big part of what 1752vc's Accelerate program teaches: founder-led go-to-market and sales training for early-stage startups ready to grow, so founders can move from directing every deal to coaching and eventually delegating a repeatable motion.

If you're still closing the first customers yourself, start with our sales advice for technical founders. Many venture firms also bring in operating partners to coach founders through exactly these transitions; our operating partner job description explains that role.

"Isn't this just micromanagement with a nicer name?"

It's a fair worry. "Hire great people and get out of their way" is popular advice for a reason, and any framework that licenses a founder to hover will get used that way by some founders. There's a live debate about how deep founders should stay in the details, which we get into in our piece on founder mode.

But.

Micromanagement ignores readiness and doesn't let go. Task-relevant maturity starts close only where experience is thin, says so out loud, and has a plan to step back. The test is direction of travel: if your involvement on a task isn't shrinking over time, it's probably micromanagement, whatever you call it.

Common founder mistakes with task-relevant maturity

Diagnosing by title. "She's a senior engineer, she can handle it." Titles measure history, not readiness for this task.
Diagnosing once. Maturity rises quickly on repeated tasks, so a mode that was right in month one can be wrong by month three.
Confusing directive with disrespectful. Clear instructions on unfamiliar work are often a kindness. Vague autonomy on unfamiliar work can set people up to fail.
Staying stuck in directive mode. Some founders find every result slightly wrong and don't move the dial. The person leaves, and the founder concludes they weren't good enough.
Delegating without context. High-maturity people still need to know what the company is optimizing for this quarter. Delegation doesn't have to mean silence.
Applying it only downward. The model applies to co-founders and to you. Where is your own maturity low? That may be where an advisor, a coach or a peer helps most, a theme we cover in how to delegate as a founder.

The bottom line

Diagnose the task, not the person. Say which mode you're in. Then keep moving the dial as people grow.

A title tells you where someone has been.

Their maturity on the task tells you how close to stand.

Key takeaways

Task-relevant maturity, popularized by Andy Grove's High Output Management, means matching your management style to a person's experience with a specific task, not to their seniority.
One practical approach uses three modes (directive, coaching, delegating) and moves between them as maturity rises or falls.
Consider diagnosing task by task using direct experience, past results, motivation, and context, then telling the person which mode you are in.
One-on-ones are where the dial usually gets adjusted; a short table updated every two weeks can help track it.
Gallup estimates managers account for at least 70% of the variance in engagement across business units, and a common founder error is diagnosing once and leaving the dial where it is.

Frequently asked questions

What is task-relevant maturity in management?

It is the idea that the right level of supervision depends on a person's drive, readiness for responsibility, training and experience for a specific task, rather than on their overall seniority. Low maturity calls for detailed direction, and high maturity calls for agreed goals, autonomy and monitoring. Andy Grove popularized it in his 1983 book High Output Management, building on Hersey and Blanchard's research.

How do you assess task-relevant maturity?

One approach is to name the task precisely, then ask whether the person has done that exact kind of work before, how it went, whether they want the task, and whether they understand the context. Choose a management mode from the answers, and it helps to tell the person which mode you are in.

What is the difference between micromanaging and task-relevant maturity?

Micromanaging is close supervision regardless of the person's readiness, and it usually continues after they have proven themselves. Managing by task-relevant maturity means being hands-on only where experience is low, and deliberately stepping back as the person shows competence on that task.

How is task-relevant maturity different from situational leadership?

They share roots, since Grove's notes point to Hersey and Blanchard's work. Paul Hersey's Situational Leadership model, dated to 1969, also matches leadership style to a person's readiness (ability and willingness) for a specific task, using four styles from directing to empowering. Grove's version uses three levels and is framed around the practical question of how closely a manager should supervise and monitor each task.

Why does task-relevant maturity matter for startup founders?

Much of the work at a startup is being done for the first time, so maturity is often low and changes fast. Founders who manage everyone the same way can either leave new hires stranded on unfamiliar tasks or smother experienced people on tasks they have already mastered.

Sources

Disclaimer: This guide is for general education only and is not legal, tax or investment advice. Laws, market data and program terms change, so it may not reflect the latest developments or fit your situation. Treat it as a starting point, not a source of truth, and talk to a qualified lawyer, accountant or financial adviser before you make decisions.