Graph engineering means designing AI work as jobs, arrows, checks and human approvals instead of one chat.
Separate the worker from the checkerAI research fails when the same model that writes the answer also grades it; in a good graph, checking is its own job.
Draw the graph before you automate itRun the lanes manually three times first; if the manual version is not better, automation only produces mediocre work faster.
Build the smallest graph that improves qualityMore agents can mean more noise and five workers repeating the same wrong idea; put human gates where mistakes are expensive.
Executive SummaryAI
Greg Eisenberg says graph engineering, unlike most viral AI terms, is genuinely useful because it gives a better way to think about how AI work actually gets done, and promises listeners they will be able to turn one workflow they already run into a map of steps, checks, handoffs, loops and human approvals.
He defines it against its neighbours: prompt engineering is asking a better question, context engineering is giving better information, and graph engineering is designing the work around the AI so a startup-idea question is not decided, researched, written and graded by one model in one pass.
He separates the two things people mean by graph, a knowledge graph that helps AI reason over relationships (like Microsoft Graph RAG) and an agent graph that describes how work moves, and says this episode is about agent graphs because founders, creators and small teams can use them today.
Using the question of whether to launch an AI bookkeeping product for Shopify merchants, he walks a diamond shape: a planner splits the question, three researchers on customers, competitors and distribution run in parallel, a skeptic attacks stale or unsupported claims, a merge writes the recommendation, and a human gate decides what to test.
He warns against starting with Langraph or Autogen: level one is running the lanes manually on an Excalibur or TL draw board, level two is a repo where each step writes plan.md, customer.md, review.md and recommendation.md, tools come after the workflow, and the goal is the smallest graph that improves the quality of work.
Key Quote
“But graph engineering is how you design the work around the AI so the whole thing stops living inside one messy giant AI chat.”
— Greg Eisenberg
Key Quote
“A lot of AI research fails because the same model that writes the answer also grades the answer.”
— Greg Eisenberg
Key Quote
“That is like asking someone to write their own performance review and then being shocked when they describe themselves as a visionary.”