A Value-First Guide to Surviving the SaaSpocalypseContents
Part V — People
Chapter 15
What "Operations" Means Now
Operations used to mean process management. People designing workflows, other people following them, managers checking compliance, analysts reporting on efficiency. The operations team was the maintenance crew, keeping the "Just In Case" machinery running.
That era is ending. What's replacing it is design work.
In June 2026, in a conversation about how AI was changing client work, I described what I say to a company that wants coaching and project work from me. The project work is the build. "The build part is the easy part, right?" The real question was a different one: "Do you understand what you're capable of, what your team is capable of, and what AI can help you do?" And then the sentence that changes the job: "Most of the project work that you would have had me do last year can now be done by AI assistant, and I want you to know it and I want you to do it."
If you work in operations, read that sentence as if it were about your own year. A lot of what filled your calendar was the build: setting things up, wiring things together, keeping them running. When the build gets easy, the work that's left is deciding what should be built, for whom, and how people and agents should work together inside it.
From maintaining the machine to designing the work
Under "Just In Case," operations keeps the machine running. Workflows are designed once, followed, monitored and reported on. Success is adherence.
Under "Just In Time," operations designs how the work gets done by people and agents together. Every decision about when an agent should act on its own and when it should bring a person in is an operations decision. Every choice about how far to trust an agent's output, the calibration from Chapter 13, is an operations decision. This is design work, not maintenance work.
The new job, in five parts
Designing the patterns. Deciding which work agents handle, which needs human judgment, and how the handoff between them works. This is where the most leverage is.
Setting the guardrails. What can an agent do on its own? What needs approval? How does it escalate? This is governance, and it's operations' to hold.
Keeping the quality. Building the loops that make agents better over time: reviewing outputs, finding where they fail, adjusting how they're set up.
Measuring what matters. Not whether the process was followed. Whether value reached the people it was for. The Unified Operations View, as Chapter 5 described it, adds something most dashboards leave out: it keeps how the work felt to the people doing it beside what the work produced. Keeping the account of value as the person who received it sees it is a practice of its own, and Value Accounting, Book 4, is about exactly that.
Building the rhythm. Making "Just In Time" run every day: knowledge at the point of relevance, execution at the moment of readiness, value at the moment of recognition. That's the Just In Time Trilogy from Chapter 3, turned into the way the week runs.
Where operations sits now
Chapter 14 introduced the Three-Org Model. Operations has its own org in it, and the methodology describes its purpose as "AI-powered coordination and enablement that makes the Customer Org effective at creating value." Its key principle is the one to remember: "Operations should be invisible to clients. They experience seamless coordination; they don't see the machinery behind it."
Operations teams also look after one of the Four Unified Views, the Unified Operations View. In the methodology, looking after a view isn't the same as owning it: "Stewardship means looking after the view; every team reads it and adds to it." That's the shift in one line. Operations stops being the department that holds the system and becomes the team that keeps it working for everyone else.
The question for you
If you're in operations, this is a change in what your job is for. The skills it asks for aren't exotic: systems thinking, design, care about quality, and the judgment to know when automation serves the organization and when it doesn't. You probably use most of them already, mostly on keeping the old machine alive.
Whether this reads as a threat to the job you have or a description of the job you'd rather have is yours to decide. I'd only ask you to picture your own week this way. What would you stop doing? What would you finally have time to design?
Where does your brain go with that?
Part V has been about people: how humans and AI work together, how roles change, and what operations means now. Part VI brings it together. First the choice in front of you, then what the shift itself is.