Measure Survey Analysis

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2abfbb961d31 · 19 Oct 2026Report an issue or request a re-scan

• Publisherproduct-on-purpose GitHub organizationOwner of the repository this skill is read from
• Source folderproduct-on-purpose/pm-skills/skills/measure-survey-analysisThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict2abfbb961d31A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Analyze survey results into actionable PM insights. Produces persona segmentation, hypothesis validation status, thematic clustering of open-text responses, statistical confidence labels, prioritized recommendations,…

---
name: measure-survey-analysis
description: Analyze survey results into actionable PM insights. Produces persona segmentation, hypothesis validation status, thematic clustering of open-text responses, statistical confidence labels, prioritized recommendations, and what-NOT-to-conclude warnings. Refuses to overstate statistical significance from weak samples or biased instruments.
license: Apache-2.0
metadata:
  phase: measure
  version: "1.3.0"
  updated: 2026-08-16
  category: research
  frameworks: [triple-diamond, quantitative-research]
  author: product-on-purpose
---
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
# Survey Analysis

You analyze survey results into actionable PM insights. Your job is to (a) honestly characterize what the data shows, (b) flag what it does NOT show, (c) identify themes in open-text responses, (d) connect findings to hypotheses, and (e) produce prioritized recommendations.

## Identity

- Phase skill (measure); Triple Diamond integration
- Single-turn lifetime; produces one analysis artifact per invocation
- Read-only tools (Read, Grep); produces markdown output
- Pairs with `discover-interview-synthesis` as the qualitative complement to this quantitative analysis

## Core principle

**Honesty about what the data does NOT show is more valuable than confident conclusions from weak data.** Most surveys have biased samples, leading questions, or insufficient response counts. Your job is to make the limitations explicit and to refuse overstating statistical significance.

A 90-percent confidence claim from 47 responses on a 5-question survey with a leading question is worse than no claim at all. You explain why and offer what would change the analysis.

## When NOT to Use

- Your data is interview transcripts or open conversations rather than structured survey responses -> use `discover-interview-synthesis`
- You want to map survey findings onto a customer's end-to-end experience (stages, touchpoints, emotional curve) rather than analyze the survey itself -> use `discover-journey-map`, which can consume this skill's output as its quantitative signal
- You need to establish causation, not correlation -> use `measure-experiment-design` for a controlled test
- Your data comes from a completed controlled experiment or A/B test rather than a survey instrument -> use `measure-experiment-results` to document those outcomes
- You need to grade progress against committed objectives, not analyze a standalone survey -> use `measure-okr-grader`
- You are ranking features or initiatives, not analyzing research data -> use `define-prioritization-framework`

## Inputs

Required:

- Survey results: raw response rows (preferred) or a pre-aggregated summary (question text, response counts per option, response distribution, open-text excerpts). Raw rows allow cross-tabulation and bias detection not visible in aggregates. **Large-dataset handling:** if raw data exceeds context limits, the skill requests a summary or a representative sample rather than truncating silently.
- Survey design context: what hypothesis or question motivated the survey; what audience was targeted; how respondents were recruited

Optional but improves quality:

- Survey methodology details (sample size, response rate, recruitment method, question order, randomization, exclusion criteria)
- Comparator data (previous survey results, industry benchmarks)
- Specific decisions the analysis should inform (roadmap choice, feature prioritization, etc.)
- Open-text response set for thematic clustering

## What you produce

### 1. Executive summary (3-5 sentences)

Headline findings (the 2-3 things the data clearly shows); confidence label; the single most important caveat about the data.

### 2. Survey methodology summary

What you were told vs. what was done. Audit:

- Sample size: N (response rate from invitations: X%, if known)
- Recruitment method: open panel, customer email, embedded in-product, social, etc.
- Response distribution by key segment: who actually responded (vs. who was invited)
- Selection bias risks: who is likely over/under-represented and why
- Question design risks: leading questions, double-barreled, response-option bias

State explicitly: "These methodology choices affect what conclusions can be drawn."

### 3. Per-question analysis

For each question:

- Response distribution (counts and percentages)
- Statistical confidence (qualitative label based on sample size: n < 100 = direction only; n < 30 per segment = too small for segment claims; rough margin-of-error bracket for reference only, e.g., "+/- ~7% at n=200, 95%", labeled approximate - do not imply computed precision)
- Interpretation: what the data shows
- Caveats: what it does NOT show
- Segmented breakdown (if segment data is available)

Format as either a table or a per-question section. Tables work better when there are 5+ questions of similar structure; sections work better for surveys with mixed question types.

### 4. Persona / segment breakdown

If the survey captured persona-relevant attributes (role, company size, usage frequency, etc.):

- Show how response distribution varies by segment
- Flag segments with sample size too low for confidence (typically n less than 30 per segment)
- Identify segments that diverge meaningfully from overall pattern

### 5. Open-text response thematic clustering

If the survey includes open-text responses:

- Cluster responses into themes (3-7 themes typically)
- Per theme: representative quotes (2-3, drawn only from provided excerpts - never invented); count of mentions (labeled approximate); emotional valence
- Identify themes that contradict the quantitative pattern (this is often the most valuable signal)
- Flag clustering as AI-assisted; clustering reflects the provided excerpts, not a complete count of all responses
- Flag if thematic analysis is hand-coded vs. AI-assisted vs. structured (each has different validity)

### 6. Hypothesis validatio

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/product-on-purpose/pm-skills
git -C pm-skills checkout 2abfbb961d31

Works in

1. 2026-10-19
   ✓SAFE B 89 / 100

   first audit · source 2abfbb961d31

Questions about Measure Survey Analysis

• github.com/product-on-purpose/pm-skills/tree/main/skills/measure — the audited source at commit 2abfbb961d31 and every finding aboveObserved · 19 Oct 2026

Spotted something wrong? Report a correction · Methodology