People Management
Measure Your Growth as a New Manager Without Taking Credit for the Team's Work
Assess observable manager behaviors and support feedback separately from team outputs, with shared attribution, evidence limits and a completed next-action cycle.
Measure your growth as a new manager through changes in your own observable behavior, the quality of support you provide, and feedback on how that support is experienced. Keep those findings separate from the team's delivery results. Describe your contribution to a shared outcome specifically, credit the people who produced the work, and state what the evidence cannot establish. A successful release is context for your assessment, not proof that your management caused it.
This LandOffer.ai guide includes a completed fictional growth-evidence table and quarterly self-assessment with a feedback-to-action example. All names, work, observations, counts, and feedback are illustrative. No employee survey, private record, management intervention, or team outcome was tested.

Separate your behavior from the team's result
A new manager's review often starts with what the team shipped. That can show the setting in which you worked, but it does not identify which parts you personally influenced or whether you improved as a manager. Start by describing the support decisions and behaviors you were responsible for.
For example, you may have clarified a priority conflict, preserved time for a colleague's learning, asked a better coaching question, or followed through on an agreed action. For each claim, identify your action, the record or observation supporting it, and what that evidence leaves unknown. “The team shipped, so I became an effective manager” skips that work.
The Center for Creative Leadership's 2020 Leadership Development Impact framework distinguishes individual, group, organizational, and societal levels of impact. This is a way to organize an evaluation, not proof that a new manager or a training program caused a specific team outcome. Keep the levels distinct when describing your own development.
A change in team results can have many explanations: engineers' judgment, earlier groundwork, product decisions, staffing, technical dependencies, or different work difficulty. You can document a plausible contribution without assigning yourself a percentage of the result or implying that everyone else's work followed from your intervention.
Choose a few behaviors that you can observe
Define growth goals around a management task, the behavior you will practice, the evidence you can inspect, and the feedback you need. Avoid broad statements such as “be inspirational” or “make the team happier” when the record cannot explain how those judgments will be made.
For example, set a goal to end priority discussions with a named decision owner and an explicit next step. Another might be to stop replacing an employee's reasoning with your preferred technical answer. The evidence would differ: a decision note for the first, and observation plus participant feedback for the second.
Do not confuse repetition with quality. Holding every scheduled conversation does not establish that the conversations helped. Completing a feedback course does not demonstrate changed behavior. Activity records establish that practice occurred; feedback and observation help examine whether the support changed.
MIT's Managers' Feedback Program describes asking direct reports for feedback, setting management learning goals, sharing those goals, and revisiting progress. That is a specific employer program, not a required method or guaranteed outcome for readers. Its useful structure is the connection between feedback, practice, and a later check of the experience.
Keep the set small enough to review honestly. A list of ten leadership traits can become a narrative of intentions rather than evidence of change. Choose the behaviors most relevant to the work and feedback you actually have.
Gather feedback without making employees prove your success
Explain that you are asking about your management behavior, not evaluating the person who responds. Use the organization's appropriate feedback route, and be clear about how comments will be handled. Do not promise anonymity that a small team or informal conversation cannot provide.
Ask for a concrete example: “When I summarized the priority decision, was it clear who could make the next call?” is more useful than asking whether you are a good manager. Invite evidence that contradicts your self-assessment. Thank people without arguing them into a more favorable interpretation.
Employees may reasonably be cautious about giving upward feedback. A positive comment, silence, or a small response set is not a representative measure of trust. Avoid converting a few informal comments into a team-wide satisfaction score or claiming that everyone feels supported.
Use your manager, a coach, or a peer observer where appropriate to examine your behavior. Keep employee comments private and record only the detail needed for the development task. Your growth record should not become an unnecessary collection of other people's personal disclosures or performance information.
Completed manager-growth evidence table
In this fictional quarter, first-time manager Dalia supports a team building a public-library catalog search service. Engineers Keiko and Mateo design and implement a new query explanation feature; quality engineer Ruth develops the validation cases. Dalia's development goals concern priority clarity, coaching, and follow-through, not authorship of that feature.
The table records her assessment at the end of the quarter. Its counts are local illustrative observations, not validated measurements of leadership effectiveness.
| Growth goal | Completed evidence in the fictional case | Finding and limitation |
|---|---|---|
| Clarify priority decisions | In four selected planning discussions, Dalia recorded the decision owner and next step. In the first discussion, the owner remained ambiguous until corrected the following day; the next three notes were clear at the close. | A specific improvement in the sampled notes. Four selected discussions do not establish that all priorities were clear across the quarter. |
| Coach without taking over | Peer manager Tomas observed two agreed practice conversations. In the first, Dalia supplied a solution before hearing the colleague's reasoning. In the second, she asked about options and let the colleague choose the next technical investigation. | Evidence of changed behavior in one later observation. It does not establish the colleague's long-term independence or that Dalia's questions caused better engineering decisions. |
| Follow through on promised support | A private action list contained six manager commitments due during the review period. Five were completed by the agreed date. A review-access request was late; Dalia recorded the missed date, notified the affected person, and arranged access afterward. | Follow-through is mixed, not complete. The record is about Dalia's commitments, not a judgment of the employee who needed access. |
| Check the experience of support | Two colleagues gave optional work-focused feedback. One found the written priority summaries useful; another said Dalia still announced decisions too late for independent preparation. | Contrasting feedback informs the next goal. Two comments are not a representative team survey or proof of trust. |
Dalia keeps both positive and uncomfortable evidence. She does not replace the late access commitment with a general statement that she “removed blockers,” or count the team's feature release as proof that her coaching goal was achieved.
She also records where the evidence came from: selected decision notes, her own commitments, an agreed peer observation, and voluntary work-focused comments. These sources have different strengths. Notes show what was recorded, an observer sees a limited interaction, and feedback describes someone's experience. None is a complete view of her management.
Credit the shared work precisely
When describing the feature, Dalia names the actual contributions: Keiko and Mateo designed and implemented it, Ruth developed validation cases, and the product partner defined the user question. Dalia's contribution was resolving a competing-priority request and arranging the review route. Those are meaningful actions without claiming ownership of the engineering result.
GitLab's organizational-structure guidance explicitly tells managers to credit their reports' work rather than present it as their own. It is an employer's stated expectation, and it supports a useful writing discipline here: name the work, the contributors, and the manager's distinct action.
Compare two statements. “I delivered the new query feature and improved team effectiveness” hides the contributors and asserts an unmeasured result. “The team delivered the feature; I resolved the priority conflict and established the review route” identifies a contribution that can be checked. Add the specific evidence and limits before using that sentence in a self-assessment.
Describe your specific support alongside named contributors. If you cannot establish that an action reduced delivery time, record the action and subsequent result without treating sequence as causation or assigning yourself a numerical share of credit.
Completed quarterly self-assessment and next action
Here is Dalia's fictional self-assessment, written from the evidence table rather than reconstructed from the team's headline achievement.

This quarter I improved the clarity of some priority discussions, but my follow-through and the timing of decision communication remain inconsistent. The first of four sampled planning notes lacked a clear owner until the next day; the next three ended with an owner and next step. I completed five of six due support commitments on time and addressed the late access request after notifying the affected colleague. I should not describe that as perfect reliability.
In two observed coaching practices, I moved from giving an early technical answer to asking about options before the colleague selected an investigation. That is evidence of one changed interaction, not proof that I have established a consistent coaching habit. Two voluntary feedback comments also differed: a colleague valued the summaries, while another needed decisions earlier to prepare independently.
Keiko and Mateo designed and implemented the query explanation feature, Ruth created its validation cases, and the product partner defined the user need. I resolved a competing-priority request and arranged its review route. The release belongs to the contributors named above. My decision and review-route records show specific support actions, without establishing that those actions caused release quality, timing, or impact.
The next action comes from the less favorable feedback. Dalia and her manager, Lionel, agree that she will circulate the decision question and available context before two upcoming planning discussions, identify what remains open, and state when a decision is needed. She will then ask whether participants had enough context to prepare, using the approved feedback route.
A completed illustrative follow-up shows why this matters. Before the first discussion, Dalia sends the context late again and records that the practice was not carried out as intended. Before the second, she shares it at the agreed time and a participant says the open question was clear but the decision boundary was still confusing. Dalia revises the next pre-read to distinguish a recommendation from a decision reserved for Lionel.
Her finding is “practice partly implemented; decision-authority explanation still needs work.” She does not turn the later positive comment into a claim that team autonomy increased, or omit the first missed attempt. Lionel reviews the revised recommendation-versus-decision explanation with her; its use in a later discussion remains unobserved.
This closes a feedback-to-action cycle without pretending the issue is solved. The record contains an observed gap, a specific practice, mixed follow-up evidence, and a further revision. The next review should examine the revised explanation, not repeat the original goal indefinitely without a change in approach.
Keep your review useful and proportionate
A manager-growth assessment should support a decision about what to practice, continue, or change. It does not need an elaborate dashboard of every conversation. Use enough evidence to substantiate the claim while keeping private material in the proper location and retaining the limits of the sample.
Review changes in context as well as behavior. An easier assignment, a new senior colleague, or additional organizational support can affect how the quarter felt. Document those conditions rather than treating every improvement or difficulty as a measure of your personal leadership quality.
Use team outcomes to ask better questions. If delivery improved, ask what contributors and systems changed. If a commitment slipped, examine your support and decision process without assuming that the team failed because of you or succeeded despite you. Both extremes replace investigation with a convenient story.
For the next period, choose a bounded behavior and a review point with your own manager. Specify the feedback source and what would count as evidence against your preferred interpretation. Leave room for an honest result such as insufficient observation or mixed progress.
Save the evidence source, limits, named contributors, next behavior, and review owner before writing a leadership-impact claim. Return to LandOffer.ai for related management guidance after your record makes clear what you changed, who produced the team result, and what you still do not know.


