Objections as coaching moments

Reframe resistance as a question

Objections are rarely disagreement — they are usually an unanswered concern. Treat each as a prompt to coach, not a wall to push against.

Common objections and how to guide them

• "Design-first slows us down." Guide them to a small spec and a mock in one session; the parallel-work gain shows up immediately.
• "We already have Swagger files." Great — those are OAS specs. Publish them to Exchange and apply governance; you are closer than you think.
• "Governance will block our teams." Introduce rulesets as warnings first; demonstrate fast author-time feedback, not a bureaucratic gate.
• "Nobody will reuse the assets." Make Exchange searchable and celebrate the first reuse publicly; reuse is a culture you cultivate.

The pattern

Acknowledge the concern, ask a clarifying question, then show the smallest proof that addresses it. You are guiding to success, not defending a product.

Coaching note

Keep a running list of the objections you hear across customers. Patterns across accounts are the most valuable thing you can bring back to the team.