Positioning design-first

Lead with the outcome, not the tool

When you guide a customer toward design-first, start with the pain they already feel — late integration, breaking changes, duplicated effort — and connect the practice to the relief.

A simple framing

• Today: teams wait on each other, surprises ship, work gets rebuilt.
• With design-first: the contract comes first, work runs in parallel, changes are deliberate, assets get reused.
• The platform's part: API Designer, Exchange, mocking, and Governance make the practice low-friction.

Keep it concrete

Show, do not tell. A ten-minute live path — spec, mock, consumer calling the mock — lands harder than any slide. Let the customer feel the parallel-work moment.

Coaching note

Your job is to help the customer succeed with the practice, not to admire the features. Anchor every capability to a problem they named. If they did not name the problem, ask more questions before showing anything.