A project feels chaotic when its state lives in several places at once — documents, messages, memory, and the vague belief that something important has been forgotten. AI is useful here because it can keep reshaping the map while you remain responsible for the destination.
Start with the undignified project dump
Gather the notes, emails, screenshots, voice memos, requirements, dates, and unresolved questions. Do not organize them first. Paste or upload what is safe to share and explain what the project is supposed to become.
Ask for four outputs only: known facts, decisions already made, unresolved questions, and next actions. This first pass is not the system. It is the act of getting the project out of your nervous system and onto a surface you can inspect.
Create a living one-page brief
The brief should contain the purpose, definition of done, audience, constraints, people involved, current phase, and the next meaningful milestone. Keep it brutally short. If it grows into a report, it stops functioning as an orientation device.
Every time the project changes, update the brief first. It becomes the stable context you can give an assistant before asking for plans, drafts, or analysis.
Separate decisions from discussion
Long projects drown in old conversations. Keep a decision log with the date, decision, reason, owner, and what would cause reconsideration. This prevents the team — or future you — from reopening settled questions merely because the reasoning has vanished from memory.
An assistant can extract candidate decisions from meeting notes, but a human must confirm them. A plausible summary is not the same thing as consent.
Maintain one list of open loops
An open loop is anything preventing clean forward motion: awaiting information, dependent on another person, unclear ownership, hidden risk, or a task too vague to begin. Ask the assistant to rewrite vague loops as observable next actions.
- “Figure out launch” becomes “Choose the launch audience and date.”
- “Website” becomes “Approve the homepage hierarchy.”
- “Talk to Sam” becomes “Ask Sam whether the supplier can meet the revised quantity.”
Use a weekly reset instead of constant management
Once a week, give the assistant the current brief, decision log, open loops, and notes from the week. Ask what changed, what is blocked, what is becoming risky, and which three actions matter next.
The value is not that it manages the project for you. The value is that it performs the rereading and comparison you would otherwise avoid until the project feels haunted.
Preserve a source of truth
Choose one home for the approved state of the project. The assistant may read from many places, but confirmed facts and decisions must land somewhere stable. Never let a chat transcript become the only record of what the project is.
Mark generated plans as proposals until accepted. This single convention prevents a machine’s confident suggestion from quietly becoming policy.
The smallest useful version
Make three files: Brief, Decisions, and Open loops. Use the assistant for a fifteen-minute weekly reset. That modest system can rescue surprisingly large projects because it gives change somewhere disciplined to land.