Preparing a desktop build for an outside review

Outside review time is expensive. Most delays we see are not about disagreement — they are about missing builds, expired licenses, or recordings that skip the painful steps.

Before kickoff

1. Nominate three to five tasks that operators actually perform, not the marketing tour.
2. Provision a time-boxed account with the same permissions a normal power user has.
3. Confirm OS versions you still support; we will not invent coverage for abandoned targets.
4. Collect two recordings if live operators are hard to schedule — including mistakes and recovery.
5. Identify a code guide who can answer “where does this dialog get its state?” within a day.

What to withhold

You do not need to open every repository. Start with the UI layer and the services the nominated flows touch. Expand only if a finding requires it.

Chiang Mai on-site notes

If observation must happen on your floor, tell us about badge access, photography rules, and whether operators can speak in English or prefer Thai facilitation. We adapt the session language; we cannot adapt to surprise security policies mid-morning.

Use the Contact form when the checklist is mostly ready — incomplete access is better flagged early than discovered on day two.