1 · No named executive owner. Decisions are slow. Junior teams without the full picture are driving the work, and trade offs get escalated but never settled.

5 · One named executive owns the outcome, stays current on progress, and manages risk before it becomes a delay.

1 · Nothing is locked. No signed off process documentation, no real sample data, and the business and the subject matter experts describe the process differently. Rules and measures arrive late, so scope drifts.

5 · Requirements and sample data are locked before the build starts. Edge cases are mapped up front, and the undocumented knowledge in people's heads has been written down.

1 · Credentials, environments and test setups take weeks, not days. The project starts before the environment is ready and waits on access it should already have had.

5 · Infrastructure is specified once, completely, and stood up before any code. Cloud, on premise or hybrid is decided, and the test environment exists before the build.

1 · Chasing every case instead of the vital few. Time goes into rare exceptions before the common path is live, and the team is tired of pursuing perfection.

5 · The high volume, high impact cases go first. The rest are scheduled deliberately, after something is running.

1 · It can read your systems but it cannot reliably write into them. Every system of record has to be read and written accurately and in real time, and most stacks never cross that line.

5 · Validated write paths into the systems you already run, including the legacy portals, with no rip and replace.

1 · It works on clean test data. It has never been through a messy month: poor scans, partial documents, supplier variations, real volume.

5 · Accuracy holds at production volume and messiness, with deterministic checks where the answer must never vary, and a real exception path.