Evidence-Backed Career Ask
Price your contribution, make the ask, and turn rejection into a decision
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 98%
The framework begins before the meeting: decide what you want, research the market, and connect your request to achievements and previously agreed measures. Present that evidence as a clear proposal rather than waiting for a manager to guess your ambition. If the answer is no, ask why. The useful response is not merely rejection but information: what evidence is missing, what criteria would change the decision, and when can the conversation be reopened? A six-month checkpoint or another measurable path can turn a refusal into a development plan. If the organisation offers neither fair reasoning nor a credible trajectory, the answer becomes evidence for a separate judgement about whether to stay. The method does not guarantee agreement; it ensures the conversation produces clarity.
Origin
Nicola Mendelsohn contrasted this method with accepting her early pay rises without negotiation on The Diary of a CEO.
Core principles
- 01Nobody else owns your career homework
- 02Decision-makers may not know what you want
- 03A credible ask links market evidence to delivered value
- 04A no should produce criteria, timing, or a stay-or-leave decision
How to run it
- 1
Define the ask
Specify the pay, role, account, opportunity, or development outcome you want.
Pro tip Make the request concrete enough to answer.
Watch out Do not hope the other person will infer it.
- 2
Do the market homework
Research comparable roles and establish a credible external benchmark.
Pro tip Compare scope and responsibilities, not titles alone.
- 3
Build the value case
List achievements, successful outcomes, and performance against agreed measures.
Pro tip Use evidence the decision-maker can verify.
Watch out Confidence without evidence weakens the request.
- 4
Make the proposal
Explain the benchmark, your contribution, and the outcome you believe follows from them.
Pro tip Leave room for negotiation without making the opening vague.
- 5
Interrogate a no
Ask for the reasoning, the criteria required, and a date for reconsideration.
Pro tip Convert broad feedback into observable milestones.
Watch out Do not accept an indefinite promise as a trajectory.
- 6
Make the judgement call
Decide whether the offered path is credible enough to stay for or whether the refusal signals a need to move.
Watch out A rejection is information, not automatic proof of unfairness.
In the wild
An employee researches comparable roles, documents performance against agreed KPIs, and proposes an adjusted salary. The manager cannot approve it immediately, so they agree on two measurable outcomes and a six-month review date. The employee records the agreement and uses the period to test whether the promised path is real.
→ The conversation ends with evidence, criteria, and a decision point rather than passive uncertainty.
Common mistakes
Saying only thank you
Accepting the first outcome without preparation gives up the chance to test your market value or clarify your path.
Waiting to be noticed
Managers may support an ambition they cannot infer, so silence can look like satisfaction.
Treating every no as final
A refusal may still yield useful criteria and timing if you ask for them directly.
Is it for you?
Best for
Employees preparing for pay, promotion, account allocation, or development conversations.
Not ideal for
Making unsupported demands without evidence of contribution or market context.
From the transcript
“the onus is on you to make sure you do their homework on your career”
“show me the path that gets me there”
From the episode
VP Of Meta: Running A Trillion Dollar Business With An Incurable Illness: Nicola Mendelsohn