Process, data, unit economics.
One of the three is usually binding. The diagnostic establishes which, what it costs, and what it
would take to move.
Is this a process, or a habit?
Software applied to undefined work encodes one person's version of the job and removes the discretion that was holding the operation together. Before anything is scoped, we establish whether the work, and the systems it runs through, are specified tightly enough to be encoded.
We ask: Could two people perform this work and produce the same result?
Would two systems agree on this number?
Most integration failures are definitional rather than technical. When a business holds more than one definition of a customer, an order or a case, no integration can reconcile the disagreement, and it surfaces later as a reporting problem. We establish whether the business holds one definition or several.
We ask: Could two systems answer the same question and return the same number?
Does the build clear its own cost at this volume?
A system carries a running cost that is rarely priced at scoping: inference, infrastructure, monitoring, human review, and the maintenance that continues for as long as the system exists. We establish the volume at which the build pays for itself, and whether the business operates above that line.
We ask: What does this cost to run in year two, and at what volume does it clear it?
An illustration. Which lens binds is what the diagnostic establishes.