Interview Design and Field Research: From Analysis to Action

Synthesis without action is entertainment

Unit 3 taught strategic logic, methods, and metrics. This capstone lesson closes the loop: how RelayOps runs Friday synthesis, converts patterns into roadmap and pilot decisions, and communicates changes to stakeholders. Interviews matter only when they change what you build, who you sell to, and what you measure next week.

RelayOps builds dispatch software for Segment A HVAC/plumbing firms. Week 14 synthesis must decide: expand pilot slots, add IT security hire, narrow prototype scope, or delay COO pricing tests.

Friday synthesis ritual

RelayOps 90-minute synthesis agenda:

One person owns synthesis memo published by EOD Friday. No memo = week did not count.

Pattern → action decision tree

Avoid knee-jerk pivots on n=1 quotes. Require pattern + assumption link.

RelayOps Week 14 decisions (illustrative)

Decision 1: Ship CRM read sync in pilot (tab_switching 9/10 interviews).

Decision 2: Defer Spanish UI (language friction 4/12, workaround exists).

Decision 3: Hire contract integration engineer for IT long tail (A3 at risk).

Decision 4: COO pricing test uses 8% overtime threshold language from 4/6 interviews.

Decision 5: Kill standalone customer reminder module (H7 explore failed saturation).

Communicating research outcomes

Internal: synthesis memo + updated assumption register.

Pilot customers: "We heard rebalance speed matters more than map cosmetics; next sprint focuses on CRM sync."

Investors: leading metrics dashboard, not quote collage.

Candidates: honest scope attracts right engineers.

Handoff to Unit 4 (evidence synthesis)

Unit 4 generalizes synthesis across interviews, shadows, pilots, and desk research into insight formation and insight portfolios. Unit 3 outputs feed Unit 4 inputs: coded tags, assumption statuses, shadow medians.

Part A: Assumption changes

Part B: Roadmap delta

Part C: Next week plan

6 IT follow-ups, 3 shadows on CRM API access, 2 COO pricing conversations with benchmark report offer.

Part D: Check

Every decision links to tagged pattern or assumption status. ✓

Decision logs and accountability

Synthesis memos need decision logs: date, decision, evidence link, owner, expected metric movement. RelayOps logs "2025-10-04: Prioritize CRM read sync (Decision 1); owner Jordan; expect tab_switching tag frequency down in shadows week 16."

Decision logs prevent silent reversals. Two weeks later engineers wonder why CRM sync is P0; log shows interview tag evidence. New hires read logs during onboarding.

Accountability includes missed decisions. If week has no decision despite interviews, synthesis failed. RelayOps rule: no decision = cap next week's interviews until synthesis catches up.

Changelog discipline for pilot customers

Pilot customers tolerate roadmap shifts when changelogs cite their feedback. RelayOps two-sentence changelog template: "We heard X in interviews/shadows; we are prioritizing Y next sprint." Changelog builds trust; silent shifts feel bait-and-switch.

Change logs differ from investor updates. Customers need concrete workflow impact, not pillar grades. Dispatchers hear about tab reduction; COOs hear about overtime chart timing.

Part B: Outcome check (week 16)

CRM sync story pointed; Spanish UI tickets closed; H7 removed from backlog.

Part C: Pilot changelog sent

"We are prioritizing CRM read sync to cut tab switching during rebalance."

Part D: Managerial read

Log ties activity to action; board can audit. Check: four decisions documented ✓

Week 17: interviews add no new tags; sales demands demo-heavy COO tour.

1. Decision log entry to protect discovery mode?
2. Does no new tags mean stop interviews?
3. Write customer changelog if demo tour still happens.
4. Risk to A1 if demos replace spend probes?

Solution

1. Log: "Cap COO calls to validation mode only; no demos until assumption register updated."

**2. Stop Segment A discovery interviews; shift to shadows/pilots per saturation rule.

3. Changelog: "No product changes this sprint; we are validating adoption metrics in pilot week 5."

4. Risk: A1 weakens to anecdotal ROI stories without spend/trigger data.

Check: saturation reallocates time ✓

Orphan insight cleanup

Friday synthesis flags orphan insights: documented beliefs with no epic or roadmap link. Orphans indicate entertainment synthesis. RelayOps Week 14 merged two tab insights into I2; retired duplicate.

Sales collateral updates after decisions

When Decision 1 prioritized CRM sync, sales one-pager updated same day. Lag between synthesis and collateral lets AEs sell obsolete story. RelayOps policy: collateral owner tagged in decision log.

Roadmap changelog SLAs

RelayOps treats roadmap changelog slas 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, roadmap changelog slas 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 roadmap changelog slas, ventures default to activity metrics (meetings held) instead of learning metrics (assumptions supported or falsified).

Decision retro templates

RelayOps uses decision retro 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.

Decision retro 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 decision retro 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 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.

Week 15: one COO says "I will never pay for dispatch software." five others support 8% threshold. Dispatcher D4 hates prototype colors but completes tasks in 95 seconds.

1. How do you code the COO interview without overturning A1?
2. Does D4 affect A2 status?
3. Write two-sentence changelog for pilot customers.
4. What instrument do you add next week?

Solution

**1. COO coded as outlier + reason probe (incumbent sunk cost, bad prior vendor). A1 stays Supported at 4/6 with note; schedule second COO call in similar firm size.

2. D4: A2 unchanged (task time supports); log UX polish separately, not adoption falsifier.

3. Changelog: "We are prioritizing CRM read sync to cut tab switching. Visual polish will follow after rebalance loop stability in pilot week 3."

4. Instrument: Second shadow on CRM API latency during live rebalance.

Key takeaways

• Friday synthesis converts interview data into explicit decisions.
• Use decision trees linking patterns to actions.
• RelayOps prioritizes CRM read sync from tag frequency; defers Spanish UI.
• Communicate changes internally and to pilot customers.
• Unit 4 builds portfolio-level evidence synthesis from Unit 3 outputs.

1. Run a mock Friday synthesis: update three assumption rows and one roadmap priority.
2. Write a customer-facing changelog sentence tied to interview evidence.
3. Return to the unit page for the Unit 3 knowledge quiz, then begin Unit 4: Evidence Synthesis and Insight Formation.