How to write a project brief your PM doesn't rewrite

A senior PM I used to work with had a small tell. When she liked a project brief, she’d reply in the thread with a one-line “let’s go.” When she didn’t, she’d reply with a new version of the brief, pasted directly into the thread, with no comment. No feedback, no “here’s what I changed” — just the new version, implicitly saying this is what I needed.

It is the most demoralizing feedback form in corporate life. Nothing’s wrong, per se. The brief just wasn’t the brief she needed.

The good news: the thing that usually breaks isn’t writing. It’s structure. If your PM keeps rewriting your briefs, the fix is to mimic the structure she uses, not to write better sentences.

The six-line brief

Here is the skeleton that almost always works. Fill in one line per section. Expand only if you have to.

Problem: [what's broken or what's changed]
Audience: [who feels it, in one sentence]
Proposal: [what we're doing about it]
Success: [what changes if we ship]
Scope: [what's in, what's out, explicitly]
Open: [what we still need to decide, with names]

Six lines. That’s a brief. Everything else is supporting material — timelines, dependencies, risks, data — that comes after the six-line top.

Most first-year briefs fail for two reasons. They either skip the six lines entirely and start with context, or they combine two lines into one and lose precision.

The two lines most people get wrong

Audience. “Users” is not an audience. “Enterprise buyers who are trialing but haven’t converted in 14 days” is. The audience line is where specificity buys you the most credibility. If a senior PM can’t picture the person in one sentence, they’re going to rewrite your brief to force that picture in.

Success. “Drive engagement” is not success. “Reduce trial-to-churn from 42% to 30% within 60 days of launch” is. Success is the thing you’d commit to being graded on. If you wouldn’t sign up to be graded on it, it’s not specific enough.

Fix just those two lines and half your rewrites disappear.

The line people forget

Scope. Scope is where senior people notice junior PMs. A brief that says “we’re going to improve the trial experience” and doesn’t say what’s in and what’s out will get rewritten every time, because without explicit scope, the PM has no idea how big the project is.

In scope: [one to three things you will do]
Out of scope: [one to three things you will NOT do, even though someone will ask]

That second sub-line is the one that earns the most credibility. It shows you’ve already absorbed the “yes but what about…” questions. It signals judgment.

What the senior rewrites usually change

If you do get a rewrite, read it carefully and look for the pattern. Nine times out of ten, the senior version does one of these:

1. Tightens the audience line. “Users” becomes “enterprise buyers on the 30-day trial who dropped off after creating one project.”
2. Makes success numeric. “Improve conversion” becomes “+5pp trial-to-paid in Q2.”
3. Adds an explicit out-of-scope. “We are not redesigning the onboarding flow.”
4. Adds names to the open questions. “Pricing TBD” becomes “Pricing: need Jen’s sign-off by Tuesday.”

If that’s the rewrite pattern, you can pre-empt it. Those four moves are the standard tells of a brief that’s ready for senior review.

Where this goes wrong: the context dump

A common junior move is to open the brief with two or three paragraphs of context. Why this is important. What the company is trying to do. Where this fits in the roadmap.

That writing is not wrong. It’s in the wrong place. It belongs as an appendix, not an opener. A senior reader wants to know in six lines whether to read the rest. Context before substance makes them start skimming.

Flip it. Six-line brief at the top. “Why this matters” at the bottom, for anyone who wants to read more.

The phrase to steal from senior PMs

“Explicit non-goals.”

Almost every senior project brief has a section called “non-goals” or “explicit out-of-scope.” It tells the reader what you’ve deliberately decided not to do. This is the line that turns a brief from “a description of work” into “a decision about work.”

Copy it. Use it on every brief. You’ll look senior for free.

The test before you send

Read the top six lines out loud. If a colleague who’s been on vacation for a week could read those six lines and say “got it, here’s what we’re doing and who it’s for” — you’re done. If they’d have to ask a follow-up to understand the gist, the brief isn’t ready yet.

—

The version of you that got rewrites was producing a description of the work. The version that gets “let’s go” is producing a decision about the work. That’s the only difference. Once you see the structure, you can’t unsee it.

For the related skill of one-page summaries that executives actually read, see what is an executive summary?. For the status update rhythm that keeps projects visible after the brief is approved, see the status update template.