A request filed under the wrong area
It went against the nearest feature name somebody recognised, and it never reached the team that owns it.
Growth
Roadmap
Requests filed where they belong, with the votes kept.
One record per product request: whether it is a new feature or an improvement, which product area it belongs to, which feature it touches, the quarter and the progress. Anyone with read access votes once and comments. The same contract runs in the form and on the server, so a refusal reads the same in both places.
- 8
- product areas a request is filed under
- 8
- rolling quarters in the picker
- 1
- vote per person, toggleable
3 of 3 in Growth
In the workspace
The pages this covers
In the app
What it looks like
Captures of Growth-OS itself, rendered with sample data rather than our own records.
The problem this solves
What goes wrong when this work lives in spreadsheets, documents and one person's memory.
A new bet reclassified as a tweak
Naming an existing feature turns a new-feature request into a refinement. The request type is asked first for that reason.
Progress that drifts
Progress is a typed claim, not a measurement, and the revisions show every jump for what it is.
Highlights
Why it matters
The feature list follows the area
Choose the product area and the feature choices narrow to it. Changing the area clears a feature that no longer belongs.
What is missing says so
Unscheduled, or progress not recorded. A card states the gap rather than leaving a blank where a number should be.
A declined request keeps everything
Votes, comments and revisions stay, so the next person to propose it can read why it was declined the first time.
How it works
From an empty record to something you can act on, in the order you do it.
- 1
Choose the request type
New feature or improvement. An improvement has to name the feature it improves.
- 2
File it against an area
The product area, then the feature within it, then the quarter and the progress.
- 3
Name an owner before it goes active
A request without one is refused rather than quietly activated.
- 4
Let the team vote
One vote per person, toggleable, plus comments. An editor changes the record for it to count.
Honest limits
What this does and does not promise
Progress is a number somebody typed. Nothing computes it from the work.
Search and the status filter narrow the page you are on, twenty-five records at a time, not the whole collection.
Questions
Frequently asked questions
Used alongside this
These pages share records with this one, so what you write here shows up there.
Do this work in Roadmap
The page opens on this project's records. The in-app guide describes every field.