Consider an experienced Quality specialist moving into Product Development. She understands how a manufacturing site assesses risk, how decisions travel between functions and why a product change needs careful review. She has yet to learn how this team develops a formulation, organises a production trial or decides whether an idea is ready to progress. Her experience is valuable, but it does not make those unfamiliar tasks hers to perform independently on day one.
That gap can feel surprisingly personal. Mid-career professionals are used to being the person others consult. In a new function, they may need to ask for explanations, have their work reviewed and accept less autonomy for a period. A sensible career decision depends on seeing the change accurately: some expertise must be built afresh, while judgement and knowledge gained elsewhere can still improve the work. Treating either side as the whole story makes the move harder to evaluate and the transition harder to manage.
A new function changes what expertise means
Competence is usually more specific than a job title or years of experience suggest. A person may understand the food-manufacturing system well, yet know little about the methods, evidence and daily decisions of a neighbouring function. Even where both teams work on the same product, they may approach it for different purposes. Familiarity with the organisation helps you find the right people and understand the consequence of a change. It does not establish that you can make every technical judgement in the new role.
The distinction matters because experienced professionals can make two opposite mistakes. One is to carry their old standing across as though it automatically authorises them to act. A Quality specialist who understands food safety review may have valuable questions about a new formulation. That does not make them the person who can design the formulation, conduct a production-equipment trial or approve the change under the organisation's arrangements. The other mistake is to behave as though every useful habit disappeared on transfer. Careful evidence reasoning, knowing when to involve others and noticing the effects of a decision on the wider site are real capabilities.
Professional judgement itself may travel better than a familiar answer. In the old role, experience may let you recognise a problem almost immediately. In the new one, the stronger use of judgement may be to slow down, identify which assumption needs checking and seek the relevant specialist's view. That can feel less impressive than supplying the answer. It is also a way of protecting the quality of work while your local knowledge develops.
The new team has a legitimate interest in knowing what you can do independently. Prior seniority may explain why you were offered the move, but colleagues still need a clear account of where you are learning. Stating that boundary is neither a confession of general incompetence nor a claim that earlier experience is irrelevant. It allows people to use what you bring without relying on expertise you have not yet acquired.
Identify the gap you would actually have to close
“I would be starting again” is too broad to support a decision. Before accepting a move, or early in it, look at the work you would actually be expected to do. Which decisions require knowledge you do not yet have? Which methods and evidence would you need to understand? What can be learned through guided work, and what calls for sustained practice before you should act without review? A named gap is easier to weigh than a general fear of losing competence.
For someone considering Product Development, the answer depends on the role. A position centred on coordinating trials has a different learning demand from one centred on formulation. An internal move may preserve knowledge of the site's products and working relationships while requiring new technical methods. An external move can add the need to learn another organisation's processes and authority arrangements. The advertisement or title alone is unlikely to settle these details. Discuss the likely first assignments, the decisions the person would make, and how their work would be reviewed.
There is a timing distinction too. Some knowledge is needed before a professional can contribute safely or credibly. Other capability develops through repeated work once the move has begun. A realistic transition identifies the boundary between them. If a new role assumes independent technical decisions from the first week, “you will learn as you go” may be an inadequate account of support. If the work starts with observation, bounded tasks and review, the same gap may be manageable.
The purpose of this assessment is not to remove every uncertainty before moving. It is to prevent a vague expectation that general experience will fill a specific technical gap. You may discover that the gap is narrower than you feared, or that the route to closing it is more demanding than the appealing title suggested. Either finding improves the choice.
Carry judgement across without claiming instant mastery
Previous experience becomes useful in a new function when it helps people understand the work more fully. A professional moving from Quality into Product Development may recognise that a proposed formulation change affects more than its intended product characteristic. They may know which site teams need to understand the change and what evidence will matter when the product is assessed. That awareness can help frame a trial or raise a concern at the right time. The development team still supplies its own methods and technical judgement; any formal approval remains with the people authorised under the site's arrangements.
The reverse move has a similar boundary. Someone from Product Development may understand why a trial was designed as it was and what a process change was intended to achieve. In Quality, that background can make their questions about evidence more informed. It does not let them skip learning the function's assessment methods or claim an approval they have not been delegated. Transfer works through contribution to the new task, not by treating two jobs that touch the same product as interchangeable.
Other portable capabilities may be less technical. An experienced professional may know how to bring a disagreement to a decision, explain uncertainty without hiding it, or follow an issue across several departments. Those habits can help a new team, especially when the work crosses functions. They need translation into the new setting. The fact that you once resolved an issue in Operations does not prove you know the best answer in Procurement; it may show that you know how to discover who has the evidence and authority that matter.
This is a stronger account of transferable value than a claim that “my skills apply everywhere”. It lets you explain where past experience gives you a useful starting point and where you need the new function's expertise. Colleagues can then test and build on your contribution. You keep the judgement you have earned by using it accurately, including when it tells you to seek review.
Plan for a period of lower fluency
Experienced people often feel pressure to look immediately capable in a new role. Concealing uncertainty can preserve that appearance for a short time while making work less dependable. A more useful approach is to agree the tasks you can take on now, the points at which someone should review your work and the decisions that remain outside your authority. These arrangements will differ by role and organisation, but the underlying purpose is practical: colleagues should know when they can rely on your independent judgement and when further expertise is needed.
Asking questions is part of that arrangement, though the quality of the question matters. “How does this trial work?” may be necessary at first. As you learn, more precise questions show progress: what decision will the trial support, what conditions must remain stable and who will interpret the result? You do not need to perform familiarity you lack. You do need to prepare, retain what you learn and apply it to the next piece of work.
The learning period also has a social dimension. In your old function, colleagues may have known what you could handle without explanation. In a new team, credibility has to be established in the work they see. Delivering a bounded task well, saying promptly when an assumption is uncertain and following through after feedback give colleagues evidence they can use. Prior reputation may open a door, but it cannot substitute for reliable contribution in the new context.
Lower fluency should be temporary in a meaningful sense, rather than a permanent excuse. If you repeatedly encounter the same gap, identify whether the learning method is working. Perhaps you need more exposure to a particular decision, a clearer explanation of the team's evidence or a chance to practise with review. Perhaps the role gives too little support for the responsibility it assigns. The response depends on the gap, not on an expectation that confidence alone will solve it.
Weigh the temporary cost against the direction you want
A function change can alter status, autonomy and the pace at which work feels satisfying. You may go from making decisions quickly to waiting for review. A title may stay the same while your day-to-day confidence falls, or a role may require a temporary step back in seniority. These are real costs. Calling them a “growth opportunity” does not tell you whether the trade-off is right for your circumstances.
Compare the transition with the work you hope to be doing after you become competent. Does the new function offer problems you genuinely want to work on, or is its appeal mainly that it is different from your present role? Is the gap one you have the time, support and interest to close? What existing capability would remain in use, and what might atrophy if the move takes you away from it? The answers may change with your career stage and commitments outside work. There is no professional virtue in accepting a poorly supported move merely to prove that you can tolerate uncertainty.
It also helps to distinguish a temporary learning cost from a role with no credible learning path. In the first case, expectations may be adjusted as your capability grows and you receive evidence that you are progressing. In the second, you may be assigned work beyond your competence while having little access to the people or experience needed to improve. The attraction of the destination does not make that arrangement sound. Clarifying support and decision boundaries before the move can reveal the difference.
Staying in your current function can be a considered decision rather than a failure of ambition. Deepening expertise, taking on a different kind of responsibility or working across an interface may meet the underlying career aim with a different cost. Conversely, remaining only because you dislike being temporarily less fluent may keep you in work you no longer want. The useful comparison concerns the actual options available to you, not a general rule that movement is always better than continuity.
Recognise progress by what you can now do
Comfort is one sign of adaptation, but it can be misleading. You may feel at ease because the new colleagues are helpful while still needing substantial review. Or you may continue to feel awkward even as your decisions become more reliable. Look instead at the work: can you explain the purpose of a task, judge the evidence relevant to it, recognise when to seek another view and carry a bounded decision through to a useful outcome?
Progress can also appear in how old and new knowledge combine. The former Quality specialist may begin to anticipate which product-development choices need early discussion with Production or a food-safety decision owner. That is more than remembering an old process. It shows growing understanding of the new work and the interfaces that shape it. The same professional should still be clear about decisions they are not authorised or ready to make.
As competence grows, revisit the career decision that led to the move. Does the work itself hold your interest now that you see it closely? Has the temporary reduction in autonomy begun to give way to capability you wanted? Are you contributing in a way that fits your own aims? A pivot need not be judged only by whether the first months feel successful. It should be judged by what you are learning, what you can increasingly do and whether that direction remains worth pursuing.
Changing function may make an experienced professional a beginner in some important tasks. It need not make them a beginner at judgement, evidence or understanding how an organisation works. The credible path is to name the new gap precisely, use previous capability where it genuinely helps and let the new function's expertise shape the work you have yet to learn. That gives you a more honest basis for both the career choice and the contribution you make while learning.
