Plexii glossary
Project brief
A short document stating why a project exists, what it will produce, for whom, by when and how success is judged.
What it means
A short document that says why, what, for whom, by when and how success will be judged; project brief vs creative brief vs project charter vs statement of work; a one-page structure people can copy.
The term is most useful as a shared description. It does not remove the need to look at the actual task, evidence or constraint in front of you.
A practical example
A one-page brief names the audience, problem, output, owner, date, constraints and measure of success.
Put it into practice
- Name the concrete situation before applying the label. Project brief is useful only when it changes a choice, boundary or next action.
- Make the state visible: write the owner, time, source or stopping condition down instead of relying on memory.
- Review what happened. Keep the part that reduced ambiguity and change the part that added ceremony without helping the work.
How it relates to Plexii
the Project Hub starter puts a Brief page, Goals and Risks stickies and a Decisions log note on a new desk (desk templates); the Page widget’s AI draft writes sections you review before they go in (widget page).