Field note
Interviewing application owners without turning the hour into a feature demo
Application owners are busy. If an interviewer opens with suite feature lists, the hour becomes a polite demo and yields little adoption evidence.
We start from a single recent week: which tasks touched the internal application, which outputs left it, and which tools received those outputs. Only then do we ask whether the cloud suite appeared in any of those paths.
Exceptions matter more than happy paths. Night batch jobs, contractor accounts, and Korean-language templates that never migrated are where suite adoption quietly fails. Capture those stories with enough detail that a heatmap cell can be defended later.
End the interview by asking what the owner would need to change before they would trust the suite for one named artefact. That answer often becomes a recommendation that survives the briefing.