diff --git a/requests-for-comments/2022-12-01-workflow-new-feature.md b/requests-for-comments/2022-12-01-workflow-new-feature.md
new file mode 100644
index 0000000..57fe692
--- /dev/null
+++ b/requests-for-comments/2022-12-01-workflow-new-feature.md
@@ -0,0 +1,60 @@
+# The first "Workflow": MVP for "Creating a new feature"
+
+Owner: @EDsCODE (team experimentation)
+Decision to be made: Should we build this in Q1 as part of team experimentation?
+Decision date: 7th December 2022
+
+## Context
+
+This RFC proposes that team experimentation builds the MVP of a workflow for "Creating a new feature" as part of their Q1 OKRs.
+
+It should sit with team experimentation as it would be a key driver of feature flag usage.
+
+This could have multiple benefits across the product:
+
+- Making PostHog the first place that product engineers go when building a new feature
+- Increasing cross-product usage (feature flags, product analytics, session recordings)
+- Encoding the best practices for PostHog and external engineers to use to build check for feature success without using PM time
+
+*This is context for the engineers leading it and should be iterated*
+
+## What's a workflow?
+
+So far we have given product engineers the individual tools to create trends, create funnels, watch recordings, create feature flags etc.
+
+We have the opportunity to connect these flexible tools with opinionated best practices to focus on specific jobs-to-be-dones in PostHog. These could be called "Workflows".
+
+Some examples of potential workflows:
+
+1. Creating and shipping a new feature - assisting with rollout and measuring success *More details below*
+2. Workbooks - making it easy to come up with questions, save related insights, clip particular bits of recordings and jot down thoughts
+3. Iterating on existing features - making sure the new feature is better than the previous iteration
+4. Conversion experiment - making sure that the funnel metrics improve (including quality of new customers)
+5. Fixing bugs - understanding what's broken and confirming that the fix works
+
+## Vision for "Creating a new feature" workflow
+
+Here's the vision of what this could be in 3 - 6 months:
+
+Sarah is a product engineer at a high-growth startup building a B2C website to help companies offset their carbon - called Carbon.io. She's working on a new feature for users to watch videos of their carbon-offsetting projects. She hypothesizes that users who watch these videos will feel more connected to the projects and retain at a higher rate.
+
+The first thing Sarah does is open up PostHog and start the workflow for "Create a new feature". It opens up a page to create the new feature where she names it "Videos of offsetting projects". Optionally, she can enter some of the background information on this feature including the hypothesis. She selects "auto-rollout" rather than "A/B test" - meaning once the feature is made it will be used internally and after manual approval will be rolled out to beta users then low-value users then high-value users. She selects "user retention" as the key metric.
+
+Sarah clicks "Done". PostHog automatically creates a feature flag to control the rollout; sets up a dashboard containing session recordings of people using it; and creates the relevant graphs.
+
+Sarah builds the feature between the feature flag and merges it to main branch.
+
+Sarah pings her team to give it a go on a few different devices. When 5 internal users have used the feature PostHog sends her a slack message to the playlist. She reviews it and the error logs - it's all working fine so she gives the thumbs up to escalate to beta users. There are no errors in beta and so it automatically deploys to prod as a phased release - sending her a slack message to her team to keep them in the loop. PostHog automatically invites 2 users to a user interview after having used the video feature *Luke is working on an MVP for the user interviews feature - can be out of scope for the MVP*.
+
+From the dashboard, Sarah learns most of the users are only watching the first 30 seconds of the 5-minute videos. During the interviews, she asks them what they thought of the videos and while they enjoyed them they said they were too long and dry. Sarah organizes a new set of videos to be made and rolls out an update.
+
+3 months later Sarah gets a slack message from PostHog to view the retention graph. They can see there's a significant correlation between retention between users that watched a video and users who retained. Success!
+
+## Potential features
+
+1. PostHog should be the starting point when you create a new feature. As the first step, you will create a feature flag. Potentially a VSCode integration or CLI tool can help with this.
+2. When the feature is ready for Beta testing, the engineer can enable the feature for a beta tester cohort or select a pre-defined rollout schedule. This way, he doesn’t have to decide who to release it to on a case-by-case basis.
+3. Users can subscribe to feature flags, so when changes have been made to a flag, e.g. a rollout, they will be notified. This way, everyone else in the team knows about the status of a feature release.
+4. When a feature is rolled out, PostHog automatically monitors relevant metrics and regressions. If those are above a certain threshold, the rollout is stopped and the relevant people are informed.
+5. On a flag itself, there is information on how many users are currently on one of the variants and when this information was last fetched. The idea here is that we distinguish whether a flag is rolled out according to the PostHog interface, but it is in fact not available in the code (anymore).
+6. Once a feature flag has been rolled out to the whole user base for x days/weeks, the relevant people are informed to archive the feature flag to prevent tech debt.