We scan new podcasts and send you the top 5 insights daily.
The biggest hurdle for automating complex enterprise workflows is that most rules aren't written down. Poetic tackles this by generating a baseline AI process from documentation, then having domain experts provide iterative feedback on it, essentially turning them into data labelers to capture unwritten knowledge.
Instead of relying on engineers to remember documented procedures (e.g., pre-commit checklists), encode these processes into custom AI skills. This turns static best-practice documents into automated, executable tools that enforce standards and reduce toil.
Rather than programming AI agents with a company's formal policies, a more powerful approach is to let them observe thousands of actual 'decision traces.' This allows the AI to discover the organization's emergent, de facto rules—how work *actually* gets done—creating a more accurate and effective world model for automation.
Instead of static documents, business processes can be codified as executable "topical guides" for AI agents. This solves knowledge transfer issues when employees leave and automates rote work, like checking for daily team reports, making processes self-enforcing.
The effectiveness of enterprise AI agents is limited not by data access, but by the absence of context for *why* decisions were made. 'Context graphs' aim to solve this by capturing 'decision traces'—exceptions, precedents, and overrides that currently live in Slack threads and employee's heads, creating a true source of truth for automation.
Poetic's architecture offers a hybrid approach to overcome the limitations of pure code or pure AI agents. Workflows execute as reliable, deterministic code. However, if the underlying application changes, an AI layer intervenes to "heal" the process, providing adaptability without sacrificing precision.
Instead of manually crafting complex "mega prompts" or training rules for AI assistants, ask the AI to generate them for you. You can have a dialogue with the AI to refine its suggestions, dramatically speeding up the process of creating sophisticated workflows.
To build coordinated AI agent systems, firms must first extract siloed operational knowledge. This involves not just digitizing documents but systematically observing employee actions like browser clicks and phone calls to capture unwritten processes, turning this tacit knowledge into usable context for AI.
Before any AI is built, deep workflow discovery is critical. This involves partnering with subject matter experts to map cross-functional processes, data flows, and user needs. AI currently cannot uncover these essential nuances on its own, making this human-centric step non-negotiable for success.
AI tools like LLMs thrive on large, structured datasets. In manufacturing, critical information is often unstructured 'tribal knowledge' in workers' heads. Dirac’s strategy is to first build a software layer that captures and organizes this human expertise, creating the necessary context for AI to then analyze and add value.
The most effective way to build a powerful automation prompt is to interview a human expert, document their step-by-step process and decision criteria, and translate that knowledge directly into the AI's instructions. Don't invent; document and translate.