A proposal can make complete sense within your own work and still leave a colleague unsure whether to support it. You may need information earlier, access to specialist time or a change in the way another team handles a request. The need is clear to you because you encounter its consequences. Someone responsible for a different part of the work has to judge the proposal alongside commitments you may see only in part.
This is a familiar challenge for specialists and project contributors who depend on colleagues they do not manage. Explaining your requirement accurately is a useful beginning. To make a case for action, you also need to show what the proposed change would mean for the people affected: which difficulties it would reduce, which decisions it would improve and which costs it would create. Those consequences give colleagues a basis for assessing the proposal through their own responsibilities.
A shared consequence does not have to be a benefit to everyone. Sometimes a worthwhile change asks one team to carry more work so that another can avoid a larger problem. Credible influence involves making that exchange visible and open to examination. You can develop a stronger proposal by explaining the connections, testing them with colleagues and being willing to revise the recommendation when their information changes the case.
Trace the consequences beyond your own requirement
Begin with the work that would change if the proposal were accepted. A statement such as “we need earlier notice” identifies a request but leaves its practical value uncertain. Explain what you would be able to do with the additional time, what currently happens without it and who encounters the next consequence. This allows someone outside your function to assess the relationship between the requested action and the benefit you expect.
Consider a specialist proposing earlier notice of planned packaging changes. In this example, some changes reach the people preparing production schedules only after those schedules have been arranged. The specialist has seen repeated revisions and wants a deadline for receiving change information. A case built solely around reducing those revisions may appear to solve the specialist's inconvenience while transferring pressure to customer-facing colleagues who are still clarifying what is wanted.
The explanation becomes more useful when it follows the work. Earlier information might allow the people responsible for scheduling to identify affected production runs before committing available time. It might also allow the colleagues responsible for specifications to identify missing details while there is still time to resolve them. Where those dependencies apply, the benefit is more than an earlier email: the relevant people gain an opportunity to make decisions before later work depends on them.
Each connection needs a sound basis. You may have records showing when information arrived and when schedules changed. Those records can establish sequence, but the cause of each revision still needs examination. Some revisions might have followed equipment availability or a change in demand. If the proposal attributes all disruption to late packaging information, colleagues can reasonably challenge its value. Separate the cases that support your explanation from those caused by something else.
Make the decision you want to improve explicit. A colleague may need to decide whether to reserve production time, seek further information or defer a commitment. Explain how the proposal would help that decision and what would remain uncertain. Earlier notice of an intention is different from an approved specification ready for use. Keeping that distinction clear prevents enthusiasm for advance information from creating confidence that the information does not yet justify.
The amount of detail should reflect what the recipient needs to assess. Someone familiar with the affected work may need only a short explanation of the dependency. A colleague further from it may need the sequence set out. The aim is to make the causal reasoning accessible without assuming that everyone shares your knowledge or requiring them to learn the whole of your function.
Include the costs that other people would carry
A proposal is incomplete if it explains its benefits while leaving other people to discover the extra work. Consider how accepting it would affect existing commitments, and compare those effects with the current arrangement. A change that saves your team time may still deserve support, but the case becomes more defensible when it acknowledges who would provide the information, absorb a delay or set aside another task.
In the packaging example, an earlier deadline could require customer-facing colleagues to obtain decisions before their customers are ready to make them. It could also encourage provisional details to be circulated as though they were settled. Those are material objections because they concern whether the proposed process would work. Repeating the cost of schedule revisions will not resolve them. You need to understand whether the deadline is feasible and whether the information available at that point would support the decisions you have described.
There may be a better option than moving every deadline. An early notification of a likely change could allow an initial assessment of the affected work, followed by confirmed information through the existing approval process. That option has costs of its own. Someone would have to keep the provisional status clear, update the notification and avoid treating every possibility as a firm commitment. A two-stage arrangement is worth proposing only if that work buys useful preparation rather than a second stream of information that people struggle to maintain.
Consequences can also fall at different times. Making a change sooner might protect a future production commitment while leaving less time to use existing packaging stock. Delaying it might reduce that stock exposure while affecting another legitimate objective. Where such effects are relevant, state them openly. A broad phrase such as “better for the business” cannot establish how these consequences should be weighed or who is authorised to decide between them.
Give uncertain estimates an honest form. If the available examples suggest that earlier information could reduce repeated scheduling work, explain the basis and limits of that expectation. Do not turn a few difficult cases into a precise saving for every change. Colleagues may accept a provisional estimate when they can see how it was formed; false precision makes it harder to distinguish evidence from advocacy.
Some requirements remain conditions of an acceptable option. Required approval, necessary technical information and relevant controls cannot be traded away merely because a different arrangement would be convenient. Establish those boundaries before comparing discretionary choices. Within them, a recommendation may still favour one objective over another. You can acknowledge a colleague's legitimate cost and recommend the proposal, provided the reasoning for that judgement is explicit.
Let colleagues test and improve the proposal
The people affected by a proposal can reveal weaknesses that are difficult to see from your own work. Involving them while the recommendation can still change gives their knowledge a practical purpose. Bring a clear initial explanation of the problem and the option you are considering, then invite them to examine the dependencies on which it rests.
For the packaging proposal, you could ask a colleague responsible for customer communication: “At what point would you have enough information to notify us of a likely change, and what would still be unresolved?” This is suggested wording for a working discussion. It directs attention to the information that might support early preparation, while leaving room for the colleague to explain why a proposed date would be premature. The response may reveal that a different event, rather than a fixed number of days, offers a more useful trigger.
An objection should lead you towards the assumption it challenges. If the colleague says that customer decisions regularly change after early notice, establish which preparation would remain useful despite that uncertainty. Identifying the affected product might help colleagues estimate the work involved, while reserving a firm production slot could be unjustified. If almost all preparation would have to be repeated, the case for early notification is weaker. Your recommendation should be able to change with that information.
Give the same scrutiny to your own evidence. A colleague might show that schedule revisions continue even when packaging details arrive early because a separate approval is delayed. That would alter the proposed remedy. A stronger message about deadlines would leave the dependency untouched; attention may need to move to the information or decision holding up approval. Recognising this is useful professional progress, even if it means withdrawing your original proposal.
Keep discussions proportionate. A routine request to move a short meeting may need little more than an explanation of the clash, a feasible alternative and confirmation from the people affected. A change to how several functions exchange information needs more examination because each participant may act on what another supplies. The depth of preparation should follow the consequences of being wrong, the uncertainty and the effort being requested.
Collaboration improves the case without settling every decision. A colleague can confirm that an approach is workable while lacking authority to commit resources or approve a change. Record what their input actually establishes. Equally, avoid presenting a conversation as their endorsement if they only supplied information. Accurate representation of other people's contributions helps preserve the trust on which future cooperation depends.
Ask for a decision proportionate to the evidence
A developed explanation should lead to a clear request. State what you recommend, why the expected benefit justifies the identified costs and what action is now needed. The recipient should be able to tell whether you are asking for information, support in developing an option, a resource commitment or formal approval. General agreement that the problem matters can otherwise leave the work in much the same position.
For the packaging example, the evidence might support a limited trial of early notifications for a defined set of changes. Such a trial would still need the relevant approval and suitable boundaries. Explain who would send and update the notifications, how provisional information would be distinguished from confirmed information, and which decisions would continue to follow existing controls. The proposal should make clear what the trial is intended to establish before anyone takes on the work.
Assess the result against the expected effect. If the aim is to allow earlier preparation and reduce avoidable schedule revisions, receiving more notifications is only evidence that the new activity happened. Review whether usable information arrived before the relevant decisions, whether colleagues could act on it and whether the additional work was justified. Notice any burden moved elsewhere, including repeated updates or effort spent preparing changes that did not proceed. A trial can be informative even when its result argues against wider adoption.
A trial will not always be appropriate. Some uncertainties need to be resolved before work begins, and some conflicts require a decision by someone with the necessary authority. If the people involved cannot reconcile the competing commitments, present the options, consequences and remaining disagreement through the appropriate route. The value of your earlier work is that it gives the decision-maker an intelligible choice, with the reasons for disagreement visible. Urgent concerns should follow the relevant immediate response arrangements rather than wait for a proposal-development exercise.
Once a decision is made, confirm the commitments that follow and do your part. If the proposal is declined, seek enough explanation to understand whether the issue was the evidence, the timing, the available capacity or the underlying objective. That distinction helps you judge whether to improve the proposal, revisit it when conditions change or stop pursuing an option that no longer deserves the effort.
Influence across teams develops through this willingness to make your reasoning available for examination. Colleagues can see the problem you are trying to solve, the effects you have considered and the conditions that would change your judgement. Agreement remains their decision where they hold that authority. Your professional contribution is a proposal they can assess responsibly, and a recommendation you can support without concealing its costs or overstating its promise.
