We use RFCs (Request for Comments) to design significant technical changes collaboratively.
When to write an RFC:
- New product features or major changes
- Architecture decisions that affect multiple systems
- Breaking changes to APIs or interfaces
- Complex technical problems requiring research
RFC process:
- Write the RFC document with problem, solution, alternatives
- Share for async feedback and iteration
- Schedule RFC review meeting if needed
- Get approval from relevant stakeholders
- Use RFC as implementation guide