Cross-functional influence is rarely won in the meeting where the decision gets made. By the time I am making the ask, most of the work should already be done.
I learn stakeholders the way I learn users: what matters to them, what risks they are carrying, how they communicate, and what information they need to make a decision. Executives need the ask, the evidence, the cost, and the expected value. Engineering leaders need the why before the what. Peers competing for the same resources need to understand the shared benefit, not hear another argument about whose priority matters more.
Do the work before the room
I bring people into the thinking early, especially when the decision will affect how their teams work. That gives me a chance to surface concerns while they are still useful input rather than hardened objections.
I also try not to arrive with a plan that only works if everything goes right. A credible fallback shows that the recommendation can survive contact with reality and gives stakeholders a way to support the direction without pretending there is no risk.
Timing changes what is possible
A good idea can still fail if the organization is not ready to act on it. Sometimes the better move is to socialize the problem, build shared language, find allies, and keep strengthening the evidence until the decision becomes easier to make.
I once proposed a platform re-architecture well before the organization was ready to adopt it. Rather than treating the initial outcome as the end of the idea, I kept developing the framework and incorporating the underlying principles into ongoing work. By the time the problem became urgent for others, the language was familiar, the evidence was assembled, and there was already a path forward.
An “I told you so” may feel satisfying, but it does nothing to move the organization forward. Lead with the solution: “Here is the plan I've been developing.”
Evidence changes the conversation
When I need to escalate an issue, I try to make the decision as concrete as possible. What is happening? What does it cost? What are the options? What changes if we act, and what happens if we do not?
Evidence does not remove decision rights from leadership. It gives leaders something more useful to work with than instinct, escalation pressure, or whoever happens to argue most forcefully in the room.
Being right matters. But product leadership is not measured by how often you saw the problem first. It is measured by whether you helped the organization recognize it, make the decision, and move forward.