As your work extends across teams, you discover colleagues who can explain how a decision developed, identify the person with relevant experience or anticipate a practical difficulty that a formal proposal has missed. Their value may have little connection with their position on the organisation chart. Learning who can help you understand the work is part of becoming effective in a wider professional role.
These relationships can make coordination more informed and less laborious. They can also create confusion when a helpful conversation is treated as permission, an influential person's preference becomes an assumed instruction or the people responsible for a decision learn about it after others have started acting.
For a cross-functional specialist, aspiring manager or established professional taking on broader responsibilities, the aim is to use organisational knowledge without making accountability harder to see. You can consult widely, build support and learn from practical experience while remaining clear about who is authorised to decide and what has actually been agreed.
Recognise the different ways people contribute
A colleague can be important to a piece of work for several reasons. They may understand its history, possess specialist knowledge, coordinate the people involved or hold the authority needed for a decision. Those contributions can overlap, but knowing that someone is useful does not tell you which contribution they are making.
An experienced colleague may explain why an earlier proposal was abandoned. That history can help you avoid repeating an error or show that circumstances have changed enough to reconsider it. Their recollection is useful context; it still needs to be checked where the detail materially affects your conclusion. Long service gives someone access to experience, not an automatic guarantee that every remembered condition remains current.
Influence has a different function. A respected specialist may help others understand the significance of an issue or draw attention to a proposal that deserves consideration. Their support can improve the discussion without giving them authority to commit resources or approve an action. Treating influence as approval can leave both the specialist and the eventual decision-maker misrepresented.
Authority concerns the decisions a person is permitted to make within a defined scope. It may be held by a manager, delegated to a specialist or assigned through a particular process. The person with the most knowledge may also be the authorised decision-maker, but that combination needs to be established in the actual organisation.
When entering unfamiliar work, learn these relationships through the task you are trying to complete. Identify the expertise needed to understand it, the people affected by it and the decision that remains to be made. This gives you a more useful starting point than trying to classify everyone as powerful, supportive or obstructive.
Use early conversations to improve the work
Informal consultation is especially useful while a proposal is still being developed. A brief conversation with someone who performs the affected work may expose an assumption that would otherwise survive into a formal discussion. They may know where information is unreliable, what a previous attempt overlooked or which colleague should be involved next.
Give the conversation a clear purpose. Explain the issue you are exploring, what you currently understand and where you need help. Make its status clear if no decision has been made. People can then contribute knowledge without having to guess whether you are seeking advice, asking them to commit time or announcing an agreed change.
Listen for information that would alter your approach. Consultation has limited value if it is only a search for endorsement of a finished position. Where someone identifies a difficulty, establish what causes it and whether the proposal can address it. A practical objection may improve the work even when it initially slows progress.
Different accounts may reflect different parts of the organisation. Someone who prepares information can experience a task differently from the person who uses it later. Explore that difference before deciding which account is correct. You may need both perspectives to understand why a hand-off fails or why apparently complete information is difficult to use.
There is a boundary between gathering relevant perspectives and repeatedly approaching people until someone gives the preferred answer. If an earlier reviewer identified a material concern, carry it into the next discussion. Explain what has changed or why you think the concern can be resolved. Quietly dropping an inconvenient qualification makes subsequent agreement less reliable.
Respect the time and responsibilities of the people helping you. A focused request, enough context and a clear account of what you will do with the advice make it easier for them to contribute. Informal access should not become an unrecognised workload that repeatedly falls on the most approachable colleague.
Keep advice and approval distinct
The distinction becomes particularly important when professional advice feeds a formal decision. Consider a hypothetical supplier-assessment situation. You are preparing an assessment and speak with a colleague who has considerable experience of that supplier. They explain an earlier concern and suggest information that would help establish whether the concern remains relevant.
That conversation can improve your assessment. You can examine the information, explain its significance and make a more defensible recommendation. The colleague's practical knowledge has contributed to the work, even if they have no authority to approve the supplier.
If the colleague says the supplier appears suitable, establish the basis and limits of that view. It might be an informal opinion based on previous experience, a technical judgement about the evidence just discussed or a recommendation within their assigned responsibility. Those are different contributions. None should silently become the organisation's approval decision.
The actual decision belongs with the person or arrangement authorised for it, using the applicable evidence and criteria. If you are responsible for the assessment, present its conclusion accurately, including the colleague's material contribution and any unresolved limitation. If you also hold the decision authority, make that decision within your scope rather than treating the conversation itself as authorisation.
The same distinction applies beyond technical approval. A colleague may favour your project without being able to allocate their team's time. A manager may support an idea while needing another person's agreement before implementation. Establish the remaining decision and the conditions for proceeding before others begin to rely on the apparent agreement.
Formal authority does not remove the need for good evidence. An authorised person can still receive incomplete information or misunderstand the proposal. Useful organisational navigation improves what reaches that decision-maker and makes important qualifications visible. It should not be used to avoid scrutiny from someone likely to notice a weakness.
Make commitments clear to the people affected
A conversation can move from exploration towards agreement without anyone explicitly marking the change. One person leaves thinking that a possibility was discussed; another believes work has been authorised. Before acting on a consequential exchange, confirm the decision that was made, its scope and anything still required.
Suggested wording might be: "My understanding is that we can prepare the proposed approach, but implementation still needs approval once the resource implications are clear. Is that the position?" This gives the other person an opportunity to correct your interpretation. The value is accurate coordination, not creating a record that makes a tentative response look final.
Use the organisation's normal method for recording decisions where one applies. A brief written confirmation can also help people retain a shared understanding of responsibilities and conditions. The level of detail should reflect the consequence of misunderstanding. An exploratory conversation need not generate a formal record of every remark, while a commitment affecting several teams needs enough clarity for them to act consistently.
Pass on material conditions with the decision. If support depends on additional evidence, a limited scope or a later review, communicating only that someone agreed can change the meaning. Colleagues who were absent from the conversation need to know what they can rely on and what remains provisional.
Include the people who must implement or accommodate the decision at the point where their involvement matters. Early consultation may reveal a practical constraint; later communication may tell them what has been agreed and what action follows. Neither sending everyone every message nor keeping the work within a small circle guarantees effective coordination.
Confidentiality still applies. Share relevant information through appropriate channels with people who need it for their responsibilities. Using a relationship to obtain information you are not entitled to receive, or circulating another person's private comments to gain support, undermines the trust on which useful informal exchange depends.
When the decision process is unclear or stalled
Sometimes the difficulty is that nobody can identify the decision-maker, the usual person is unavailable or an approval repeatedly stalls without a clear reason. Informal relationships can help you understand the obstacle and find an appropriate route forward. They do not, by themselves, transfer the missing authority to whoever is willing to help.
Ask whether an authorised deputy, delegation or escalation arrangement applies. A colleague may be able to identify that arrangement or help you reach the right person. Confirm its scope before relying on it. Someone covering routine work during an absence may not have authority for every decision normally taken by the absent role holder.
Where responsibility is genuinely unclear, make the ambiguity explicit to a person able to resolve it. Describe the decision needed, the consequences of delay and any actions you can take within your existing remit. That creates a basis for allocating responsibility rather than allowing a convenient assumption to become an unofficial arrangement.
Urgency makes clear authority more consequential. Use the applicable route for urgent concerns and communicate material information promptly. Do not wait for a perfectly polished proposal where delay itself creates exposure. Equally, familiarity with a senior colleague is not a reason to invent an exception to the controls governing the work.
If an informal workaround is repeatedly needed, consider whether the underlying arrangement should be clarified or improved. A recurring dependence on one person's private contacts may keep work moving temporarily while leaving it vulnerable when that person is absent. You can raise the pattern and its consequences without claiming authority to redesign the organisation yourself.
Build relationships people can rely on
The long-term value of organisational knowledge depends partly on how you use it. Colleagues are better able to help when they can trust you to represent their advice accurately, preserve qualifications and return with the outcome where it matters. Credit their contribution without using their name to imply an endorsement they did not give.
Make the exchange reciprocal through useful work. Share relevant context, complete the actions you have accepted and help others understand your own area when appropriate. A relationship need not involve an immediate exchange of favours to be valuable. Dependable professional contribution gives people a reason to continue working together.
Build connections beyond the people who are easiest to approach. Different shifts, functions and levels of experience may hold knowledge that is missing from your usual conversations. Seeking those perspectives can improve the work and reduce dependence on a small group whose assumptions go untested. Access should broaden understanding rather than create a privileged route available only to insiders.
Keep your understanding current as roles, responsibilities and working arrangements change. A colleague who once approved a type of decision may now provide advice while someone else carries the authority. Checking the present arrangement is part of professional care, particularly when others will act on the result.
Effective informal relationships help you find knowledge, test ideas and coordinate work. Their professional value increases when the resulting decisions remain clear: who made them, what they cover and what others need to do. As your organisational scope grows, that combination lets you contribute more widely while remaining someone whose judgement and commitments colleagues can understand.
