Avoid creating a single, massive context document that quickly becomes stale. Instead, maintain 3-5 small, focused, and dated files on specific topics (e.g., team, product). Treat context as an ongoing practice of curation: whenever you re-explain something to the AI, it should be added to a context file.

Shift from creating visually-polished documents for humans to producing structured, machine-readable plans. This allows team members' agents to parse, summarize, and act on the information, making collaboration faster. The focus becomes the quality of the plan, not its presentation.

Providing too much raw information can confuse an AI and degrade its output. Before prompting with a large volume of text, use the AI itself to perform 'context compression.' Have it summarize the data into key facts and insights, creating a smaller, more potent context for your actual task.

As AI agents become prevalent, they will need to consume internal knowledge. Messy PDFs and spreadsheets are brittle and difficult for agents to parse. Websites, built on structured languages like HTML, are inherently designed for agent consumption, future-proofing a company's knowledge artifacts for automated workflows.

Traditional file formats like PowerPoint and Word documents are difficult for LLMs to parse. The future of work involves creating artifacts, like SOPs or presentations, in formats such as HTML that are easily understood by both humans and AI, improving workflow automation and knowledge transfer.

Standard file formats like .docx and .pptx are filled with complex code that LLMs struggle to parse. To build effective AI workflows, companies must create deliverables in formats that are both human-readable and AI-friendly. HTML is a prime example, as it is visually appealing for people and easily ingested by AI.

Instead of forcing an AI to read lengthy raw documents, create consistently formatted summaries. This allows the agent to quickly parse and synthesize information from numerous sources without hitting context limits, dramatically improving performance for complex analysis tasks.

To create a high-quality Product Requirements Document with AI, avoid short prompts. Instead, provide a long, stream-of-consciousness 'brain dump' of all context and ideas. Then, ask the AI to identify blind spots and ask you follow-up questions, turning the process into an iterative partnership rather than a one-shot command.

The rise of AI support agents is changing the purpose of internal documentation. Knowledge bases are now being written less for human readers and more for AI agents to consume. This leads to more structured, procedural content designed to be parsed by a machine to answer questions accurately.