The core idea in one glance
- It measures readiness for one task, not overall talent.
- High experience does not automatically mean high ownership, and vice versa.
- The right response ranges from detailed direction to light-touch oversight.
- Public-sector work often needs tighter controls when risk, auditability, or public impact is involved.
- The framework works best when you revisit it as tasks change.
What task-relevant maturity actually measures
The idea goes back to Andy Grove’s High Output Management, but it remains practical because it reflects something managers see every day: the same person can be highly capable in one task and still need close support in another. I think that is why the concept still matters. It stops us from making lazy assumptions based on grade, tenure, or confidence.
At its simplest, task-relevant maturity combines four things:
- Knowledge of what the task requires.
- Experience with similar work in a similar setting.
- Judgment about risks, sequencing, and trade-offs.
- Willingness to take responsibility for the outcome.
That last point is easy to miss. A person may know how to do the work but still avoid ownership, hesitate on decisions, or wait to be rescued at the first sign of friction. I have seen senior staff who were excellent in one operational area but still needed detailed guidance when asked to produce a board paper, manage a new process, or handle a sensitive stakeholder issue. That is why this measure is task-specific rather than person-specific. Once you see that distinction, the next question becomes how supervision should change in response, which is where the framework becomes useful in real management.
Why it changes the way you supervise
Supervision fails when managers use the same style for everyone and every task. The point of task-relevant maturity is that the level of oversight should move with the person’s readiness for the work. In practice, that changes four things: how much detail you give, how often you check in, how much decision authority you hand over, and how quickly you step back.
When maturity is low, the manager should be more directive. That means specific instructions, clear deadlines, examples of what good looks like, and frequent early checks. When maturity is medium, the manager should spend more time coaching than instructing. When maturity is high, the manager should set the outcome, define the boundaries, and then leave room for independent execution.
In a UK public-sector setting, this matters for more than productivity. It affects audit trails, fairness, compliance, and public trust. A capable colleague may still need structured oversight on safeguarding work, procurement, casework sign-off, or a ministerial brief because the risk profile is higher than the task’s surface simplicity suggests. That is not mistrust. It is sensible supervision. The next step is learning how to judge readiness without turning every conversation into a formal assessment.
How I judge readiness without overcomplicating it
I do not try to turn this into a score out of ten. In my experience, that becomes fake precision. I look for evidence in the task itself, because people often look more confident than they are and more cautious than their experience suggests.
These are the signals I pay closest attention to:
| Signal | What it usually tells me | What I ask next |
|---|---|---|
| They can explain the next step without prompting | They understand the sequence, not just the headline task | “What would you do first, second, and third?” |
| They know the local process and the people involved | They are more likely to move safely through the organisation | “Who else needs to be involved before this moves forward?” |
| They can spot risks, not just complete actions | They are starting to think like an owner | “Where could this go wrong, and what would you do if it did?” |
| They have delivered similar work in this setting before | Their judgment is based on real context, not theory | “What was different the last time, and what would you repeat?” |
| They ask for the right kind of help | They understand what they do and do not need | “Do you need direction, review, or a decision from me?” |
A simple rule I use is this: start with a short scoping conversation, agree what done looks like, and put an early checkpoint in place for the first draft, first case, or first deliverable. For many tasks, a 10 to 15 minute brief is enough to prevent a costly misunderstanding later. I would rather review a rough version early than discover a major gap at the deadline. Once the work proves itself in the actual environment, autonomy can widen quickly. That leads straight into the most useful part of the framework: how to adjust your supervision style by maturity level.
How I adjust supervision by maturity level
This is where the concept becomes operational. I do not think of it as a personality test; I treat it as a management choice about structure, review, and decision rights.
| Maturity level | What I do | What I avoid | Public-sector example |
|---|---|---|---|
| Low | Give exact steps, examples, deadlines, and an early checkpoint before the next stage | Vague delegation and open-ended expectations | A new officer handling a casework template for the first time |
| Developing | Agree the outcome, ask for a draft approach, and review the important decisions | Taking the work back too early or rewriting everything myself | A colleague drafting a policy briefing with some prior exposure |
| High | Set the target, boundaries, and risk triggers, then step back | Checking every detail or re-approving every decision | An experienced manager leading a familiar service improvement project |
The useful twist is that the same person may sit in different rows depending on the task. A senior officer may need very little oversight on stakeholder coordination but more structure on procurement. A confident team member may be brilliant in routine casework and still need coaching on writing a board paper. In other words, the unit of analysis is the task, not the person. That is easy to forget, and it is where a lot of managers get into trouble.
Where public-sector managers usually get it wrong
The most common mistake is using grade or tenure as a proxy for readiness. In reality, those are weak signals. A person can have fifteen years of service and still be low in maturity for a new digital process, a new policy area, or a new stakeholder environment. I see the opposite too: a newer colleague who is sharp, organised, and ready for more than their title suggests.
These are the errors I see most often in leadership and supervision:
- Confusing confidence with competence. A polished update can hide shallow task knowledge.
- Assuming one good result means full readiness. One delivery is evidence, not a pattern.
- Keeping a capable person on a tight leash. Overchecking drains motivation and slows learning.
- Removing structure too early. A good start is not the same as stable performance.
- Ignoring context shifts. New systems, new stakeholders, and new risk levels can reset maturity fast.
In UK public-sector teams, this shows up in familiar places: a council officer moving into committee work, an NHS manager taking on a new service line, or a civil service colleague learning how to write for a different audience. The work may look adjacent, but the local rules, pace, and consequences are different. Once you recognise those shifts, it becomes easier to design a better routine for day-to-day supervision.
The routine I would use in the first 30 days
If I were leading a new task or a new assignment, I would keep the routine simple and consistent. Complexity is usually not the answer; clarity is.
- Name the task clearly. State the exact output, the deadline, and the standard it has to meet.
- Separate the non-negotiables from the flexible parts. Some decisions must be right; others can be adjusted later.
- Agree the first checkpoint before work starts. For a new task, I like an early review after the first draft, first case, or first milestone.
- Ask for evidence, not reassurance. I want to see the plan, the draft, or the logic, not just hear that it is under control.
- Reduce oversight only after repeated proof. Two or three clean repetitions in the same context are more persuasive than one strong performance.
For a higher-risk task, I would shorten the feedback loop rather than lengthen the brief. A 15-minute check-in every week is often enough for a developing task, but a sensitive or public-facing task may need a review before sign-off, not after. The aim is not to watch people constantly; it is to create the right amount of friction at the right moment. That is what helps people grow without exposing the service to avoidable mistakes.
Use the framework as a lens, not a label
The real value of task-relevant maturity is not the label itself. It is the discipline of matching supervision to the work, the person, and the context. In a local authority, NHS team, or civil service unit, that usually means giving more structure where the task is new, risky, or ambiguous, and stepping back when the person has already shown they can deliver in that exact setting.
If you use it well, you will usually see three things fairly quickly: fewer unnecessary check-ins, fewer avoidable errors, and faster growth in judgment. That is the point. The framework only matters when it changes what you do on Monday morning, so start with one task, one person, and one decision about how much oversight is actually needed.
