https://www.deepgrain.ai/assets/from-prompts-to-systems-BwSdWWck.js

1import{j as e}from"./index-vt5iT7Dr.js";import{u as p}from"./index-JNXMGXG5.js";const g={title:"From prompts to systems",slug:"from-prompts-to-systems",category:"people-ops-foundations",primaryCluster:"prompting-and-craft",clusters:["workflows-and-automation","enablement-and-change"],track:"people-ops",description:"Buying tools or nudging people to use ChatGPT is not building AI capability. The move from prompts to systems has one order: workflows, automations, agents.",keywords:["from prompts to systems","building AI capability in People Ops","workflows automations agents","AI systems for HR","how to build AI capability in a People team","People operations AI"],readTime:"10 min",publishedAt:"2026-04-19",updatedAt:"2026-09-21",author:"Matthew Bradburn",featured:!0},f=[{question:"Why hasn't anything changed six months after we started doing AI?",answer:"Because most teams fall into one of two traps, dabbling or tool-shopping, and both look like progress from the outside. The tell is simpler than either trap. Ask who owns the workflow that was meant to change, and whether they can name it in one sentence. If nobody can, nothing has moved, whatever the strategy deck says."},{question:"What is the difference between a workflow, an automation and an agent?",answer:'A workflow has humans deciding at the hard points. An automation runs the same rule every time with nobody watching. An agent decides what to do next on its own, inside guardrails you set. Quick test: if you can finish the sentence "if X happens, do Y" without adding "it depends", you have an automation, not an agent. Most teams reach for an agent before they have finished that sentence.'},{question:"Which one should a People team build first?",answer:"Workflows, almost always, and it does not take long. Documenting one properly, start to finish, with the decision points marked, is usually a single working session, not a project. Automate the rule-based parts inside it once it is stable. Only reach for an agent when a new starter could run the process from the doc alone."},{question:"What does a real AI capability inside a People function actually look like?",answer:"Four things held together: context the system holds rather than context you retype every time, workflows the team can re-run and trust, a few internal builders who can wire tools together, and governance that says where the human stays in the loop. The piece missing most often is the builders. Teams gather context and sketch workflows fine, then stall because nobody inside the team can build the thing."},{question:"How do you build AI capability inside a People team without hiring engineers?",answer:"You grow builders from the people who already understand the work. A recruiter or an HRBP who learns to wire two tools together and document a workflow will out-build an outside engineer who does not know the process. Pick one painful, well-bounded workflow, put one person who knows it and one who can build next to it, and rebuild it with AI in the loop. Then take the next one."}];function u(o){const t={a:"a",h2:"h2",li:"li",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...p(),...o.components},{ComparePanel:a,DecisionFilter:s,FieldNote:i,KeyTakeaways:r,ProcessFlow:h,PullStat:l,TLDR:d,Takeaway:c}=t;return a||n("ComparePanel"),s||n("DecisionFilter"),i||n("FieldNote"),r||n("KeyTakeaways"),h||n("ProcessFlow"),l||n("PullStat"),d||n("TLDR"),c||n("Takeaway"),e.jsxs(e.Fragment,{children:[e.jsx(d,{children:e.jsxs(t.ul,{children:[`
2`,e.jsx(t.li,{children:"A prompt is a sentence. A system is a workflow with state, an owner, and a review cadence, and only systems compound."}),`
3`,e.jsx(t.li,{children:"Most People teams are stuck between two traps that both look like progress: dabbling in ChatGPT, or shopping for tools and writing strategy decks."}),`
4`,e.jsx(t.li,{children:"Real capability is four things running together: held context, repeatable workflows, internal builders, and clear governance. The builders are the piece missing most."}),`
5`,e.jsx(t.li,{children:"The build order is fixed: workflows first, automations second, agents only when both are stable."}),`
6`,e.jsx(t.li,{children:"The third path is to rebuild one painful, well-bounded workflow, watch where it breaks, fix it, then take the next."}),`
7`]})}),`
8`,e.jsx(t.p,{children:`Most People leaders think the job is to buy the right AI tool, or to get people using ChatGPT more. It is neither. Both of those are still operating at the level of a single sentence typed into a box, and a sentence does not compound. The move that actually changes how work gets done is the move from prompts to systems: from asking a model to do a thing once, to building a workflow that produces the thing reliably, every time, with an owner and a review cadence. The technology is cheap, the curiosity is high, the leadership pressure is real, and six months in almost nothing has changed. Recruiters still triage by hand. Onboarding still hangs on one person's calendar. The dashboard says "AI initiative in progress." The work says otherwise.`}),`
9`,e.jsx(c,{children:"Workflows, then automations, then agents. In that order. Skipping straight to agents is how People Ops AI projects collapse."}),`
10`,e.jsx(t.h2,{children:"The answer"}),`
11`,e.jsx(t.p,{children:"Because most teams fall into one of two traps, dabbling or tool-shopping, and both look like progress from the outside. The tell is simpler than either trap. Ask who owns the workflow that was meant to change, and whether they can name it in one sentence. If nobody can, nothing has moved, whatever the strategy deck says."}),`
12`,e.jsx(t.h2,{children:"The two traps that both look like progress"}),`
13`,e.jsx(t.p,{children:"There are two ways this goes wrong, and they look like opposites. One is too small, one is too grand, and both burn six months while producing nothing the team uses on a Monday."}),`
14`,e.jsx(t.p,{children:'The first is the dabbler. Someone curious opens ChatGPT, asks it to write a job description, gets back something acceptable but generic, and quietly stops. The next day they are back on the template they already had. They tell themselves AI is "interesting" but "not quite there yet." What actually happened is simpler. They asked once, got a generic answer, and never built any of the context that would have made the second answer better. They treated the model like Google, and Google has no memory of you. Neither did the model, because nobody gave it any.'}),`
15`,e.jsx(t.p,{children:"The second is the tool shopper, and it is the more expensive failure because it looks so much like leadership. A Head of People decides to do AI properly. They book a strategy day. They evaluate vendors. They pilot an AI recruiter, then an AI coach, then an AI policy assistant. They write a deck, share it in an exec meeting, and nobody disagrees, because nobody understood it well enough to disagree. Seventeen tools. No strategy. Six months pass, the market moves twice, three new categories of tooling exist that the deck never mentions, and the team has been busy producing nothing they run."}),`
16`,e.jsx(a,{a:{heading:"The dabbler",items:["One curious person, working alone in a chat window","Asks once, gets a generic answer, gives up","Never builds the context that makes the next answer better","Produces individual tricks, not team capability","Fails quietly: goes back to the old template"]},b:{heading:"The tool shopper",items:["A Head of People running a formal programme","Strategy day, vendor evaluations, back-to-back pilots","Buys tools faster than the team can absorb one","Produces decks, not team capability","Fails expensively: a strategy the market already outran"]},caption:"Opposite in style, identical in result. Neither builds anything the team owns."}),`
17`,e.jsx(t.p,{children:"Both traps share one fault. They treat AI as a thing you procure, a tool, a model, a feature, rather than as something you build with. They mistake the answer for the system that produces the answer. A dabbler collects tricks. A tool shopper collects licences. Neither ends the year with a workflow that runs differently from how 

17it ran in January."}),`
18`,e.jsx(t.h2,{children:"What a real capability is actually made of"}),`
19`,e.jsx(t.p,{children:"Strip away the tools and the decks and a genuine AI capability inside a People function is four things running together."}),`
20`,e.jsxs(t.ul,{children:[`
21`,e.jsxs(t.li,{children:[e.jsx(t.strong,{children:"Held context."})," The system knows what your company is, who your people are, what your policies say, what last quarter looked like. Not because you paste it in each time, but because the system holds it for you and reaches for it."]}),`
22`,e.jsxs(t.li,{children:[e.jsx(t.strong,{children:"Repeatable workflows."})," The work that used to eat an afternoon now runs as a chain of steps the team can re-run, refine, and trust. Documented, teachable, owned."]}),`
23`,e.jsxs(t.li,{children:[e.jsx(t.strong,{children:"Internal builders."})," A few people inside the team who can wire two tools together, write a workflow, deploy a small agent. Not engineers. People who know the work and have learned the craft."]}),`
24`,e.jsxs(t.li,{children:[e.jsx(t.strong,{children:"Clear governance."})," Where the human stays in the loop, where the model never goes alone, what is logged, what is reviewed, what is forbidden."]}),`
25`]}),`
26`,e.jsxs(t.p,{children:["The one that goes missing is almost always the builders. Teams gather context and sketch workflows without much trouble. They stall at the same place every time: nobody inside the team can actually build the thing, so they hire it out, the outside builders leave, and the capability leaves with them. The builders left. The capability went with them. That is the failure mode that outlives every strategy deck, and the only durable fix is growing builders from the people who already understand the work. A recruiter who learns to wire tools together will out-build an engineer who has never sat in a hiring panel, because the engineer does not know where the process actually snags. This is the whole argument behind ",e.jsx(t.a,{href:"/intelligence/the-champion-model",children:"the champion model"}),": capability has to be resident, not rented."]}),`
27`,e.jsx(t.h2,{children:"Workflows, automations, agents: the order is the point"}),`
28`,e.jsx(t.p,{children:'The move from prompts to systems has a shape, and the shape is a sequence. Not "use more AI." Workflows first, automations second, agents only when both are in place. The order is not a preference. It is the difference between something that holds and something that collapses the second reality shows up.'}),`
29`,e.jsx(h,{stages:[{label:"Workflows",body:"Map one process at click level, mark the decision points, make it teachable. Most teams have habits here, not workflows. If you cannot draw it on a whiteboard, you cannot improve it.",meta:"Build first"},{label:"Automations",body:"Once the workflow is stable and the rules are clear, automate the boring, rule-based parts. Errors drop, hours come back, nobody is interpreting anything.",meta:"Build second"},{label:"Agents",body:"Only when the process is stable enough that a new starter could run it from the doc. An agent takes a goal, decides a next action, uses tools, and needs a stack of context under it to not fall over.",meta:"Build last"}]}),`
30`,e.jsx(t.p,{children:"A workflow is the foundation layer. A structured, step-by-step process: hiring manager raises a requisition, recruiter posts the role, candidates apply, interviews get scheduled, offer goes out, background check, first day. Humans decide at the right points. Most People teams are missing this layer entirely, and they do not know it, because habits feel like workflows until you try to write one down."}),`
31`,e.jsxs(t.p,{children:["An automation is the efficiency layer. Once the rules are stable and judgement adds nothing, you automate. A time-off request triggers a balance check, a manager notification, a calendar update, a payroll sync. The system runs, and it keeps running when the person who built it is on holiday. This is where the tooling starts to matter and where cost gets real. A workflow engine runs at roughly £20 per builder seat per month, is SOC 2 and ISO 27001 compliant, and can be self-hosted inside your own boundary, which is the difference between a defensible automation and a personal browser hack nobody can audit. The ",e.jsx(t.a,{href:"/intelligence/automation-patterns-that-pay-off",children:"automation patterns that pay off"})," are almost always the dull, high-volume ones, not the clever ones."]}),`
32`,e.jsx(t.p,{children:'An agent is the autonomy layer, and it is where most teams go to fail. Most "agents" in production are prompts with ambition. They hallucinate confident answers, forget what they were doing mid-task, call the wrong tool at the wrong moment, and work perfectly in the demo before falling apart the second real volume arrives. An agent needs task context, process context, organisational context, state, tooling contracts, exception handling, observability, and a human escalation path. Without that you have a roulette wheel with a nice interface. The three are genuinely different kinds of thing, and confusing them is what makes people reach for the last one first.'}),`
33`,e.jsxs(t.table,{children:[e.jsx(t.thead,{children:e.jsxs(t.tr,{children:[e.jsx(t.th,{children:"Dimension"}),e.jsx(t.th,{children:"Workflow"}),e.jsx(t.th,{children:"Automation"}),e.jsx(t.th,{children:"Agent"})]})}),e.jsxs(t.tbody,{children:[e.jsxs(t.tr,{children:[e.jsx(t.td,{children:"Who decides at the hard points"}),e.jsx(t.td,{children:"A human, every time"}),e.jsx(t.td,{children:"Nobody, the rule decides"}),e.jsx(t.td,{children:"The system, inside guardrails"})]}),e.jsxs(t.tr,{children:[e.jsx(t.td,{children:"Who is watching"}),e.jsx(t.td,{children:"The person running it"}),e.jsx(t.td,{children:"A logged trigger"}),e.jsx(t.td,{children:"Observability and an escalation path"})]}),e.jsxs(t.tr,{children:[e.jsx(t.td,{children:"Best when"}),e.jsx(t.td,{children:"The process is new or judgement-heavy"}),e.jsx(t.td,{children:"Rules are stable and inputs are clean"}),e.jsx(t.td,{children:"The process is stable and the long tail is large"})]}),e.jsxs(t.tr,{children:[e.jsx(t.td,{children:"Falls apart when"}),e.jsx(t.td,{children:"Nobody documented the decision points"}),e.jsx(t.td,{children:"The rules change every quarter"}),e.jsx(t.td,{children:"It was built before the workflow was stable"})]})]})]}),`
34`,e.jsx(t.h2,{children:"When you are actually ready for an agent"}),`
35`,e.jsx(t.p,{children:'The readiness question is not "can the model do this?" It usually can. The question is "is the process underneath it stable enough to hand off?" Run the honest version of that test before anyone builds.'}),`
36`,e.jsx(s,{title:"Before you reach for an agent, run these",criteria:[{test:'Can you finish "if X happens, do Y" without adding "it depends"?',fail:"You keep adding exceptions. That is a workflow that still needs a human, not an agent."},{test:"Could a new starter run this process from the written doc alone?",fail:"The process lives in one person's head, so the agent will inherit gaps nobody can see"},{test:"Does the data flow on its own, on a schedule, with permissions?",fail

36:"Someone prepares a clean export by hand before the pilot runs"},{test:"Is there a written line on what the agent must never decide?",fail:"The policy is a Slack thread and a shrug"},{test:"Who owns this on the Monday after it ships?",fail:"No named owner from the business, only IT keeping the lights on"}],verdict:"Every 'later' in those answers is a workflow that was wished into existence, not designed. Build agents last, on stable workflows and tested automations, or do not build them."}),`
37`,e.jsxs(t.p,{children:["That filter is not there to slow you down. It is there because an agent built on an unstable process does not fail loudly and get fixed. It degrades quietly, gives a confidently wrong answer to a real employee, and gets switched off three weeks later with nobody quite sure when. The ",e.jsx(t.a,{href:"/intelligence/prompting-patterns-for-people-ops",children:"prompting patterns for People Ops"})," that people obsess over are a fraction of this. The prompt is a small part of the system. The system is the thing that survives."]}),`
38`,e.jsx(t.h2,{children:"Outcomes, not outputs"}),`
39`,e.jsx(t.p,{children:'Underneath the whole stack sits a habit shift that most teams find harder than any tool: working from outcomes, not outputs. A traditional task list says "schedule interviews", "send offer letters", "process onboarding paperwork." That is work broken into outputs, and AI cannot do much with an output except run it slightly faster. An outcome-shaped workflow says "cut time-to-hire from twenty-eight days to fourteen without dropping quality." Now there is a target. You can design a chain of steps, decide where a human adds judgement, decide where automation removes friction, decide where a small agent could absorb the long tail of candidate questions, and you can measure whether any of it moved the number.'}),`
40`,e.jsx(t.p,{children:"That shift, from tasks to outcomes, is the shift from doing AI to building with AI. It also makes the work measurable, and measurable is what survives a budget conversation. When the compounding starts to show, it shows as reclaimed capacity, not as a longer tool list."}),`
41`,e.jsx(l,{value:"83",unit:"hours/week",children:e.jsx(t.p,{children:"In one defence-tech engagement, the team reclaimed eighty-three hours a week, not from a bigger tool budget but from a handful of workflows they rebuilt and now own themselves."})}),`
42`,e.jsxs(t.p,{children:["Notice what that number is not. It is not a licence count, not a number of pilots run, not a strategy deck circulated. It is capacity, handed back to people, from systems the team can run without the person who built them in the room. That is the only kind of AI progress that shows up in an operating review. If you cannot point at a moved number, you have been dabbling or shopping, whatever the deck says. This is also why ",e.jsx(t.a,{href:"/intelligence/diagnosing-ai-readiness-in-people-ops",children:"diagnosing AI readiness in People Ops"})," starts with where the work snags, not with which model to buy."]}),`
43`,e.jsx(t.h2,{children:"The third path: from prompts to systems, one workflow at a time"}),`
44`,e.jsx(t.p,{children:'The path that keeps working is unglamorous from the outside. No strategy day. No vendor parade. A small group inside the People team takes one workflow, usually a painful and well-bounded one, and rebuilds it with AI in the loop. Inbound applications, or first-week onboarding, or the manager check-in cycle. One person who knows the work sits next to one who has learned to build. They run it, watch where it breaks, fix it, then take a second workflow. Six months on, the team has not ticked a box marked "done AI." Four pieces of its work run differently, the change compounds, and people outside the team start asking how. The People function quietly becomes the part of the company most fluent in building with AI.'}),`
45`,e.jsxs(t.p,{children:["It stalls in one predictable way: picking a first workflow that is too big or too political to fail safely on. Pick something where a bad first attempt costs an afternoon, not a quarter, and the rest of the pattern takes care of itself. A single, bounded process, rebuilt end to end, is exactly what a ",e.jsx(t.a,{href:"/grain-audit",children:"Grain Audit"})," exists to hand you: one workflow taken to production plus a ranked plan for the next ones, in two weeks, for £2,000."]}),`
46`,e.jsxs(i,{label:"From the field",children:[e.jsx(t.p,{children:"A transit operator was carrying about £40,000 a year in licence cost for a tool that two peo

46ple inside the team later replaced with one workflow they built and understood. The licence went. The capability stayed, because it lived in people who worked there, not in a contract that renewed."}),e.jsx(t.p,{children:"That is the whole case for building rather than buying. A licence is capability you rent and lose. A workflow your own people can run is capability you keep."})]}),`
47`,e.jsxs(t.p,{children:["This is what the track is about. Not which model to use, not which vendor to back. The slow, stubborn discipline of moving from prompts to systems, and the patterns that make it stick. It is the practical face of the wider ",e.jsx(t.a,{href:"/intelligence/pillar/people-ops-ai",children:"People Ops AI system"}),": held context, repeatable workflows, resident builders, governance that protects judgement instead of strangling it. It is not a strategy. It is a practice. And like any practice worth having, it has a grain."]}),`
48`,e.jsx(r,{children:e.jsxs(t.ul,{children:[`
49`,e.jsx(t.li,{children:"Stop optimising prompts in isolation. Optimise the workflow they sit in, and give it an owner and a review cadence."}),`
50`,e.jsx(t.li,{children:"Build in order: workflows first, automations second, agents only when a new starter could run the process from the doc alone."}),`
51`,e.jsx(t.li,{children:"Grow builders inside the team. Rented capability leaves when the builders do."}),`
52`,e.jsx(t.li,{children:"Pick one painful, well-bounded workflow where a bad first attempt costs an afternoon, rebuild it end to end, then take the next."}),`
53`]})})]})}function y(o={}){const{wrapper:t}={...p(),...o.components};return t?e.jsx(t,{...o,children:e.jsx(u,{...o})}):u(o)}function n(o,t){throw new Error("Expected component `"+o+"` to be defined: you likely forgot to import, pass, or provide it.")}export{y as default,f as faqs,g as frontmatter};