Short on time? Start here
Influence is not the art of getting people to do what you want. It is the practice of helping people see enough of the whole system to make and keep a useful commitment.
A TPM often coordinates work they do not manage. The weak substitute for authority is pressure: invoking a senior leader, manufacturing urgency, or making a request sound already decided. It may produce a quick yes, but it spends trust.
Durable influence is quieter. Bring credible context. Understand the other person's constraint. Make the decision or request precise. Offer a path that respects ownership. Then make it safe for the person to give you a real answer, including no.
Start with this moment
Meridian Pay needs a fraud-model change before a seasonal traffic peak. Lena, the TPM, asks the identity platform team for a new event field. Their manager says the team cannot commit this quarter. Two production migrations already consume their capacity.
Lena could escalate immediately. She could say, "The vice president has made this a priority," and leave the team to absorb the collision. Instead, she asks what makes the request expensive. The platform team explains that adding the field is easy, but proving backward compatibility across six consumers is not.
Now the conversation has shape. Lena brings the fraud team, the platform lead, and the two highest-risk consumers together. They find a narrower path: publish the field behind a versioned contract, validate two consumers before the peak, and migrate the remaining consumers afterward.
The platform team still owns its design and estimate. The fraud owner still owns the business need. Lena owns the cross-team picture and the path to a decision. No borrowed title is required.
What is really happening?
Most resistance contains information. A team may be protecting reliability, a prior promise, scarce expertise, or people who have carried too much urgency for too long. If you treat resistance as disobedience, you throw away that information.
Influence begins with accurate curiosity, then moves toward a clear choice.
Diagram: Durable influence moves from a shared need through visible constraints and respected ownership to a commitment that can be kept.
This is not endless consensus. A decision may still need escalation when priorities genuinely conflict. Clean escalation names the collision, the options, and the appropriate decision maker. It does not use hierarchy as a threat.
Keep the boundaries clear:
- Functional leaders allocate their people and own discipline-specific quality.
- Product and business owners explain the outcome and its priority.
- Architects and engineers own technical proposals and judgments.
- Executives resolve priority conflicts at the level only they can resolve.
- The TPM exposes the dependency, makes the tradeoff legible, and helps commitments fit together.
Your influence grows when people learn that your requests carry context, your meetings lead somewhere, and your recaps match what was actually decided.
A day in a TPM's week
On Monday, Lena hears "no capacity" and does not answer with a bigger title. She asks for thirty minutes to understand the constraint.
On Tuesday, she draws the dependency in one line: the fraud release needs a trustworthy identity signal; the platform change affects six consumers. She separates the small code change from the larger validation burden.
On Wednesday, one consumer refuses the proposed timeline. Lena uses a three-part no on behalf of the program: "I understand why you need a full quarter for migration. We cannot make all six migrations a condition of the seasonal fraud protection. We can version the contract now and schedule your migration after the peak, with compatibility support until then."
On Thursday, the owners agree. Lena records who owns the contract, validation, rollout decision, and later migrations. She includes confidence and assumptions instead of turning the agreement into false certainty.
On Friday, she closes two loops she promised to close. Influence is being built in those small acts, not only in Wednesday's meeting.
Pause and think
- When you hear resistance, do you first look for a constraint or for a way around the person?
- Which of your current asks is too vague to receive an honest commitment?
- Where is an escalation needed because two legitimate priorities cannot both win?
Try this today
Choose one cross-team request. Rewrite it in five lines:
- Shared need: What outcome or harm makes this matter?
- Your constraint: What date, dependency, or decision cannot remain vague?
- Their constraint: What are they reasonably protecting?
- The ask: What exact commitment, decision, or estimate do you need?
- The path: What can be narrowed, sequenced, tested, or escalated?
If the answer is no, practice a useful response:
"Thank you for being clear. What condition would need to change for this to become possible, and who should choose between the remaining options?"
That sentence keeps dignity in the room and moves the work toward its proper decision point.
Add this to your TPM compass
Write three promises for how you will use influence:
- I will make the shared need visible by ____________________.
- I will respect other people's ownership by ____________________.
- When priorities truly collide, I will escalate by ____________________.
Now write your three-part no. It should acknowledge the need, state the constraint, and offer a path.
- Acknowledge the need: "I understand that ____________________."
- State the constraint: "We cannot ____________________ because ____________________."
- Offer a path: "What we can do is ____________________, or ask ____________________ to decide between ____________________."
A good no is not a disguised yes. It is an honest boundary with a next move.
Keep this thought
Authority can compel motion. It cannot guarantee care, candor, or a commitment people believe they can keep. Influence without borrowed authority is slower in the first conversation and faster across the life of the program because it leaves trust behind.
The aim is not to become impossible to refuse. The aim is to become worth answering honestly.
Go deeper when you need the operating method
Use the flagship TPM course for practical structures, scripts, and decision tools: