Your API Design & Governance coaching compass
A quick pre-session checklist to walk in ready to guide the customer.
Discovery questions
- How do your teams document APIs today — before or after implementation?
- Where do consumers go to find an existing API? Is there a reuse hub?
- Do you have written API standards, and are they enforced or aspirational?
- What happened the last time an API change broke a consumer?
- Is there a C4E or central team curating reuse and standards?
Talk track
- Open with the customer's named pain, not a feature tour.
- Connect design-first to parallel work, early feedback, and reuse.
- Position governance as warnings-first, fast feedback — an enabler.
- Frame the C4E as a multiplier measured by reuse, not approvals.
- Anchor every capability to a problem they actually described.
Demo flow
- Spec in API Designer: one resource, with a response example.
- Toggle the mocking service and call the mock live.
- Publish to Exchange; show the asset and its versioning.
- Apply a governance ruleset and read the conformance report.
- Optionally show the developer portal / Experience Hub listing.
Follow-ups
- Share the RAML vs OAS cheatsheet and help them pick one per program.
- Co-author a starter ruleset with their architects (warnings first).
- Agree a small first spec the team will ship and mock this week.
- Capture objections you heard to bring back to the SG team.