METHODS / BRIEFINGS, MEETINGS, AND COMMUNICATION / WRITTEN BRIEF MEETING
METHOD
Written Brief Meeting
A written brief meeting uses one short page as the shared source of context before, during, and after a meeting. The page states the outcome needed, presents the relevant facts and tradeoffs, and becomes the place where the final decision and actions are recorded.
WHERE IT COMES FROM Atlassian, the Page-Led Meetings play
A consequential decision where several functions need the same facts, and a stalled project where participants hold different versions of reality. The Fit section below lists the rest.
The page still needs a clear meeting outcome and a named decision owner. Written context cannot resolve unclear authority on its own.
WHAT IT IS
How the page supports the meeting.
A short written brief reduces the time spent rebuilding context in the meeting. It gives participants the outcome needed, relevant evidence, options, tradeoffs, and a recommendation in a form they can review before discussion.
During the meeting, participants correct the facts and discuss the decision. Afterward, the same page records the confirmed outcome, owners, open questions, and actions that move into the decision log or project system.
THE PAGE
What to include in the brief.
Aim for three to five minutes of reading for an ordinary leadership meeting. Use a longer format only when the decision genuinely requires it.
- Outcome needed: decide, advise, approve, or unblock
- Decision or question, in one clear sentence
- Context: only what participants need to understand the issue
- Evidence: relevant facts, source, and material uncertainty
- Options: viable choices and their tradeoffs
- Recommendation: the page owner's proposed path and reasoning
- What could change the recommendation
- Outcome record: decision, rationale, owner, due dates, open questions
FIT
When a written brief meeting is useful.
Reach for it when
- Several functions need to make or advise on one decision.
- A project is stalled because participants hold different versions of the facts.
- Leadership must compare options and tradeoffs.
- A proposal, operating change, or investment needs structured review.
- The result must remain understandable after the meeting ends.
Choose another format when
- The update can simply be read asynchronously.
- It is an announcement.
- It is live incident response.
- It is early ideation, where a polished page would narrow thinking too soon.
- It is sensitive conflict or relationship repair.
- The real disagreement is political, and the page is being used to avoid it.
HOW TO RUN IT
Use the page before, during, and after the meeting.
EXAMPLE
Choosing how to handle implementation capacity.
A SaaS company can support three customer implementations, but five are scheduled. Leadership must choose among temporary contract capacity, delaying two customers, or reducing implementation scope.
The operations lead prepares a short page with the capacity data, customer commitments, churn exposure, temporary labor cost, three options, a recommendation, and the assumptions that need review. Participants read it, correct two facts, discuss the tradeoffs, and make one decision. The confirmed rationale goes to the decision log, and the actions go to the project system. This example is fictional.
KEEP IT USEFUL
Common implementation and participation considerations.
Common implementation issues
- A long document with no visible decision request.
- A slide deck rewritten as paragraphs.
- Selective evidence that supports only the author's preferred answer.
- A facilitator who presents the page instead of opening the decision.
- No named decision authority.
- Decisions and owners left off the page after the discussion.
- Polished writing that hides uncertainty.
- Silence from junior participants treated as agreement.
Framing and participation
- The author controls the initial frame. Let affected contributors correct the factual record and name missing viewpoints.
- Separate evidence from assumptions on the page itself.
- Include a direct prompt: "What could make this recommendation wrong?"
- Restrict confidential pages, and offer an accessible format for different reading, language, and disability needs.
AI AND JUDGMENT
Use AI to assemble the brief. People set the question and make the decision.
AI can help
- Draft the page from approved reports, notes, messages, and project records.
- Compare source material and flag missing facts, conflicting figures, or open questions.
- Organize options and tradeoffs using criteria supplied by the page owner.
- Draft the outcome, actions, and unresolved questions from the meeting record.
People remain responsible for
- Defining the meeting purpose, decision question, and decision owner.
- Choosing reliable evidence and explaining material uncertainty.
- Testing the framing, recommendation, and tradeoffs.
- Confirming the outcome, owners, access, and distribution.
AI can reproduce gaps or bias in the material it receives. The page owner verifies every material claim, and the decision owner confirms the outcome.
SOURCES
What the evidence covers.
Practitioner-created method
Atlassian reports positive results from an internal experiment on page-led meetings where facilitators also received training. Independent sources support related practices such as clear goals, advance context, structured discussion, and written follow-up, but they do not test this exact format as one package.
View sources (5)OpenClose
WHERE IT FITS