- Home
- Research skills
- Insight Activation and Socialisation
Insight Activation and Socialisation
Diagnose why your research is not being used, then build the formats, moments and ownership that get it used, without breaking the findings.
Free. Works on Claude, ChatGPT, Gemini or any assistant that accepts a skill file.
What this skill does
The method, encoded.
The most common outcome of a research project is that nothing happens. The report is delivered, praised and filed, and the same question is asked again a year later by someone who does not know it was answered.
That is rarely a slide design problem. Research goes unused for one of seven identifiable reasons: it arrived after the decision, it answered a question nobody owned, it contradicted a commitment already made, it was too long, it reached the wrong people, it had no owner after delivery, or it was genuinely not useful. Each needs a different remedy, and six of them are not fixed by a better deck.
This skill runs the diagnosis first, then maps the decisions the findings bear on, the people who actually make them and the moments in the calendar where they are made. It fixes an invariant set of core findings, builds audience-specific cuts by selection and framing only, and chooses formats that fit real moments: decision briefs, one-pagers, team summaries, principle sets, embedded references in documents people already open.
It is strict on one thing. A finding may lose precision as it gets shorter. It may never gain scope.
Best used for
- A completed study that has produced no visible consequence
- Getting one body of evidence to four functions with different decisions
- Preparing findings for a specific decision forum with a fixed format constraint
- Converting findings into durable principles, guidelines or embedded references
- Handling a finding that contradicts a commitment already made
- Demonstrating, honestly, whether research has been used
- Planning activation before fieldwork rather than after delivery
Typical inputs
What you give it.
Quality-checked findings with evidence references, bases and confidence levels, The decisions the research was meant to inform, and whether each is still open, Names of the people who make and shape those decisions, A record of what has happened since delivery, Optional organisational decision calendar and recurring forums, Optional commissioning brief and stated stakeholder hypotheses, Optional record of prior research on the same subject, Optional existing internal artefacts the findings could be embedded in, Optional confidentiality and consent terms from the study
Typical outputs
What you get back.
Diagnosis of non-use, with the cause ranked and evidenced, Decision map naming signer, shaper, date and relevant findings, Numbered invariant core findings with references, confidence and review dates, Audience cut specifications with inclusion and exclusion reasons, Artefact plan by audience, moment, owner and status, Compression register with rejected phrasings and reasons, Handover record with named owner, remit and acceptance, Use measurement plan distinguishing exposure from use, with attribution limits stated
Method coverage
What the skill works through.
- Why research gets delivered and never used
- The seven causes of non-use, and why the fix differs by cause
- Mapping decisions, decision-makers and decision moments
- Fixing the invariant core before building anything
- Audience cuts by selection and framing, not by claim
- Formats beyond the report: briefs, one-pagers, principles, embedded references
- Making findings memorable without making them wrong
- The compression ladder and the truth line
- Handing over to an owner in the business
- Measuring whether research was used, honestly
- Setting review dates and expiry on findings
- Knowledge, belief and capacity barriers
Download
Free skill. One file.
Enter your email once. Every skill you download after that takes a single click.
How to install
Add the skill file and the five kernel protocols to a Claude Project, a ChatGPT Project, a Gemini Gem, or paste them at the top of any assistant conversation. Then give it your real research material, not a description of it.
Download skillQuestions
Common questions.
Why does research get ignored even when it is good?
Usually for a structural reason rather than a quality one. The commonest are that it reached the commissioner rather than the people whose work would change, that no one in the business owned the question, that it arrived after the decision was made, or that it had no owner once the project closed. Diagnose which before doing anything, because the remedies are different and only one of them is about formats.
How do I make findings memorable without oversimplifying?
Compress until, but not past, the point where someone acting on the short version would act differently from someone acting on the full one. A useful rule: a statement may lose precision as it gets shorter, but it may never gain scope. Dropping a decimal place is precision. Turning "among claimants" into "customers" is scope, and it is a different claim.
What formats work better than a research report?
It depends on the audience and the moment, but the highest-leverage option is usually an embedded reference: putting the finding into a document people already open, such as a design principle set, a brief template, a service standard or a decision checklist. That removes the requirement that anyone choose to read your artefact. Decision briefs, one-pagers and team summaries all beat a full report for activation; a talk builds belief but leaves no durable record.
Can you write different versions of findings for different teams?
Yes, and it is often necessary, but versions may differ only in which findings they include and how those findings are framed in the audience's language. They must never differ in what a finding claims, what number it carries, what confidence it holds, or whether its caveat is present. Make every version cite numbered core findings so the check can be mechanical.
How do you measure whether research was actually used?
Distinguish exposure from use. Views, downloads and attendance measure exposure. Use is evidenced by traces: the finding appearing in a brief, a business case, a roadmap justification or a specification. The cheapest instrumentation is to ask owners to cite the finding reference when they use it. Be honest about attribution: a decision consistent with the research is not proof the research caused it.
What do you do when a finding contradicts something the organisation has already committed to?
Recognise it as a political problem rather than a communication one. Better formats will not help. Brief a sponsor privately before any wider distribution, frame the finding against the decisions still open rather than the one already closed, and do not put the researcher in the position of being the only person holding it.
Who should own a finding after the project ends?
Someone in the business whose decisions the finding bears on, with a written remit and an explicit acceptance. A handover contains the core findings with references, what they are for, where the artefacts live, what the owner is expected to do, a review date, and who to ask about interpretation. If no owner can be found, that is itself a finding worth recording rather than an obstacle to work around.
When should you plan activation?
Before fieldwork. If you know the decision, its date and its forum while the design is still open, the study measures what the decision needs and the format constraint is known while there is time to design for it. Activation planned after delivery is recovery work.
The skill chain
Works well with.
Research where people already are.
Analyse it where you already work.
Yazi helps researchers conduct surveys, AI interviews and longitudinal research directly through WhatsApp.
%202.png)
