Experience can be substantial and still be difficult for someone in another function to assess. Your colleagues may understand what managing a corrective-action programme, planning production or supporting a product launch involved. A manager considering you for different work may recognise the activity without seeing the judgement, coordination or analysis you contributed. An accurate account of your previous duties can therefore leave much of your capability unexplained.
For an experienced specialist or a professional changing function mid-career, this creates a particular challenge. You want previous work to count, while accepting that it took place in a different context. Describing everything in your old function's language can make the connection hard to see. Replacing that language with broad claims about communication and problem-solving can remove the detail that made the experience credible in the first place.
A useful account connects what the work required, what you personally did and what happened afterwards to the demands of the possible new role. It gives the receiving manager enough evidence to judge the connection. It also helps you distinguish capability that may transfer from experience that would need further development before it could support a different responsibility.
Begin with the work the new function needs
The relevance of experience depends on the work it is being considered for. A statement about being good at analysis means little until the kind of analysis is clear. Investigating inconsistent records, evaluating a process change and forecasting demand may all involve information and judgement, but they require different subject knowledge and may support very different decisions.
Understand the destination role well enough to identify its important demands. A role description provides a starting point, while conversations with people doing or managing the work can clarify what the responsibilities involve. Look for the decisions the person makes, the evidence they use and the people whose contribution they need. These details help you select examples that bear on the work rather than relying on a shared word such as leadership or improvement.
Suppose an experienced Quality professional is considering a role involving operational improvement. Their experience of investigating recurring defects may be relevant where the new work requires testing explanations, gathering evidence across teams and following actions through. The connection becomes less convincing if it is described only as experience in Quality, or as a general ability to solve any operational problem. The receiving manager needs to see which part of the previous work supports which part of the new responsibility.
This preparation can reveal that a familiar example is less relevant than a quieter one. The largest project on your record may show specialist depth that the new role rarely uses. A smaller assignment may provide clearer evidence of coordinating work across functions or making a decision with incomplete information. Select for the capability that needs demonstrating, while retaining enough context to show the scale and difficulty of the work.
Explain what the experience demanded
A task label names an activity; it rarely reveals the reasoning required to carry it out. Managing corrective actions, for example, could include administering records, coordinating investigations, deciding what evidence is needed or checking whether an action addressed the cause. Those contributions are related, but they are not interchangeable. An account becomes more useful when the listener can see the work behind the label.
Consider a recurring packaging defect investigated with input from Quality, Production and Engineering. To explain your experience, establish what made the issue difficult. The available records might have been incomplete, different colleagues might have favoured different explanations, or earlier action might have failed to prevent recurrence. Include the difficulty that actually existed in your case. It gives the listener a basis for understanding why your actions required judgement.
Then explain how you approached that difficulty. If you compared records to test whether an apparent pattern held, identify the kind of comparison and what it helped establish. If you brought operators and engineers into the investigation, explain what knowledge each contributed and how their input changed the understanding of the issue. Naming the departments alone leaves the coordination work invisible.
A strong example contains a decision or change of understanding that can be examined. You may have found that the initial explanation did not account for all the evidence and asked for further investigation before an action was agreed. That is more informative than saying you challenged assumptions. It shows the basis of the challenge, its timing and the effect on the work. The explanation does not require a dramatic disagreement or a claim that you alone discovered the cause.
Keep technical terms where they preserve useful distinctions. Root-cause analysis, for instance, names an investigation into underlying causes rather than stopping at the immediate error. Explaining why that mattered in your example helps someone outside your original function understand the capability involved. Replacing every technical term with a general expression such as problem-solving can make the account less precise, while leaving unexplained acronyms to carry the argument can make it inaccessible.
The amount of detail should serve the recipient's decision. A brief account can establish the problem, your contribution and the evidence of its value. Further discussion can explore the methods and constraints. You do not need to reproduce the investigation record or disclose confidential information to explain your reasoning. Choose details that preserve the important relationships while respecting what can appropriately be shared.
Separate your contribution from the wider result
A team outcome can demonstrate useful experience without belonging entirely to one person. Your account needs to make your contribution visible within that shared work. If Engineering diagnosed a mechanical problem, Production organised access and you coordinated the evidence and follow-up, describe those responsibilities accurately. Claiming the whole result obscures the capability you can actually substantiate.
Verbs matter because they establish the level of responsibility. Contributing information, coordinating an investigation, recommending an action and approving a change involve different decisions. If you say that you led the work, be ready to explain what you organised, what you decided and where someone else's authority applied. A clear boundary can make a substantial contribution easier to appreciate: the listener can assess it without having to guess how much of the claim belongs to the wider team.
Coordination deserves explanation in its own right. Bringing the right expertise together, resolving gaps in information and ensuring that agreed work is followed through can require considerable judgement. There is no need to imply that you personally performed every technical task to make that work valuable. The relevant evidence might be how you identified a missing contribution, secured it and used it to move the investigation forward.
Describe the outcome at the strength the evidence supports. If defect levels fell after an action, explain the basis and period of the comparison where that information is available and appropriate to share. Consider whether changes in volume, product mix or reporting could affect the interpretation. A favourable result can support the account without proving that your contribution alone caused it or that the improvement will persist indefinitely.
Some valuable work produces no simple headline number. You might have made responsibilities explicit, prevented an unsupported conclusion from being accepted or enabled a decision by resolving contradictory information. Explain the change and why it mattered. Where a risk was reduced, distinguish evidence that a weakness was addressed from an unverifiable claim about the exact loss that would otherwise have occurred. Precision is more useful than inventing a saving because an achievement is expected to contain one.
An example with an imperfect outcome can still show capability, provided its limits are clear. Explain what worked, what did not and how the evidence changed your approach. That gives a receiving manager information about your judgement under difficulty. It should not turn a failure into a disguised triumph or erase a part of the work for which you were responsible.
Show where the capability could transfer
Once your contribution is clear, explain its proposed use in the new function. In the investigation example, testing explanations against evidence and coordinating specialist input may be relevant to improvement work. The connection rests on similar demands in the work, rather than the fact that both functions sometimes investigate problems.
Make that connection specific enough to assess. If the new role involves understanding variation in a process, experience of checking whether a reported defect pattern is supported by the records may offer a useful starting point. It does not establish familiarity with every analytical method or process involved. The receiving manager can then explore how you would apply the underlying reasoning and which technical knowledge would need to be learned.
A change in context can alter the difficulty of an apparently familiar task. You may have coordinated colleagues who already knew you and accepted your role in an investigation. In a new function, you may need to build those relationships and understand different priorities before obtaining the same cooperation. Likewise, a decision you previously recommended may be one you would now own. That brings a different responsibility even if the information looks familiar.
Your existing expertise can still have value beyond the most obviously transferable skill. A Quality background may help you recognise evidence gaps or consider the effect of a proposed change on product requirements. That perspective can contribute to improvement work while other colleagues supply process or engineering expertise. Explain the useful perspective without implying that one function sees all the consequences or that specialist knowledge automatically confers authority in another role.
Be explicit about the important gap. If you have experience coordinating an investigation but limited experience with a particular analytical technique, say what you have done and what you would need to develop. Where you have already completed relevant work under guidance, describe that evidence. A learning plan is useful context, but it does not become evidence of competence merely because it is well intentioned.
This can affect the kind of move that is credible. Your experience may support entry into a role with development and supervision, or a narrower initial remit, before it supports full autonomy. Whether that is worthwhile depends on your aims and circumstances. Making the distinction visible allows you to discuss the opportunity accurately without either claiming complete readiness or treating years of relevant judgement as having no value.
Test whether your account is understood
A useful test is whether someone familiar with the receiving function can identify the capability your example demonstrates. Share a concise account with an appropriate colleague, mentor or manager and ask what they understand you to have contributed. Their response can reveal where the explanation still depends on knowledge of your previous role.
If they repeat only the activity label, add the missing reasoning or decision. If they attribute technical work to you that someone else performed, correct the wording. If they understand your contribution but cannot see its relevance to the destination role, reconsider the connection or choose a different example. These are different problems, and making the same explanation more polished will not resolve all of them.
Prepare enough detail to answer follow-up questions without memorising a performance. An interviewer may want to know why you selected particular evidence, what alternative you considered or how you judged whether an action worked. Being able to explain those choices makes the account more useful than a rehearsed list of desirable attributes. Where you cannot remember or substantiate a detail, keep the claim within what you can support.
Use the same discipline in written material. A short statement can identify the relevant contribution and outcome, leaving room for fuller discussion later. It should still preserve the actor and level of responsibility. Compressing coordinated into delivered, or a team improvement into a personal achievement, changes the claim you are making rather than merely shortening the sentence.
The result should give both you and the receiving function a clearer basis for judgement. Your previous work becomes understandable through the decisions, evidence, relationships and consequences it involved. Its value can then be considered alongside the demands of the new role and the development still required. That is a stronger basis for a function change than expecting an old job title, a familiar acronym or a broad claim of transferability to do the explaining.
