A manager gets worn down when an employee checks in on every small decision. The team calls it a lack of initiative. The manager starts wondering whether this is just how younger employees work.
That explanation is convenient. It puts the problem in a generation instead of in the conditions the manager controls.
Repeated questions can mean someone needs more training, has too little experience, or is carrying too much work. They can also mean the employee cannot tell what they are allowed to decide, what a good result looks like, or how the manager will respond if something goes wrong.
You cannot know which explanation fits by labeling the behavior. You have to look at the work.
Have you made the standard clear? Does the employee know which decisions are theirs to make? Is feedback frequent enough that they can adjust before a small mistake becomes a major correction? Or do they mostly hear from you when you are frustrated?
If your expectations change with your mood, checking in may be the rational choice. The employee is trying to avoid a consequence they cannot predict.
That does not make every question the manager’s fault. Some people need closer direction. Some are still learning the job. And at some point, employees have to use what they know and take responsibility for a decision.
But if you want more initiative, “just be more confident” is not a management system.
Give people a clear outcome, explain which decisions they can make without you, and be explicit about when they should bring you in. Then let them work within those boundaries. When a decision misses the mark, address the decision and the standard. Do not make the employee guess whether one mistake has changed your view of them.
Consistency does not mean lowering the bar. It means the bar does not move without warning.
And it is worth being honest about the part managers often miss: being the person who approves every step can feel like responsibility. It can also be a way to keep control. If no one acts without your permission, you may have trained the team to wait—and then criticized them for waiting.
So before you call someone hesitant, check the rules they are working under. Are they clear enough to act on? Does this person have the skill and authority the task requires? If not, fix the gap. If they do, make room for them to own the work.
Then pay attention to what happens next. If the questions continue, you may be looking at a training need, a workload problem, or an employee who is not taking responsibility. Those are different problems. Treating them all as generational is not a diagnosis.
Your team does not need you to make every hard thing easy. It needs to know what the work requires, where its authority begins and ends, and whether the standard will still be the standard tomorrow.
If people are spending more energy predicting your reaction than doing the work, that is worth examining. Not because every hesitation is your fault, but because you may be asking for initiative in a system that rewards permission-seeking.
