How to Lead a Project without Authority
To lead a project without authority, name each decision and the person who owns it, make every ask small enough to finish this week, and keep progress where everyone on the project can see it. Check in before each deadline, so a slipping date shows up while there's still time to fix it.
Everyone agreed to the plan at the kickoff. Then the first date slipped. None of the people doing the work report to you.
Why Does a Project Stall When No One Reports to You?
A project can stall for several reasons when you lead without authority at work. Four of them come from gaps in how the work is coordinated.
Check a stalled project for these four gaps.
A decision with no owner. The work is waiting on a choice, such as which vendor or which launch date, and nobody knows the choice is theirs to make.
No agreed order. Two or three people are each waiting for someone else to finish first.
A task that hasn't started. People agreed to it in the meeting and haven't begun.
A problem nobody has raised. Someone can see a date slipping and hasn't said so.
When a date slips, check for these gaps before you look at the person who missed it. If the task was waiting on a decision nobody owns, a conversation about that person's effort leaves the decision unmade, and every other task that needs it will wait too.
How Do You Get People to Do the Work When You Don't Have Formal Authority?
Offer something the person values in return, and make the ask easy to do.
Allan Cohen and David Bradford's influence model treats getting what you need from people you have no authority over as an exchange (Cohen and Bradford, 2005, Journal of Organizational Excellence). You trade something you have that the other person wants for what you need, and they call the things people trade currencies. They describe at least five types that people often value.
Inspiration-related. Work with larger significance, the chance to do something well, and doing what's right.
Task-related. New resources such as budget or staff, challenge, help with their work, backing, a faster response, and information.
Position-related. Recognition, visibility to people higher up, reputation, a sense of being an insider, and contacts.
Relationship-related. Acceptance, being listened to, and personal support.
Personal. Gratitude, ownership of important tasks, affirmation of how they see themselves, and avoiding hassles.
They suggest asking the person what they care about. If you can't ask, look at how they're measured and rewarded and what their manager expects of them. On a project, what you can offer might be a clearer scope for their part, credit with their manager, help with a piece of their work, or a date that avoids their busiest week.
The ask itself also affects whether people act. BJ Fogg's behavior model says a behavior happens when motivation, ability and a prompt come together at the same moment (Fogg, 2009, Proceedings of the 4th International Conference on Persuasive Technology). His 2009 paper calls the prompt a trigger. On the model's website, Fogg names five things that can make a behavior hard to do. They are time, money, physical effort, mental effort, and whether it fits a person's routine. The one that's scarcest for the person at that moment is what makes the behavior hard (Fogg, Fogg Behavior Model website). He recommends making the behavior smaller.
Fogg built the model to help design persuasive technology. For a request at work, it means asking for less at a time. "Review the whole plan" takes time and mental effort that a busy person may not have between meetings. "Can you confirm the launch date by Thursday? Reply yes or give me a new date." takes a minute to answer.
How Do You Hold People Accountable without Authority?
Agree on who does what by when, and write it down the same day where everyone on the project can see it. Make the agreement go both ways, so it names what you'll do too. "You send the draft Tuesday. I'll get you the numbers Monday, so you have them before you start."
Put the order of the work in the same agreement. If the draft can't start until the numbers arrive, say so, and give the numbers the earlier date.
Ask each person when they'll do their part. Paschal Sheeran and Thomas Webb reviewed research on the gap between what people intend to do and what they do (Sheeran and Webb, 2016, Social and Personality Psychology Compass). One of the best-tested ways to close that gap is an if-then plan, where a person decides ahead of time when and how they'll act, such as "If it's Monday morning, then I'll send the numbers." In the studies they reviewed, people with if-then plans were better at remembering to act, taking chances to act, and getting past procrastination.
If the project has a RACI chart that isn't working, add a date and the order of the work to each task on it.
How Do You Make Sure People Follow Through after a Meeting?
Check in once, partway between the meeting and the deadline. Sheeran and Webb also describe what happens once people have started on a task. Other goals that need the same time and effort can pull them away, and old habits can take over. These are some of the reasons teams agree in meetings and don't follow through.
Keep the check-in to one short message, such as "Are we still good for Thursday, or has something changed?"
The question also makes it easier for someone to tell you about a problem. Amy Edmondson described team psychological safety as a shared belief that a team is safe for interpersonal risk-taking (Edmondson, 1999, Administrative Science Quarterly). She wrote that a person who admits an error or asks for help may look incompetent. In her study of work teams at a manufacturing company, psychological safety went with more learning behavior, such as asking for help, seeking feedback and talking about errors. Saying a date will slip is that kind of admission.
Keep progress where everyone can see it, such as a shared tracker, a pinned list or one board. Sheeran and Webb report that keeping track of progress makes people more likely to do what they intended. In the research they reviewed, programs that got people to track their progress had larger effects when progress was written down or made public.
What Should a Project Manager with No Authority Stop Doing?
Stop three habits that take your time without fixing why the work is late.
Following up with no agreed date. If nobody agreed when you'd check in, each follow-up comes as a surprise. Agree on the check-in date when the task is assigned, so everyone expects the follow-up.
Explaining the reasons for the project again. If people already agree with the goal, another explanation doesn't give them a next step. Ask what's in the way, then name the next step and who owns it.
Doing a stuck task yourself. If the task is stuck on a decision, doing it yourself finishes that task and leaves the decision open.
Start with the item on your project that has waited longest. Write down the decision it's waiting on and who owns that decision. Then send that person a message today with the decision, the date you need it by, and what moves if it isn't made, such as "The vendor decision is still open, and it's yours to make. If it's still open on Friday, the pilot date moves."
Frequently Asked Questions
Is It Normal to Own a Project without Authority over the People on It?
Yes, on any project that needs work from several teams. Each team takes its priorities from its own manager. If you run the project, you coordinate teams that don't report to you. People who run projects like this call it having all the responsibility and none of the authority.
Do I Need a Title to Lead a Project?
No. Naming a decision's owner, asking for small steps with dates, and checking progress before a deadline don't depend on a title. To build influence at work without a title, start by finding out what each person on your project needs from their part of the work and what you can offer them.
What Do I Do When Someone Ignores My Requests?
To get people at work to act on your requests, check the request before you follow up. It should name one task, a date and the person it's for, and it should be small enough to do between meetings. If it met those tests and still got no answer, ask the person what's in the way. Add the item and its date to the shared tracker. If it stays stuck, take it to the person who sets their priorities.
When Should I Escalate a Problem on My Project?
Escalate when the decision or resource the work needs belongs to someone who hasn't answered, and waiting will move a date. Talk to that person directly first. Escalating takes the decision to someone with authority over it, such as your sponsor or the owner's manager. Tell them the decision, the date you need it by, and what moves if it isn't made.
Does Leading without Authority Work with Someone More Senior?
The steps are the same. Cohen and Bradford's exchange model covers anyone you have no authority over, including people above you. They list things people can offer their own manager, such as getting work done on time, passing on information from other parts of the organization, and warning them about likely problems. Keep the ask to one decision and a date.
If you're moving work forward with people who don't report to you, Get the Buy-In walks you through who needs to say yes, in what order, and what each person needs to hear.
Related Blog Posts:
How to Lead without Authority at Work
How to Handle Responsibility without Authority at Work
Why Do Teams Agree in Meetings and Then Not Follow Through?
How Do I Get Three Teams to Cooperate When None Report to Me?
How to Build Influence at Work without a Title
How Do I Get Things Done in a Hierarchical Organization
References
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
Fogg, B. J. (2009). A behavior model for persuasive design. In Proceedings of the 4th International Conference on Persuasive Technology (pp. 1-7). ACM. https://doi.org/10.1145/1541948.1541999
Fogg, B. J. (n.d.). Ability in the Fogg Behavior Model. Fogg Behavior Model. Retrieved October 10, 2026, from https://behaviormodel.org/ability/
Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. https://doi.org/10.2307/2666999
Sheeran, P., & Webb, T. L. (2016). The intention-behavior gap. Social and Personality Psychology Compass, 10(9), 503-518. https://doi.org/10.1111/spc3.12265
