goms-klm-analysislisted

# GOMS / KLM Analysis Use this skill when the useful artifact is an explicit workflow model. It is best for repeatable tasks with known steps, such as dashboard triage, form submission, search/refine/open flows, command palettes, editor workflows, and mobile settings tasks. ## Choose The Model - Use **KLM** when the task is procedural and the user already knows what to do. It estimates expert, error-free execution time. - Use **GOMS** when there are meaningful alternatives, decision rules, or multiple methods to achieve the same goal. - Use a lightweight cognitive walkthrough when the risk is discoverability, comprehension, or first-time use rather than speed. ## KLM Operators Start with these operator families and adjust for the product context: - `K`: keystroke, tap, click, button press, or discrete command. - `P`: point to or visually acquire a target. - `M`: mental preparation before a chunk of action. - `H`: hand movement between input devices or postures. - `R`: system response wait time. - `V`: visual verification or reading needed to continue. Do not overfit exact timings. Count removed operators and wait states first; add timings only when comparison needs a rough total. ## Workflow 1. Name the task and user expertise level. 2. Capture the current method as numbered user actions. 3. Mark operators for each action. 4. Insert mental operators before decisions, strategy shifts, mode changes, or non-obvious commands. 5. Insert response waits only when the UI blo