State is part of the answer
A system should show whether a result is final, partial or still changing. Name the state in plain language and keep it close to the result; a distant spinner cannot explain whether the user may safely act.
Progressive disclosure helps when detail is optional. It becomes harmful when caveats that change the decision are hidden behind an icon or secondary panel.
Example scenario: a generated summary
Example scenario: a document assistant has processed eight of ten files and can already show a draft summary. Label the result “Draft — 8 of 10 sources processed,” list the missing files and disable the final approval action until processing completes. Let the user inspect useful partial work without mistaking it for a finished answer.
This is a design example, not a claim about a shipped product or measured user outcome.
Trade precision for useful guidance
A confidence percentage appears precise but rarely explains the next action. Calibrated labels such as low, medium and high can be easier to understand when each label is paired with evidence and a recommended review step. The trade-off is less numeric detail in exchange for clearer decisions.
A short interface checklist
Label partial and final states; show source and freshness; preserve user input on failure; explain what can be retried; keep destructive actions unavailable during ambiguity; and test every state with keyboard navigation, narrow screens and reduced motion.