Skip to content

afeezadebayo/research-learning-skills / research-synthesis

research-synthesis

Verified

Turn research into insight: organising and coding observations, affinity mapping, insight statements, counting and weighing evidence, tensions and surprises, frameworks such as journeys and jobs, implications and prioritised recommendations, and presentations that answer the research question first. Use whenever someone needs to synthesise interviews, surveys, desk research or literature, find themes in research notes, write insights, run affinity mapping or turn findings into recommendations.

Research Synthesis

Research only creates value when raw material becomes insight people act on. Many projects stall at this step: dozens of interview notes, survey charts and desk research findings sit in folders, and the final report lists what each source said instead of what it all means. Synthesis is the disciplined work of grouping evidence into themes, finding patterns and tensions, explaining why they matter and turning them into clear implications and recommendations.

This skill synthesises research from interviews, surveys, desk research, data and literature: organising evidence, coding and clustering it (affinity mapping), writing insight statements, weighing strength of evidence, building frameworks such as journeys, jobs or segments, prioritising implications and presenting findings so decision makers can act.

Operating principles

  1. Insights, not summaries. An insight explains something non-obvious and why it matters.
  2. Evidence behind every claim. Each insight links to quotes, data or sources.
  3. Count and weigh. Note how often a pattern appears and how strong the evidence is.
  4. Look for tensions and surprises. Contradictions and unexpected findings are often the most valuable.
  5. Implications drive action. Every insight ends with "so what" for the decision.
  6. Synthesis is collaborative. Involve the people who will act on it.

From data to recommendation

Observation: what was seen or heard (quote, number, fact)
Theme: a group of related observations
Insight: what the theme means and why it happens
Implication: what it means for our decision or product
Recommendation: what we should do, with owner and priority

Insight statement formula

<Who> <does or feels what> because <underlying reason>, which means <implication for us>.

Example: "Small business owners abandon setup at the bank connection step because they fear giving account access to an unknown company, which means trust signals at that step matter more than speed."

When to use, and when not to

Use it after interviews, surveys, usability tests, desk research or literature reviews, and when combining several research streams into one recommendation.

Don't use it to force conclusions the evidence cannot support; when data is thin, say so and recommend further research.

Inputs

  • Notes, transcripts, survey data, research logs and sources.
  • The original research questions and decision.
  • Participant or source details (segments, roles).
  • People who should take part in synthesis.

Workflow

Step 1. Gather and prepare

Collect all material in one place; one observation per note or row, tagged with source and segment.

Step 2. Re-read the questions

Keep the research questions and decision visible to stay focused.

Step 3. Code observations

Tag each observation with codes such as problem, trigger, workaround, goal, emotion, quote or number.

Step 4. Cluster into themes

Group related observations (affinity mapping); name each cluster with a sentence, not a single word.

Step 5. Count and weigh

For each theme: how many sources, which segments, how strong (behaviour versus opinion, data versus anecdote).

Step 6. Write insights

Use the formula; one insight per theme; keep the strongest five to eight.

Step 7. Look for tensions

Where segments disagree or data contradicts interviews; explain or flag for follow-up.

Step 8. Build a framework if useful

Customer journey, jobs to be done, segments or a two-by-two that makes patterns easy to grasp.

Step 9. Derive implications and recommendations

For each insight, what it means and what to do, prioritised by impact and confidence.

Step 10. Present

Lead with the answer to the research question, then insights with evidence, then recommendations.

Evidence strength

StrengthExample
StrongPattern in many interviews across segments, confirmed by data
ModerateClear pattern in one segment or method
WeakA few mentions, opinions rather than behaviour

Synthesis board layout

| Theme | Observations (count) | Segments | Key quotes or data | Insight | Strength | Implication |
| Fear at bank connection | 9 of 12 interviews; 41% drop-off at step | Small business | "I didn't know who you were" | Trust, not speed, blocks setup | Strong | Add trust signals and alternatives |

Running a synthesis workshop

TimeActivity
10 minRecap research questions and decision
30 minSilent clustering of observation notes
20 minName clusters as sentences; merge or split
20 minWrite insight statements per cluster
20 minVote on importance and confidence
20 minAgree implications, owners and next steps
Invite people who will act on the findings; joint synthesis builds shared understanding and commitment.

Frameworks that help

FrameworkUse when
Customer journeyExperiences change by stage
Jobs to be doneMotivations matter more than demographics
Segments or personasClear behavioural groups emerge
Two-by-two matrixTwo factors explain most differences
Opportunity treeMany problems map to a few outcomes

Keeping evidence traceable

Give every observation an ID linked to its source (interview number and time stamp, survey question, document and page). Insights then cite IDs, so anyone can check the evidence and future research can build on it rather than repeat it.

Research repositories

Store synthesised insights with tags, dates and evidence links in a shared repository so teams can search past findings before starting new research. Review and retire outdated insights each year.

Share the synthesis widely and record decisions taken from it.

Keep raw notes until decisions are final.

Edge cases and judgement calls

SituationWhat to do
Too much materialSynthesise by research question; prioritise strongest evidence
One loud participantWeight by pattern across sources, not intensity
Stakeholders want a specific answerPresent evidence openly; separate findings from preferences
Conflicting methodsExplain differences (who, how, when); recommend follow-up
Small sampleLabel findings as directional
AI summarisationUse AI to draft clusters; verify against raw notes and quotes

Handoffs to related skills

  • Interviews: expert-user-interviews
  • Surveys: survey-design
  • Literature: literature-review
  • Presenting: the Communication and Presentations presentation-storyline and data-storytelling skills
  • Reports: the Workplace Writing reports and executive-summaries skills

Worked example

A fintech team had 14 interviews, a 500-response survey and funnel data on onboarding. Synthesis coded about 300 observations, clustered them into nine themes and wrote six insights. The strongest showed that small business owners abandoned setup at the bank connection step mainly because of trust concerns, supported by nine interviews and a 41% drop-off at that step. A tension appeared: survey respondents rated speed highly, but interviews showed trust mattered more at the moment of connection. Recommendations added trust signals, a manual alternative and a call-back option, and completion rose noticeably over the next month.

Common mistakes

  • Summarising each interview in turn.
  • Themes named with single words that hide meaning.
  • Insights without evidence or counts.
  • Ignoring contradictions.
  • Recommendations that do not follow from insights.

Output format

1. Answer to the research question
2. Insights with evidence and strength
3. Tensions and open questions
4. Framework (if used)
5. Implications and prioritised recommendations
6. Appendix: themes, counts and sources

Self-check before you answer

  • Is each insight linked to evidence with counts or sources?
  • Are tensions and weak evidence flagged?
  • Does each insight lead to an implication and recommendation?
  • Does the output answer the original research question first?

Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/productivity/research-learning/research-synthesis/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall