How to write PRD non-goals that stop scope creep
A step-by-step guide to writing PRD non-goals with reasons and revisit triggers, so scope stops growing quietly during build and review.

Most PRDs have a goals section and an empty or vague non-goals section. Then build starts, someone asks for just one more thing, and nothing on the page says no. This guide shows how to write non-goals that do that job.
- A non-goal is something a reasonable person would expect, which you are choosing not to do now.
- Give each one a reason and a revisit trigger.
- Label it: not now, not ever, or not our decision.
- Put the list right after the goals and read it aloud at kickoff.
Product managers at startups and mid-size companies who write PRDs and keep hearing “can we also just add…” from stakeholders and engineers. At the end you will have a non-goals section you can point to when that happens.
Step 1: Know what counts as a non-goal
A non-goal is not a list of things you would never do. It is something a reasonable person might expect you to do, and you are deciding not to do it now.
That test removes the filler. “We will not rebuild the billing system” is not a non-goal for a small export feature. Nobody expected it. A non-goal earns its place only if someone could, in good faith, ask for it in review.
The steps
Collect candidates
Look in five places: stakeholder requests you already declined, adjacent user segments, other platforms, edge cases, and “phase 2” items that keep coming up in reviews. If the same item has been raised twice, it belongs on the list.
Sort them into three kinds
Not now, not ever, or not our decision. Each kind is handled differently, as the table below shows.
Write a reason and a trigger
One short reason per item: cost, timing, risk, or unproven need. Then a revisit trigger: a metric, a count, or a date.
Place them after the goals
Put the section directly after goals, not in an appendix. Goals say what you will do. Non-goals say where that stops. Readers should see both together.
Read them aloud at kickoff
Go through the list out loud with design, engineering and stakeholders. Ask who disagrees. An objection in kickoff costs a conversation. In week five it costs a replan.
Revisit after launch
Check each trigger once the feature is live. Move items into scope, keep them out, or delete them. A list nobody reopens turns into a graveyard.
Sorting: three kinds of non-goal
Lumping everything under “out of scope” hides what each item needs from you. Separate them.
| Kind | What it means | How to handle it |
|---|---|---|
| Not now | Reasonable, but the cost, timing or evidence is not there yet. | Write a reason and a revisit trigger. Review it after launch. |
| Not ever | It conflicts with the product’s direction or the user you serve. | State the reason plainly. No trigger needed, but say who decided. |
| Not our decision | Another team or owner decides, such as legal, security or a platform team. | Name the owner and what you need from them. Do not promise an outcome. |
The third kind is the one people skip. If a request depends on a decision outside your team, saying “no” is wrong and saying “yes” is a promise you cannot keep. Naming the owner keeps the request moving without putting it in your scope.
Writing each one: reason plus trigger
A bare list invites argument. “No scheduled exports” sounds like a preference, and preferences can be argued with. “No scheduled exports, because we have not shown people need them; revisit if requests pass a set count” is a decision with terms.
Keep the reason to one of four types: cost, timing, risk, or unproven need. If you cannot pick one, you may not have a real reason yet. The trigger can be a metric, a count of requests, or a date. It tells the person asking what would change your answer, which is usually all they want to know.
Worked example: bulk CSV export
Say you are writing a PRD for bulk CSV export in a B2B dashboard. The goal is simple: admins can export up to 100k rows. Here is the non-goals section before and after.
- Advanced export features are out of scope.
- We will not support every format.
- Other roles later.
- Real-time stuff TBD.
- Scheduled exports. Not now. Unproven need. Revisit if we get over 20 requests per quarter.
- Excel formatting. Not now. The goal is a clean CSV, and formatting adds work without proving the core. Revisit if people keep asking after launch.
- Export for viewer roles. Not now. Letting more roles take data out is a risk we have not scoped. Admins only for v1.
- Real-time streaming. Not in this feature. It is a different problem from a one-off file download.
See what changed. The vague version cannot be checked, so an engineer asking “is Excel formatting advanced?” gets no answer. The specific version answers before the question is asked. It also gives the scheduled exports request a number: if the 21st request arrives in a quarter, the decision reopens on its own terms.
The reasons here are short on purpose. One line each is enough. If you draft your PRD in the PikoPM PRD tool, or in any other document, the same rule holds: one line, one reason, one trigger.
Mistakes that make non-goals useless
- Listing absurd items to look thorough. If nobody would ask for it, it is not a non-goal. Padding hides the ones that matter.
- Giving no reasons. Without a reason, every item is an invitation to negotiate.
- Hiding the section at the bottom. If readers stop before it, it does nothing. Put it next to the goals.
- Treating them as permanent. Most are “not now.” Say so, and say what would change that.
- Never revisiting them after launch. The triggers only work if someone checks them. Put a review on the calendar.
A quick check before you share the PRD
Read your non-goals as if you were the stakeholder who asked for something. Can you find your request? Can you see why it was set aside, and what would bring it back? If yes, you have given them an honest answer in writing, which is what stops the quiet growth. If no, fix that line before kickoff, not after.


