Count the second conversation before adding another screen

The cost of an unclear request often appears after the form has done its apparent job. Staff ask which item the customer meant, correct a quantity or reconcile a second submission. A new screen may help, but only if it changes the reason for that additional work.

Use a small representative sample and classify what people actually had to do. Do not begin with an assumed saving that every software feature must justify.

Keep clarification separate from investigation

Consider a fictional sample of thirty enquiries. Nine require a second conversation because the selected pack size is missing. Each of those conversations takes an average of four minutes of active staff work. That is 36 minutes of clarification effort in the sample.

Three other enquiries require eight minutes each to determine whether repeated submissions describe the same request. That is 24 minutes of duplicate investigation. Together these two categories account for 60 minutes of active work, but they have different causes. Adding a pack-size reference could address the first category while leaving the second unchanged.

The sample is illustrative, not a prediction for a real business. The counts and average durations need observation in the actual process before they support an investment decision.

Do not add elapsed waiting as if it were staff effort

A customer may take a day to answer a clarification. The request is delayed, but an operator did not necessarily spend that whole day working on it. Record elapsed waiting separately from active handling. Both may matter: waiting can affect the customer experience, while active time affects staff capacity.

The review also needs the outcome. A conversation that confirms an essential technical specification may be valuable work that should remain. Removing it merely to shorten the measured handling time could make the request less reliable.

Include the work the change creates

A structured catalogue field has to be maintained. Someone must own its values, review changes and understand how old requests retain their original context. A duplicate-handling process may need investigation instructions and a responsible operator. These are operating costs, even when the interface is small.

Estimate the proposed improvement against the particular category it can affect. In the fictional sample, eliminating all nine pack-size clarifications would remove at most the observed 36 minutes in that category; it would not automatically remove the other 24. Real results may be smaller if some conversations serve additional purposes.

Choose an observable comparison

After a suitable change, compare a similar sample using the same definitions. Note volume, product differences and other process changes that could influence the result. A reduction is evidence to examine, not a guaranteed return promised before development.

The scope and budget page connects these observations to a first delivery. The workflow breakdown guide helps discover the missing information that created the extra conversation.