A promotion only changes your authority when the decisions attached to the role move with it. If the product roadmap can still be approved without you, the first executive meeting is less a celebration than a test of what your new title means.
Consider Ama, a composite fintech product leader in Accra. At 8:47 on Monday morning, she entered a glass meeting room carrying a new notebook, still stiff at the spine, for her first meeting as Chief Product Officer. Her name appeared beside the new title on the agenda.
Then the finance director opened the approved roadmap.
Ama recognised the projects, but not the order. The merchant onboarding work her team had spent six weeks preparing had moved below a partner integration. Two engineers had been reassigned. The roadmap had been approved on Friday afternoon, before her promotion was announced, and nobody had brought it back for her review.
She had a choice to make while nine people waited for her response. Accept the plan and begin her new role by implementing a decision made without her, or challenge it and risk being described as territorial before she had completed her first executive meeting.
The roadmap exposed the real reporting structure
The exclusion may have been procedural. Friday’s meeting may already have been scheduled. The CEO may have believed the promotion announcement would settle the question of product ownership from Monday onward.
None of those explanations changed the operating fact in front of Ama: the company had committed engineering time, partner expectations and product sequencing without the executive now accountable for the result.
This is where a new leader can make the wrong argument. Ama could have focused on recognition: “Why wasn’t I included?” That question would have been understandable, but it would have made the conversation about respect and personal status.
The harder question was operational: who had the right to approve product priorities, and who would carry the consequences when those priorities failed?
Ama closed the notebook. She said she could work from the approved roadmap for the week, but she could not accept accountability for its delivery until the executive team clarified three decisions: who could change priority, who could reassign product engineers, and whose approval was required before a partner commitment entered the roadmap.
The room went quiet.
The bad ending remained possible. The CEO could treat her request as a refusal to execute. If that happened, Ama would begin the role with responsibility for product outcomes and no reliable control over the choices producing them.
Challenge the decision without staging a reversal
A Monday confrontation often tempts people into one of two poor responses. They either stay silent to appear collaborative, or reopen every decision to prove the promotion has changed the hierarchy.
Ama did neither.
She separated the roadmap already approved from the process that would govern the next one. She asked the engineering lead to confirm what work had started since Friday. She asked finance which commitments depended on the partner integration. Then she asked for a short decision meeting before any additional engineers moved.
That distinction mattered. Reversing the roadmap immediately would have imposed fresh costs before she understood the original reasoning. Accepting the approval process unchanged would have allowed the same exclusion to happen again.
Founders face the same problem when a senior hire arrives. They want the person to own an outcome, yet continue making the consequential calls through old relationships and informal Friday conversations. The hire receives a senior title while the founder retains the decision rights.
I explored the cost of that mismatch more directly in The Decision Rights Ama Didn’t Have, and What the Promotion Could Cost Her. A promotion can increase exposure faster than authority. Every missed target now belongs to the new executive, including targets shaped by decisions she never made.
Put decision rights into the next calendar invite
By Monday afternoon, Ama had not won control of the full roadmap. That would have been an implausibly neat ending.
She had secured something more useful: the CEO agreed that future roadmap approvals required product, engineering and finance in the room. Partner commitments could enter discovery without automatically displacing approved product work. Engineer reassignments affecting delivery dates needed a named approver and a recorded trade-off.
One point remained unresolved. The CEO still wanted the right to accelerate a commercial request when a major deal was at risk. Ama wanted a clear threshold for using that exception. They scheduled the argument instead of pretending it had disappeared.
This is the work beneath an executive title. Authority needs to appear in meeting attendance, approval paths and the written record of who chose what. Otherwise, it exists mainly in the announcement.
The same discipline applies when a smaller team changes its product plan after losing a key person. The useful response is to redraw commitments around the capacity that remains, as in Senior Engineer Resignation: How Kojo Redesigned the Product Plan Around a Smaller Team. In both cases, clarity comes from connecting decisions to the person expected to deliver them.
The next Monday looked different
A week later, Ama entered the same room with the same stiff notebook. This time, the roadmap document listed an owner beside every proposed change. One request from sales had no trade-off recorded, so it stayed out of the approval column.
No speech was required. The meeting itself had changed.
That is the practical test after a breakthrough promotion. Look past the title on the agenda. Find the next irreversible decision, then check whether the person accountable for its outcome is present before it is approved.
Comments
No comments yet.