How to brief a result analytics consultant

Consultants waste days reconstructing context you already have. Send three release cycles of raw result archives, a list of suite owners, and the exact questions your release board asks today. Those three items replace a week of discovery meetings.

Include one example of a past go decision that later proved wrong, and one hold decision that proved unnecessary. Those stories reveal which signals your current reports amplify or bury.

Agree upfront which systems the consultant may read but not change. Result analytics work should leave runners untouched until your team chooses follow-on engineering work.