Why Projects Without Briefs Fail
Handing a virtual assistant a multi-step project over a quick message — "Can you research 10 competitors and put together a report?" — creates a situation where the output is almost guaranteed to disappoint. Not because the VA lacks skill, but because the instruction left every critical decision undefined: What depth of research? What format for the report? Which competitors? By what date?
According to the Project Management Institute's 2024 Pulse of the Profession report, 37% of project failures are attributed to unclear objectives or scope at the start. For delegated VA projects, that figure is almost certainly higher, since VAs have no organizational context to fill in the gaps and often hesitate to ask clarifying questions for fear of appearing incompetent.
A one-page project brief written before work begins eliminates this dynamic entirely.
The Seven-Part Project Brief Structure
1. Project Title and Owner
Give the project a specific name (not "Research Project" but "Q2 Competitor Analysis — Pricing and Features"). List the owner (you) and the assigned VA.
Example:
- Project: Q2 Competitor Analysis — Pricing and Features
- Owner: [Your Name]
- Assigned VA: [VA Name]
- Date assigned: [Date]
2. Project Objective
One to two sentences answering: What should exist at the end of this project that does not exist now, and why does it matter?
Example: "The goal is to produce a side-by-side comparison of pricing and feature sets for our top 8 competitors. This will inform the pricing update planned for May and should be usable in the executive presentation without further formatting."
Avoid process-oriented objectives ("research competitors") and use outcome-oriented language ("produce a usable comparison document").
3. Scope and Deliverables
List every deliverable that must be produced, formatted, and submitted for the project to be considered complete. Be specific about format.
Example:
- A Google Sheets file with one row per competitor and columns for: company name, pricing tiers, core features, unique differentiators, last verified date
- A 200-word written summary of the top three competitive threats for the executive presentation slide
- All research sources listed in a separate Sources tab
Out of scope for this project:
- Do not include companies outside the US market
- Do not include companies below $1M estimated annual revenue
Explicitly stating what is out of scope prevents scope creep and saves the VA from spending time on work that will not be used.
4. Timeline and Milestones
Break the project into phases with a due date for each.
Example:
| Milestone | Due Date |
|---|---|
| Competitor list confirmed (VA submits list for owner approval) | [Date + 2 days] |
| Data collection complete (spreadsheet draft shared for review) | [Date + 5 days] |
| Written summary submitted | [Date + 6 days] |
| Final deliverable formatted and submitted | [Date + 7 days] |
Including an intermediate milestone for owner review prevents the VA from spending the full timeline on a direction that turns out to be off-target. Catching misalignment at day two costs one hour. Catching it at day seven costs seven days.
5. Resources and Access
List every resource the VA needs to complete the project: databases, tools, budget (if applicable), contacts, or existing internal documents.
Example:
- Competitor names to research: [link to existing list in Drive]
- Access to SEMrush account: credentials in LastPass under "SEMrush VA"
- Reference document: [link to last year's competitor analysis for format guidance]
- Research budget: up to $0 (use public sources only; flag if paid access is needed)
6. Success Criteria
Define what "done well" looks like before work begins. List three to five criteria the final deliverable must meet.
Example:
- Spreadsheet is complete for all 8 competitors with no blank cells
- Every data point has a source URL in the Sources tab
- Pricing information was verified within the last 30 days
- Executive summary is 175–225 words and free of jargon
- File is named "Q2-Competitor-Analysis-[YYYY-MM-DD]" and saved in the correct Drive folder
7. Questions and Blockers Protocol
Specify how the VA should handle uncertainty during the project:
- Questions about scope or direction: Slack DM within the same business day
- Technical blockers: flag immediately with a proposed workaround
- If a milestone cannot be met: notify the owner at least 24 hours before the deadline with an updated estimate
When to Use a Project Brief vs. a Task Assignment
A task is a single-step action completable in under two hours. A project is multi-step, involves judgment calls, or produces a deliverable that will be used by stakeholders beyond the VA-owner pair.
Use a task list entry for: "Schedule Tuesday's client call." Use a project brief for: "Compile a resource guide for new clients with links to our top 10 knowledge base articles."
When in doubt, if you catch yourself writing more than three sentences of instructions, write a brief instead.
For business owners who want structured project delegation as part of a fully managed VA service, Stealth Agents offers dedicated VAs with experience handling complex multi-step projects across industries.
Project Brief Checklist
- Project title, owner, and VA assigned in writing
- Objective written as an outcome, not a process
- Deliverables listed with specific format requirements
- Out-of-scope items explicitly named
- Timeline includes at least one intermediate review milestone
- All required resources and access confirmed before work begins
- Success criteria documented before the project starts
- Questions and blocker protocol communicated to the VA
A one-page project brief written in 20 minutes eliminates the revision cycles, re-work, and missed objectives that cost business owners hours every month.
Sources:
- Project Management Institute, Pulse of the Profession Report, 2024
- Asana Anatomy of Work Index, 2024
- Harvard Business Review, "How to Delegate Complex Work," 2023