The Project Discovery Brief: the document that stops projects starting on the wrong foot

Without a brief, scope lives in people's heads, and everyone's head holds a slightly different version. The client remembers the verbal aside about "maybe extending it later." The account lead remembers the number in the proposal. The PM inherits both and finds out they don't match three weeks in, usually from a client asking why something "obviously included" isn't on the plan.

A brief isn't paperwork for its own sake. It's the one place all of that gets reconciled before it costs anything.

In scope and out of scope belong on the same page, not just the first one. Out of scope is the line that actually prevents creep later, because "we never agreed to that" only works if there's a document that says so.

Budget, start date, end date and 2-4 key milestones sit alongside scope for a reason: a scope change is really a budget or timeline conversation wearing a different hat. Keeping them on one page means nobody can renegotiate one without the others being visibly in the room.

Every project runs on assumptions nobody says out loud: that a client resource will be available, that a platform will behave a certain way, that last year's numbers still hold. An assumptions log with an owner and a stated risk turns a silent guess into something somebody is accountable for checking.

The stakeholder table works the same way for people. Name, role, interest or influence, and whether they hold decision authority. Half of "stakeholder management" problems are really just nobody having written down that a particular person needed to be in the room from day one.

Scope, budget and timeline changes need one name attached to final sign-off, not a committee. Committees are where decisions go to get diluted into "we'll come back to that." Name the person, and name who covers if they're unavailable, so a stalled decision never becomes the reason a project drifts.

A kickoff meeting on the calendar proves a project has started. It says nothing about what finishing looks like. Definition of done and acceptance criteria, agreed at the brief stage, are what let everyone recognise the finish line when they actually reach it, rather than debating it retrospectively.

A call is a conversation people half-remember. A brief is a reference every person on the project can go back to when memory and Slack threads disagree. It's also the fastest way to onboard anyone who joins after week one, hand them the brief instead of thirty minutes of "let me catch you up."

The Project Discovery Brief is the first template in the PM Hub library, live now for members, mapped to the Brief stage of the Delivery Lifecycle Model. Stakeholder Map, Project Kickoff Deck and Scope Statement pick up from here.