A doubled salary can still be the wrong offer when the role rewards a professional identity you do not want to build. The useful question is simple: what kind of work will this job make you better known for by Monday morning?
Consider Adwoa, an illustrative composite of designers I have worked around. At 6:18 on a Friday evening in Accra, she sat in a nearly empty coworking space with the offer open beside a cold bottle of water. The number was twice her current salary.
The title was Product Operations Lead.
She had until Monday to respond. If she declined, she would return to a design role where budgets were tight and progression was unclear. If she accepted, she could clear family obligations faster, rebuild her savings and stop calculating every discretionary expense twice. There was also a harder possibility: six months later, she might have more money and a CV pointing away from the work she wanted to master.
She closed the laptop without replying.
The offer contained two different promotions
The obvious promotion was financial. Adwoa could see that immediately.
The second promotion was less visible. The company wanted someone who could coordinate releases, chase dependencies, prepare product reviews and keep engineering, sales and leadership aligned. Her design background made her credible because she understood the product and could translate between teams.
That did not make the role a design promotion.
Every week in product operations would reinforce a different set of skills: escalation, planning, reporting, coordination and organisational judgement. Those are valuable skills. They can lead to serious responsibility. But they would not produce the portfolio, research depth or interaction-design practice she had spent four years building.
Job offers do more than pay for your current ability. They select which ability receives another forty hours of practice.
Adwoa had been evaluating the offer as a reward for her past work. She needed to evaluate it as a training programme for her next identity.
Monday morning revealed the actual choice
On Saturday, she made two columns on a sheet of paper. One said “what I gain now.” The other said “what Monday starts repeating.”
The first column filled quickly: twice the salary, a stronger title, more access to leadership and relief from immediate financial pressure.
The second column took longer. Monday would begin with a release meeting. Tuesday would bring dependency tracking. By Friday, she would probably be compiling updates from teams whose work she did not control.
None of this sounded bad. That was precisely why the decision remained difficult.
A weak offer is easy to reject. A strong offer can pull you into a career you would never have chosen deliberately.
I use a practical test for decisions like this: imagine the role goes well for eighteen months. What work will people call you to do next?
If Adwoa succeeded, she would receive more product-operations opportunities. Recruiters would see evidence that she could keep a product organisation moving. Founders would ask her to repair delivery problems. Her market value would rise, but along a path she had not yet agreed to follow.
This is close to the identity tension explored in Product Designer Moving Into Operations: What a Four-Week Trial Revealed. A temporary test can expose the daily reality before a title hardens into a career direction.
Money still belongs in the decision
It would be easy to turn Adwoa’s choice into a speech about purpose. That would ignore the material reality of building a career in Accra, Lagos, Berlin or Atlanta while supporting other people and protecting limited savings.
Twice the salary changes lives.
The better response is to price the trade honestly. Adwoa asked what the additional income would buy beyond comfort. It would remove one pressing family obligation and create a financial buffer. Those outcomes mattered enough that she could accept a temporary move away from design, provided she protected a route back.
So she returned to the company with three requests: a clearer boundary around operational work, ownership of one design-heavy product initiative and a review point after several months. She wanted evidence that the job could expand her range without erasing her design practice.
The company accepted the product initiative and review point. The operational scope remained broad.
At 4:41 on Monday afternoon, with less time left than she wanted, Adwoa accepted.
That was not a declaration that product operations had become her calling. It was a bounded decision: use the income to solve a current constraint, test the work in practice and preserve enough design ownership to keep the next choice open.
Decide what the role is rehearsing
A title can disguise the direction of travel. “Product,” “strategy” and “innovation” appear in roles with completely different Monday mornings.
Before accepting an offer, write down the tasks you will repeat each week. Then ask what those repetitions will make easier to claim in your next interview, pitch or partnership conversation.
Also name the exit condition before the first day. Adwoa chose three signals: she would review whether design work remained part of her week, whether operations was teaching her judgement she valued and whether the financial problem that justified the move had been resolved. Without those conditions, a temporary compromise could quietly become her default identity.
On her first Monday, Adwoa joined the release meeting and opened a fresh document. At the top she wrote two lines: “What this role is teaching me” and “What I refuse to stop practising.”
The salary had answered Friday’s pressure. Those two lines would decide what came after.
Comments
No comments yet.