Research Synthesis Example: SaaS
Research: 8 dispatcher interviews at Fieldlight customers (service companies, 50-300 technicians) Question: why do rescheduled days still go wrong? Hypothesis going in: "Dispatchers need smarter auto-scheduling" (the team's belief)
Why this example exists: the hypothesis was a solution. The synthesis shows the need underneath it, and one contradiction that changed the insight.
## Research frame
Participants: 8 dispatchers, recruited from customer accounts by CS (so possibly friendlier than
average). Hypothesis held: smarter auto-scheduling is the answer. [FROM YOU]
## Coded observations (excerpt)
| # | P | Observation | Unprompted | Contradicts hypothesis |
|---|---|---|---|---|
| 14 | P3 | "I print the schedule and rebuild it in a spreadsheet at 2 p.m." | Yes | No |
| 22 | P5 | "The auto-schedule is fine. I can't tell which jobs I'm allowed to move." | Yes | **Yes** |
| 31 | P7 | "I don't trust the board once a rush call lands." | Yes | No |
## Themes
| Theme | Participants | N |
|---|---|---|
| The 2 p.m. rebuild | P1, P3, P4, P5, P7, P8 | 6 of 8 |
| Can't see what's movable | P2, P5, P6, P7 | 4 of 8 |
| Calling customers to renegotiate | P1, P4, P6 | 3 of 8 |
## Insights
| # | Insight | Evidence | N | Confidence |
|---|---|---|---|---|
| 1 | Dispatchers rebuild the day by hand not because the schedule is poor, but because they can't see which jobs are safe to move | Obs 14, 22, 31 | 4-6 of 8 | Suggestive (CS-recruited sample) |
## Opportunity statements
| # | "I need to..." | From | Ideas heard |
|---|---|---|---|
| 1 | "...know which jobs I can move without calling the customer." | 1 | "Color-code flexible jobs" (P2) |
| 2 | "...trust the plan after a rush call lands." | 1 | none |
## Contradictions
Obs 22 (P5): the auto-schedule is fine. It cuts against the hypothesis that scheduling quality is
the problem. It **changed** the insight from "better scheduling" to "visibility of flexibility."
## What the research does not show
- No dispatchers from companies under 50 technicians
- Recruited by CS, so likely engaged customers; unhappy accounts missing
- "Movable" job rules rest on P5 and P7 only; ask others what makes a job movableWhat to learn from this
- The contradiction was the finding. P5's remark turned a scheduling story into a visibility story.
- Counts, not percentages. "6 of 8" says what was true of these eight people.
- The solution (P2's color-coding) was kept, not buried, and kept out of the opportunity.