The Three-Option Ask
Never walk into a pay negotiation with just one number — always have three asks ranked.
Most people go into a pay negotiation with a single number. If it is rejected, they have nowhere to go — the conversation collapses into awkward silence or a face-saving retreat. Wayne Clarke argues the smarter approach is to prepare three distinct asks before sitting down: the target salary increase (the 'star prize'), a development-time arrangement (a percentage of working time reallocated to a project, team, or skill that benefits both the employee and the organisation), and a funded learning or growth opportunity.
The three-option structure does several things at once. It signals to the manager that this person has thought seriously about their career, not just their pay packet. It gives the manager multiple ways to say yes — which psychologically lowers the cost of saying yes to something. And it means the conversation cannot be closed down with a single 'no'. If the salary is off the table, the next ask is: 'Could I spend 10% of my time working with this other team?' A manager who has already said no once finds it significantly harder to say no again, especially to a request that is low-cost and value-adding.
Clarke also notes a deeper logic: the development-time option is often more valuable than the pay rise itself. If 10% of your working week is spent learning a high-value adjacent skill or building a relationship with a senior team, the long-term income effect of that compounding investment outweighs a one-off salary bump that adjusts to normal within two months.
- A single-number ask creates a binary outcome — yes or no. Multiple asks create a spectrum of possible wins.
- Development time is compensation — it builds market value that either earns more here or makes you competitive elsewhere.
- The second ask after a 'no' is psychologically easier for the manager than the first — use the structure to force a second decision.
- Non-cash options framed as benefits to the manager and team are far harder to reject than ones framed as benefits to you.
- A 10% pay rise and 10% of your time spent on a growth initiative have very different long-term returns — know which you actually want.
- Define your star prizeThe primary ask is a specific salary increase — Clarke suggests 10% as a number that is meaningful, inflation-beating, and not so large it sounds irrational. Prepare the case for this number before the meeting.Pro tipKnow the range: 10% is the floor of a meaningful ask, 20% is where most managers start to baulk. If your case supports 15%, ask for it — but be prepared for it to land as a counter-offer.WarningDo not lead with the development options. The star prize is what you want — present it first and clearly.
- Design the development-time optionIdentify one internal team, project, or initiative where spending 10% of your working week would demonstrably add value to the organisation AND build your own skills or network. This needs to be real — not a vague 'I want to learn more about X.'Pro tipFrame the development time explicitly as a benefit to the manager: 'I could help bridge the gap between our team and the data team — I know that relationship has been a friction point.' That makes it easy to say yes.
- Identify a funded learning or external opportunityName a specific course, conference, qualification, or secondment that would make you more valuable in your role. Calculate its approximate cost so you can present it as a concrete ask, not an open-ended budget request.Pro tipExternal investment signals the organisation's belief in you in a way that internal praise does not — and the qualification stays on your CV whether you remain or leave.
- Sequence the asks with built-in pivotsPresent the salary ask first. If it is declined or deferred, pivot to the development-time option without showing disappointment: 'I understand — could we look at a different structure instead?' If that is also declined, present the learning investment. Sequencing turns a 'no' into a 'next question', not a conversation-ender.Pro tipName the pivot explicitly: 'I have a couple of other things I wanted to raise.' This signals that the conversation is not over, which changes the manager's body language and posture.WarningDo not present all three asks simultaneously — it looks like a demands list and allows the manager to reject the whole bundle at once.
Clarke uses the hypothetical of an employee whose salary ask is declined, proposing instead to spend 10% of their working time with another team. The employee frames this as helping bridge a relationship problem the manager has to manage upward.
Clarke's own ask at Arthur Anderson was non-standard: not more money, but one day per week to build his own business on the side. The managing partner required a business plan and three months of back-and-forth.
Clarke tells master's students that when a pay ask fails, a legitimate secondary request is an internal or external development opportunity — for example, half a day per week working with another team, or funding for a specialist qualification.
This framework emerges from Clarke's observation that pay-rise conversations fail in predictable ways — not because employees lack entitlement, but because they lack a structure for the conversation. He draws on his own three-month negotiation with his managing partner at Arthur Anderson: the initial ask (a day off per week to grow a side business) was met with a counter-request for documentation and a business plan, which felt uncomfortable but ultimately worked. The lesson was that having a clear first ask does not mean it is your only ask — the conversation is a process, not a single moment.