How to Lead without Authority at Work

How to lead without authority at work depends on what each person needs and who holds each decision. Offer the people whose work you need something they value. Make each ask specific, with an owner and a date, and keep decisions where everyone can see them. Take a decision you can't make to the person who holds it.

You're responsible for a project or a change that needs work from people in other teams. None of them report to you, and each takes priorities from their own manager. Some of the decisions the work needs belong to people more senior than you.

What Does Leading without Authority at Work Mean?

Leading without authority is getting work done through people who don't report to you when the result is your responsibility. Those people can include colleagues in other teams, people more senior than you, and your own manager.

People who run projects across teams call this having all the responsibility and none of the authority. To handle responsibility without authority at work, list the outcomes you answer for, the decisions each one needs, and the person who holds each decision.

How Is Influence Different from Authority at Work?

Authority is the right your role gives you to make a decision or assign work. Influence is what gets someone to act on a request they're free to turn down.

David Krackhardt and Jeffrey Hanson wrote that much of a company's real work happens despite its formal structure (Krackhardt and Hanson, 1993, Harvard Business Review). They pointed to the informal networks of relationships people form across functions and divisions to get tasks done fast. These networks can restart stalled initiatives. They can also block communication and build opposition to change.

To see the difference between authority and influence at work on your own project, write down who people consult before a decision and whose agreement others wait for, and compare that list with the org chart. When you need to get things done in a hierarchical organization, find out who has to agree before a decision reaches the person who formally approves it, and talk to them first.

To build influence at work without a title, spot problems early, translate between executives and frontline teams, and write down how the work depends on other teams and why past decisions were made.

How Do You Get People to Help When You're Not in Charge?

Allan Cohen and David Bradford treat getting help from someone you have no authority over as an exchange (Cohen and Bradford, 2005, Journal of Organizational Excellence). You offer something the other person values in return for what you need. They call the things people value currencies, and they group them into five kinds, related to inspiration, the task, a person's position, relationships, and the person themselves. Examples include help with someone's work, information, recognition, and gratitude.

They wrote that much of what a person cares about at work is shaped by organizational forces, such as how they're measured and rewarded and what their manager and peers expect. Ask the person what they care about in their work. If you can't ask, look at what they're measured on and what their manager expects of them, and offer something that helps with it.

Cohen and Bradford also advised making relationships before you need them. In weeks when you need nothing from anyone, build allies at work by sharing information that helps people with their work and asking about what's blocking them.

To get teams to cooperate when none report to you, talk to each team lead one on one before the group meeting. Ask what they need from you and what would stop their team from doing its part. Use the group meeting to confirm the order of the work and the dates.

Which Influence Tactics Work without Authority?

Gary Yukl and J. Bruce Tracey asked the subordinates, peers and bosses of managers in five large companies how often each manager used nine influence tactics, and how often those attempts led to their full commitment to the task (Yukl and Tracey, 1992, Journal of Applied Psychology). Three tactics went with more commitment from all three groups.

• Rational persuasion. Logical arguments and facts that show a request can be done and is likely to meet the task's objectives.

• Inspirational appeal. Connecting the request to the person's values and ideals.

• Consultation. Asking the person to help plan how the work will be done.

Pressure, such as threats, went with less commitment from subordinates and peers. Legitimating, which means showing that a request falls within your authority or the organization's rules, went with less commitment from peers. Getting other people to back a request didn't go with more commitment from any of the three groups.

Rational persuasion also went with higher ratings of a manager's effectiveness from their boss. The authors suggested that link may come from how expert the manager seemed, since using reasons and facts skillfully takes considerable expertise. The researchers measured the tactics managers already used and didn't change them, so the study can't show that a tactic caused the commitment. The authors called for caution in offering guidelines until other research confirmed the results.

Before you ask a peer for help, write down the reason and the facts behind the ask, how it connects to something they care about, and one question about how they'd do their part. Leave out "my director wants this" as the reason, since it rests the request on another person's backing. Use the same three things when you want to get people to listen to you at work about a problem or an idea.

How Do You Lead a Project When You're Not the Manager?

A project can stall for several reasons when the people doing the work don't report to you. Some come from gaps in how the work is coordinated, such as a decision nobody owns, no agreed order for the tasks, a task people agreed to and haven't started, and a problem someone can see and hasn't raised.

To lead a project without authority, name each decision and the person who owns it, and keep each ask small enough to finish this week. Write down who does what by when and in what order, where everyone on the project can see it. Put your own part in the same agreement, and meet your own dates. Check in once between the agreement and each deadline, so a slipping date shows up while there's still time to change the plan.

If your RACI chart isn't working, check that the person marked accountable for each task holds the decision or budget the task needs, and add a date and the order of the work to each line.

When people want different things from the project, align the stakeholders on your project by asking each one what they need, noting where their goals overlap and where they conflict, and taking each conflict to the person who sets priorities for both sides.

When a sponsor asks for a date the team can't meet, negotiate the project timeline with options and what each one costs, such as a smaller scope by the same date or the full scope at a later date.

How Do You Raise a Project Risk with Stakeholders?

As soon as you can see a risk, send it to the person who can decide what to do about it. When you communicate project risk to stakeholders, say what could happen and when, what it would cost the project, the decision you need, and the options with your recommendation.

When the risk starts as a complaint from the team, such as "this process doesn't work," translate between executives and frontline teams by naming where the work is waiting and how much time that adds.

If the person decides to accept the risk, document the project decision with the date and the name of the person who made it, in a log the whole project can read.

How Do You Get a Team to Adopt a New Tool or Process?

Katherine Klein and Andrew Knight wrote that a key reason organizations don't get the benefits of something new they adopt is failed implementation, which they describe as failing to gain skilled, consistent and committed use from the employees expected to use it (Klein and Knight, 2005, Current Directions in Psychological Science). The conditions they describe as making implementation more likely include a workplace climate that supports using the new tool, support from management, enough money, and an organization that values learning.

If you've been asked to drive adoption of a new tool without authority, list what the rollout needs that you don't control, such as management support, money for training, and time set aside to learn the tool, and ask your sponsor for each one.

Klein and Joann Sorra proposed that how consistently and well people use something new depends on the climate for using it and on how well it fits the users' values (Klein and Sorra, 1996, Academy of Management Review). In their model, people's responses can range from resistance and avoidance to compliance and commitment. To get developers to follow Scrum, ask them which parts of the process conflict with how they think good work gets done and which cost them time without helping the work, and change those parts with the team.

If the change hasn't been approved yet, the first job is getting stakeholder buy-in without authority from the people whose approval or resources it needs. When a rollout stalls, list the steps that didn't happen and the specific objections people raised, because change initiatives fail for several reasons and the fix depends on which one you're facing.

How Do You Manage Up When You Lead without Authority?

John Gabarro and John Kotter described the relationship with your boss as one of mutual dependence (Gabarro and Kotter, 1980, reprinted 2005, Harvard Business Review). Your boss needs cooperation, reliability and honesty from you. You rely on your boss for connections to the rest of the organization, for priorities, and for resources. They advised understanding your boss's strengths, weaknesses, work style and needs, and your own, and agreeing on clear expectations with each other.

To manage up without overstepping, bring your manager what you're seeing, your recommendation and the options you weighed, and leave the decision with them. Raise a problem or a disagreement with them before anyone above them hears it.

If you want to get pulled into decisions earlier, add what you've learned and your recommendation to each status update.

When Should You Escalate a Problem You Can't Fix Yourself?

Escalate when fixing the problem needs a decision or a resource that someone with more authority controls, and waiting is adding cost, such as a missed deadline or work that will have to be redone. Before that, make one specific request to the person who can act, with what you need, the date you need it by, and something you can offer them.

When you escalate a problem at work, say what's at risk and by when, what you need from the person you're escalating to, and what you've already tried. Tell your own manager before it goes.

To escalate at work without harming the relationship, keep the message about the blocked work, and tell the colleague involved which decision you're raising and with whom before you send it.

Before you escalate a teammate who isn't delivering, talk to them, ask what's in the way, and agree on a new date. If that date passes and the delay is costing the project, go to the person who assigns their work.

How Do You Make Coordination Work Visible?

Susan Leigh Star and Anselm Strauss argued that no work is visible or invisible in itself (Star and Strauss, 1999, Computer Supported Cooperative Work). Whether people see it depends on the cues they use to judge it, and those cues change with the setting. Work done in the background is one of the kinds of invisible work they discuss.

Coordination work includes work done in the background, such as noticing two teams booked for the same week or preparing the options for a decision before a meeting. To make your invisible work visible, name that work in your updates. Say what you caught, what you did about it, and what it kept on schedule.

When you describe your role in a performance review, use those updates to show why coordination work counts as strategic work, with the dependencies you tracked and the teams you connected.

If you're asking whether AI will replace project managers, list the coordination tasks you did last month. Mark which ones a tool your organization already uses could do today, and which needed a conversation or a decision from a person.

How Do You Lead as a Tech Lead without Authority?

When you're promoted to tech lead and the engineers report to someone else, ask your manager which technical decisions are yours to make, which ones you recommend, and who decides the rest. Tell the team what you agreed. Before you make a technical decision, ask the engineers who will build it how they'd do it.

If you're weighing whether to step down as tech lead and go back to coding, list the parts of the role you'd keep as an engineer and the decisions that would move to someone else. Then talk it through with your manager, including whether you can try the change for a set period first.

What Should You Do First When You Lead without Authority?

Pick one piece of work that's waiting on someone who doesn't report to you. Write down what it's waiting on, who holds it, what that person is measured on, and what you could offer them. Then send them one request with the task, the date you need it by, and what you'll do in return.

Frequently Asked Questions

Can You Lead without Authority in a Junior Role?

Yes. Naming owners and dates, giving the reason and the facts behind a request, and asking colleagues how they'd do their part don't depend on seniority. Cohen and Bradford list currencies that need no budget or anyone's permission to give, such as gratitude, recognition, and help with someone's work. Start with the colleagues whose work connects to yours.

How Is Influencing Your Boss Different from Influencing Peers?

In Yukl and Tracey's study, offering a favor in return and using flattery or praise went with commitment from peers and subordinates and didn't go with commitment from bosses. Managers used rational persuasion more often with bosses than with subordinates or peers. With your manager, start with your reasons, the facts and a recommendation. Cohen and Bradford's examples of what to offer a manager include work done on time, information from other areas, and early warning of possible problems.

Where Is the Line between Influence and Manipulation?

Cohen and Bradford wrote that people who fake interest in a colleague, or flatter them at every step of an ask, come to be seen as manipulative. They also wrote that no influence technique works well when people see the person using it as only self-interested. Tell the other person what you need, why you need it, and what you gain from it, and offer something they value in return.

How Do You Lose Influence at Work?

Cohen and Bradford wrote that overusing a currency, such as praise or gratitude, can devalue it until it no longer works. Ignoring the relationship to win one exchange can cost you later ones. A negative approach, such as a threat, can prompt the other person to respond in kind. Cohen and Bradford advised using retaliation that costs both sides only as a last resort. Keep track of what you've asked of each person and what you've done for them.

How Do You Know If Leading without Authority Is Working?

Check what happens to the work between your requests. Look at whether decisions get made by the dates you set, whether people tell you early when a date will slip, and whether tasks start on the day agreed. When work keeps stopping at the same point, find the decision or the person it's waiting on.

Related Blog Posts:

How to Build Influence at Work without a Title

Why does Coordination Work Count as Strategic Work?

How Do I Get Things Done in a Hierarchical Organization

How Do I Get Three Teams to Cooperate When None Report to Me?

How Do I Translate between Executives and Frontline Teams?

How Do I Get Pulled into Decisions Earlier?

Why Does Strategy Get the Credit and Execution Get the Blame?

How to Get Stakeholder Buy-In without Authority

References

1. Cohen, A. R., & Bradford, D. L. (2005). The influence model: Using reciprocity and exchange to get what you need. Journal of Organizational Excellence, 25(1), 57-80. https://doi.org/10.1002/joe.20080

2. Krackhardt, D., & Hanson, J. R. (1993). Informal networks: The company behind the chart. Harvard Business Review, 71(4), 104-111. https://hbr.org/1993/07/informal-networks-the-company-behind-the-chart

3. Yukl, G., & Tracey, J. B. (1992). Consequences of influence tactics used with subordinates, peers, and the boss. Journal of Applied Psychology, 77(4), 525-535. https://doi.org/10.1037/0021-9010.77.4.525

4. Klein, K. J., & Knight, A. P. (2005). Innovation implementation: Overcoming the challenge. Current Directions in Psychological Science, 14(5), 243-246. https://doi.org/10.1111/j.0963-7214.2005.00373.x

5. Klein, K. J., & Sorra, J. S. (1996). The challenge of innovation implementation. Academy of Management Review, 21(4), 1055-1080. https://doi.org/10.2307/259164

6. Gabarro, J. J., & Kotter, J. P. (2005). Managing your boss. Harvard Business Review, 83(1), 92-99. Originally published 1980. https://hbr.org/2005/01/managing-your-boss

7. Star, S. L., & Strauss, A. (1999). Layers of silence, arenas of voice: The ecology of visible and invisible work. Computer Supported Cooperative Work, 8(1-2), 9-30. https://doi.org/10.1023/A:1008651105359