Most audits start backwards.
They schedule interviews, ask broad questions, and hope to piece together truth from memory and opinions.
The problem? People forget details, overestimate efficiency, and describe the process as it's supposed to work—not as it actually works.
This step flips that. You gather data first—metrics, logs, evidence. Then when you interview, you're validating facts and uncovering the "why," not starting from scratch.
Why Request Data Before Interviews?
Conversations are more valuable when you already know the facts.
With data upfront, you can:
- Ask specific, targeted questions instead of generic ones
- Validate what people tell you against real metrics
- Spot contradictions between documentation and reality
- Save interview time by not asking what data already answers
Without data, you're guessing. With data, you're diagnosing.
Step 1: Create Your Data Request Tracker
Create a simple table with:
- Data Item | Owner | System | Purpose | Due Date | Status
This becomes your single source of truth.
Step 2: Define What Data You Actually Need
Only request data that helps you make decisions.
Typically:
- Process docs: SOPs or workflow guides (even outdated ones)
- Performance metrics: KPIs, volume metrics, cycle time, SLA reports
- Failure data: Error logs, rework rates, escalation patterns
- Tool usage: Login frequency, automation usage, feature adoption
- Sample work: Emails, tickets, forms (to see what "done" looks like)
Key rule: If you can't explain why you need it, don't request it.
Step 3: Map Each Request to a Question
For every data item, write: "This helps us understand ___."
Examples:
- "This helps us understand how long customer onboarding actually takes."
- "This helps us understand where support tickets get escalated most often."
If you can't complete that sentence, remove the request.
Step 4: Assign Clear Ownership
Every data item needs one named owner. Never "the team" or "someone in marketing."
Vague ownership = nothing gets done.
Step 5: Set a Hard Deadline
Deadline must be before your first interview.
State clearly: "We need this by [date]. Interviews will assume missing data doesn't exist. Conclusions will be based on available evidence."
Without a deadline, requests sit in inboxes forever.
Step 6: Send a Clear Data Request
Use plain language. Include:
- What you're asking for
- Why it matters
- How it will be used
- Acceptable formats
Make it easy to say yes.
Step 7: Pre-Review Everything
Don't wait until interviews to look at data.
Note:
- Gaps: What's missing?
- Contradictions: Does data conflict with documentation?
- Outdated metrics: Is data old or stale?
These become follow-up questions.
Step 8: Update Your Interview Questions
Use data to sharpen questions.
Instead of: "How long does onboarding take?" (generic)
Ask: "Your data shows onboarding takes 12 days average, but the SOP says 5. What's happening in those extra 7 days?" (specific)
What You Should Have Now
✅ Completed Data Request Tracker
✅ Centralized folder with labeled data
✅ Documented data gaps
✅ Interview questions refined with evidence
Quality Check
- Every data item has a clear purpose
- Every item has a named owner
- You removed all "nice-to-have" requests
- You reviewed all data before interviews
- Interview questions reference real metrics
- Missing data is documented
Next Step: With data in hand and stakeholders selected, you're ready to conduct your first interviews.
Want this done for you? Learn about our AI Audit service → OpsSystem.ai