Designing an Approach to Evidence Synthesis and Insight Formation

Synthesis needs a system, not a heroic Friday night

Lesson 1 defined insight quality. This lesson designs the operating system for synthesis: workflows, tools, roles, templates, and integration with pilots and desk research. RelayOps will run this system while scaling from 3 pilot customers to 10 without losing decision clarity.

The evidence funnel

Bottleneck is usually cluster → draft. RelayOps schedules monthly 2-hour insight workshop separate from weekly assumption updates.

Synthesis templates

Pattern card:

• Pattern name
• Segment scope
• Frequency (n/N)
• Methods (interview, shadow, pilot)
• Representative quote
• Counter-evidence
• Proposed insight ID

Insight card:

• Statement
• Falsifier
• Confidence
• Linked assumptions
• Decision impact (P0/P1/P2)

Templates force counter-evidence field. Teams that skip it overfit narratives.

Integrating pilot data

Pilots produce behavioral evidence stronger than interviews. RelayOps pilot metrics feed synthesis:

Synthesis rule: pilot metrics can upgrade insight confidence if segment matches beachhead. One pilot cannot override 19 interview segment definition without segment tag check.

Desk research and competitive evidence

Synthesis includes external evidence: competitor release notes, review sites, analyst reports, job postings (incumbent hiring priorities). RelayOps logs competitor scheduling module updates; if incumbent ships fast reroute, insight I2 urgency rises.

Desk research weight is lower than primary customer evidence but catches market moves interviews miss.

Roles in synthesis workflow

At three founders, Maya = synthesizer, Jordan = insight owner alternate months, shared decision vote.

Tooling choices

Spreadsheet works to 50 interviews. Beyond that, use database (Notion, Airtable) linking notes → tags → insights. RelayOps links insight IDs to Jira epics for traceability.

Linking synthesis to venture thesis

Venture thesis is one paragraph plus three pillars (segment, job, wedge) each backed by insight IDs. Monthly synthesis revises thesis only when A insight changes or B insight upgrades to A with pilot data.

Part A: Pattern cards promoted

Part B: Counter-evidence

Pilot 3 at 220 tech firm: adoption 48% week 4 (below 70% target). Segment tag: borderline size. Action: services-heavy onboarding, not thesis change yet.

Part C: Thesis revision

Add clause: "Implementation playbook required for 200-250 tech accounts."

Part D: Check

Every thesis clause maps to insight ID. ✓

Scaling synthesis from two founders to eight person team

RelayOps headcount grows; synthesis cannot remain in founders' heads. Role clarity prevents duplicate tags and orphan insights. Interviewer codes within 24 hours; weekly synthesizer updates assumption register; monthly insight owner runs workshop; CEO commits P0 roadmap.

Handoff quality metrics: percent notes complete, percent tagged, percent linked to assumptions. RelayOps targets 95% complete within 24 hours or interview does not count toward gate metrics.

New hires read insight portfolio on day one. Customer success uses insight IDs in onboarding checklists. Sales battlecards cite I2 and I3 language, not generic benefits.

Linking desk research without overweighting it

Competitor release notes and review sites inform urgency (I2) but do not override customer shadows. RelayOps desk research log includes source, date, insight impact, and revalidation date. QuickReroute beta logged Month 8 triggers Advantage pillar review.

Desk research cannot upgrade confidence alone. It can downgrade Advantage or raise priority of competitive workstream. Synthesis design keeps external signal in appendix until triangulated with win/loss calls.

Part A: Week with 8 interviews

Part B: Corrective action

Missing assumption links block gate credit; interviewers redo Friday before standup.

Part C: New hire onboarding

Day 1: read I1-I4; shadow synthesis memo ritual.

Part D: Managerial read

Handoff scorecard scales discipline beyond founders. Check: 88% fails gate → rework ✓

Month 6: 10 pilots, 60 interviews, Notion database proposed.

1. Minimum fields for note records?
2. Weekly vs monthly outputs at this scale?
3. Rule when pilot OT -4% conflicts with interview pain A grade?
4. Desk note: incumbent free reroute: which insight IDs affected?

Solution

1. Fields: Note ID, segment tags, obstacle tags, assumption IDs, insight IDs, evidence level, pilot metrics JSON.

2. Weekly: assumption register, tag frequencies. Monthly: insight portfolio, thesis revision, competitive log.

3. Rule: Pilot behavior (level 4) downgrades Solution pillar; Problem pillar holds until fresh pain sample <50% (falsifier on Problem).

4. Insights: I2 urgency up; Advantage down; thesis differentiation shifts to OT proof.

Check: conflict resolved with pillar split ✓

Epic linkage in Jira

RelayOps links insight IDs to Jira epics. Sprint review asks: which insight does this ship address? Unlinked tickets flagged. Traceability scales synthesis to engineering.

Monthly workshop agenda template

Two-hour insight workshop agenda: pattern card review, promote/demote insights, counter-evidence mandatory, thesis diff, competitive desk notes, retirements.

Synthesis SLA for hires

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

Insight portfolio limits

RelayOps uses insight portfolio limits 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.

Insight portfolio limits 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 insight portfolio limits 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.

Design RelayOps synthesis system for Month 6 (10 pilots, 60 interviews). Specify: tool fields, weekly vs monthly outputs, role assignment, one rule for when pilot data falsifies an insight.

Solution

Tool fields: Note ID, segment tags, obstacle tags, assumption IDs, insight IDs, pilot metrics JSON.

Weekly: Assumption register + tag frequencies.

Monthly: Insight portfolio, thesis revision, retired insights.

Roles: Rotating synthesizer; CEO decision on P0 changes.

Falsify rule: If 2+ pilots miss adoption threshold with qualified Segment A tags, downgrade I2 and pause scale marketing.

Key takeaways

• Evidence funnel from capture to decide needs templates and owners.
• Pattern cards and insight cards include counter-evidence.
• Pilot metrics upgrade confidence when segment-qualified.
• RelayOps links insights to epics and thesis pillars monthly.
• Workshop cadence separate from weekly assumption updates.

1. Draft a pattern card and insight card from your latest customer conversation.
2. Define weekly vs monthly synthesis outputs for your team.
3. Continue to Lesson 3: Common Risks and Failure Modes in Evidence Synthesis and Insight Formation.