A 1 on 1 self review is a short check of how you used your attention in recurring conversations. After the meeting, ask who shaped the agenda, what you learned, when you moved into solution mode, what felt difficult to say, and whether both people left with clear commitments. Review several meetings for patterns. The aim is better presence and follow through, not a perfect script.
Why review a conversation that felt fine?
Comfort is not the same as usefulness. A friendly 1 on 1 can stay on project updates while uncertainty, conflict, or growth remains untouched. A difficult conversation can be valuable if both people understand more and know what happens next. Reflection helps you look beyond the mood at the end.
Managers also remember their own contribution more clearly than the other person's. You recall the thoughtful question you asked, but not the three minutes of explanation before it. A brief review captures structure and effect while the exchange is fresh. Over time, it reveals habits that neither person would name from one meeting.
The practice should remain light. You are not scoring the employee or creating a hidden record of emotion. Note your behavior, shared topics, and commitments. Protect personal details and follow company requirements. Reflection should make the relationship safer, not create surveillance.
What should you check after each meeting?
| Area | Reflection question | Possible next move |
|---|---|---|
| Agenda | Whose important topics had room? | Invite their priority before yours |
| Attention | Where did my mind or device drift? | Protect the time and remove distraction |
| Listening | Did I understand before advising? | Reflect and ask before offering a view |
| Power | What may have felt risky to say? | Name choice and make passing acceptable |
| Commitment | Who promised what by when? | Write a concise shared follow up |
| Continuity | Did I return to the previous topic? | Open next time with the commitment |
You do not need a written answer for every row after every meeting. Choose the question that carries useful tension. Once a month, scan all six areas across recent conversations to catch what your selective attention misses.
Who shaped the agenda?
A useful 1 on 1 belongs primarily to the report's needs, while still making room for responsibilities only the manager can address. If your project updates consistently fill the session, move them to another channel. Ask what would make the time useful before presenting your list.
Ownership does not require the report to arrive with a polished agenda. Newer engineers, people under stress, or someone unused to supportive 1 on 1 meetings may need prompts. Offer choices such as a decision, a relationship, workload, feedback, or growth. Avoid interpreting initial silence as lack of interest.
Review whether urgent work repeatedly displaces longer concerns. An engineer may mention wanting broader design responsibility, then spend every meeting discussing the current release. If you never return, your calendar teaches that development matters only when delivery is calm.
How can you examine your listening?
Recall the moment you first formed advice. Did you continue listening for information that could change it, or did you wait to speak? Good listening is not silent performance. It is willingness to let the other person's meaning revise your understanding.
Notice question types. Questions beginning with “Have you tried” often contain a solution. Questions such as “What options are you considering?” or “What makes this difficult?” leave more room. Leading questions are sometimes efficient, but a pattern can train reports to search for your preferred answer.
Check whether you reflected important meaning. “You are concerned the review process rewards speed but leaves you holding maintenance” gives the person a chance to correct you. Reflection slows premature solution work and communicates that the effect matters, not only the task.
When does solution mode become a problem?
Engineering managers often earned their role through problem solving. Advice can feel helpful and may be exactly what is needed in a crisis. The problem is automatic advice before the purpose of the conversation is clear. The report may want help thinking, emotional acknowledgment, authority, context, or a direct answer.
Consider an engineer describing conflict with an infrastructure partner. If you immediately draft a message for them, you may solve today's wording while taking away ownership. Ask what outcome they want and what they have already tried. Then agree whether you should coach, intervene, or simply listen.
In your review, mark where your answer shortened exploration. Do not ban advice. Practice asking, “Would it help to think together, hear my view, or decide what support you need?” Choice improves both efficiency and agency.
What might have remained unsaid?
You cannot know every withheld thought, so avoid mind reading. Look for cues: a topic introduced then dropped, a long pause after a performance question, sudden agreement, or a concern described as something “people” feel. These cues invite gentle curiosity, not interrogation.
Power makes some topics costly. A report may hesitate to criticize your decision, name overload, discuss ambition, or say a recurring meeting is useless. Make the boundary explicit: “You do not have to answer now, but I want you to know disagreement with this plan is welcome.” Then respond well when disagreement appears.
Review topics you consistently avoid too. Managers may defer career uncertainty, team tension, or their own mistake because they lack a clean answer. Naming uncertainty is often better than silence. You can say what you know, what you need to learn, and when you will return.
How should you review an engineering conversation?
Suppose a senior engineer says code reviews consume every afternoon. You ask for queue numbers and suggest faster review blocks. Afterward, note that you treated the issue as scheduling. The engineer may have been describing their role becoming a permanent gate and their fear that quality depends on them.
At the next meeting, reopen it: “I moved quickly to scheduling last time. I want to understand what the review load means for your role and the team.” They may explain that newer engineers are not trusted with core services. Now the conversation can address knowledge, delegation, and identity as well as calendar time.
Your self review did not produce the answer. It revealed an assumption and created a better question. That is the practical value of reflection: it helps you return with more attention before a repeated pattern hardens.
What does good follow through look like?
End with clear ownership. If you promised to clarify promotion expectations or resolve access, record it and set a realistic date. If the report chose an action, let them own it without repeated checking unless support was agreed. Ambiguous commitments create disappointment on both sides.
Open the next relevant conversation by returning to the commitment. This shows that the topic mattered after the meeting ended. If you could not complete your action, say so before being asked and give a new plan. Reliability in small follow through builds permission to raise larger issues.
Do not turn every emotional conversation into tasks. Sometimes the commitment is simply to remain attentive or revisit after time. Ask what the person needs. The purpose of clarity is shared understanding, not converting human experience into a ticket queue.
How can you review patterns fairly?
Look across at least a month. Different reports need different conversation shapes. One may think aloud while another arrives with focused decisions. Fairness does not mean identical speaking ratios or topics. Ask whether each person has credible access to your attention, context, challenge, and support.
Notice differences linked to status or communication style. Do you interrupt fast speakers less? Do you offer senior engineers strategy while newer engineers receive only task advice? Do remote conversations drift toward updates? Treat the pattern as a hypothesis and ask for feedback.
Include your constraints honestly. A week of incidents may produce shorter meetings. The question is whether disruption became a habit and whether you repaired it. Reschedule promptly, name what was lost, and protect the next conversation.
Which improvement should you try next?
Select one behavior for several meetings. You might open with the report's priority, allow five seconds of silence, reflect before advising, or review the last commitment first. One behavior is easier to remember under pressure and easier to evaluate afterward.
Tell reports only when it helps them participate. “I am practicing asking before I give advice, so I may pause more” can reduce confusion. Do not ask them to grade every attempt. Invite a comment if the change becomes unhelpful.
A 1 on 1 self review improves management by making attention visible. Brief reflection, respectful notes, and reliable follow through help you notice when habit replaces curiosity. The goal is not a flawless meeting. It is a relationship where meaningful work and difficult truth have somewhere to go.
Frequently asked questions
What is a 1 on 1 self review?
It is a manager's brief review of who shaped the agenda, what they learned, how they listened, what commitments were made, and what may have remained difficult to say.
Should managers record 1 on 1 meetings?
Usually no. Use brief respectful notes about topics and commitments. Recording can damage privacy and candor unless there is a clear agreed need and appropriate protection.
How often should managers review their 1 on 1s?
Take two minutes after each conversation and review patterns monthly across several meetings. Do not judge the relationship from one session.
What is a sign that a 1 on 1 is too manager led?
The manager speaks most, repeatedly supplies solutions, or uses the meeting mainly for status while the report's concerns and agenda receive little room.
How can a manager improve the next 1 on 1?
Choose one behavior such as asking a broader opening question, allowing silence, reflecting before advising, or returning to a previous commitment.
Related: manager self evaluation, manager self assessment, manager development plan.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.