Influence Without Authority: The Art of Building Credibility

It doesn’t come free, and it doesn’t happen overnight. Here is how to earn it.

The Credibility Bank: This generative AI generated visual captures the “invisible currency” of a TPM. The left panel shows the friction of an unprepared ask, while the right panel shows the “Easy Yes” that comes from depositing homework and goodwill into your stakeholder relationships.

Not a Medium Member ? Read this story via my “Friend Link” here.

If you want someone to do something for you, especially when they don’t report to you, they need to believe two things: that you know what you’re talking about, and that you have their back.

This is Credibility. It’s the difference between a stakeholder ignoring your Slack message and them prioritising your request over everything else.

1. Learn the Ecosystem

We are all busy. The temptation is to skim the surface and just “project manage” the dates. Resist that. Spending time up front understanding the systems will save you weeks of rework later.

To build technical credibility, you need to “lurk” where the work happens:

• Read the Paper Trail: Don’t just read your own team’s Product Requirement Documents (PRDs); read the neighboring teams’ docs too. Understand the dependencies before they become blockers.
• Study the Architecture: You don’t need to write the code, but you need to understand the flow. Read the architecture docs until you can explain them to a 5-year-old.
• Go to the “Dirt”: Read the customer tickets. Find the common issues and the recurring pain points. When you can speak to the actual problems customers are facing, engineers will listen to you.
• Watch the Reviews: Lurk in code reviews and PRs. It’s the best way to see how the team thinks and what they value in code quality.

2. Build a Goodwill Surplus

Technical knowledge gets you in the door, but being a decent human being keeps the door open. Credibility is built on trust, and trust is built on goodwill.

• Public Praise, Private Feedback: When someone does something great, shout it out in a public channel. Be specific. Instead of “Great job, Sarah,” try “Sarah’s fix for the latency issue saved us 200ms, huge win.”
• Be the “Shield”: Use your credibility to protect the team from distractions. When you’re the one fighting the “noise” so the engineers can focus, you earn a level of loyalty that no “status update” can buy.
• Build the “Neighbour” Bridge: Don’t just be nice to your team; be nice to the teams you will work with. Building a relationship before you need a favour is the ultimate TPM move.

The Bottom Line

Credibility is an investment. It’s slow, it’s quiet, and it requires you to do the work that no one else wants to do. But once you have it, the “Influence” part of your job becomes infinitely easier.

Disclaimer: The core ideas presented in this article are solely from the author. A generative AI model (Gemini) was used to enhance the structure and speed of drafting and editing. The final article has been thoroughly reviewed and edited by the author.