How to Lead an RFC Discussion in English
Learn the English phrases for facilitating a technical RFC discussion: framing trade-offs, managing disagreement, and driving toward a decision.
Leading an RFC discussion well means keeping a room full of strong opinions moving toward an actual decision, rather than letting the conversation circle the same trade-offs indefinitely.
Opening the Discussion
Set the scope and goal for the session clearly before diving into details.
- “The goal of this discussion is to reach a decision on the approach, not to re-litigate whether we need to solve this problem at all.”
- “I’d like us to focus specifically on the open questions in section three — the rest of the document is considered settled unless someone objects strongly.”
- “Let’s timebox this to thirty minutes and capture anything unresolved as a follow-up rather than trying to close every thread today.”
Framing Trade-offs Neutrally
Present competing options without signaling a predetermined answer.
- “Option A is simpler to implement but adds latency; option B avoids that latency at the cost of more operational complexity — I want to hear where people land on that trade-off.”
- “Neither option is strictly better here — it depends on whether we’re optimizing for time to ship or long-term maintainability.”
- “I want to make sure we’re comparing these fairly — can someone who prefers option B state the strongest case for it?”
Managing Disagreement Productively
Acknowledge disagreement without letting it stall the discussion.
- “I hear two clearly different positions here — let’s make sure we understand the reasoning behind each before deciding.”
- “This sounds like a disagreement about risk tolerance more than about the technical facts — is that a fair characterization?”
- “Let’s separate what’s a genuine blocker from what’s a preference, so we don’t block a decision on a preference.”
Surfacing Silent Disagreement
Draw out concerns from people who haven’t spoken up.
- “I want to check in with anyone who hasn’t weighed in yet — does this direction raise any concerns for you?”
- “Before we move forward, is there anyone who feels strongly enough about a different approach that we should hear it now rather than after the decision is made?”
Driving to a Decision
Close the discussion with a clear, recorded outcome.
- “Based on this discussion, I’m going to move forward with option A, and I’ll note the concerns raised about latency as a follow-up risk to monitor.”
- “It sounds like we have rough consensus — I’ll update the RFC to reflect this decision and circulate it for final sign-off.”
- “We don’t have consensus yet, so I’ll take the open question offline with the two people most affected and bring back a recommendation.”
Vocabulary Reference
| Term | Meaning |
|---|---|
| RFC (request for comments) | A written proposal circulated for team feedback before a decision is finalized |
| Timebox | A fixed time limit set on a discussion to keep it moving |
| Rough consensus | General agreement sufficient to proceed, even without unanimous support |
| Blocker | An objection serious enough to prevent moving forward without resolution |
| Sign-off | Formal approval indicating a decision is finalized |
Key Takeaways
- Open by stating the discussion’s scope and goal so the conversation stays focused on reaching a decision.
- Present trade-offs neutrally, without signaling a preferred answer before hearing the room.
- Distinguish genuine blockers from preferences so a decision isn’t stalled unnecessarily.
- Actively invite input from quieter participants before finalizing a direction.
- Always close with a clear, recorded decision or a concrete next step if consensus isn’t reached.