Most founders communicate direction through conversation. A team meeting, a Slack message, a recorded Loom that half the team watches at 1.5x speed while doing something else. The direction gets transmitted — but not documented. And undocumented direction drifts.
Every contractor, DA, and collaborator working from memory rather than a written reference is working from their own interpretation of what they heard last. As the founder’s thinking evolves — even slightly, even without a formal direction change — the gap between what leadership intends and what the team executes widens. Not because the team is not listening. Because memory degrades, priorities compete, and without a written reference point, each person fills in the ambiguity with their best judgment.
The Team Direction Brief closes that gap. It is one page. It takes a DA approximately two hours to draft. The operational alignment it produces is not achievable through any volume of verbal updates.
What the Team Direction Brief Is
The Team Direction Brief is a written document that communicates the committed direction to every operational stakeholder in the business. It is not a strategic plan — it does not explain the reasoning behind the direction or present the market analysis that informed it. It is not a task list — it does not assign specific deliverables or set deadlines. It is a reference document: the authoritative written record of what the business is building right now, what each person is executing against, and what the operational boundaries of the current cycle are.
Its function is specifically to replace inference with information. When a team member is making a judgment call about whether a particular task, communication, or decision serves the current priority, the brief is the reference they check. When a new request arrives that could be interpreted as either within or outside the current scope, the brief is what determines the answer. When a collaborator who has been away for two weeks needs to re-orient to the current state of the business, the brief is the document they read.
A brief that does this job well is short, specific, and written in language that can be understood without additional context. A brief that requires the founder to explain or interpret it has not done its job.
The Six Elements That Make It Actionable
A Team Direction Brief that produces operational alignment consistently contains six elements.
The committed direction in one sentence. Not a paragraph, not a vision statement — one sentence that describes what the business is building in the current 90-day cycle. Specific enough that two people reading it independently would come to the same conclusions about what it means for their work.
The 90-day focus in two to three sentences. What the committed direction looks like in practice over the current cycle. What is being built, for whom, and what the primary outcome looks like at day 90. This is the context that makes the one-sentence direction interpretable in operational terms.
Role-specific execution notes. For each collaborator, contractor, or functional role: what they are specifically executing against in this cycle. Not a task list — a clear statement of their lane. Enough specificity that each person can make independent decisions about their work without checking in for clarification on routine items.
The explicit not-priority list. A short list of directions, projects, or categories of work that are not being pursued in the current cycle. This element is frequently omitted and consistently produces problems when it is. Without it, team members continue investing time in directions that have been deprioritized because no one told them not to. The not-priority list closes that gap.
What has changed from the previous cycle. A brief notation of what is different from the last direction brief the team operated under. This gives collaborators who were executing competently under the previous direction a clear map from the old state to the new one, without requiring them to re-read the entire brief to figure out what shifted.
Escalation criteria. The specific categories of decision that require founder input versus those the DA and team can resolve independently. This element transforms the brief from a communication document into an operational protocol. It is the part that most directly affects the founder’s time — because it defines the boundary between what requires them and what does not.
How the DA Drafts and Distributes the Brief
The drafting process starts with a structured input session between the founder and the DA. The session runs 20 to 30 minutes and covers six questions, one for each element of the brief. The DA takes notes in real time — not a verbatim transcript, a structured extraction of the information each element requires.
After the session, the DA drafts the brief using the extracted information. The draft goes back to the founder for a single round of review — corrections and clarifications only, not additions. The brief is designed to be short; additions typically indicate that the direction itself needs more clarity before it can be documented, which is a founder-level problem to resolve before the brief is finalized.
Once approved, the DA distributes the brief to every operational stakeholder — each contractor, collaborator, and support role that has any contact with the business’s execution. Distribution is not passive. The DA confirms receipt from each recipient and flags any non-responses. A brief that has been sent but not confirmed as received has not been distributed.
The DA maintains a distribution log: who received the brief, when they confirmed receipt, and whether any clarifying questions came back. Clarifying questions are surfaced to the founder as a batch, not one at a time, and the answers are added to the brief as an FAQ appendix if the same question comes from multiple recipients.
How Often It Gets Updated and Who Owns the Update Process
The Team Direction Brief is a living document. It is not updated continuously — that would undermine its function as a stable reference — but it is updated at specific trigger points.
The primary update cycle is the direction cycle itself. A new brief is drafted at the start of each 90-day committed direction. This is the standard cadence and accounts for the majority of updates.
Between-cycle updates are triggered by three specific events. A significant change in the committed direction — not a minor tactical adjustment, but a change in what is being built or for whom. A change in the team composition that affects who the brief is distributed to. A clarification from the day-30 or day-60 milestone review that materially affects what one or more team members should be executing against.
The DA owns the update process. When a trigger event occurs, the DA schedules a 20-minute input session with the founder, updates the relevant sections of the brief, and re-distributes with a change summary — a two-to-three sentence note at the top of the document that tells every recipient what changed and what it means for their work, so they do not have to re-read the entire brief to identify what is different.
The founder’s role in the update process is input and approval. They are not drafting, formatting, or distributing. That overhead belongs entirely to the DA.
What Changes in Team Execution When a Written Brief Exists
The operational difference between a team working from verbal direction and a team working from a written brief is observable and specific.
The volume of clarifying questions drops. When team members have a written reference for routine judgment calls — does this task serve the current direction, is this request within scope, should this communication go out or get held — they make those calls independently rather than escalating them. Founders who track this typically notice a 40 to 60 percent reduction in the category of “quick question” messages within two weeks of the brief going live.
The alignment of independently produced work increases. Content pieces, client communications, and operational outputs that were produced without direct founder oversight become more consistently aligned with the committed direction, because the brief provides the reference point that oversight previously provided.
The speed of onboarding new collaborators improves significantly. A new contractor or DA can be productive within days rather than weeks when a current Team Direction Brief exists, because the orientation process has a document to anchor to rather than relying entirely on conversation and observation.
The founder’s re-entry rate into delegated tasks decreases. One of the most reliable indicators of an unclear brief is a founder who keeps reclaiming tasks that were previously delegated. When the brief is specific and current, the team can execute against it without the founder stepping back in to correct course.
The Relationship Between the Brief and the 90-Day Move Map
The Team Direction Brief and the 90-Day Move Map are complementary documents with different functions. Treating them as interchangeable produces both documents doing their jobs poorly.
The brief answers the question: what are we building and what is each person’s role in building it? It is the reference document for judgment calls. It is updated at trigger points. It is read, not executed against directly.
The Move Map answers the question: what specific tasks are being done, by whom, in what sequence, by when? It is the execution document. It is updated continuously as tasks are completed and new ones are added. It is worked, not referenced.
The brief informs the Move Map — the direction the brief establishes determines what belongs in the Move Map’s three columns. The Move Map operationalizes the brief — the tasks in the founder column and the DA column are the specific actions that build the committed direction the brief describes.
When both exist and are current, the team has everything they need to execute without the founder in the operational loop on routine decisions. When either is missing or outdated, the other one cannot fully compensate.
For nonprofit executive directors: the Team Direction Brief at the organizational level replaces the multi-page strategic plan summary that most staff never read with a one-page operational reference that every staff member can use. Distributed at the start of each program cycle and updated at board-approved direction changes, it gives program staff a reliable reference point for decisions that would otherwise require escalation to leadership — reducing the executive director’s involvement in routine program decisions and returning that time to strategy and relationship-building.
