Once you have become dependable in a specialist role, broader experience can look like the obvious next step. You want to understand more of the business, contribute to larger decisions or prepare for work that reaches beyond your current responsibilities. Yet the expertise you have built is also part of what makes you useful. Taking on unfamiliar assignments can create a reasonable concern: will a wider range of experience strengthen that expertise, or gradually replace it with superficial familiarity?
This matters particularly for established professionals considering cross-functional projects, lateral moves or broader roles. Your existing capability gives you something to contribute, but it can also shape what you notice. A technical specialist may understand the evidence behind a recommendation while knowing little about how that recommendation affects purchasing, scheduling or implementation. Broader understanding can improve the recommendation itself, as well as your ability to work with the people who act on it.
The aim is to build a combination of capabilities that supports the work you want to do. That involves choosing experience with a useful connection to your existing depth, learning enough to contribute honestly, and maintaining the work through which your strongest judgement continues to develop. A long list of assignments is less informative than a clear account of what those assignments have made you better able to understand and do.
Identify the capability you want to keep deepening
Professional depth is more than knowing a subject's terminology or having spent years in a role. It becomes visible when you can handle an unfamiliar case, distinguish strong evidence from a persuasive assertion, explain a difficult judgement and recognise when your usual approach will not work. Repeated exposure matters when it develops those abilities. Repeating familiar tasks indefinitely may keep you proficient without extending your judgement very far.
Start by identifying a capability that already gives your work value and that you want to develop further. It might be investigating recurring problems, assessing supplier evidence, designing workable processes or interpreting operational performance. Describe the capability through the work you can perform and the decisions you can support. A job title alone tells you little about which part of your expertise should remain central as your scope changes.
Evidence helps make this choice more reliable. Consider the difficult work that colleagues bring to you, feedback that recurs across different situations, and problems you can now handle that previously required substantial help. These observations reveal strengths more usefully than a general belief that you are good at a subject. They can also expose a narrow base: perhaps you know one site's processes extremely well but have had little opportunity to test your reasoning elsewhere.
The capability you choose as an anchor need not define the rest of your career. It provides a basis for the next period of development. An experienced specialist may want deeper technical mastery; another may want to use technical judgement within broader commercial or operational decisions. Both can develop breadth, although they will need different experiences and different amounts of continuing specialist practice.
Broader experience should improve your existing judgement
Useful breadth gives you access to relationships or decisions that your present work leaves partly hidden. The connection may lie in what happens before your contribution, how another function uses it, or what happens after someone acts on it. Understanding that connection can change what you investigate, how you present a recommendation and which consequences you consider.
For example, an experienced supplier-assurance professional might join Procurement and Planning in reviewing recurring delivery difficulties. Their established strength is assessing supplier and material evidence. The broader work gives them a closer view of how supply reliability affects schedules and how purchasing decisions respond to operational constraints. In an agreed role, they could contribute the technical assessment while learning why a recommendation that appears straightforward from one perspective creates difficulty from another.
That experience becomes valuable when the professional can connect the information. Delivery problems might prompt a closer examination of whether the material received is consistent with the information previously assessed, or whether a reported change needs further investigation. Understanding the planning consequences might also help them explain the timing and implications of a technical concern. Commercial pressure remains a consideration to understand; it does not make unsupported technical conclusions more defensible.
Compare this with attending unrelated meetings without a defined contribution. Attendance may provide useful orientation, especially at the beginning, but continued exposure needs something more to build capability. You need enough involvement to understand why decisions are made and enough feedback to discover where your interpretation is incomplete.
Adjacency is therefore a useful starting point. Look for work close enough to your existing capability that you can contribute, but different enough to reveal a limitation in your current understanding. An investigation specialist might follow an issue into implementation and review. An engineer might learn more about how maintenance decisions affect production planning. The purpose is to make your judgement better informed, rather than to acquire a little knowledge of every department.
More distant experience can still be worthwhile, particularly if you are testing a different career direction. Its value should be explicit. A move away from your current specialism may build a new capability rather than deepen the old one, and maintaining both at the same level may be unrealistic. Recognising that trade-off makes the decision more deliberate.
Different work requires different levels of expertise
Broader work does not require equal depth in every subject. Often you need enough understanding to collaborate effectively: to recognise another function's constraints, ask informed questions and know when specialist advice is necessary. This is a useful capability in its own right. It makes communication more accurate and reduces the chance of proposing actions that overlook essential conditions.
Some work requires a greater level of competence. You may need to apply a method independently within a defined scope, with clear limits and a route for review when a case becomes unfamiliar. Specialist judgement extends further, including the ability to assess exceptions and challenge the assumptions behind the method. Moving between these levels takes more than learning the vocabulary.
In the supplier-assurance example, understanding how Planning evaluates schedule disruption can improve the professional's contribution to a review. It does not establish that they can independently redesign the production schedule. Equally, a colleague's familiarity with supplier-assurance discussions does not establish that they can make every technical assessment. Each person can broaden their understanding while continuing to rely on another's deeper capability.
Make these limits visible through the way you work. State which part of an assignment you can undertake, which conclusions need expert review and which decisions belong elsewhere. Where a new assignment changes your responsibilities, clarify the authority attached to it. Participation in a cross-functional project does not automatically confer the right to approve another function's decisions.
This clarity protects learning as well as credibility. If you pretend to possess expertise you are still developing, colleagues may assume you need no support. You lose opportunities to test your reasoning and expose errors before they matter. Conversely, treating everything outside your specialism as someone else's concern can prevent useful development. A bounded contribution allows you to stretch while keeping the quality of the work and the need for support clear.
Exposure becomes capability through application and feedback
An experience has to change how you work if it is to become part of your capability. Preparation helps you notice the right details. Before joining a project or review, identify a specific limitation in your understanding: perhaps you cannot explain why your recommendations are difficult to implement, or you lack experience of weighing alternatives when information is incomplete. This gives your participation a learning purpose beyond being present.
Seek a contribution that allows you to encounter that limitation. Preparing part of an assessment, comparing options or following an agreed action through implementation can reveal more than listening to a discussion from the edge. The contribution should fit your competence and the support available. Taking on an uncontrolled high-consequence decision is a poor substitute for a well-designed development opportunity.
Feedback then connects participation to learning. Discuss your reasoning with someone who understands the work: what did you notice, what did you miss, and why did they interpret the situation differently? Asking for an explanation of a particular decision usually produces more useful insight than requesting a general opinion on whether you did well. Follow the consequences where practical, so you can compare the assumptions made at the time with what subsequently happened.
Returning to the supplier review, the professional might discover that their technical report gives a conclusion but leaves the timing of further information unclear. Planning consequently cannot tell whether a decision can be made before a scheduled requirement. A colleague's feedback could help the professional improve the report by distinguishing what is established, what remains to be checked and when the next update is expected. The underlying technical judgement remains intact; the information becomes more useful to the people depending on it.
Apply the learning in your ordinary work afterwards. A better report, a more focused investigation or earlier recognition of a dependency is evidence that the exposure has been integrated. If every lesson remains attached to one project and never changes your wider practice, the connection is still weak. You may need another opportunity to apply it, a more challenging task or feedback on how to transfer it.
Keep a short account of the decisions or contributions that changed. This makes development easier to discuss with a manager and helps you choose what to do next. Preserve confidentiality and give colleagues credit for their part. The useful record explains your reasoning and learning; it need not claim sole responsibility for a team outcome.
Make room for depth as your scope grows
Broader responsibility competes for the time that previously supported specialist work. Meetings, coordination and unfamiliar assignments can gradually displace difficult cases, technical discussion and sustained practice. If that happens without a deliberate choice, you may retain a specialist reputation while becoming less able to exercise the judgement that earned it.
Decide what continuing engagement your anchor capability needs. This might involve retaining responsibility for selected complex work, reviewing challenging cases with experienced colleagues or applying new learning to live problems. Reading can help maintain knowledge, but it may not replace the practice needed to make difficult judgements. The appropriate balance depends on the capability and the direction you are pursuing; there is no useful universal percentage of time to allocate to breadth and depth.
Discuss capacity with your manager before assuming that development can be added indefinitely. Explain the capability you want to build, the work through which you could build it and what may need to be reassigned or delayed. Your manager has legitimate delivery responsibilities. A proposal is easier to assess when the contribution, support requirement and effect on current commitments are visible.
The host function has interests too. Its colleagues need useful work and may have limited time to supervise someone learning their area. Agree a bounded task and a workable feedback arrangement rather than asking for indefinite access. A reciprocal arrangement might let you contribute an assessment while another professional explains how it informs their decision. Neither person has to become the other's unpaid tutor or absorb an unlimited additional workload.
Opportunities will sometimes be restricted. A small team may be unable to release you; another function may have no suitable project at that point. A narrower piece of work, an authorised review of a completed decision or an explanation from a colleague may still improve your understanding. If repeated attempts produce little access, that is relevant evidence about what the current role can offer. You can consider a lateral move or another setting without treating an employer's limitations as a personal failure to be sufficiently proactive.
Signs that the balance needs attention include repeatedly relying on outdated assumptions, avoiding specialist cases you previously handled or receiving feedback that your analysis has become less thorough. Examine the cause before responding. A demanding transition may temporarily reduce fluency; prolonged disengagement may require a different allocation of work. Reclaiming depth or deliberately moving towards a broader role are both possible responses, depending on what you want to become able to do.
Progress is visible in the work you can now do
Review breadth and depth together. You should be able to explain both the capability that continues to deepen and the wider understanding that makes it more useful. A meaningful change might be recognising a dependency earlier, evaluating an option with better information or helping colleagues act on your work more accurately. These changes say more about development than the number of functions you have encountered.
Look for evidence across more than one favourable episode. Can you apply the learning in a different situation? Do colleagues see an improvement in the quality of your contribution? Can you explain the limits of what you now know? A successful project can support a claim about the work you performed, but it does not automatically establish competence across every subject the project involved.
This also improves how you describe your experience. Distinguish contributing to a review, preparing an assessment and holding authority for a decision. Explain what you learned and where you applied it. A credible account of a bounded contribution is stronger than a broad claim that cannot withstand questions about your actual responsibility.
The review may support continued specialisation with a better understanding of the surrounding business. It may reveal that you enjoy connecting functions and want a role with greater coordinating responsibility. It may also show that the broader work interests you less than expected. Learning about fit is valuable even when it changes the original plan.
If a different direction repeatedly proves more attractive, reconsider which capability should become your anchor. You may retain earlier expertise as supporting knowledge while building depth elsewhere. Make that transition deliberately, allowing for the practice and support the new work requires. You do not have to preserve every former strength at its previous level to justify moving on.
Broadening works best when you can trace the connection between experience and capability. Choose wider work that reveals something important, contribute at an honest level of competence, and bring the learning back into decisions you can explain. Continued depth gives that breadth substance; broader understanding gives your depth a wider field of useful application.
