Andrew read the offer document twice, set it back down on the glass table, and asked if he could have a week. His manager — who had prepared for questions about the salary figure, the team size, the reporting lines — hadn't prepared for that one. The room went quiet in a way that made Andrew's two colleagues outside, who heard about this later, describe it as the moment they realised something different was happening.
The offer was real. Head of Data Operations, APAC Infrastructure. Seventeen percent above his current band. A title that would have looked significant on anyone's resume. His manager had clearly expected a yes, or at worst a yes with a small negotiation about the number.
What he got instead was someone who wanted to read the document carefully before agreeing to be responsible for what was in it.
"Everyone assumed I said no because I didn't want the job. I said no because I understood exactly what the job was — and what it wasn't."
Seven days later, Andrew walked back in and declined. The word around the team was mixed — disbelief from some, quiet curiosity from others. Within six months, almost everyone who'd had an opinion had quietly revised it. Not because Andrew had explained himself, but because what happened next made the reasoning obvious.
What the Offer Contained — and What It Didn't
The role was new. Not new-to-Andrew new — new to the organisation. No one had held it before. No predecessor to shadow, no institutional memory to inherit, no team that already knew what they were reporting into. He would be building the function while simultaneously managing his existing delivery responsibilities through a transition period described in the offer document as "approximately three months."
Three months is not a transition period for a role of that scope. It is a pressure valve — a way of packaging "we haven't figured out how to hand this over yet" as a temporary condition rather than a structural gap.
A role created in response to an organisational gap — a restructure, a departing leader, a board-level pressure to show depth — often arrives without the infrastructure that makes it viable. The title looks senior. The mandate looks substantial. The budget autonomy, confirmed headcount, and executive alignment that would make the mandate achievable are frequently either absent or still being worked out when the offer lands on the table.
Andrew knew the three direct reports attached to the new role were each matrixed into two other teams with their own competing deadlines. The budget for the function hadn't been separated from the broader technology cost centre. And the role's core mandate — consolidating three legacy data platforms — was a project that had stalled twice before, under previous structures, because of stakeholder resistance that had never been formally resolved.
He was being offered accountability for a politically complex transformation programme. The authority and resources to run it were still theoretical.
The Seven Days — What He Was Actually Checking
What a Real Promotion Offer Looks Like
The social pressure around promotion offers is real and it works in the organisation's favour. Declining one — even temporarily, even with clear reasons — risks being read as a lack of ambition or a failure to understand your own value. Most people accept because the optics of acceptance feel safer than the optics of scrutiny.
What distinguishes the people who avoid the trap from those who walk into it is almost always the same thing: the willingness to evaluate the offer on what it actually delivers rather than what it symbolises.
| What to Check | Red Flag | Green Signal |
|---|---|---|
| Budget Authority | No confirmed budget line; costs absorbed into existing centres | A discrete budget under your direct approval authority |
| Headcount | Direct reports matrixed into other teams with competing priorities | Confirmed primary reporting lines with no conflicting accountability |
| Executive Sponsorship | Your mandate affects teams whose leaders haven't been briefed on your role | Named executive sponsor with authority to resolve cross-team conflicts |
| Salary Benchmarking | Increment feels significant relative to current band but is below market for the new scope | Compensation benchmarked against external market data, not internal relativities |
| Role History | Newly created position; related roles have seen high turnover | Established function with clear institutional knowledge transfer |
What Happened to the Colleague Who Said Yes
Three months before Andrew received his offer, a colleague at the same firm accepted a comparable management role. Similar structural gaps. She hadn't audited it the way Andrew would later audit his. She had looked at the title, the increment, and the vote of confidence it represented — all of which were real — and said yes.
By the time Andrew formally stepped into his reconditioned role eight months later, she had been quietly reassigned to a lateral position with less scope than her original individual contributor role had carried. The platform migration she'd been made responsible for had stalled under the same cross-team resistance that had stalled its predecessors. With no executive sponsor to escalate to and no confirmed budget to make decisions from, she had absorbed the conflict and eventually been moved sideways out of it.
The difference between their outcomes wasn't talent or ambition. It was the willingness to read the offer document as an operational proposal — and to ask, before accepting the accountability, whether the authority to deliver on it had actually been confirmed.
Who controls the budget for this role, and what is the confirmed annual figure? Which direct reports have a primary line to this role versus a dotted-line matrix arrangement? Who is the named executive sponsor for cross-functional decisions? What is the market compensation benchmark for this scope — not the internal band adjustment? And if the role is newly created, what specifically caused the organisation to need it now, and what happened to the people who previously tried to fill the gap it represents?
What People Said When This Went Around
Three weeks after Andrew submitted his counteroffer, his manager returned with a modified proposal. Budget autonomy confirmed. A formal C-suite executive sponsor assigned to the platform consolidation — something that had not existed under any previous structure. Salary landed at 24%, not the 28% he'd asked for, but with a confirmed annual review clause tied to programme milestones rather than the standard performance cycle. The 90-day scoping period was agreed to in full.
The platform consolidation delivered its first major migration milestone six weeks ahead of schedule. The executive sponsorship Andrew had insisted on as a precondition turned out to be the one structural element that had been missing every time the programme had stalled before.
He didn't do anything his colleagues couldn't have done. He just slowed down at the moment when the pressure to say yes was highest, read the document as a proposal rather than a reward, and asked for what the role actually needed before agreeing to be responsible for it.
"A title without infrastructure is just a label. Before you accept the accountability, make sure the authority to deliver on it has actually been confirmed."