A readout works when the room already agrees on what “good enough” meant for this milestone. Bring the target frame budget, the device list that matters for this launch, and the three player complaints you hear most often from soft-launch channels.
Export permissions should be settled before the analysis window starts. Waiting on access mid-audit compresses the days that should be spent on hitch tagging.
Invite the people who can change the build, not only the people who report on it. A findings brief without an owner in the room becomes a PDF that ages poorly.
Ask for one recent patch note that changed load behavior. Context prevents false alarms when a known temporary hitch is already scheduled for removal.
Finally, decide in advance which questions are out of scope. Creative UA, store screenshots, and community management deserve their own conversations; mixing them into an engine readout dilutes both.