How do you know if you are doing well as a manager?

A manager self evaluation works when you compare your intentions with repeated evidence from the people and work around you. You are probably doing well when engineers understand what matters, raise risks before a crisis, make decisions without waiting for you, and tell you difficult truths. No single delivery result or compliment proves this. Look for patterns, ask directly, and test one improvement at a time.

What does doing well actually mean?

Doing well means your presence improves the team's ability to think, decide, learn, and work together. It does not mean every sprint is smooth or every person is happy with every call. Engineering includes uncertainty. A useful manager helps people face that uncertainty with clear context, fair decisions, and enough safety to expose problems while they are still manageable.

Your intent matters, but impact gives you evidence. You may intend to give autonomy while rewriting every technical proposal. You may intend to be available while frequently moving 1 on 1 meetings. Self evaluation asks what people reasonably experience. It replaces the comforting question, “Am I trying hard?” with the more useful question, “What does my behavior make easier or harder?”

Keep the judgment personal and practical. This is not an organization scorecard, a leadership course review, or a comparison with another manager. You are examining choices within your control: how you listen, clarify, delegate, challenge, support, and repair. The result should be a better next action, not a permanent label.

Which evidence should you trust?

Trust evidence that appears in several forms. Notice what people say, what they do under pressure, and what work artifacts reveal. If reports say priorities are clear but three engineers pursue conflicting interpretations, ask what your communication missed. If people praise your availability but decisions stop whenever you take leave, your help may have become dependence.

Specific moments are more useful than broad ratings. Review a design disagreement, a missed commitment, a difficult 1 on 1, or an incident response. Ask what you knew, what you assumed, what you did, and what happened next. One moment cannot define your management, but several moments can reveal a habit.

Seek evidence that could disconfirm your preferred story. A manager who values kindness may avoid asking whether their delayed feedback created confusion. A manager who values urgency may overlook people becoming silent. Honest evaluation includes strengths, but it spends attention where pride or fear makes curiosity difficult.

What are the five parts of a useful review?

1. Read what a manager self assessment is and choose a small set of behaviors to examine.
2. Study which signals show a manager is effective without turning them into a team score.
3. Learn how to get feedback on your management without asking people to manage your feelings.
4. Use a 1 on 1 self review to inspect where your attention goes in recurring conversations.
5. Create a manager development plan based on one behavior and visible practice.

Follow the parts in order the first time. They move from definition to evidence, then from feedback to practice. Later, return to the part that fits your current question. A tense planning cycle may call for signal review. A pattern of shallow conversations may call for inspecting your 1 on 1 notes.

How can engineering work reveal your impact?

Imagine a service migration stalls because two senior engineers disagree about ownership. A manager can settle the design personally, schedule repeated debates, or clarify the decision owner and constraints. The result matters, but so does the method. If the engineers can make the next comparable decision with less intervention, your management increased capability.

Consider a junior engineer who reports a risky deployment assumption. If your first response is curiosity, they are more likely to bring the next concern early. If you immediately defend the plan, they may comply and stay quiet. The deployment can succeed either way, so delivery alone misses the management signal. What people learn about speaking up is evidence.

Look at your absence as well. When you take a week away, can the team resolve normal tradeoffs, find context, and ask the right partner for help? Healthy independence does not make a manager irrelevant. It shows that context and authority have been distributed instead of stored in one calendar.

How do you avoid grading yourself by mood?

A hard week can make competent management feel like failure. A successful release can make weak habits feel harmless. Separate emotional weather from observed behavior. Write down facts before interpretations: what was decided, who spoke, what changed, where confusion remained, and what you did next. Then consider possible explanations.

Use a regular review window. Ten minutes each Friday can capture moments while they are fresh. A longer monthly review can group them into patterns. Regular notes reduce the temptation to build your whole story around the most recent conflict or compliment. They also make gradual progress easier to see.

Include context without using it as an excuse. A sudden incident, a vacant role, or an unclear company decision can limit your options. Still ask how you responded within those limits. Good self evaluation is fair, not harsh. Harshness narrows learning because it turns every observation into a threat.

What should you ask the people you manage?

Ask questions tied to behavior: “When do I add useful clarity?” “Where do I enter decisions too early?” “What concern is harder to raise with me than it should be?” Specific prompts help people recall examples and reduce the pressure to summarize you as good or bad.

Offer more than one route. Some people will answer in a 1 on 1, some in writing, and some only through a private collection process. Power changes candor. Saying “be honest” does not remove the risk a report feels. Make questions optional, avoid pressing for names, and never debate a person's experience in the moment.

Close the loop with proportion. Say what you heard, what you will try, and what you are not changing yet. Then let behavior carry the message. Repeatedly asking for feedback without visible response teaches people that disclosure creates work but not change.

Which warning signs deserve attention?

Notice when every decision returns to you, meetings become quieter after you speak, bad news arrives late, or the same person repeatedly rescues delivery. Notice frequent cancellations of coaching conversations and technical debates that stay polite but never become clear. These signs are questions, not proof. Explore them before assigning cause.

Also notice positive signals that may conceal a cost. Rapid execution can depend on an exhausted lead. Harmony can mean disagreement is unsafe. High responsiveness can mean nobody protects focused time. Ask what produces the visible result and whether people could sustain the pattern during an ordinary demanding month.

Your own defensiveness is useful data. If a comment makes you immediately explain, pause and record the reaction. You do not have to accept every claim, but urgency to reject it can point to an identity you are protecting. Return when you can ask what example led to the view.

How should you choose one improvement?

Choose a behavior small enough to practice and important enough to matter. “Become a better listener” is vague. “Wait until the engineer finishes, reflect the concern, and ask one question before offering a solution” is observable. You and the other person can tell whether it happened.

Connect the behavior to a real setting. Practice it in design reviews, 1 on 1 meetings, or incident discussions rather than waiting for a perfect coaching moment. Predict what might improve and what could feel awkward. A clear prediction helps you learn instead of merely hoping the change works.

Review after several repetitions. Ask whether people offered more context, whether decisions improved, and whether you maintained the behavior under pressure. Keep it, adjust it, or choose another approach. Personal development is a sequence of informed experiments, not a dramatic reinvention.

What does an honest conclusion sound like?

An honest conclusion is balanced and specific: “I create clarity when work is ambiguous, but I enter technical decisions too quickly when deadlines tighten. Over the next month I will name the decision owner before sharing my preference.” This statement recognizes value, identifies a pattern, and commits to action.

Avoid conclusions such as “I am a bad manager” or “the team is doing well, so I must be fine.” Both end inquiry. Your management changes across situations and relationships. One report may experience useful challenge while another experiences interruption. The variation deserves attention without erasing genuine strengths.

You know you are doing well as a manager when the evidence shows that your behavior helps people exercise judgment, speak honestly, and grow more capable together. You know you are evaluating well when contrary evidence can change your view. That combination of confidence and revision is itself a leadership skill.

Frequently asked questions

Related: manager self assessment, signs of a good manager, feedback for managers.

Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.