Lessons from a decade of getting things done without being the boss
When I started as a project manager over a decade ago, I felt like I lacked the authority to get things done. I stepped on a few engineering and product managers’ toes along the way. My ego kept me from discovering the joy and freedom of influencing without authority. Some people are naturals at it. I had to learn it through experience.
As a program manager, I influence people at every level of the org, including:
- People outside my reporting line
- People above me
- Entire teams
- Those skeptical of project management
- People so busy they regularly skip lunch
Tactics & Strategies
Some approaches are longer term (strategic), others more immediate (tactical). I’ve learned to weave both into the everyday.
Build relationships
Meet with your partners and stakeholders—if not regularly, then often enough to know what they need and how they operate. Use the time wisely and gauge each person’s tolerance. Come ready with questions: how they see their place in the org, what they struggle with, what their priorities are, how they communicate, and who they are. The goal is a deeper relationship and a real understanding of their style, needs, and preferences.
Questions worth asking:
- What wastes your time?
- What are your team’s priorities?
- What worries you?
- What does success look like for your team?
- Do you have conflicting priorities?
- Are you a dog person, a cat person, neither, or both?
Personal note: I got to spend a few sessions with the CTO of a large company. His advice: “Make strategic connections across reporting lines. Anyone can help you; don’t discount them.”
Lead with the “why”
You’re not asking for a favor. You’re asking people to do something for the good of the organization. Give a clear reason and the expected outcome behind the request, such as:
- Expected revenue growth
- Time saved
- Dollars tied to a contract
- Total value of contracts where customers are hitting this bug
- Cost savings
- Potential cost of security weaknesses
It’s a red flag if you can’t articulate the value of an ask at the organizational level. If the ask comes from you, you owe people the “why.” If it comes from someone else, find their reasoning and make sure the organization supports it.
Remove roadblocks
You’re a servant leader. Clearing operational hurdles, unblocking dependencies, and making others’ jobs easier is core to your job. Find the roadblocks and remove them, or work with those who can. If a roadblock won’t budge, help the team raise the risk with credible information and reasoning, and offer alternatives or mitigations. Connect the dots for every stakeholder so you can form a goal-focused coalition.
Build credibility
Credibility is earned. Deliver what you promise, when you promise it. Speak and present with facts and data. Treat colleagues with respect and calm. And don’t shy away from “I don’t know, but I’ll find out.” A few ways to build credibility (and trust):
- Deliver consistently and on time
- Present facts
- Deliver tangible value
- Understand the technical side:
- Know the architecture, dependencies, and risks
- Sit in on design reviews and read the design docs until you understand them
- Be able to sketch a box diagram of the key components, with inputs and outputs
Leverage transparency & data
This is my personal favorite! Lean on data as much as is appropriate and available:
- Use objective metrics
- Keep emotions out of it
- Ground opinions in facts and experience
Communicate clearly, for every audience
Give people just enough information to absorb quickly, be ready for clarifying questions, and help leaders make decisions with confidence. Keep your presentation consistent and professional:
- Simple, shared dashboards
- Clear dependency and risk tracking
- Tailor to your audience—flex between the weeds and the big picture, and tie the forest to the trees (and back again)
- When issues come up, give a clear problem statement, the trade-offs, and a recommended path
Be flexible
It should never be “my way or the highway.” Hopefully you’ve already learned what makes your colleagues tick, so it’s on you to adjust to the realities in front of you. Ask questions instead of giving orders. Be ready to unlearn what you know and adapt.
Ponder Your Influence Style
Influence comes in different flavors:
- Rationalizing: logic, data, structured analysis
- Inspiring: energy and bold vision
- Negotiating: working through conflicting priorities with give-and-take
- Bridging: building coalitions and listening to skeptics to find common ground
I often mix a few depending on the situation—presenting clear data while bridging gaps between people or negotiating changes. Less often, I’ll try to energize a team with a big, audacious vision. Most importantly, your style should be yours. Be authentic to yourself, your audience, and your situation.
Insight: The Influence Style Indicator (ISI) assessment analyzes your influence profile. This is typically given by a trained pro in conjunction with coaching (that’s not me). I approximated it with Claude or ChatGPT for the sake of self-reflection. It’ll show where your style falls short and how to draw on the other styles—or let you celebrate your adaptability. Mine said I lean on data and miss out on what being more inspiring could get me. Its advice: “Pair Rationalizing with Inspiring to win hearts as well as minds.” Fair point! Though you’ll never see me all fired up like Steve Ballmer sweating out a bold vision.
Conclusion
At the end of the day, influencing without authority takes a mix of long-term strategic effort and short-term tactics. It’s a dance, and it should be done authentically and respectfully, never through manipulation.
Further reading
- 7 Ways to Influence Without Authority (PMI Blog)
- How to Influence Without Authority as a TPM by Mario Gerard (this guy is a wealth of neat stuff)
- How to Win Friends and Influence People by Dale Carnegie (a little dated, so keep an open mind)