Created
March 4, 2026 16:48
-
-
Save rodrigozrusso/525ca8f97f01c861ce954248c3ee2bcc to your computer and use it in GitHub Desktop.
PROBE Framework for RFC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # RFC: <Title> | |
| - Author: <name> | |
| - Date: <yyyy-mm-dd> | |
| - Status: Draft | |
| - Reviewers: <names> | |
| - Related docs: <links/JIRA issues> | |
| --- | |
| ## 1. Problem | |
| - What **problem** are we trying to solve? | |
| - Why is this a problem now (impact, urgency)? | |
| - Who is affected (teams, users, systems)? | |
| - What happens if we do nothing? | |
| --- | |
| ## 2. Requirements | |
| - Goals (what success looks like, measurable if possible). | |
| - Non-goals (explicitly out of scope). | |
| - Constraints (technical, legal, timeline, budget). | |
| - Assumptions and dependencies. | |
| --- | |
| ## 3. Options | |
| - Option A – short description. | |
| - Approach. | |
| - Pros. | |
| - Cons. | |
| - Risks/failure modes. | |
| - Option B – short description. | |
| - Approach. | |
| - Pros. | |
| - Cons. | |
| - Risks/failure modes. | |
| - Chosen option and rationale (why this, why not the others). | |
| --- | |
| ## 4. Beta / Proof | |
| - Validation strategy (POC, spike, feature flag, A/B test, canary). | |
| - Metrics to monitor (technical and product). | |
| - Rollout plan (phases, cohorts, fallback). | |
| - Testing strategy (unit, integration, load, security). | |
| --- | |
| ## 5. Execution | |
| - High-level architecture and components. | |
| - Timeline and milestones. | |
| - Ownership and responsibilities. | |
| - Operational plan (monitoring, alerting, runbooks). | |
| - Open questions and next steps. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment