RFC
Topics: Communication
Steve Crocker wrote the very first RFC in 1969 on ARPANET, compiling notes from a meeting of graduate students and staff. He titled his memo “Request for Comments,” or “RFC” for short. Today, the RFC format continues to be computer scientists’ preferred method of introducing new ideas, behaviors, and specifications to the workings of the internet.
The RFC method isn’t limited to technical proposals, though. In all kinds of teams and business situations, especially in a Remote Work setting, the RFC approach can be adopted to build consensus while practicing Asynchronous Work.
Motivation
RFC lifecycle
An RFC can have the following phases:
- Draft: The authors are working on the RFC before asking for wider feedback.
- Feedback: The RFC has been submitted and is waiting for feedback from stakeholders. This phase can have multiple iterations during which the RFC gets continuously improved and refined based on feedback.
- Active: The deadline for comments on this RFC has passed, and the authors have decided to go ahead with it.
- Abandoned: The authors have decided not to move forward with the changes proposed in this RFC.
- Retired: The changes proposed on this RFC aren’t in effect anymore, the document is kept for historical purposes.
Feedback
Not every feedback will be incorporated into the RFC, but reviewers should never feel like they wasted their time contributing. That’s why it’s important that the authors acknowledge every piece of feedback given.
RFC format
A good format to follow in an RFC is the NABC model. It comprises the four fundamentals of the RFC’s Knowledge Base/Value Proposition:
- Need
- Approach
- Benefits
- Competition (alternatives)
Need
An idea without a practical need for it remains just what it is: a good idea and nothing more. On the other hand, the value of a proposed solution has to be measured by how well it resolves a practical issue. Start your RFC with describing the specific problem you’re aiming to solve.
Approach
Only after the specific need is clearly defined, this section now outlines a compelling solution. Text can be accompanied by drawings, diagrams, simulations and mockups that help convey the vision.
As the approach develops through iterations, it becomes a full proposal or business plan, which can include market positioning, cost, deliverables and a roadmap or timetable.
Benefits
The benefits of the proposed approach deserve their own section. What are its effects on cost, performance, time to market, customer satisfaction, brand recognition etc?
Competition/alternatives
The optimal solution can only emerge after multiple alternatives have been considered. A general recommendation for any solutioneering is to come up with at least three options to choose from.
The purpose of this section is to outline the alternative options that were considered, and to highlight their shortcomings compared to the proposed approach.
Example template
# RFC #NUMBER: TITLE
- Authors:
- To be reviewed by: DATE
- To be revisited by: DATE
- State: Draft | Feedback Requested | Active | Abandoned | Retired
## Summary
_A short description of the goal of this document_
## Need
_The need that is addressed by the solution described in the following section_
## Approach
_A detailed description of the proposed solution_
## Benefits
_Compelling advantages of the proposed solution compared to the alternative options described in the following section_
## Competition/Alternatives
_Alternatives that were considered with their shortcomings that ruled them out as the best solution._
## References
_A list of sources and materials related to this document_