Interfaces

Define What One Team Can Reliably Expect From Another

Interface Pairing Table — requester inputs, deliverer promises, and historical cases that prove whether the agreement is realistic.

Requester · expects
  • Pilot account list with IdP metadata
  • Committed go-live week
  • Escalation when SAML test fails
  • Acceptance: first successful IdP login

Context · Priority · Deadline · Acceptance criteria

Historical cases

Pilot Northwind failed SAML in Week 2 — Engineering had account list but no acceptance criteria from Sales.

  • Case windowRecent Launch cycle
  • OutcomeAgreement incomplete
Deliverer · promises
  • IdP connector ready for named accounts
  • Response within 2 business days
  • Escalate if Security block list hits
  • Reject: incomplete IdP metadata

Outputs · Response time · Escalation · Rejection criteria

Switch pairs — requester, cases, and deliverer update together. Publish syncs the version to team documentation.