The Strategic Logic of Interview Design and Field Research

Interviews are instruments, not conversations

By Unit 3, RelayOps has selected an opportunity, defined Segment A, and prioritized the same-day rebalance job. The next failure mode is unstructured talking: friendly meetings that produce quotes but not decisions. Customer discovery interviews are deliberate instruments designed to falsify assumptions, extract job stories, and observe workflow. They are not sales calls, not user experience usability tests, and not investor pitches disguised as research.

This lesson explains the strategic logic of interview design for RelayOps, a B2B SaaS dispatch venture serving 80-200 technician residential-heavy HVAC and plumbing firms. You will learn what interviews can and cannot prove, how they fit a learning plan, and why field research (shadowing, artifact collection) pairs with talk.

What interviews prove in early discovery

Interviews excel at revealing language, priorities, workflow narrative, and perceived constraints. They are weaker at predicting future behavior, precise willingness to pay, and organization-wide buying process unless you interview multiple roles.

RelayOps treats interviews as hypothesis tests, not validation ceremonies. A pattern across 15 structured interviews is level 3 evidence (from Unit 1). A single enthusiastic quote is level 5.

Strategic logic: allocate interviews to the riskiest assumptions on the decision memo. If integration risk is top pre-mortem item, interview IT stakeholders with a different guide while ops interviews continue.

Discovery versus validation interviews

Discovery interviews explore unknowns: what triggers rebalance, what tools are used, what outcomes matter. Open-ended, past-behavior focused.

Validation interviews test known hypotheses: does overtime drop in pilot, will dispatchers adopt under 120-second loop, will COO fund at 8% savings threshold. More structured, metric-linked.

RelayOps Week 10-16 mix: 70% validation on primary assumptions, 30% discovery on adjacent modules (parts view, customer comms).

Mixing modes in one call confuses participants. Tell them the purpose upfront: "Today we want to learn how last Tuesday unfolded, not show software."

Multi-role interview strategy

B2B purchases involve users, champions, economic buyers, and blockers. RelayOps interview plan per account:

Sequence: dispatcher first (ground truth), ops second (context), COO third (economic framing), IT parallel track.

Strategic error: only interviewing champions who attended conferences. You will hear thought leadership, not Tuesday workflow.

Field research complements talk

People rationalize workflow in interviews. Field research includes shadowing, photographing artifacts (with permission), collecting anonymized reports, and mapping tools on screen. Field research tests what happens, not what people remember.

RelayOps field protocol pairs every third interview with a shadow. Discrepancies between interview recall and timed shadow are flagged as high-value learning (memory smooths chaos).

Ethical and access considerations

Field research requires consent, confidentiality, and minimal disruption. RelayOps sends a one-page research agreement: no recording without permission, anonymized notes, no sharing customer end-user PII (personally identifiable information, data that identifies individuals*).

Access strategy: lead with founder credibility ("we operated dispatch at Summit Climate"), offer benchmark summary in exchange for time, never ambush dispatchers during 911-level peaks.

Interview capacity as a scarce resource

Founders have finite hours. RelayOps caps 12 interview hours per week with mandatory note synthesis Friday. Strategic logic: declining low-fit meetings protects instrument integrity.

Sunk cost in scheduling bad interviews makes founders reluctant to cancel. Cancel anyway. Evidence pollution costs more than polite reschedule.

Top risks from Unit 2 memo: (R1) dispatcher adoption, (R2) COO budget trigger, (R3) IT integration delay.

Part A: Instrument assignment

Part B: Weekly cadence

Part C: Stop rule

If R3 shows >60 day security review in 4/5 IT calls, escalate integration partner strategy before Gate 2 commit.

Part D: Managerial read

Investors should see interview plan tied to risks, not generic "customer discovery." Operators should see role coverage per account.

Check: every top risk has instrument ✓

Interview ethics and trust in field research

Discovery interviews access operational pain during stressful moments. RelayOps treats ethics as strategic, not legal checkbox. Consent means explaining purpose, note-taking, optional recording, and anonymization before deep questions. Dispatchers share customer phone numbers and employee names casually; researchers must stop and redact.

Confidentiality promises must be kept. RelayOps shares benchmark summaries, not other companies' names. Breaking confidentiality ends recruiting pipelines in tight vertical communities. HVAC ops leaders talk at association dinners; one broken promise closes ten doors.

Minimal disruption means avoiding shadows during 911-level peaks unless dispatcher invites. RelayOps schedules shadows after 8 a.m. triage settles. Researchers who respect rhythm get invited back; tourists get polite one-time access.

Trust compounds into artifact access. Firms that trust RelayOps share overtime PDFs and CRM screenshots. Ethics enable evidence level upgrades from 3 to 4.

Sequencing interviews across the buying unit

Buying unit sequence matters in B2B. RelayOps default order: dispatcher ground truth, ops director context, COO economic framing, IT parallel. Skipping dispatcher and starting with COO produces strategy theater without workflow truth.

Parallel tracks run when calendar pressure hits. IT discovery must not wait until pilot contract; integration killers appear late and burn cash. RelayOps books IT 30-minute calls while ops interviews continue, linked to same account when possible.

Sequence errors include champion-only paths: ops director loves product, dispatcher never interviewed, COO never engaged. Pilots built on champion-only paths collapse at rollout. Strategic logic of interview design is role coverage per account, not maximum meeting count.

Part A: 10 account audit

Part B: Quality rule

Segment A gate requires dispatcher + COO or ops with budget authority on 80% accounts.

Part C: Gap closure plan

Week 11: schedule 3 COO calls for accounts with dispatcher-only coverage.

Part D: Managerial read

Coverage audit prevents false validate confidence. Check: 6/10 full coverage below 80% → action required ✓

RelayOps has one hour with a COO who refuses dispatcher access.

1. Accept interview or defer? Why?
2. Write three COO questions that partially compensate for missing dispatcher.
3. Evidence strength ceiling without dispatcher shadow?
4. Tag assumption impact for A2 adoption.

Solution

1. Defer unless COO agrees to dispatcher follow-up within two weeks; partial hour risks level 2 only evidence.

2. COO questions: "Walk through last heat-week overtime report line by line." "Who rebuilt the board last Tuesday morning?" "What would make you fund software this quarter?"

3. Ceiling: Level 2-3 for workflow claims; A2 remains Open until dispatcher instrument runs.

4. A2 impact: Challenges Supported status; downgrade to Testing until dispatcher data arrives.

Check: deferral protects assumption register integrity ✓

Cancelling low-fit meetings as leadership signal

When founders cancel misfit meetings, team learns segment discipline. RelayOps founder email template: reschedule with explanation of beachhead focus and offer intro to later phase. Politeness plus clarity beats ghosting or accepting bad fit.

Leadership signal matters because AEs and advisors watch calendar choices more than slide decks.

Pairing interviews with desk research

Desk research on incumbent forums supplements interviews. RelayOps logs forum threads complaining about scheduling module; threads become recruiting leads and hypothesis support. Strategic logic: instruments include public artifacts, not only private calls.

Interview ROI per hour

RelayOps treats interview roi per hour as operational discipline for mid-market HVAC and plumbing dispatch discovery, not a one-time workshop topic. Founders document decisions in the opportunity decision memo and segment strategy memo so Maya Chen and Jordan Okonkwo align daily calendar choices with beachhead rules.

In practice, interview roi per hour connects to measurable leading indicators: qualified interviews, shadow medians, assumption register statuses, and pilot telemetry. When indicators diverge from thesis language, the team runs a forcing function review within five business days rather than waiting for quarter-end board meetings.

Corporate innovation teams can mirror the same discipline: name owners, dates, falsifiers, and budget hooks before scaling a discovery squad. Without interview roi per hour, ventures default to activity metrics (meetings held) instead of learning metrics (assumptions supported or falsified).

Research agreement templates

RelayOps uses research agreement templates in weekly synthesis and monthly validation committee reviews. Customer success, sales, and engineering read the same RelayOps anchor facts: Segment A 80-250 technician residential-heavy HVAC and plumbing, same-day rebalance job, Core pricing near $2,800 per month, COO overtime trigger near 8 percent.

Research agreement templates prevents drift after competitive shocks such as ServiceSuite QuickReroute. Advantage pillar narratives update while Problem and Segment pillars remain stable unless new evidence crosses kill thresholds written in Unit 1 and Unit 6.

Operators should be able to explain research agreement templates to a dispatcher, a COO, and a seed investor without changing the core claim. That tri-audience test is the ENT 401 standard for applied validation work.

Part A: Baseline

Beachhead Segment A; 9 paid logos Month 9; cold OT -4%; warm OT -9%.

Part B: Intervention

Apply lesson concept to cold cohort playbook for next 30 days.

Part C: Expected movement

Cold OT toward -7%; DAU toward 68%; services toward 28 hours per logo.

Part D: Managerial read

Link intervention to validation pillar grades. Check: metrics named ✓

RelayOps cold pipeline 22 opportunities; 6 in contract; IT median 52 days.

1. Name two leading indicators for next 30 days.
2. Which Unit 3 assumption register rows move?
3. Write one falsifier sentence.
4. Continue, pivot, or kill if cold OT stays -4% at Day 90?

Solution

1. Cold OT median and IT median days on new pipeline. 2. A2 adoption and A3 integration rows. 3. If cold OT median above -4% at Day 90 with ritual shipped, pivot packaging or segment narrow. 4. Conditional continue until Day 90; pivot if falsifier hits.

Check: falsifier linked to pillar ✓

RelayOps applied review: connecting this lesson to validation

Every ENT 401 lesson supports the same Month 9 validation decision for RelayOps, the B2B SaaS dispatch and scheduling venture serving mid-market HVAC and plumbing firms with 80 to 250 technicians. Maya Chen and Jordan Okonkwo founded RelayOps after operating dispatch at Summit Climate. Their beachhead job is same-day crew rebalance under absenteeism and demand spikes, sold to COOs on overtime reduction near an 8 percent trigger, with Core pricing near $2,800 per month and CRM read integration in phase one.

This subsection ties lesson concepts to pillars investors grade: Problem, Segment, Solution, Economics, Market, and Advantage. Problem and Segment stay strong when qualified operations leaders rank rebalance pain in top three weekly pains and spend on overtime or scheduling modules. Solution weakens when cold cohort dispatcher daily active use sits near 63 percent while warm cohorts reach 76 percent. Economics weakens when customer acquisition cost payback stretches past 20 months and services hours per logo exceed 28. Advantage weakens when ServiceSuite QuickReroute bundles free reroute features that narrow speed-based differentiation.

Operators should translate every abstract framework in this lesson into calendar events, owners, and falsifiers. Founders should write what would change their mind before the next board meeting. Investors should ask for cold cohort tables, not blended averages. Learners should practice explaining RelayOps decisions to three audiences without changing the underlying evidence chain from Units 1 through 6.

Corporate innovators can map the same structure: opportunity memo, segment rules, interview instruments, insight portfolio, sizing brief, validation scorecard. The vocabulary changes by industry; the sequence does not. Selection before segmentation, segmentation before instrument design, instruments before synthesis, synthesis before sizing honesty, sizing before continue or pivot or kill.

Managerial stakes when this lesson is misunderstood

Teams that skip this lesson's discipline usually show predictable failure signatures within two quarters. Sales promises outrun evidence. Engineering builds features no economic buyer funds. Services teams drown in custom integration work. Marketing speaks at category level while dispatchers live at Tuesday morning chaos level. Finance models heroic TAM instead of obtainable SOM tied to account executive productivity.

RelayOps guards against those signatures with written memos, assumption registers, insight portfolios, and Month 12 thresholds. A lesson is not academic when it prevents a $195,000 monthly burn company from raising seed extension on warm cohort fiction. A lesson is not academic when it helps a corporate squad kill an innovation theater project before a seven-figure build.

Re-read the worked examples and practice problems with this validation lens. Each exercise should produce a decision, an owner, and a metric. If an answer only restates theory, revise until a RelayOps operator could execute it Monday morning in Phoenix or Dallas metros where reference density strategy concentrates learning and word-of-mouth among HVAC and plumbing operations leaders.

Study integration checklist for ENT 401 learners

Before moving to the next lesson, confirm you can: (1) state RelayOps beachhead in one sentence with inclusion and exclusion rules; (2) name the core job in situation-motivation-outcome form; (3) cite at least one falsifier with an instrument; (4) identify which validation pillar your lesson topic affects most; (5) describe what warm versus cold cohort split would do to your conclusion if ignored.

If any item is difficult, return to the worked example and practice problem sections. ENT 401 is cumulative by design. Unit 5 sizing fails when Unit 2 segment definition is vague. Unit 6 validation fails when Unit 3 assumption thresholds are missing. Unit 4 synthesis fails when Unit 1 evidence strength hierarchy is ignored.

RelayOps remains the anchor venture so you can see those links across 24 lessons without resetting context. The depth bar from the lesson authoring guide requires prose that teaches, not bullets that index. This integration subsection is intentionally repetitive on anchor facts because repetition builds fluency beginners need before running real discovery programs.

RelayOps has 8 hours next week. Options: (a) four dispatcher shadows, (b) six COO phone interviews, (c) three IT workshops + two dispatch interviews.

Primary risk this week: R2 COO budget trigger uncertain after mixed pilot pricing talk.

1. Allocate 8 hours with rationale.
2. Write opening script sentence setting discovery (not sales) tone for COO call.
3. Define one success metric for the week's interviews.
4. What do you explicitly not do this week?

Solution

1. Allocation: 4h six COO shortened to 4 calls (30 min + 15 min prep each) = 3h; 2h two dispatcher shadows for adoption context; 1h synthesis; defer IT workshops (R3 stable last month).

2. COO opening: "Thanks for the time. We are not pitching today. We want to understand how you decide whether overtime spending is acceptable after a heat-week, using last month as an example."

3. Success metric: 4 COO interviews with documented budget trigger threshold (%, $, or headcount rule).

4. Not this week: No prototype demos to COOs; no IT workshops; no new segment explores.

Key takeaways

• Interviews test assumptions; they do not replace pilots or analytics.
• Separate discovery and validation modes; state purpose upfront.
• Multi-role coverage is mandatory in B2B discovery.
• Field research verifies what interviews only recall.
• RelayOps maps interview hours to top risks, not random availability.

1. List your top three assumptions and assign an interview or field instrument to each.
2. Audit last five meetings: discovery, validation, or sales? What would you change?
3. Continue to Lesson 2: Methods and Models for Interview Design and Field Research.