A fractional CMO wants to scale acquisition; the fractional COO expects onboarding to break. Both can understand the strategy and still rationally oppose each other's recommendation. Their disagreement may concern forecasts, acceptable risk or who will absorb the extra work.
An effective alignment workshop makes those differences operational. It specifies what can be committed now, which observation releases the next commitment, and whose capacity must exist when that happens. Teams Facilitator can guide the live framework discussion while you contribute your expertise; the decision design below supplies the substance.
Separate belief conflict from value conflict
Ask each leader to complete two sentences: “I expect this action to produce…” and “Even if that forecast is right, I would object because…”. The first exposes disagreement about consequences. The second exposes different objectives or unacceptable costs.
For example, the CMO expects ten new customers and the COO expects four. That forecast can potentially be tested. If both expect ten but disagree over whether existing delivery commitments may move, the sponsor must choose the tradeoff. A test cannot decide whose objective deserves priority.
Roger Schwarz's mutual-learning guidance recommends making reasoning visible and combining advocacy with inquiry. State your authority separately from your recommendation: “I own campaign execution, but the founder owns changes to delivery commitments. Here is the evidence behind my forecast.”
Convert a forecast disagreement into a contingent commitment
Harvard's Program on Negotiation describes contingent agreements for parties with different expectations about future outcomes. Adapt the logic to an internal resource decision: authorize a limited action now and make the next action depend on observable results.
Consider a fictional campaign. Marketing believes it can generate qualified demand; delivery believes most interested prospects need custom work. A useful agreement distinguishes demand from serviceability:
| Element | Proposed rule |
|---|---|
| Initial commitment | One standard offer to a defined buyer group; fixed spend and founder-hour caps |
| Demand gate | Signed paid pilots from eligible buyers within the observation window |
| Delivery gate | Each pilot fits the standard package and has a named delivery slot |
| Release | Founder authorizes the next capped batch after both gates pass |
| Failure response | Stop spend at the cap; diagnose the failed gate before redesigning |
| Expiry | Authorization ends on the review date unless explicitly renewed |
Specify what happens when the gates disagree. Strong demand with uneconomic delivery requires changing the offer or model. Available capacity without purchases requires revisiting demand. Calling either outcome “partial alignment” obscures the decision.
Make the condition observable and hard to game
“Qualified pipeline” is too elastic if the campaign owner can change qualification after seeing results. Define buyer eligibility, accepted evidence, attribution window and exclusions before launching. A verbal expression of interest and a signed standard pilot should remain different events.
Assign measurement and interpretation roles. The revenue owner verifies signed pilots; delivery verifies scope and capacity; the founder resolves the resulting tradeoff. Let the campaign owner explain anomalies without becoming the sole judge of whether their gate passed.
Examine incentives through an awkward case. Could a heavily discounted pilot pass the demand gate while destroying contribution? Could a delivery owner block every release by declaring capacity unavailable? Add a price condition and a visible capacity schedule where those problems are plausible.
Use paired measures that preserve the objective: eligible paid pilots alongside delivery effort, or acquisition volume alongside contribution. Ten additional dashboard metrics will not repair an ambiguous release condition.
Test coupling between commitments
A reversible campaign can trigger harder-to-reverse obligations. Customers may receive delivery promises, sales may sign annual tooling, or engineering may pause another release. Map those dependencies before describing the trial as low risk.
For every commitment, ask what must be undone, who bears the cost and whether reversal remains possible after the next step. Cap exposure at the coupled system level. A €1,000 media limit means little if it creates €20,000 of unapproved implementation work.
Retain the option to stop by defining a maximum batch size and avoiding promises beyond the trial's authority. If delivery capacity is reserved provisionally, state when it expires and which other work can reclaim it.
These are supporting operating rules. A Bullseye session structures channel exploration and tests; Business Model Canvas examines revenue and delivery dependencies; SWOT examines strategic constraints. Choose the live framework around the disputed business question.
Use sensitivity to avoid negotiating meaningless precision
Ask: “At what onboarding effort would we stop supporting this offer?” Suppose the contribution case changes sign at 12 delivery hours per customer. An argument over whether the estimate is six or eight hours may not change the immediate choice. A plausible range of six to 20 hours deserves investigation.
Also test the uncomfortable joint case: weaker conversion and higher delivery effort together. Separate optimistic assumptions can compound into an implausible plan. Assign a small scoping task if its result could materially change the commitment.
When the disagreement is genuinely about risk appetite, make that visible to the sponsor. Do not manufacture a probability estimate merely to conceal a preference about which downside is acceptable.
Rehearse failure before recording agreement
Use Gary Klein's premortem method: assume the proposed trial has failed and ask each function privately for a plausible causal chain. Then translate the most consequential chains into operating changes.
“Delivery becomes overloaded” becomes: the campaign succeeds, customers demand simultaneous starts, the same specialist handles every setup, and existing customers lose support. The preventive response might be staggered start dates, a batch cap or explicit displacement approval. Assigning “monitor delivery” would leave the mechanism intact.
Finish with an independent restatement from each owner. Ask them to apply the rule to one real upcoming customer and one exception. If their answers differ, correct the condition before closing.
Keep the reviewed decision, strongest objection, release evidence and expiry in the session record; transfer execution into the client's work system. On your next fractional engagement day, review the gate and its exceptions. Reopen the strategy when assumptions change, rather than when an influential participant simply dislikes the result.
Prepare independent inputs, or use the first-month diagnostic to identify the decision worth testing. Start the guided workshop with the contingent commitment ready to challenge.