Aglet

Triage a file preview that appears after selection

Preview generation can involve decoding, orientation, thumbnails, metadata, or a later processing handoff. Triage should capture the selection event, when the file became usable, and what the interface offered during the gap. The question is whether work is slow, invisible, or incorrectly blocking selection.

Establish what is happening

  1. Record the selection path

    Capture file size, dimensions, format, selection time, first visible item, preview start, preview ready time, and any error. Note whether users can select another file or continue without a preview while generation runs.

  2. Separate work boundaries

    List decode, thumbnail, metadata, validation, and processing transitions that occur after selection. Identify which operation controls readiness and whether visible pending text corresponds to that operation or hides several distinct states.

  3. Classify the delay

    Classify the case as expected asynchronous work, missing progress, unnecessary blocking, repeated generation, or failure without explanation. Record a small and large file comparison so the next investigation can distinguish size scaling from a fixed state gap.

What to carry forward

Triage is complete when selection, preview readiness, intermediate work, and available actions are timed for one file. If the workflow has no readiness contract, record that definition gap before treating elapsed time as proof of a performance fault.

Technical background: MDN reference.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow