You were hired for execution. The work, now, is influence.

There is a moment in the career of every senior product or technology leader I work with where the work starts to feel like the wrong work.

The leader has been promoted, sometimes more than once. They are still the smartest person in many of the rooms they sit in. They still have the same operating instincts that got them noticed in the first place. The instincts say ship. Decide. Execute against the metric. Those instincts produced the leader’s career, and the leader has every reason to trust them.

The trouble is that, somewhere between the senior director seat and the VP-or-higher seat, the criteria the leader is being measured on quietly change, and nobody tells them.

For most of their career, the leader has been hired for execution. They were the person who delivered the launch. They were the person who fixed the platform problem. They were the person who took a project from stuck for six months to shipped in one quarter. Their reputation is downstream of those moments. Promotions reinforced the pattern. The pattern works.

What they are now being asked to do, without anyone saying it cleanly, is something different. They are being asked to move the organization. Not their team. Not their product line. The organization. The decisions they are now responsible for require people who do not report to them, who do not necessarily share their priorities, and who are running their own playbooks, to change what they are doing. The leader’s authority is no longer enough. The leader’s intelligence is no longer enough. The leader’s track record is helpful but does not transfer cleanly across functions.

The leader notices this. They do not always have a vocabulary for it.

What I hear, when a senior leader is in this transition, is some version of I am working harder than ever and I cannot point to what I shipped this quarter. Or, more revealing: I do not know what game I am playing.

Both of those sentences are diagnostic. The leader is still trying to play the execution game. The role has moved on. The game is now influence, and the leader does not yet have the moves.

Influence, in the sense I am using the word, is not politics. I want to be careful about this because most senior operators have an allergy to the word influence that is well-earned. They have watched the people who were promoted ahead of them play games they considered hollow. They do not want to become those people. The allergy is correct in its instinct and wrong in its conclusion.

The conclusion is wrong because influence, properly understood, is craft. Allan Cohen and David Bradford, in Influence Without Authority, describe it as a currency exchange. People in an organization care about different things; the leader’s job, when they cannot order a peer to act, is to understand what currency the peer trades in and to make a deliberate exchange. Inspiration. Task help. Position and visibility. Relationship. Personal comfort and self-concept. Five categories, roughly. Most operators trade in the second one and are then puzzled when their finance partner does not respond. The finance partner is trading in the third category. Different currency. Same conversation.

That kind of work is a skill. It is teachable. It is also, importantly, not manipulation. Manipulation is asymmetric: the manipulator is taking value the other person did not knowingly offer. The currency exchange is symmetric: both parties get what they need, in the currency they value, with the exchange visible. The leader who learns this stops experiencing the work as politics and starts experiencing it as a more honest version of the work they were already doing.

There is a second piece, which is harder to articulate but which I find I am working on with senior leaders more often than the first piece.

Edgar Schein, in Humble Inquiry, makes a small claim that is harder to enact than it sounds. Ask before you advocate. The senior operator’s reflex, formed across years of being the smartest person in the room, is to walk into a conversation with the answer. The answer might be right. The conversation almost always goes worse than the leader expected when the leader walks in with the answer.

It goes worse for a reason that has nothing to do with the answer’s quality. People support what they help build. A peer who is told the answer either accepts it (in which case they have not been involved in the work) or pushes back (in which case the leader has now created the resistance the leader was trying to prevent). A peer who is asked, before the answer arrives, help me understand how you are thinking about this, is being invited into the work. The answer the peer arrives at is sometimes different from the leader’s answer; the answer the peer arrives at is also the answer the peer will support and execute against.

This sounds like it should be obvious. It is not obvious in the moment. The execution-trained operator is fluent at advocacy and has practiced it for fifteen years. Inquiry is the disused muscle. It is also the muscle that does most of the work at the altitude the leader is now operating at.

I am simplifying. The full picture has more pieces, and the pieces interact. But the move that gets the senior leader unstuck, when they are in this transition, is almost always the recognition that the work has changed and that the instincts that produced their career are not the instincts that will produce the next leg of it. The instincts were correct for execution. The role is now influence. The two are different, and the leader is not failing at the new role; the leader is succeeding at the old one in a context where the old one no longer pays.

The transition is teachable. It is also not optional, if the leader intends to keep operating at this altitude. You were hired for execution. The work, now, is influence. The leader who does not name this for themselves either learns it on their own, slowly, or quietly stops growing.