Doing a task many times can make it feel familiar without making your judgement better. The same handover can run smoothly because the conditions were forgiving, while a persistent weakness in how you explain a decision goes unnoticed. Experience gives you material to learn from. It becomes development when you examine what happened, hear how the work affected others and use that understanding in a later attempt.
This can happen within ordinary work. You do not need a new job title or a formal course to improve how you assess evidence, coordinate with another function or communicate a recommendation. You do need a particular part of the work to improve and enough attention to tell whether your next approach made a difference.
Choose a specific part of the work to improve
A learning aim is easier to act on when it names a decision or behaviour within your reach. “Get better at cross-functional work” is a useful direction, but it gives you little to examine after a particular assignment. “Explain the evidence and unresolved points before asking another team to decide” identifies something you can try and observe.
The opportunity may come from a difficulty, but it can also come from work that went well. Perhaps a colleague understood a handover immediately because you made the remaining action and its owner clear. That success is worth examining: what did you do, and would the same approach help when the situation is more complicated? The aim is to understand the contribution of your method, not to search every completed task for a fault.
Choose an aspect where you have some agency. A professional may not control the deadline, the decision holder or the availability of another team. They can often change how they prepare information, identify uncertainty, invite a response or follow up. Keeping the aim within that scope makes the next attempt possible and prevents a development goal from becoming a complaint about conditions you cannot alter alone.
Look closely at the work, not just the result
Reflection works best when it separates the result from the choices and conditions that produced it. A meeting ended with agreement, for example, but agreement alone does not show whether the recommendation was well understood, whether a concern was left unspoken or whether the decision happened to be easy. Reconstruct the sequence while it is still fresh: what information you had, what you chose to emphasise, what others needed and what happened afterward.
Suppose a quality professional hands over an unresolved verification point to a colleague before a planned decision. The colleague later seeks clarification because the handover describes the issue but not which evidence is still missing or who is obtaining it. The professional can examine their own note and the follow-up conversation. The useful lesson may be about how to distinguish an open point from an assigned next action. It would be too much to infer from this one handover that they are generally poor at communication, or that the colleague should have understood without asking.
Reflection also needs room for alternative explanations. The colleague might have had different background information, the circumstances might have changed, or the note might have been clear to someone closer to the work. That does not make the episode useless. It tells you what to check before turning one result into a broad conclusion about your capability.
Ask for feedback from people who saw different parts
Feedback can show how your work landed beyond your own view of it. Ask someone who used the handover, reviewed the recommendation or took the next action what was clear and what they still had to discover. A person who only saw the final result may be able to comment on that result, but not on every decision you made along the way.
Specific prompts tend to produce more useful feedback than a request for an overall rating. In the handover example, the professional could ask whether the colleague could tell which evidence remained outstanding and what action was expected. They could also ask the decision holder whether the handover made the uncertainty visible at the right time. Those perspectives may differ because the people needed different information.
Treat feedback as evidence to interpret, not an automatic verdict. A colleague's frustration is relevant, but you still need to understand what they encountered and whether a change to your method would help. Equally, praise from one person does not prove the approach will work for every audience. Where feedback conflicts, look at the different roles, conditions and observations before deciding what to change.
Change something in the next suitable attempt
The learning cycle depends on trying a different approach when comparable work arises. A reflection that ends with “communicate more clearly” is unlikely to alter much. In the handover example, the professional might separate the evidence already reviewed from the outstanding item, identify who is obtaining it, and say which decision is waiting on it. The revised handover can then be assessed by whether the next recipient understands the status and action without unnecessary reconstruction.
The next opportunity need not be identical. Work rarely repeats under controlled conditions. A more complex handover may still let you test whether the distinction between evidence, action and decision is clearer. Notice what changed besides your approach, including the recipient's experience, the time available and the stakes. If the next handover goes well, you have a useful observation, though not yet proof that the adjustment alone caused it.
Sometimes the first adjustment is too narrow. A clearer note may still leave the recipient unable to act because the decision owner was never agreed. That result suggests a different issue to examine. Learning is more useful when it can change your interpretation, not just confirm the original plan.
Decide what improvement the evidence supports
Professional development is a stronger claim when an improved method works across more than one suitable situation. Keep a brief record of the initial difficulty or opportunity, the change you made, feedback from people who used the work, and what happened in later attempts. This helps distinguish a new habit from a single favourable outcome.
The evidence may support a modest conclusion: your handovers now identify open evidence and next actions more consistently, or colleagues need fewer clarifying exchanges in comparable cases. It may also show that the approach works with one audience but needs adaptation for another. A changed context does not by itself show that your ability has failed; it provides information about where the method transfers and where further judgement is needed.
You can use such examples in a development conversation because they show more than attendance or repetition. They show a point of judgement, an observed effect, a deliberate change and an honest assessment of its limits. Over time, ordinary work becomes a source of better decisions when each relevant experience informs the next one.
