- Why doesn't adding headcount reduce process cycle time?
- What is the difference between touch time and elapsed time in a process?
- What are deciding, fetching, and checking work?
- How do you calculate coordination share and wait multiple?
- How does wait multiple relate to process cycle efficiency?
- What do coordination share results mean for agentic process redesign?
- Which processes are good candidates for Agentforce Operations?
- What can the Coordination Cost Diagnostic not tell you?
- How does OSF Digital deliver Agentforce Operations?
Why doesn't adding headcount reduce process cycle time?
Adding headcount often leaves process cycle time unchanged when the constraint sits in the coordination between teams and systems. New hires there add requests rather than capacity. A new coordinator sends more emails to the same upstream teams, and those teams got no extra capacity. The queue moves out of the function where it shows on a dashboard and into functions where it doesn't.This pattern is common in processes that run between systems, such as supplier onboarding, invoice exceptions, claims, complaints, and account changes. Each system does its part. The work between the systems falls to people: chasing a document, keying data from one system into another, rebuilding a file for a reviewer. When that work makes up most of the effort, the process is coordination-constrained, and hiring addresses a different problem from the one slowing it down.When most of the hands-on work is genuine judgment, the process is capacity-constrained. Then the honest answer is more skilled people, better decision support, or clearer decision rules. Telling the two situations apart is the first decision, and it takes two measurements that most operations dashboards don't include.Find out where your process time goes. Download the Coordination Cost Diagnostic, walk one process, and send your results to OSF Digital for review.What is the difference between touch time and elapsed time in a process?
Touch time is how long the work in a process step takes once someone is actually doing it. Elapsed time is how long the step takes from the moment it is ready to the moment it is finished, including every hour it sits in a queue. A risk review might take 40 minutes of reading and four days of waiting for the reviewer.Operational reporting usually merges the two. Average handle time counts a genuinely complex case and a case that sat three days in an inbox the same way. Both show up as elapsed days, and only one of them represents work. Separating touch time from elapsed time makes the waiting visible, and waiting is usually where cycle time accumulates.What are deciding, fetching, and checking work?
Every hands-on step in a process falls into one of three types of work: deciding, fetching, or checking. The balance between them shows where a team's effort goes.- Deciding is judgment work: assessing facts, applying rules, weighing options, approving or rejecting, and writing down the reasoning behind a decision.
- Fetching is getting something: requesting records from a system the team cannot access, chasing replies, pulling data from several systems into one place, assembling a file so someone else can follow it, and keying information from one system into another.
- Checking is verifying or redoing work that has already been done once: second-reviewer passes that re-read rather than sample, reconstructing a file for an escalation, and re-running cases after a rule or policy change.
How do you calculate coordination share and wait multiple?
Coordination share and wait multiple come from walking one process step by step as it is actually performed, usually 8 to 15 steps. For each step, record the role, the touch time, the elapsed time, and the activity type.- Coordination share = (fetching touch time + checking touch time) ÷ total touch time × 100
- Wait multiple = total elapsed time ÷ total touch time
| # | Step | Role | Touch | Elapsed | Type |
|---|---|---|---|---|---|
| 1 | Request arrives by email from the business unit | Ops coordinator | 10 min | 10 min | Fetching |
| 2 | Coordinator emails requester for missing tax documentation | Ops coordinator | 15 min | 3 days | Fetching |
| 3 | Supplier checked against sanctions list in a separate system | Ops coordinator | 20 min | 20 min | Fetching |
| 4 | Coordinator compiles submission pack for review | Ops coordinator | 45 min | 45 min | Fetching |
| 5 | Risk reviewer reads pack and assesses supplier | Risk analyst | 40 min | 4 days | Deciding |
| 6 | Second reviewer re-reads same pack per two-person policy | Risk analyst | 35 min | 2 days | Checking |
| 7 | Coordinator keys approved supplier into the ERP | Ops coordinator | 25 min | 1 day | Fetching |
| 8 | Coordinator notifies requester and closes the record | Ops coordinator | 10 min | 10 min | Fetching |
How does wait multiple relate to process cycle efficiency?
Wait multiple is closely related to process cycle efficiency, the lean measure that divides value-added time by total lead time. Wait multiple uses all hands-on time as its base and inverts the ratio. A wait multiple of 24 is the same as a flow efficiency of about 4%. Teams that already use lean methods will recognize the logic.Coordination share adds a second cut. Lean analysis would class much of the fetching and checking as non-value-added. Coordination share separates that portion explicitly from deciding. The result shows how much hands-on time exists only because information has to be moved, gathered, assembled, or verified a second time. That is the portion of the work that agents can take on.What do coordination share results mean for agentic process redesign?
A coordination share result places a process in one of three bands. Each band points to a different response.| Coordination share | Band | What it suggests |
|---|---|---|
| 60% or above | Coordination-constrained | Most hands-on time is spent moving information. Adding people shifts the bottleneck elsewhere. Agents taking on the fetching and checking between systems is worth assessing. |
| 40% to 59% | Mixed | The process is probably a composite. Split it into sub-processes, calculate each one separately, and start with the sub-process that has the highest share and the clearest measure. |
| Below 40% | Capacity-constrained | Most of the work is genuine judgment. Improvement comes from decision quality, decision support, or the decision rules themselves. Putting agents into this process adds a layer without releasing much time. |
- Find the three steps with the largest gap between touch time and elapsed time. Those are the queues.
- Separate checking that serves as a deliberate control from checking that exists because the first pass could not be trusted or followed. Only the second kind is removable.
- Confirm the coordination is repeatable. Agents can coordinate handoffs that happen consistently and in a consistent sequence. Genuinely varied handoffs are harder.
Which processes are good candidates for Agentforce Operations?
Agentforce Operations is a process layer that sits above existing systems and orchestrates AI agents and human approvers inside the same flow, with the same audit trail. It turns unstructured inputs such as emails, spreadsheets, and documents into coordinated workflows. Agents carry out tasks across systems and teams, communicate through the email and Slack channels people already use, and route each decision to the person who owns it. In a coordination-constrained process, agents take on the fetching and checking between systems and people keep the decisions. A process owner sees in one place what the agents are doing, what the people are doing, and where a decision is still owed.Strong candidates share four traits:- Volume. The process runs daily or weekly, so improvement compounds.
- Manual coordination. The work between system steps lives in email, spreadsheets, chat, and phone calls.
- A measure with consequences. A defined SLA, cost target, or error rate gives the improvement something to move.
- Clear boundaries. The process has a defined trigger and a defined completion, and it crosses two or three teams at most.
What can the Coordination Cost Diagnostic not tell you?
The Coordination Cost Diagnostic shows where time goes in one process. It does not confirm that the process is ready for agentic execution. Feasibility depends on data availability, the integration surface, and how much genuine variation sits underneath the steps on the worksheet.The diagnostic also stops short of a business case. Multiplying released hours by a loaded cost rate overstates the result, because released time does not convert to saved cost one for one. It produces a directional figure strong enough to justify a closer look.Each result reflects one process at one point in time, as described by whoever filled in the worksheet. Two people from the same team will often produce different worksheets, and that divergence usually tells its own story about how the process runs.How does OSF Digital deliver Agentforce Operations?
OSF Digital delivers Agentforce Operations through a dedicated global practice and a gated journey that runs from diagnosis to an operating model the customer owns. The journey starts with an assessment of the process landscape, data readiness, architecture gaps, and team maturity. The first domain is chosen where three things meet: high business value, real organizational readiness, and strong proof potential. That phase ends with a prioritized use-case set, an architecture gap analysis, and executive alignment.A forward-deployed pod then builds a running workflow on a real process, in the customer's own environment, with real data and real users, within four weeks. The Forward-Deployed Industry Strategist diagnoses the process from the inside, the Field CTO builds the blueprint live, and the Value Engineer builds the ROI model from the customer's actual baseline. The phase ends with a live process and a quantified business case to support the decision on the next phase.Scaling puts production processes live across the chosen domain and, in parallel, builds the customer's Center of Excellence: the ways of working, the governance model, and the internal capability to keep building. Each engagement starts from OSF Digital's industry process libraries and implementation playbooks. Knowledge transfer runs throughout, and success is measured by whether the customer's team can run the next wave on its own. A completed Coordination Cost Diagnostic is a useful starting point for the first assessment conversation.Find out where your process time goes. Download the Coordination Cost Diagnostic, walk one process, and send your results to OSF Digital for review.More on OSF Digital’s Agentforce Operations practice: Watch the executive briefing on Agentforce Operations with Sean Catlin, EVP and Global Head of Strategy at OSF Digital and one of Channel Insider’s 2026 AI Leaders in the Channel. Or hear one of our customers talk about working with OSF Digital on Agentforce Operations.Frequently asked questions
Coordination share is the percentage of hands-on time a team spends fetching and checking information rather than making decisions. It is calculated by dividing fetching and checking touch time by total touch time. A coordination share of 60% or more indicates that most effort goes into moving information between people and systems.
No universal target exists, because acceptable waiting depends on the process and its controls. A wait multiple above 10 is a strong signal that cycle time is driven by queues and handoffs rather than by the work itself. The useful comparison is the same process measured again after a change.
Much of the first wave of Agentforce adoption focused on conversational AI and the CRM experience. Agentforce Operations is a process layer that orchestrates AI agents and human approvers across complete end-to-end processes in functions such as finance, procurement, HR, supply chain, and customer operations. It sits above Salesforce, ERP, and communication systems and connects to more than 250 applications, so a single process can span every system it touches.
The Coordination Cost Diagnostic takes about an hour for one process. It needs someone who knows how that process actually runs and a willingness to record it as performed rather than as documented. The output is two ratios, coordination share and wait multiple, with an optional third ratio for rework share.
A high coordination share shows where time goes, and feasibility is a separate question. It depends on data availability, the integration surface, and how much variation sits underneath the process steps. An assessment of the process landscape, data readiness, and architecture tests those factors before anything is built.
A completed worksheet gives OSF Digital a concrete starting point for an assessment that identifies the strongest first domain for Agentforce Operations. Qualifying processes move into a four-week build of a working process in the customer's own environment, with a quantified business case based on the customer's actual baseline.
OSF Digital Launches Global Agentforce Operations Practice to Accelerate Enterprise-Scale Agentic Transformation
Agentforce Operations: Bring the Work Between Your Systems Under Intelligent Control
Agentforce Operations for Complaints: Deciding vs. Fetching


