Build credibility through visible follow-through
Choose commitments you can complete and communicate early when a dependency changes. Colleagues form expectations from repeated behaviour. Technical expertise can help, but reliability also means explaining uncertainty and acknowledging when another person has relevant knowledge. Start by examining where your everyday actions make it easier or harder for others to trust your requests.
Understand who needs to be involved
A cross-functional problem often has several owners. Identify who does the work, who makes the decision and who is affected. Ask about their priorities before presenting your preferred solution. Relationships are easier to build through ordinary cooperation than through urgent requests made only when a project is already in trouble.
Frame a request around shared value
Explain the problem, the benefit and a realistic next step. Be specific about the effort required and any trade-off. “Could we test this handover checklist for one week?” is easier to consider than a broad demand to change how another department works. Make it possible for colleagues to raise concerns or suggest an alternative.
Choose an improvement you can responsibly influence
Start with a manageable issue inside your remit. Seek the appropriate approval where the change affects policy, systems, spending or other teams. Record what you expect to improve and what evidence you will review. A small, well-supported experiment can demonstrate initiative without creating confusion about accountability.
Worked example: Improving a handover without becoming the boss
An analyst notices recurring questions between two teams. She asks both groups what information is missing, drafts a short checklist and seeks the process owner’s agreement to a trial. The request is limited, the owner remains clear and the review date is agreed. Her influence comes from understanding the problem and making cooperation easier.
Put it into practice
- Review the commitments that build your credibility.
- Map the decision owner and affected colleagues.
- Make one specific request around shared value.
- Agree approval, scope and a review date.