Request For Comments (RFC)
A document proposing changes or new ideas for collaborative review and feedback before implementation.
Also known as: RFC, Design Doc, Technical Proposal
Category: Software Development
Tags: software-engineering, collaboration, processes, documentation
Explanation
Request For Comments (RFC) is a collaborative process for proposing and discussing significant changes before implementation. Originating from the IETF's internet standards process, RFCs have become a common practice in software organizations for architectural decisions, API designs, and major features. An RFC typically includes: (1) problem statement - what issue needs solving, (2) proposed solution - detailed approach, (3) alternatives considered - other options evaluated, (4) trade-offs - pros and cons of the proposal, (5) implementation plan - how the work will be done. The RFC process creates documentation, enables asynchronous collaboration, surfaces concerns early, and builds consensus. For knowledge workers, the RFC mindset encourages thinking through ideas thoroughly before acting, inviting diverse perspectives, and creating records of decision rationale. RFCs complement ADRs (Architecture Decision Records) by capturing the discussion process, not just the outcome.
Related Concepts
← Back to all concepts