Two-Assistant Project Knowledge System
Split project knowledge by source, then give each source a focused AI assistant.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 98%
The system divides project knowledge into two source classes: meeting transcripts and strategic documents. Each class receives a narrowly focused assistant rather than being combined into one overloaded prompt. The executive assistant analyzes conversations for decisions, action items, owners, deadlines, and priorities. The project assistant analyzes plans and reports to produce status summaries, risk assessments, gap analyses, strategic recommendations, decision histories, and new documents. A consistent folder structure supplies the knowledge base, while explicit instructions and output formats make responses predictable. New files must be added as the project evolves, manually or through available automation. This separation reduces context confusion and gives users a repeatable interface for retrieving operational and strategic intelligence.
Origin
Extracted from Marketing Against The Grain, where the host demonstrates the two assistants used across three large HubSpot work pods.
Core principles
- 01Organize source material by how it will be used.
- 02Give each assistant one focused responsibility.
- 03Define analysis tasks and output formats explicitly.
- 04Keep each assistant's context current.
- 05Treat starter prompts as foundations to customize.
How to run it
- 1
Separate the knowledge sources
Create one project folder for meeting transcripts and another for strategic documents. Keep the categories distinct because they support different types of analysis.
Pro tip Use the same two-folder pattern across every major project or work pod.
Watch out Do not mix every source into one undifferentiated knowledge base.
- 2
Capture project activity
Record relevant meetings and save their transcripts in the meeting folder. Store plans, presentations, status reports, specifications, and other strategic material in the strategic-documents folder.
Pro tip Automate transcript delivery into the correct folder when your meeting platform permits it.
Watch out An assistant using stale documents may produce outdated owners, deadlines, or recommendations.
- 3
Build the executive assistant
Instruct one assistant to analyze meeting transcripts, identify decisions and action items, track deadlines and ownership, and flag high-priority items. Define the exact output structure you want it to follow.
Pro tip Include recurring requests such as the latest meeting summary and unresolved follow-ups.
Watch out Confirm consequential assignments and deadlines against the original transcript.
- 4
Build the project assistant
Give a separate assistant expertise in project management, risk analysis, and organizational dynamics. Load strategic documents and offer services such as status analysis, risk assessment, tactic generation, strategic recommendations, document generation, and decision-log maintenance.
Pro tip Present the available services as a menu so users can select the required analysis.
Watch out Avoid adding meeting-analysis duties that dilute the assistant's project-management focus.
- 5
Customize and maintain
Adapt the prompts, services, and output formats to the project's needs. Add current transcripts and documents whenever new material becomes available.
Pro tip Compare outputs across supported AI platforms and retain the tool that handles your document types and analysis needs best.
Watch out Do not assume a connected drive automatically updates an assistant's active context.
In the wild
The host keeps meeting transcripts and strategic documents in separate folders for each work pod. The executive assistant retrieves decisions, owners, deadlines, and follow-ups, while the project assistant creates status summaries, risk assessments, gap analyses, recommendations, and executive one-pagers from the strategic material.
→ The host can retrieve project history and create useful management outputs without manually rereading every meeting and document.
A project lead loads current plans and reports into the project assistant, requests a one-page executive summary, and asks it to emphasize accomplishments, challenges, outlook, and overall status. The lead verifies the facts before sharing the document.
→ A first draft of the executive update is produced quickly from the project's existing evidence.
Common mistakes
Combining both assistants
Putting meeting analysis and strategic project management into one assistant weakens task focus. Keep their source material and primary responsibilities separate.
Using a generic copied prompt
A starter prompt may not reflect the project's terminology, risks, outputs, or stakeholders. Customize it rather than copying it unchanged.
Forgetting context updates
New files in a storage folder may not automatically enter the assistant's context. Add or synchronize current documents before relying on its analysis.
Is it for you?
Best for
It is best for knowledge workers managing recurring meetings, evolving projects, and frequent executive updates.
Not ideal for
It is not ideal for projects whose sensitive documents cannot be uploaded to an approved AI platform.
From the transcript
“I build an AI executive assistant for the median transcripts, and I build an AI project assistant for all of the strategic Docs.”
“It's actually better to keep them separate. They work much better if you have one very focused on project management, one very focused on meeting…”
“you should just not copy and paste for your needs. You should use it as a foundation and then build upon that foundation and tweak…”
From the episode
I Built 2 AI Assistants That Made Me 10x More Productive