Become Negotiator

Proof required

Submit a pre-negotiation planning document: BATNA, target outcome, walk-away point, and an interests-not-positions analysis of the other party (what do they actually want to achieve beyond their stated position?). Submit a post-negotiation debrief: outcome summary (numbers or concrete terms), the most significant moment in the negotiation, one thing you wish you had done differently, and confirmation that the deal was closed (signed, accepted, or agreed — not just 'it went well').

What gets checked

• BATNA is specific and actionable — 'find another job' is not a BATNA; 'accept the counter-offer from [Company B] at £65,000' is a BATNA that gives you a real walk-away point
• Interests analysis names the other party's underlying goals — 'they want a lower price' is a position; 'they are running thin margins and need to reduce fixed costs before their Q3 reporting deadline' is an interest
• Post-negotiation debrief names a specific moment — not 'the negotiation went well overall'; 'when they paused after I named my number and didn't speak for 8 seconds, I filled the silence by offering a concession I hadn't planned to offer' is specific

Common mistakes

• A negotiation where you accepted the first offer without any back-and-forth — a 'negotiation' where you asked for X and they agreed is a request, not a negotiation; the material must evidence genuine back-and-forth with at least one exchange of concessions
• Interests analysis that describes the other party's position rather than their interests — the most common error is saying 'they want to pay less' (position) instead of 'they need to preserve budget for a supplier dispute they have in Q4' (interest); these require genuinely different preparation and tactics
• A deal that was never closed — the debrief must confirm closure; a negotiation that ended in 'we'll follow up' without a documented outcome did not produce the evidence needed

Resources

What a verifier looks for

• Ask the submitter to name their BATNA and their walk-away point and whether those two things are the same — many submitters confuse BATNA (the alternative) with the walk-away point (the minimum acceptable outcome); they are different and the distinction matters
• Ask what they said in the most significant moment they documented in the debrief — if they cannot reconstruct it reasonably from memory, it was not a genuinely significant moment to them
• Ask what the other party's primary interest was and how they know that — the quality of the interests analysis is the single strongest predictor of negotiation skill; a submitter who inferred interests from facts rather than from asking is more advanced than one who assumed them
• Ask what they would do differently — the one-thing-differently answer in the debrief is the most revealing; a generic answer ('prepare more') has not produced genuine negotiation learning

You'll sign in first, then come straight back here.

Proof required

Submit your framework document (the 5 components, one paragraph each). Submit the pre-negotiation planning document for the second negotiation (completed from the framework). Submit a post-negotiation framework audit: for each component, a sentence on what the framework called for and one sentence on what actually happened — and one overall revision to the framework based on what you learned.

What gets checked

• Framework components are prescriptive, not descriptive — 'anchoring: set a high anchor early' is not a component; 'anchoring: open with an extreme anchor (30–40% above target) framed as a reasonable starting point, and justify it with a named rationale, not just a number' is
• Post-negotiation audit addresses every component — not every component will produce learning, but each must be accounted for; 'N/A — didn't use this one' is a valid entry and reveals something important about when the component applies
• Framework revision is a specific change, not a general reflection — 'I need to prepare more' is not a revision; 'moving opening strategy above information gathering because I tend to anchor before I've finished researching their situation' is

Common mistakes

• A framework that is a summary of a book chapter rather than a personal system built from M1 experience — the framework must be derived from what you learned in M1 and tested in M2; it must show evidence of personal construction
• Post-negotiation audit that is purely positive — a framework applied to a real negotiation always produces at least one failure mode or gap; a clean 'everything worked' audit is a documentation failure, not a performance success
• A second negotiation that is lower stakes than the first — the framework should be tested at least at the same stakes level; the most common way to game the requirement is to apply the framework to a trivial negotiation where the framework's quality cannot be evaluated

Resources

What a verifier looks for

• Ask the submitter to apply one framework component live — pick a simple hypothetical (salary negotiation, £50K asked / £45K offered) and ask them to walk through their concession strategy step by step; this distinguishes a documented framework from an internalised one
• Ask which component changed most between M1 and M2 — the framework should be visibly different from what a first-principles M1 debrief would have produced; if it is identical to M1's lessons, no framework development happened between negotiations
• Ask what the framework does not cover — the most important constraint on any framework is its scope; a submitter who can name what their framework is not for has thought about it more carefully than one who describes it as universal
• Confirm both negotiations are at meaningful stakes — if M2 was a £20 freelance negotiation and M1 was a £40K salary negotiation, the framework has not been tested at comparable stakes

You'll sign in first, then come straight back here.

Proof required

Submit your M1 debrief and M2 framework plus the reviewer's written assessment: the framework weakness challenge and your response, a brief per role-play scenario (what the reviewer played, what the submitter did, what worked and what didn't), and their sign-off confirming their role and a live session.

What gets checked

• Framework weakness challenge response names the scenario type where the framework fails and what you would do in that scenario — not 'I'll adapt' but 'my framework doesn't handle multi-party negotiations where I have two principals with different interests; in that case I'd need to negotiate internal alignment first'
• Role-play briefs name a specific technique used in each scenario — not 'I tried to build rapport' but 'I used a calibrated question — what's most important to you in this deal? — to defer the price discussion until I had mapped their priorities'
• Multi-party role-play brief acknowledges at least one coalition dynamic — in multi-party negotiations, the most important skill is managing relationships among the other parties; the brief must show awareness of this

Common mistakes

• Role-play briefs that describe outcomes rather than tactics — 'we reached a deal' is not a brief; 'I used a late concession to close — I offered free delivery only after they had accepted the core price, making the concession feel significant while protecting the margin I had planned to give from the start' is
• A reviewer who is primarily a negotiation trainer rather than a practitioner — the role-plays require someone who has personally navigated high-stakes negotiations with real consequences; a trainer who teaches negotiation without regular personal practice will not create realistic pressure in the scenarios
• Framework weakness challenge response that is defensive — the reviewer is testing whether the submitter has a clear understanding of their framework's limits, not whether the framework is without limits

Resources

What a verifier looks for

• The multi-party scenario should have at least 3 parties (the reviewer plays 2 counter-parties with different interests) — the submitter must navigate the fact that satisfying one counter-party's interest partially conflicts with satisfying the other's
• After each role-play, ask the submitter what their biggest mistake was before giving your own assessment — self-diagnosis accuracy is one of the clearest markers of negotiation maturity
• Reviewer minimum qualification: 5+ years of high-stakes negotiation with personal accountability for outcomes (not advisory or training-only roles); M&A, procurement, commercial, or senior sales with quota ownership are all acceptable
• The framework weakness challenge should target a specific real scenario from the submitter's professional life — 'what would break your framework if you had to negotiate with someone who had significantly more information than you?' is a more productive challenge than a generic 'what's the weakness?'

You'll sign in first, then come straight back here.