When operators invent a side path, believe them

During walkthroughs, operators often apologize for “not doing it the right way.” They rename exports in Explorer, keep a paper checklist beside a settings panel, or bounce through an older build for one dialog that still works.

In a Desktop Amberbase review, those behaviors are not noise. They mark places where the official path taxes memory, hides state, or fails under house rules the product never modeled.

What we capture

We ask the operator to finish the task however they normally would, then we annotate:

• Where they leave the application
• Which values they copy by hand
• Which errors they have learned to ignore
• Which older screens they still prefer

Only after that do we open the settings that “should” have covered the need. Often the setting exists but is named for an engineer’s mental model, not the operator’s vocabulary.

Linking back to code

A side path becomes actionable when we can point at a module: duplicate preset logic, a modal that resets on focus loss, a file picker that ignores the project’s working directory. Without that link, the UX note stays decorative.

If you are preparing for a review, list the workarounds you already know. They make excellent seeds for the observation agenda.