What’s the minimum viable set of rituals to start with?

Start with a 15‑minute dependency standup, repo‑native ADRs with a 48‑hour decision SLA, and a change calendar wired to PagerDuty Change Events. Those three reduce 80% of cross‑team surprises.

We already have CABs. How do we move to guardrails?

Keep CABs for teams breaching error budgets. For everyone else, require green SLOs, passing OPA policies, and progressive delivery. Publish this as policy and enforce it in CI/CD.

How do we measure collaboration quality?

Track decision-to-doc time, cross‑team blocker age, contract test coverage, and cross‑repo PR lead time. Pair with DORA metrics and MTTR. Set targets and review weekly.

What about AI‑generated code and ‘vibe coding’?

Treat AI output like a junior engineer’s PR. Enforce PR templates, require tests, and run linters. Budget time for vibe code cleanup and refactoring. Document risks in ADRs and risk registers.

Culture · Dec 7, 2025 · 10 minute read

The Cross‑Functional Rituals That Saved Our PCI Re‑Platform (And the Ones That Almost Killed It)

You don’t fix complex initiatives with standups and vibes. You fix them with crisp rituals, visible ownership, and telemetry-backed decisions. Here’s the playbook we use when the stakes are regulatory, the architecture is messy, and the calendar is unforgiving.

Back to all posts

The Cross‑Functional Rituals That Saved Our PCI Re‑Platform (And the Ones That Almost Killed It)

Key takeaways

Implementation checklist