Your client signs a strategic partnership after three months of negotiation. You held firm on the standard terms: strict liability caps, broad IP warranties, extensive audit rights, termination for convenience. The contract protects your client. You did your job.
Six months later the partnership is dying. The other side does the bare minimum, goes quiet, delivers a tenth of what was projected. The CEO asks why this strategic partnership is not strategic. What happened is that you optimised for winning the negotiation and never asked what happens after you win.
We are trained to think one move ahead: close the deal, protect the client, get the best terms. That is first-order thinking — the direct result of the action. But the immediate outcome is rarely the final one. Aggressive IP warranties make the other side defensive about integration. Strict audit provisions signal you do not trust them. Holding multiple cascading consequences in your head while also doing the live legal work is close to impossible, which is exactly where a model helps — not by being smarter, by having no bandwidth limit.
The prompt
I'm considering [decision / action / position] in this situation:
[what I'm trying to achieve, the parties, what's at stake, what I plan
to do]
Map the second-order consequences — not what happens immediately, but
what happens BECAUSE of what happens.
1. IMMEDIATE OUTCOME — the direct result. (What I'm optimising for.)
2. SECOND-ORDER — what does that outcome cause? How do the parties
respond? What shifts in behaviour, incentives, or dynamics?
3. THIRD-ORDER — what happens because of those responses? Where does
this lead if the pattern continues?
For each level: how each party's behaviour changes, what new constraints
or openings appear, which assumptions break, how risks amplify or fade.
Be specific. Don't say "the relationship deteriorates" — say exactly how
and why, and what that deterioration then causes.What the cascade looks like
A mid-sized SaaS company is integrating a fifteen-person startup’s AI features — a market segment worth €5M+ a year. Your client has battle-tested partnership terms: €50k liability cap, broad warranties, heavy audit rights, 30-day termination for convenience. The startup pushes back; they cannot carry unlimited liability and the audit provisions feel invasive. Business development says “just get it done.” Your instinct is to hold firm.
Map it forward. Immediate: the startup accepts after some negotiation fatigue, both sides announce the deal. Second-order: their leadership now sees your client as the corporate partner who squeezed them, so they assign their B-team to the integration, quietly start hedging with your competitors, and default to “what does the contract say?” whenever a problem comes up. Third-order: twelve months in, the integration is functional but undifferentiated, the startup has signed something deeper with a competitor who treated them like a partner, and the market opportunity is gone. The strict terms protected your client from contract risk and guaranteed the partnership would underperform.
So you go back with different terms: a €250k cap — real but not crushing for a fifteen-person company — reciprocal audit rights, termination for cause rather than convenience. You frame it to your client as terms that make the partner invest fully instead of merely comply. Same parties, same technology, a different trajectory — because the question changed from “how do we win this negotiation?” to “what do we want to be true in eighteen months?”
When to map it forward
Before finalising any long-term relationship — partnerships, joint ventures, anything where the parties keep working together. Especially when you hold the leverage, because power imbalances produce the worst second-order effects. And before enforcing a right: being correct and being effective are not the same thing. The win in front of you is easy to see. What it sets in motion is the part worth slowing down for.