Ama should ask for decision rights in writing before accepting the promotion. A title that makes her accountable for a fintech launch, without control over budget, hiring or launch approval, gives her the downside of leadership without the authority to change the outcome.
In January 1986, engineer Roger Boisjoly was arguing against launching the space shuttle Challenger. He and other Morton Thiokol engineers had warned that the O-ring seals could perform poorly in unusually cold conditions at Kennedy Space Center.
During a conference call on the evening before launch, Morton Thiokol initially recommended waiting. After an internal discussion, its managers reversed that position and recommended proceeding. Challenger launched on January 28 and broke apart 73 seconds later, killing all seven crew members.
The Rogers Commission later documented the warnings, the disputed recommendation and the decision process. Boisjoly had relevant knowledge and a grave responsibility to raise the risk. He did not hold the final authority to stop the launch.
Ama’s decision carries nothing close to those stakes. The structural problem is still worth noticing: responsibility can travel further down an organisation than authority does.
The missing terms matter more than the title
Ama has until Monday to accept a role leading a fintech launch. The offer names the outcome she will own. It says nothing about the resources or decisions required to produce that outcome.
Before she accepts, she needs answers to three questions.
Who controls the budget? If another executive can decline essential spending, Ama needs to know how disagreements get resolved and how quickly.
Who approves hiring? A launch plan built around two engineers, a compliance lead and customer support capacity means little if Ama cannot recruit them or secure named people from existing teams.
Who can stop the launch? Fintech products can encounter unresolved security, compliance, reliability or partner issues close to release. If Ama sees a serious problem on Thursday evening, can she delay Friday’s launch? If she can only recommend a delay, who makes the decision, and where is that responsibility recorded?
These are operating terms. Without them, the title describes visibility, while the organisation keeps control elsewhere.
Convert verbal support into a decision map
The useful conversation on Monday is not, “Do you trust me to lead this?”
Trust is too broad to settle a budget dispute or hold a release. Ama needs a short decision map covering the launch period:
- She can approve spending within an agreed limit.
- Named roles are assigned to the launch, with a process for replacing anyone pulled away.
- Product, compliance and commercial leaders have defined approval areas.
- One named executive resolves conflicts that cross those areas.
- The person with final launch authority is identified.
- Ama’s authority to pause the release is explicit, including the conditions that justify a pause.
The company may reject some of those terms. That response is useful information. It reveals whether leadership wants Ama to direct the launch or absorb the pressure around it.
A similar issue appeared in Ama’s earlier compliance review: work can be complete while the approval path remains unclear. The delay begins long before the final decision. It begins when nobody names who can say yes, who can say no and who breaks a tie.
Separate a negotiable gap from a structural warning
An incomplete offer can come from haste. A founder may have written the title and compensation first, assuming operating details would follow. Ama can test that possibility by asking for a written amendment or role charter.
A clear response sounds concrete: a named budget owner, defined hiring scope, a launch decision process and a date for reviewing whether the role has enough capacity.
A warning sounds flattering but vague: “You will have full support,” “Everyone knows this is your priority,” or “We will work out the details together.” Those statements disappear when revenue targets, compliance concerns and engineering deadlines collide.
Ama should also ask what happens if the launch date moves for reasons outside her control. Will performance be judged against the quality of her decisions, or against the original date regardless of new evidence? That distinction tells her whether the company values judgment or compliance with a plan.
Write Monday’s answer before Monday
Ama does not need to reject the role on Friday. She needs to make acceptance conditional on the authority required to do it.
Her reply can be short:
“I am interested in leading the launch. Before I accept, I would like the offer to confirm budget authority, hiring authority, the approval path and who holds the final decision to launch or delay. I would also like us to record how my performance will be assessed when another function controls a dependency.”
That wording keeps the conversation on the work. It avoids turning a governance problem into a debate about confidence, loyalty or ambition.
Roger Boisjoly’s warning entered the record because he stated the technical risk clearly. The final decision sat elsewhere. Ama should establish that boundary before Monday, while the company still needs her agreement and the title remains open to definition.
Comments
No comments yet.