The Lobbi Delivery Team
Operational Systems Engineering
Most failed ops engagements look the same on the way out: a beautifully detailed swimlane diagram of the wrong process, with the wrong boundaries, owned by the wrong team. The work is good; the target was wrong from day one.
That's a scoping failure, not an execution failure — and it's the failure SIPOC and RACI exist to prevent.
What the lens answers
SIPOC — Suppliers, Inputs, Process, Outputs, Customers — answers two questions about the process you're about to model: where does it actually start, and where does it actually end. That sounds trivial. It is not. The "order-to-cash" process at most companies has at least three reasonable starting points (a quote, a signed order form, an issued invoice) and at least two reasonable endings (cash received, revenue recognized). Pick a different combination and you're modeling a different process.
RACI — Responsible, Accountable, Consulted, Informed — answers a different question: for each major decision inside that scope, who actually owns it. Not who attends the meeting. Not who emails about it. Who would still have authority to make a call if everyone else was on PTO.
Why we run it first
Every other lens — swimlane diagrams of handoffs, value stream maps of time, customer journeys of experience — assumes you've already agreed on what counts as "the process" and who counts as "the owner." If those two things drift during the engagement, the maps drift with them.
The classic symptom is what we call lens drift: the swimlane diagram covers steps 1 through 11; the value stream map covers steps 4 through 14; the customer journey covers steps 1 through 7. They look like three views of one process. They are actually three views of three different processes. Trying to reconcile them takes weeks. Skipping that reconciliation produces decisions optimized against a fictional system.
What "good" looks like
A SIPOC that's done its job fits on one page. Five columns, eight to twelve rows, every input traceable to a supplier and every output traceable to a customer. It is boring. It should be boring. The point of SIPOC is to make scope so explicit that there is nothing left to argue about when a stakeholder shows up two weeks in and says "wait, I thought this also covered…"
A RACI that's done its job has exactly one A per row. Multiple Accountables means nobody is. That single rule has caused more useful arguments in our engagements than any other single artifact.
How we use it inside an engagement
We treat SIPOC + RACI as a 90-minute working session, not a deliverable. The artifact that comes out the other side gets pinned to the top of the workspace and referenced every time someone proposes adding a step, removing a stakeholder, or extending the boundary. If the boundary moves, the artifact updates. If the artifact gets stale, the rest of the maps get stale with it.
It is the most powerful lens we use, and the one most consultants skip because it doesn't look like work.
If your SIPOC and your value stream map disagree about where the process starts, one of them is wrong — and it's almost always the value stream map.
Sources
Topic clusters