Does This Situation Actually Need You?

There is an email thread moving through the team. Several people have already responded, the issue is progressing, and the next steps are reasonably clear. Nothing material appears to have been missed.

You reach the email later than everyone else. You have a thought. Perhaps there is a question you could ask, a point you could clarify, or simply another perspective you could add.

So you start typing.

The question is not whether you have something useful to say. Most experienced managers will frequently have something useful to say. The harder question is whether the situation actually needs you to say it.

This is a small management moment, but it points to a larger developmental challenge. As managers become more experienced, they usually gain more opportunities to intervene. They see potential issues earlier, recognise patterns faster and have views shaped by experience. Yet becoming more capable of contributing does not necessarily mean contributing more often.

Sometimes good management is knowing when to step in. Sometimes it is knowing when to wait.

Why contributing can feel like managing

For much of our careers, contribution is how we demonstrate value. We answer questions, solve problems, identify gaps and improve the work in front of us. Being responsive is usually rewarded, while having something useful to add is evidence that we understand what is going on.

Those instincts do not disappear when someone becomes a manager.

I have seen developing managers remain closely connected to work even when others are already carrying it forward. They may reach an email after the conversation has largely moved on but still feel the need to add a comment because they have only just got around to reading it. They may ask several clarification questions while an issue is still developing, even though some of those questions may resolve themselves as more information becomes available.

It is easy to interpret this as an inability to let go, but that judgement may be too quick. The behaviour can come from a genuine desire to contribute. There may also be habits carried forward from being a strong individual contributor, or simply discomfort with something happening in their domain area without their knowledge.

Understanding those motivations matters. But understanding why a behaviour makes sense to someone does not require us to conclude that the behaviour continues to serve them well.

That is where development sometimes requires an honest challenge: is your involvement improving the work, or is it mainly demonstrating that you are involved?

Having something to add is not the same as needing to add it

Managers will almost always see things they could question, clarify or improve. Experience makes that more likely, not less.

But a thought inside a manager's head and an intervention in somebody else's work are not the same thing.

Once the manager speaks, the situation changes. A casual question can become something the team feels obliged to investigate. A preference can be interpreted as a requirement. A late comment can reopen a discussion that others thought had been resolved.

One additional email may not reopen the discussion. One unnecessary question is unlikely to undermine someone's confidence. The issue is more subtle than that. If the manager repeatedly enters situations because they can see something else to contribute, the team gradually works in an environment where managerial involvement is always nearby.

This creates a different test for when you need to contribute.

Instead of asking, Do I have something useful to add?, the manager might ask:

Will my involvement materially improve what happens next?

The threshold is higher, as perhaps it should be.

Small interventions can change how work moves.

Delegation is often discussed as a transfer of work. The manager gives someone responsibility and tries not to take the task back when difficulties appear.

But ownership is shaped by more than who has formally been given the work.

A manager can say, “This is yours,” while remaining present around it. They can be copied into every exchange, ask questions at each stage, correct small differences and routinely provide the final view.

Formal ownership has moved. Psychological ownership may not have moved nearly as far.

Over time, repeated intervention can create an expectation that the manager will eventually appear. People may leave space for the manager's opinion, not because they have been explicitly told to wait for approval, but because experience has taught them that another comment is probably coming.

This is one reason apparently small interventions deserve more thought than their individual importance suggests.

A manager does not need to take work back completely to make ownership feel conditional. Sometimes it is enough to keep reminding everyone, however unintentionally, that nothing is quite complete until the manager has had their say.

Repeated small interventions can change how people carry work even when the manager never formally takes ownership back. If experience tells people that the manager usually adds the final question, qualification or view, they may begin to leave room for it. The issue is not that ownership has disappeared. It is that the work never quite gets the chance to continue without managerial presence nearby.

Let the work take shape

One of the lessons I have had to learn is that when you have capable people you can trust and there is sufficient alignment around what you are trying to achieve, letting things develop before intervening is sometimes the more useful choice.

That does not mean the work will unfold exactly as I would have done it.

That is part of the point.

Someone else may take a different route. Their first response may not contain every detail I would have included. A question that occurs to me immediately may not yet have occurred to them.

The temptation is to close those gaps as soon as we see them. Yet sometimes the gap is simply the space in which another person is still thinking.

Give the situation time and the question may answer itself. The person may identify the issue without prompting. A potential issue that initially did not present itself may become clearer once the work has taken shape.

Waiting does not prevent the manager from contributing later. In some situations, feedback is more useful once there is enough substance to respond to. The manager can see how the person thought, what choices they made and where their judgement led them rather than directing each intermediate step.

Waiting can reveal something that immediate intervention hides. You see whether the person notices the issue themselves, whether the unanswered question resolves as more information appears, and whether a different approach eventually produces an acceptable result. The manager has not disappeared. They have simply allowed the situation to generate more information before deciding what it needs from them.

Waiting is not always good management

There is a danger in taking this argument too far.

A manager who notices something material and stays silent in the name of empowerment is not necessarily demonstrating trust. There are situations where intervention is part of the responsibility that comes with the role.

This is where managerial judgement comes in.

The harder cases are the smaller ones. A clarification question that could be asked now but may resolve itself tomorrow. A preference about how something should be approached. A piece of work that is different from how you would have done it but is not necessarily wrong.

In those moments, a useful question is:

Will things become materially worse if I wait?

If the answer is clear, intervene.

If the answer is not clear, waiting may provide information of its own. You see what the person does next. You learn something about their judgement. They discover something without your prompting.

The choice is therefore not always between intervening and doing nothing. Sometimes it is between intervening now and returning when the work has developed enough for your contribution to matter more.

Care enough to know when not to intervene

I have sometimes described this to developing managers as needing to “care less”.

I no longer think that is quite right.

Caring about the work is not the problem. We should want managers who care about the quality of what their teams produce, remain interested in what is happening and feel responsibility for the outcomes they oversee.

The developmental challenge is learning that care does not always need to express itself through intervention.

Sometimes caring means stepping in quickly because something material has been missed. Sometimes it means asking the question others are avoiding. Sometimes it means offering experience that changes the quality of a decision.

And sometimes it means letting capable people continue.

That requires trust, but it also requires judgement. The manager has to distinguish between a situation that genuinely needs their experience and one that simply offers another opportunity to express it.

This is particularly difficult because intervention can feel productive immediately. You have answered, clarified or improved something. Restraint produces less visible evidence of contribution.

As managers gain experience, they usually become capable of seeing more things they could improve. That makes restraint harder, not easier. The question is no longer whether you can make the work slightly better. It is whether the improvement is important enough to justify another intervention now.

Sometimes it is. Sometimes the comment can wait until the work has taken shape. And sometimes the work is already good enough to continue without another managerial contribution.

You can have an opinion and not express it yet. You can see another way and let someone test theirs. You can know the answer and leave enough room for another person to reach it.

And sometimes you must step in.

The real work is knowing the difference.

Reflection question

Where might stepping back allow someone else to step forward?

Continue Exploring

Good management is not measured by how often the manager contributes. Sometimes the more useful leadership choice is to create enough space for someone else to think, decide and carry the work forward. If this article was useful, you may also enjoy:

• What Am I Holding Onto That Someone Else Needs to Learn — why managers sometimes need to release work, judgement and responsibility so others can build capability.

• What Support Helps Without Removing Ownership? — how managers can provide guidance and coaching without making people dependent on their involvement.

• The Right Stretch Helps People Grow — why development requires enough challenge and responsibility for people to exercise their own judgement.

• Challenge Is Not the Same as More Work — why meaningful development comes from purposeful stretch and ownership rather than simply adding tasks.

Continue Your Leadership Journey

If this article was useful, explore the practical resources designed to help you become a more confident and thoughtful manager.

📘 100 Questions Every Manager Should Ask

A practical reflection companion with 100 questions for real management situations.

🎓 Riverstone Mini Courses

Short practical video courses with workbooks and tools you can apply immediately.

Stay Connected

Receive new articles and practical leadership ideas as Riverstone grows.