Better conversations. Better decisions. Better work.   Independent practical guidance.
Leadership

Leading without authority: influence across teams

Win support across departments with shared outcomes, thoughtful proposals and realistic commitments.

Influence at work is easier when people see how your proposal helps them achieve something they already care about. Authority can demand attention; good influence earns cooperation.

In this guide

You’ll find a practical method, a realistic workplace example and a short checklist to try.

Begin with the other team’s priorities

Before requesting support, ask what that team is responsible for and what trade-offs they face. Marketing may value speed while compliance values evidence and risk control. Both have valid concerns. Reframe your proposal so it shows how those concerns will be handled instead of asking everyone to adopt your priorities.

Make requests specific and modest

“Can you help with this project?” is hard to accept. “Could you review a two-page proposal by Wednesday and flag any regulatory issues?” is easier to evaluate. Clarify how much time you are asking for and what people will receive. Give a genuine option to negotiate scope or timing rather than presenting an impossible yes-or-no choice.

Use small tests before big campaigns

Where uncertainty is high, propose a reversible pilot that generates evidence. A two-week trial can reveal operational problems more quickly than an elaborate presentation. Agree in advance what success means and what would cause the trial to stop. Be honest about what a pilot can and cannot prove.

Build relationships before you need favours

A reliable cross-functional partner shares useful information, credits others and does not disappear when their own work is complete. Schedule brief check-ins with important collaborators to understand their upcoming demands. Relationships built only during emergencies tend to feel transactional.

Close the loop visibly

After receiving help, explain what changed because of that contribution. Thank people accurately and share the result, including lessons from unsuccessful tests. This helps collaborators decide that working with you is worth their limited time next time.

An example from everyday work

You want the data team to prioritise a new dashboard. Instead of escalating, you show one concrete decision the dashboard will improve, offer to supply clean requirements and ask for a short discovery call. The smaller request earns a clearer answer and often a stronger design.

Put it into practice

Choose the actions that fit your role, responsibilities and the people involved. You do not need to implement everything at once.

  1. Ask one partner team what success looks like for them.
  2. Rewrite a vague request as a small, time-bounded contribution.
  3. Identify one low-risk experiment to test the idea.
  4. Share a short outcome note after receiving support.
Question to take away

What does the other person need to protect while helping me?

What to do next

Pick one change you can observe in the next week. Explain it to anyone affected, check whether it helped and adapt based on what you learn. For issues involving employment rights, workplace safety, discrimination, formal performance procedures or health, seek appropriate professional support and follow your organisation’s policies.

Further reading and sources

These external resources provide wider professional or official context. Our frameworks and examples are original interpretations rather than quotations from these publications.